- Posts: 19306
- Thank you received: 0
Python Interface Feed Hold
2 years 5 months ago #299712
by andypugh
Replied by andypugh on topic Python Interface Feed Hold
If you set it off in Python then on again with G53, does Python still "win"?
Please Log in to join the conversation.
2 years 5 months ago #299722
by JT
Replied by JT on topic Python Interface Feed Hold
Issuing a M53 P0 then turning off python feed-hold (which is really feed-hold-enable) then turning on M53 with M53 P1 the python status feed_hold_enabled is true and setting motion.feed-hold on stops motion.
I 'think' I just misunderstood what does what with python set_feed_hold(int) which should be named set_feed_hold_enabled(int).
Turning off M53 then setting python set_feed_hold true it turns on M53 and updates the python mcodes status.
Setting python set_feed_hold False does not update the python mcodes so it 'looks' like M53 is on when it's really off.
In any case the python status feed_hold_enabled always shows the correct status of feed hold enable.
JT
I 'think' I just misunderstood what does what with python set_feed_hold(int) which should be named set_feed_hold_enabled(int).
Turning off M53 then setting python set_feed_hold true it turns on M53 and updates the python mcodes status.
Setting python set_feed_hold False does not update the python mcodes so it 'looks' like M53 is on when it's really off.
In any case the python status feed_hold_enabled always shows the correct status of feed hold enable.
JT
Please Log in to join the conversation.
Time to create page: 0.033 seconds
