After upgrade to v3.2 and v3.2.1 my mbot dosent work propertly
Only led #2 is on light blue
Set led RGB and light sensor onboard doesnt work
Can’t duplicate the error. I did the same thing from 3.2.1 and I’m getting both LEDs lighting up. 
You might want to drop an email to support@makeblock.cc and ask @pioneer about it.
EduLibre
#3
Hi chuckmcknight, you are right, both leds lighting up when upload to arduino
Problem is when green flag clicked, before upgrade worked properly
light sensor onboard has the same problem
Weird, I was running it with the when [green flag] clicked block and it worked here. :-/
marcopic
#7
Yes, it’s all true, but as I mentioned in a thread of mine on this forum, this workaround (upgrading the firmware) deactivates the remote control. Probably most of users doesn’t need to run the mBot by the remote control, so it’s not a real problem.
Pioneer
#8
@marcopic Firmware could only be upgraded via USB. If you want to run the mBot with remote control(via 2.4G wireless or Bluetooth), you need to switch to 2.4G wireless or Bluetooth connection mode. After upgrading firmware, unselect Connect>Serial port> Com x(for windows), select Connect>2.4G Serial/Bluetooth, when you connected, you are able to run your program remotely.
rakembuzz
#9
@Pioneer, I think you may have misunderstood. When you upgrade the firmware using USB, then yes, the on-board LEDs do work. And yes, you can reconnect with 2.4G or Bluetooth and run your program. BUT you cannot get any functionality from the included infrared push button remote control. This is also the case with my mBot, which my 8 year old likes to use both with the remote control and through a program.
Does anyone know of a fix after upgrading firmware to restore IR push button remote control capability?
hmbot
#10
@rakembuzz i’m getting the same thing. I upgraded firmware, then when I send a simple set led command, only LED 1 illuminates, and not the color i selected. If i select red 255, it illuminates as green. I can’t get LED2 to illuminate no matter what.
Pioneer
#11
In your case, you can add remote control functionality in your mBlock program.
Then you are able to use both with remote control and through a program.
hmbot
#12
as an update:
i re-downloaded the default program and everything seems to be working fine now.
marcopic
#13
Yes, you understood what I referred to: infrared push button remote control (I didn’t know the exact name in English, thanks!).
@Pioneer your workaround must pass through Scratch; what happens if I just want to move the mBot by the infrared push button remote control? This way I need before “restore default program” in Scratch. Consider that some children just want to play mBot by infrared push button remote control. It’s easier for the beginners.
Pioneer
#14
@marcopic , if you just want to control the mBot by remote control, things would be much easier, we have the user guide, you can refer the page 9 of the file here: mBot instruction.zip (9.0 MB)