You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've purchased a myCobot 280 Pi and updated the Atom board to version 6.4. However, we are experiencing a recurring issue where the robot stops working after each power cycle. This requires us to manually reflash the Atom board firmware from the Raspberry Pi to restore functionality.
Problem:
After each power cycle, the motors do not respond to commands (e.g., send_angles([0,0,50,0,0,0],100) has no effect).
Temporary Solution:
Manually reflashing the Atom board firmware using the myStudio app on the Raspberry Pi restores functionality. However, this needs to be repeated every time the power is cut, which is highly inconvenient.
Steps to Reproduce:
Update the Atom board firmware to 6.4.
Power cycle the myCobot 280 Pi.
Observe that the motors no longer respond to commands.
Manually reflash the Atom board firmware using the myStudio app on the Raspberry Pi.
The robot starts working again.
Request:
Could you please provide a permanent solution or suggest a method to avoid having to reflash the Atom board after every power cycle?
Thank you for your assistance!
The text was updated successfully, but these errors were encountered:
Manually reflashing the Atom board firmware using the myStudio app on the Raspberry Pi restores functionality. However, this needs to be repeated every time the power is cut, which is highly inconvenient.
A colleague, @gursi26, seems to be experiencing the same issue and can reproduce the behavior.
Description:
We've purchased a myCobot 280 Pi and updated the Atom board to version 6.4. However, we are experiencing a recurring issue where the robot stops working after each power cycle. This requires us to manually reflash the Atom board firmware from the Raspberry Pi to restore functionality.
Problem:
send_angles([0,0,50,0,0,0],100)
has no effect).Temporary Solution:
Steps to Reproduce:
Request:
Could you please provide a permanent solution or suggest a method to avoid having to reflash the Atom board after every power cycle?
Thank you for your assistance!
The text was updated successfully, but these errors were encountered: