Cannot sync-up with MBot

#1

This is getting very frustrating, I have tried everything I could to sync-up the mBot with mBlock 3.4.11 but NOTHING seems to work.

I can connect the mBot with USB fine. COM3 shows up and I can see a green light in the mBot extension (which means it’s correctly connected I guess).
I am selecting the board “mBot (mCore)”

Now I have tried over and over again to upload software, nothing happens, I always get the following message:
"avrdude: Version 6.0.1, compiled on Apr 15 2015 at 19:59:58
Copyright © 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright © 2007-2009 Joerg Wunsch

     System wide configuration file is "D:\Progs\mBlock\Arduino\hardware\tools\avr/etc/avrdude.conf"

     Using Port                    : COM3
     Using Programmer              : arduino
     Overriding Baud Rate          : 115200

avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x93"

I have tried “Reset Default program”, same thing, no response.

Please help, this is very frustrating for my son who cannot use his brand new robot.

Thanks,

Christophe

#2

Hi Christophe,

Several questions if you don’t mind.

  1. May I assume that you have installed the Arduino driver from the Connect menu? The Makeblock robots use a 2. slightly different chip set that requires a custom driver to be installed. From your comment about COM3, I assume that you are using the Windows operating system. Might I ask what version you are using?
  2. May I assume that you have powered up the mBot?

I’ve heard there some issues with Windows 10 but I haven’t confirmed those yet (will look at that tomorrow).

Regards,

Chuck

P.S. It’s usually a good idea to copy @tech_support for a faster “official” response. :slight_smile:

#3

Thanks for the answer!

  1. Yes, you are correct, I installed the driver from the Connect menu. Can you please point me towards the correct driver?
    Also yes, I am using Windows 10

  2. I have tried with mBot powered off (i.e. switched “off”) and you were right, switching it on solved the issue!!

Thanks a bunch!!

#4

Glad to hear your issue is resolved! :slight_smile:

I believe the driver included with mBlock is the correct one, but sometimes folks forget to install it. :slight_smile:

For what it’s worth, the mBot, unlike the mBot Ranger, must be powered on because it doesn’t draw power from the USB cable.

Happy New Year!

Chuck

P.S. I wrote an eBook that covers programming the mBot using mBlock 3.x (link) that starts with turning on the LEDs and ends with a maze solving robot. The proceeds from the book to fund local robotics programs for middle and high school students.

#5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.