New mBOT obstruction detection does not work

#1

I just brought the mBot for my kids we assembled it and tried the different mode, the white led mode and the blue led mode work fine. However the green led obstruction detection mode does not work the bot keeps running into walls etc, what could be wrong? The small red LED on the ultrasonic sensor is on and the wire from the sensor Blue is connected to #3 on the main board.

Thanks for any help.

Obstruction detection doesn't work
#2

Do you have a iOs or Android device and a bluetooth mBot? If yes, please install the app Makeblock, connect it to the mBot, and start the default project. There should be a widget showing the value from the ultrasonic sensor. Does it work?

#3

To add to @Andreas comment, you should download the current version of mBlock, connect to the robot via the USB cable, and upgrade the firmware. That has a tendency to fix a lot of ills. :slight_smile:

#4

Thanks For your reply. I tried it out on an iOS device and see that it is stuck at 400. Now will try to to upgrade.

Thanks for your quick replies much appreciated.

#5

Ok the upgrade with a mac did not help either. Still just shows 400.

#6

BTW, how many lights should show up on the ultrasonic sensor when on? I just see one red led that is light all the time.

#7

Could you try another cable between sensor and mainboard? If needed use the cable from the line follower.

#8

The 400 reading indicates that the Ultrasonic sensor is not detecting anything. I’m only seeing a single red light on my Ultrasonic sensor for what it’s worth.

Things to check:

  1. Make sure the sensor cable is firmly seated. You should feel a slight click when the cable is properly inserted.
  2. Make sure that you note the port where the cable from the Ultrasonic is connected.
  3. If you have a Mac, you will need to install a driver. A free driver is here, and a paid-for driver is here.
  4. Connect the mBot to the Mac using the USB cable.
  5. Connect the mBot to mBlock using the Connect->Serial Port menu item. Mine shows /dev/tty.wchusbserial410 as the correct port but I have seen /dev/tty.wchusbserial420, etc. on other devices.
  6. Try running this program:

You should see the panda “saying” an ever-changing number.

#9

Thanks Chuck trying this out today.

#10

Chuck thanks for the detailed instructions, i tried changing the cable, installing the new driver via mblock also. Entered the program as show in your message. No luck stuck at 400 :frowning:.

#11

Hi, Smistry,
Thanks for purchasing our products!
I. Upgrade firmware first then try running the program example provided by Chuck. 1. How to Upgrade Firmware for mBot.docx.zip (690.6 KB)

II. If the step I doesn’t work,attach the RJ25 cable with the ultrasonic sensor with port 4. Then try to run the program example, but choose “ultrasonic sensor Port4 distance” this time.
Please let me know if the above instructions work for you : )

#12

XW_makeblock. Tried all the instruction with mBlock v 3.4.6, including moving form port 3 to port 4, and chasing the cables.

I either get the reading as 400 all the time. Also tried the same with the iOS app where the value from the ultrasonic sensor always shows up as 400.

Really appreciate everyone help and quick replies.

#13

Hi, smistry,

Can I ask where did you purchase your mBot? Please kindly send the receipt to this e-mail: support@makeblock.com
We will be happy to assist you.

#14

XW_makeblock,

We received the mBot as a gift. I can send further correspondence to support@makeblock.com is there a reference number i need to use?

Thanks.

#15

Hi, Smistry,
You can send the link of this discussion page within your e-mail so we could better assist you.
Best,
XW

#16

sure will do.

#17