Skip to content

Conversation

@Sigma1912
Copy link
Contributor

@Sigma1912 Sigma1912 commented Dec 16, 2025

Joints set to volatile are automatically unhomed when task state switches to OFF or ESTOP
If a joint is thus unhomed motion state needs to be set to 'free'
Fixes #3658

Joints set to volatile are automatically unhomed when task state switches to OFF or ESTOP
If a joint is unhomed motion state needs to be set to free
Fixes LinuxCNC#3658
@Sigma1912 Sigma1912 force-pushed the fix_state_not_set_to_free_with_volatile_joints branch from 29e679d to c29e9b1 Compare December 19, 2025 12:50
@Sigma1912
Copy link
Contributor Author

Closing this for further investigation into failing tests.

@Sigma1912 Sigma1912 closed this Dec 22, 2025
@Sigma1912
Copy link
Contributor Author

Sigma1912 commented Dec 22, 2025

The reason some test are failing is that some of these tests actually run in unhomed mode.
This PR assumes that motion state should not be 'teleop' or 'coord' while not all-homed which is not correct.
Linuxcnc can also be run in unhomed state (NO_FORCE_HOMING = 1).
Hence we would need to know if this option has been set before checking 'if (!get_allhomed() ...'
However this information seems to only be available in task:

if ((inistring = inifile.Find("NO_FORCE_HOMING", "TRAJ"))) {

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.

Python Interface motion_mode fails to change with VOLATILE_HOME = 1

1 participant