-
Notifications
You must be signed in to change notification settings - Fork 8
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
First axis stuck in a moving state, remaining axes work fine #12
Comments
I don't see anything that would explain m1 being stuck in the moving state, but I have a few questions:
|
Also, is the |
See my substitutions file below:
The
The only change made to 7.0.5 is to enable the debug build in CONFIG_SITE - our build system automatically turns that on. Currently I am not autosaving anything for these IOCs. |
Is m1 stuck in the moving state at iocInit, or does it get stuck in the moving state after the first time it is moved? |
Also, can you share the output of the following command?
|
It gets stuck right at init, before I have a chance to move anything.
|
Can you post the output of this command:
|
Sure:
|
The asynReport output shows this for the first axis, parameter list 0. The value is 1, which means the axis is moving.
The 7 other parameters lists have value=0, which means the axis is not moving.
You may need to add some debugging to figure out why that first axis is set to 1. |
After setting up a few motor sim IOCs, I noticed that on all of them the first axis is always stuck in a moving state, while all the remaining ones work as expected. Is there something I am potentially mis-configuring here in my IOC initialization?
Below is the output from the startup:
At least to my eye there doesn't appear to be anything overly suspicious there.
The text was updated successfully, but these errors were encountered: