Ignore hard and or softlimits for toolchange
03 Nov 2024 10:10 #313704
by anfänger
Ignore hard and or softlimits for toolchange was created by anfänger
My toolchange uses two custom hydraulic rams in top z position to release the tool.
They are leaking and I am not sure if I can fix them. An alternative would be to make them fixed and move Z up to release the tool.
But this has to be avoided during normal usage.
The reference switch is at the end of the tool change travel. So I could use this as a combined end and reference switch.
But I would need to be able to move over this point for toolchange.
Is ip possible to set something like this up?
Thanks Patrick
They are leaking and I am not sure if I can fix them. An alternative would be to make them fixed and move Z up to release the tool.
But this has to be avoided during normal usage.
The reference switch is at the end of the tool change travel. So I could use this as a combined end and reference switch.
But I would need to be able to move over this point for toolchange.
Is ip possible to set something like this up?
Thanks Patrick
Please Log in or Create an account to join the conversation.
03 Nov 2024 12:42 - 03 Nov 2024 12:43 #313714
by Aciera
Replied by Aciera on topic Ignore hard and or softlimits for toolchange
Softlimit values are accessible in the ini.* hal pins after startup has completed.
If changed during gcode execution (eg by using a custom mcode) they need a queuebuster command to be updated internally.
Limit switches can be disconnected/reconnected in hal.
If changed during gcode execution (eg by using a custom mcode) they need a queuebuster command to be updated internally.
Limit switches can be disconnected/reconnected in hal.
Last edit: 03 Nov 2024 12:43 by Aciera.
Please Log in or Create an account to join the conversation.
03 Nov 2024 13:41 #313716
by anfänger
Replied by anfänger on topic Ignore hard and or softlimits for toolchange
Thanks that already helped a lot.
linking and unlinking Hal I can mange in a bash script.
I would switch reference and limit switch for toolchenge and Bach afterwards.
What I don't understand is the queuebuster command.
What I understand ist the the limits are part of the milltask an I can alter the values with halcmd without altering the infile.
Where and how do I need the queuebuster?
Thanks
Patrick
linking and unlinking Hal I can mange in a bash script.
I would switch reference and limit switch for toolchenge and Bach afterwards.
What I don't understand is the queuebuster command.
What I understand ist the the limits are part of the milltask an I can alter the values with halcmd without altering the infile.
Where and how do I need the queuebuster?
Thanks
Patrick
Please Log in or Create an account to join the conversation.
03 Nov 2024 14:02 #313719
by Aciera
Replied by Aciera on topic Ignore hard and or softlimits for toolchange
A 'queuebuster' is a command that tells the interpreter to stop parsing Gcode until actual code execution has caught up (ie the command queue is empty). After such an event the new ini.* values are reloaded and Gcode parsing restarts.
The queue buster (eg reading an analog input) needs to be right after the change
in the ini values (eg done in the 'M123'). I usually put a queue buster in front as well:
The queue buster (eg reading an analog input) needs to be right after the change
in the ini values (eg done in the 'M123'). I usually put a queue buster in front as well:
M66 E0 L0 ; queuebuster
M123 ; switch limits
M66 E0 L0 ; queuebuster
The following user(s) said Thank You: tommylight, anfänger
Please Log in or Create an account to join the conversation.
03 Nov 2024 15:12 #313720
by anfänger
Replied by anfänger on topic Ignore hard and or softlimits for toolchange
Many thanks! this sounds way easier than I tought.
Please Log in or Create an account to join the conversation.
Time to create page: 0.113 seconds