Lego Boost. Problem with motors

C

coilamo

New member
After connect to the move hub I don't see one of two internal motor and external motor (A and B labeled as None). How fix it?
 

Attachments

  • Безымянный.png
    Безымянный.png
    20.5 KB · Views: 14
I have the same effect since the last Lego App update. Lego changed some function ports. You can see the necessary changes for pylgbst here:
github.com

New LEGO-Boost Firmware 2.0.00.0017 breaks pylgbst... (#33) · undera/pylgbst@990ccdb

* - Updated Port-Numbers (New Firmware 2.0.00.0017) - Skipping Device without Mac-Address (Seems to occur randomly after Firmware-Update, referring to https://github.com/LLK/scratch-vm/issues/22...
github.com github.com

So we need an update to S2Bot.

Cheers,
Torsten
 
Hello,
Could you open-source the "s2bot" code so the Picaxe Community can contribute to a quick fix to this issue.
Thank you.
Best Regards,
Laurent
 
Hello,

LEGO BOOST newest firmware changed the port number for all motors:
motor_A changed from 0x37 to 0x00
motor_B changed from 0x38 to 0x01
motor_AB changed from 0x39 to 0x10
motor_D changed from 0x02 to 0x03

Could you make this change to the "s2bot" code?
Thank you
Best Regards,
Laurent
 
If anyone else has reached the brick wall of Lego apps not being sufficiently flexible (Wedo software won't work with PU hubs/PU app won't work with Wedo for example) you may be interested to learn of the brick automation project, a free piece of software which allows control of ALL Lego BLE devices, as well as 3rd party devices such as SBrick. More info here. This should go some way to solving the challenge that Scratch no longer being usable with Boost for example presents.
 
You must log in or register to reply here.
Back
Top