Automatic Touch-Off after tool change
26 Jul 2015 02:30 #60929
by cahlfors
Replied by cahlfors on topic Automatic Touch-Off after tool change
By using your suggested method, I have concluded that all the Python code indeed executes and that the execution stops in the manual_change.ngc on either of the following lines:The first line executes if there is no movement to do, but the second line always seizes since there is always at least a Y movement to do.
If I comment these lines out, the manual_change.ngc code continues until the next movement should take place and seizes there instead.
The really weird thing is that if I copy one of these lines and paste into the GUI in the MDI tab, the mill moves to the coordinates as defined in the *.ini file, just as expected. But not from the program.
Maybe even more puzzled now,
/Christoffer
; move to toolchange position: z, then xy
g53 g0 Z #<_ini[change_position]z>
g53 g0 X #<_ini[change_position]x> Y #<_ini[change_position]y>If I comment these lines out, the manual_change.ngc code continues until the next movement should take place and seizes there instead.
The really weird thing is that if I copy one of these lines and paste into the GUI in the MDI tab, the mill moves to the coordinates as defined in the *.ini file, just as expected. But not from the program.
Maybe even more puzzled now,
/Christoffer
Please Log in or Create an account to join the conversation.
30 Jul 2015 19:34 #61038
by cahlfors
Replied by cahlfors on topic Automatic Touch-Off after tool change
@andypugh:
The values of the suggested HAL pins are:
motion.feed-hold = false
motion.adaptive-feed = 1
motion.spindle-at-speed = true
I believe this is correct?
To follow through on the idea, I checked all the other motion HAL pins and any other pins that looked relevant. All seem okay.
But I did notice another thing. In the MDI tab in Axis, there is a window where you can see which G-codes that are active:I understand that F0 means feed=0 and that could be the culprit. With zero feed, a move would take forever - just as is the case! So I tried to issue an F50 first and even inserting it into the manual_change.ngc, but the behavior is the same regardless.
The beginning of manual_change.ngc is setting some parameters which I do not understand (I always thought # is for comment?):Clearly, feed is one of them. I tried to comment these lines away (with a semicolon;), but then I get a missing parameter error.
Do you think feed is the issue here? If so, what would be the next logical step to try?
@newbynobi:
I am using manualtoolchange.hal (spelled this way). Could there be a confusion?
Also, I am using Axis. Similar code to what you are referring to is executed (is that a correct way to call it, or is it more of parameter setting?) in manualtoolchange.hal:
and in gladevcp.hal:
Thanks to you both for reaching out to help!
A noob in need is a noob indeed!
/Chris
The values of the suggested HAL pins are:
motion.feed-hold = false
motion.adaptive-feed = 1
motion.spindle-at-speed = true
I believe this is correct?
To follow through on the idea, I checked all the other motion HAL pins and any other pins that looked relevant. All seem okay.
But I did notice another thing. In the MDI tab in Axis, there is a window where you can see which G-codes that are active:
G80 G17 G40 G21 G90 G94 G54 G49 G99 G64
G97 G91.1 G8 M5 M9 M48 M53 M0 F0 S0The beginning of manual_change.ngc is setting some parameters which I do not understand (I always thought # is for comment?):
#<metric> = #<_metric>
#<absolute> = #<_absolute>
#<feed> = #<_feed> Do you think feed is the issue here? If so, what would be the next logical step to try?
@newbynobi:
I am using manualtoolchange.hal (spelled this way). Could there be a confusion?
Also, I am using Axis. Similar code to what you are referring to is executed (is that a correct way to call it, or is it more of parameter setting?) in manualtoolchange.hal:
# in case they were linked already
unlinkp iocontrol.0.tool-change
unlinkp iocontrol.0.tool-changed
net tool-change-loop iocontrol.0.tool-change iocontrol.0.tool-changed
# rest is in gladevcp.haland in gladevcp.hal:
net tool-change motion.digital-out-00 => gladevcp.change-led
net tool-changed gladevcp.changed <= motion.digital-in-00
net toolno motion.analog-out-00 => gladevcp.number
net probing motion.digital-out-01 => gladevcp.probing-led
net enable motion.digital-out-02 => gladevcp.enable
net probe-contact gladevcp.probe-contact <= motion.probe-input
net reftool gladevcp.reftool <= motion.digital-in-01
net reflen motion.analog-out-01 => gladevcp.reflen
net currlen motion.analog-out-02 => gladevcp.currlenThanks to you both for reaching out to help!
A noob in need is a noob indeed!
/Chris
Please Log in or Create an account to join the conversation.
Time to create page: 0.161 seconds