mBlock 3.2.1 loads faulty default program

#1

To the mBlock team:
There have been a number of threads where users have run into trouble through using the ‘reset default program’ command. The problem is that the program loaded has a number of faults - most noticeable if which is LED control.

These are corrected once the ‘Update Firmware’ operation is performed.

I have run into this issue with the latest (3.2.1) IDE - which is frustrating as I used the provided instructions to reload (after running my own program) the default believing it to be a solid and functional version.

Is it possible for the next release to use the latest, correctly operating, version as the default?

Thanks very much,
Graham

#2

With all the mBlock and mBot threads about various features that aren’t working with the factory default program (i.e., use “Reset Default Program”), I tried to make a comprehensive program to test all the mBlock features for mBot.
Here’s my program: test mBot Features.sb2 (6.9 KB)

Here was my conclusion: the program crashes mBlock.

So I broke it down into pieces:

  • Light sensor: Not working. Produces arbitrary or max range values that don’t change with change in ambient light levels. Cause appears to be mBot code referencing incorrect analog input.
  • Ultrasonic: Working!
  • Line follow: Working!
  • On board button: Working!
  • On board LEDs: Not working! Only LED 2 illuminates and with the wrong colors. Cause appears to be mBot code calling setColor function with incorrect arguments.
  • Buzzer: Working!
  • Motors: Working!
  • IR Remote Decoding: Crashes mBlock. As soon as I the “<ir remote [XXX] pressed>” conditional block is executed in mBlock, the program crashes. Cause unknown, but I suspect that mBot is sending back an incorrect length return value via the serial interface.

If I repeat the test with the binary uploaded when using “Upgrade Firmware”:

  • All mBot supported features work properly.

Conclusion: The “Default Factory Program” binary needs to be updated with the mBlock interfaces from the “Upgrade Firmware” binary.
I suggest that a similar program be used as a regression test before every mBlock release.

#3

Hi Lentil,
Thanks for the feedback, the test program and expanding the list of symptoms. I am sure other users will find this information useful.

The bottom line: to regain control after loading a user program into the mBot is a two step process of

  1. use the ‘Reset Default Program’ and then
  2. upgrade with the ‘Upgrade Firmware’ command
    before attempting to run a program that controls mBot.

Note: The point 2) above must be performed when first using a newly purchased mBot for it to respond correctly.

I am not sure if it is possible to go directly to ‘Upgrade Firmware’ - something to try when I have time.

Anyway, I am hopeful that the next release will have corrected the default program and so save a lot of angst for users.

Regards to all,
Graham

#4

Graham,
The problem is that once we “Upgrade Firmware” all the features of the mBot work correctly EXCEPT FOR the included push button IR remote control, which no longer has ANY effect on the mBot. The IR remote control works again after we “Reset Default,” but then the mBot features return to dysfunction as described perfectly by Lentil. We currently have to choose between using the IR remote control or having the mBot functions perform correctly when programmed.

So yes, we will all appreciate if if the next release addresses this issue. Thanks for listening.

#5

Hi there,
Thanks for reading and contributing valuable information to this thread.

Hopefully, the keepers of mBot will also fix problem with the IR function in the ‘Update Firmware’ version, and make the fix available to all in the next release.

I am quite baffled that there have been comments posted from a moderator or expert that represents the team behind mBot/mBlock. It does make me wonder if they listen to their user community - but I err on the side of hope, that they do.

Time will tell,
Graham

#6

I totally agree with you @rakembuzz

#7

Hi guys,
I have just upgraded to 3.2.2 and ‘restored default program’ my mBot.

My first test, that of the LED, indicate that they operate correctly which is exciting.

And my crude motor test worked correctly as well.

Could those who reported specific problems retest and post the results?

Thanks mBot,
Graham

#8

Hi,
I am on mBlock 3.2.2 and did some simple programming to button D on the IR controller. It worked perfectly. However it does wipe out the default program of the remote control. To restore the remote control I can choose to reset the default program in mBlock. If I choose to “upgrade firmware” this also wipes out the remote control option. This appears to be very disappointing. So I can either have the out of the box IR remote control functions or I can have my own mBlock designed programs but I can’t have both. I was hoping to have the standard functions on A,B and C and then add my own code to D,E, and F. Can anyone confirm this to be the case for them too?
Thank you