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

Values not available in Modbus reading #186

Open
TomSAVU opened this issue Sep 21, 2023 · 1 comment
Open

Values not available in Modbus reading #186

TomSAVU opened this issue Sep 21, 2023 · 1 comment

Comments

@TomSAVU
Copy link

TomSAVU commented Sep 21, 2023

All below refers to Modbus operations with Gen3 Lite.

When reading the Fault Flag Discrete Inputs (address 32 to 62), I am expecting to see some flags changing.
The "Emergency stop activated" flag is changing correctly, but I was expecting the "Unable to reach pose" flag to change if I am trying to send the arm in an impossible position. This is not happening.
The same when reading the Fault Flag Registers, addresses 2 and 3.

When reading the warning flags, either discrete inputs (address 64 to 94) or registers (addresses 4 and 5), I am receiving no data, all the bits are False when I am stopping the arm with the emergency button.
When are these warning flags activated?

@martinleroux
Copy link
Collaborator

Hi @TomSAVU ,

The faults and warning flags refer to the safeties of the robot, as seen in the Safeties page of the Web App. The robot not being able to reach a position does not put the robot in a fault state, hence why you don't see the flags changing.

The warnings are the same, but trigger for values slightly lower than faults (again, see the Safeties page).

Cheers

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

2 participants