Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

myCobot 280 Pi Firmware Issue - Requires Reflashing After Power Cycle #48

Open
Tareq-Mh opened this issue Jun 16, 2024 · 2 comments
Open

Comments

@Tareq-Mh
Copy link

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:

  • 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:

  1. Update the Atom board firmware to 6.4.
  2. Power cycle the myCobot 280 Pi.
  3. Observe that the motors no longer respond to commands.
  4. Manually reflash the Atom board firmware using the myStudio app on the Raspberry Pi.
  5. 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!

@always-lgtm
Copy link

How did you manage this? When i launch myStudio on the rpi, mine says no board detected and does not even allow me to flash.

@sgbaird
Copy link

sgbaird commented Sep 25, 2024

  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants