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.

Sign up for GitHub

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

Jump to bottom

Investigate SDO malfunction #511

Open
jbbjarnason opened this issue Feb 21, 2024 · 2 comments
Open

Investigate SDO malfunction #511

jbbjarnason opened this issue Feb 21, 2024 · 2 comments
Labels
exes:ethercat Ethercat related to library functions

Comments

@jbbjarnason
Copy link
Contributor

No description provided.

@jbbjarnason
Copy link
Contributor Author

Tried reproducing by sending changes to sdo on all parameters for one motor, did not occur.

The problem was most likely that the ethercat exe got to many ping pong requests on motors and was unable to keep the cycle running stably. However, @omarhogni found that the reset might need to be pulsed, this wasn't verified nor implemented. @omarhogni can you put a link or screenshot for reference? and close as we cannot reproduce.

@omarhogni omarhogni added the exes:ethercat Ethercat related to library functions label Feb 29, 2024
@omarhogni
Copy link
Contributor

omarhogni commented Mar 25, 2024 •
edited
Loading

the ATV320 Programming Manual Page 265
image

There is mention of a value change for the reset bit from low to high.

The case i was talking about was

  • Our reset bit is high
  • a auto resetable fault occurs
  • the fault does not reset because the reset bit was already high and now we hold it high.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
exes:ethercat Ethercat related to library functions
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jbbjarnason @omarhogni