robobasic v2.7 problems?
robobasic v2.7 problems?
by serithseraki
Thu Sep 29, 2011 4:36 am
I am currently debating installing the v2.7 to update my v2.5 but the firmware upgrade for flash memory seems dodgy to me. I have also read that certain commands run differently. Does anyone currently use this version and can tell me what problems occur? Also, once I upgrade the controller's firmware, can reset it to default?
by i-Bot
Thu Sep 29, 2011 10:35 am
The firmware update from 2.5 to 2.7 is done by Robobasic 2.7 and has never given me a problem. Make sure batteries are well charged though. You cans switch controller type to use flash or eeprom for downloaded program storage.
To revert to 2.5 software is possible, but you need to use my Roboflash or similar to download the old firmware image. Roboflash and firmware images are in my file area.
I have switched between 2.5 and 2.7 hundreds of times on two C3024 without mishap. The bootloader appears to be in a protected part of flash and is not updated.
The only problems I have found while using 2.7 are due to it being faster, so any loops with critical timing may need adjustment. It is not of significant value to go to 2.7 if you are only using standard robot and moves. The value comes if you are using lots of sensors, or driving I2C peripherals. Complex maths is restricted more by the limited robobasic data types and functions than speed.
To revert to 2.5 software is possible, but you need to use my Roboflash or similar to download the old firmware image. Roboflash and firmware images are in my file area.
I have switched between 2.5 and 2.7 hundreds of times on two C3024 without mishap. The bootloader appears to be in a protected part of flash and is not updated.
The only problems I have found while using 2.7 are due to it being faster, so any loops with critical timing may need adjustment. It is not of significant value to go to 2.7 if you are only using standard robot and moves. The value comes if you are using lots of sensors, or driving I2C peripherals. Complex maths is restricted more by the limited robobasic data types and functions than speed.
by i-Bot
Thu Sep 29, 2011 10:22 pm
It is hard to specify a simple speed comparison. The C3024 spends much of its time running the motion engine. Other time is available for running the Robobasic script, which is much more efficient under 2.7, but only if you really understand what is going on, and how the processes interact.
Not sure what serial communication problem you refer to. Communication speed again is limited more by the interaction of the serial interface with the motion engine, and also the serial protocol used.
Not sure what serial communication problem you refer to. Communication speed again is limited more by the interaction of the serial interface with the motion engine, and also the serial protocol used.