Skip to content

Conversation

@acmorrow
Copy link
Contributor

@acmorrow acmorrow commented Nov 6, 2025

Fixes #394.

I think this is really all that is required, unless you have unit tests that you need, but I didn't find any results in the codebase for other symbols from this enumeration.

@codecov
Copy link

codecov bot commented Nov 6, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 42.71%. Comparing base (276120d) to head (d4f6f11).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #401      +/-   ##
==========================================
- Coverage   42.83%   42.71%   -0.13%     
==========================================
  Files          99       99              
  Lines        8626     8623       -3     
  Branches     1170     1170              
==========================================
- Hits         3695     3683      -12     
- Misses       4652     4660       +8     
- Partials      279      280       +1     
Flag Coverage Δ
start_ursim 82.89% <ø> (-1.66%) ⬇️
ur20-latest 40.68% <ø> (-0.09%) ⬇️
ur5-3.14.3 40.57% <ø> (-0.07%) ⬇️
ur5e-10.7.0 35.70% <ø> (-0.03%) ⬇️
ur5e-5.9.4 40.70% <ø> (-0.06%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

IS_FAULT = 9,
IS_STOPPED_DUE_TO_SAFETY = 10
IS_STOPPED_DUE_TO_SAFETY = 10,
IS_SYSTEM_THREE_POSITION_ENABLING_STOPPED = 11
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest following the RTDE documentation regarding the naming:

Suggested change
IS_SYSTEM_THREE_POSITION_ENABLING_STOPPED = 11
IS_3PE_INPUT_ACTIVE = 11

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @urfeex for the feedback.

So, I picked this name by analogy with what I found in SafetyStatus: SafetyStatus::ROBOT_EMERGENCY_STOP goes to UrRtdeSafetyStatusBits::IS_ROBOT_EMERGENCY_STOPPED, so I analogized SafetyStatus::SYSTEM_THREE_POSITION_ENABLING_STOP to the proposed UrRtdeSafetyStatusBits::IS_SYSTEM_THREE_POSITION_ENABLING_STOPPED. Just let me know which you prefer. If you still prefer the one you proposed here over the analogized one, I'll just accept your edit and you can merge.

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

Successfully merging this pull request may close these issues.

UrRtdeSafetyStatusBits does not have an entry for 3PE signal

2 participants