On board LEDs don't work as instructed

#1

Anyone else having issues with the 2 on board LEDs not working properly?
I have no LED code in the file currently and the LED #2 is on Light blue and the LED #1 is on bright blue.
And with other files when I do try to turn them on they don’t come on, or they don’t come on correctly.

Any Ideas?

#2

@BeeAMaker,

Here’s what I faced:

In: http://learn.makeblock.cc/get-started/, I followed the same steps, as the video tutorial.

My “set LED” block is slightly different compared to the tutorial.

In "Set LED…red [drop down menu], green [drop down menu], blue [drop down menu]"
a) I clicked 60 at the drop down menu beside red, the LED becomes green color,
b) I clicked 60 at the drop down menu beside green, the LED becomes blue color,
a) I clicked 60 at the drop down menu beside blue, the LED does NOT light up.

There are 2 LEDs, 1 at port 1, the other at port 2, But only port 2 LED lights up.

I am new to this forum, but I did a search “LED”, still can’t find any solution. I’ve fed backed to Makeblock, hopefully help is coming.

Thank you, Ivan Hoe

#3

Thanks for that info, I’ll check it out.

Something i did notice, the On Board LEDs don’t seem to work properly while tethered to the USB port. Once the USB is removed they seem to work as instructed. However, I still have the Blue/Light blue combo even if no LED instruction is in the code.

#4

My friend and me met today.

Edit V:
His mBlock is V2.2, his LED test run on USB works.
I am unsure if he is running Windows 10, but I think unlikely it’s W10.

Mine using W10, V3.0 did not.

#5

I had the same problem, and it disappeared after I hit “Upgrade Firmware” on the mBlock Connect menu.

#6

@kenv98223 Tried that too

#7

Hi kenv98223, thanks for sharing, I did what you said and also changed to new batteries. Now everything works fine.

Funny thing is, in the video, the person also highlighted “Upgrade Firmware”, but somehow I missed it.

#8

Have a look at this conversation

#9

I’m having the same problem with my on board LEDs. I can’t update my firmware because it’s dim. Does that mean it’s already updated. Please help.

#10

I’m having the exact same problem. I can’t update the firmware because it’s dim. Does anyone have an idea to help?

#11

I’m having the exact same problem - just starting to figure out how to communicate with this thing. I can connect the USB cable to my computer and choose COM1, which results in my PC saying it is connected through serial port (though I don’t know what to) and then the option appears to upgrade firmware. I choose that option and it says Uploading 0%, but then fails every time without making any progress. I can connect with Bluetooth, but then don’t get the upgrade firmware option.

What am I missing? I’d like to be able to control both LEDs and actually get the color I’m commanding. The lights both work correctly during built-in programmed activity, like using the A mode on the remote.

#12

Found out something that worked. I unplugged the USB cable from my PC and plugged it into a different port with the mBot connected and powered on. The PC installed drivers and assigned COM5 to the new port. Chose that one and the upload worked. And now the lights work correctly as well.

#13

I confirm that the on board LEDs do not work as desired when the “Default Program” is running on the mbot. This is still true with the latest mBlock 3.2.

When connected via USB serial:
If I choose “Upgrade Firmware”, which (I believe) replaces the onboard code with a basic scratch-capable program, the LEDs controlled by mblock/scratch work as expected. If I choose “Reset Default Program” only one LED lights, and it does so incorrectly. If I actually compile and upload my program to the board (Upload to Arduino), the LEDs work as expected. This appears to be a bug in the binary image for “Reset Default Program”.
A separate thread under the “mblock” category on this forum indicates that there is an error in the source code for the default program. However, clicking the menu item doesn’t appear to compile code, just upload a binary… so fixing this bug won’t change the binary unless you manually replace it.

makeblock: Could you fix this in the next mBlock release please? My kids are very confused when their simple LED flashing programs don’t work.

#14

I’m in the exact same boat here. I am using USB to the mBot, mBlock sees my mBot connected on the serial port assigned to it. I get the green light in mBlock indicating that the mBot is connected. I wrote a simple “mBot” program that would show the lights flashing, and in the binary output window you can see it sending code when I double click the program. But the RGB LEDs do not physically light up.

#15

I confirm all that written by Lentil; I’m working under Windows 7 64 bit and mBlock 3.2.
It’s fully true that upgrading the firmware fixes the issue regarding on-board leds, BUT I found out the “remote control” doesn’t work any more, so if I want to move the mBot by remote control I must first “restore default program”. This is a very bothering thing! Please, fix this issue.
Thanks in advance
Marco

#16