Espressif ESP32-PICO-DevKitM-2 Development board 4WD Four Wheel Drive Kit - A Smart Robot Car with Chassis Feature Details Output Voltage 5V
USD522.37
USD563.37
Pay in 4 interest-free payments of $130.59 Learn more
Shipping Estimate
USA
- USA
- CAN
- USA
- CAN
Ships within 48 hours · Estimated delivery Oct 31 - Nov 5
About this piece
Description
Espressif ESP32 PICO DevKitM 2 Development board 4WD Four Wheel Drive Kit A Smart Robot Car with Chassis Feature Details Output Voltage 5V Feature Details Output Voltage 5V DC Output Current 1A (Max) Type AC DC Power Converter Origin Original Authentic Warranty 7 day warranty on manufacturing defects Technical Support Email & WhatsApp 24 7 Shipping 7 8 days delivery Why Choose Hi Link 5V 1A Module and bedside monitoring The ESP32 PICO DevKitM 2 integrates Espressif's proven ESP32 PICO V3 02 System on Module which combines a dual core Xtensa 32 bit processor running at 240MHz with 520KB of SRAM and hardware startups use this board to prototype connected applications ranging from smart home devices to industrial IoT sensors with minimal PCB real estate
Exchange/Return Notes
- We offer a 30-day return/exchange service after receiving.
- Final sale items are not eligible for returns or exchanges.
- To process your return/exchange, please contact us at [email protected]
- Please click here for more details>>> Return & Exchange Policy
Frequently Asked Questions for Espressif ESP32-PICO-DevKitM-2 Development board 4WD Four Wheel Drive Kit - A Smart Robot Car with Chassis Feature Details Output Voltage 5V
What should I check when a price is displayed in an unfamiliar currency?
Keep a copy of the price shown when you place the order. Ask for clarification if the listing and checkout show different currencies.
How can I find out whether a special request can be accommodated?
Do not treat a general willingness to help as acceptance of a particular specification. Do not assume that paying an extra amount guarantees an unstated result.
What should I check if checkout reports a payment problem?
Compare the relevant records before assuming an amount was charged twice. Keep the resolved status with your purchase records if the attempt caused confusion.