Tool offset
15 Jul 2015 00:47 #60628
by andypugh
I finally got round to this. (spare time in a hotel room working in Spain) and I have not yet seen the issue described.
What I did was compile master, then ran it, and selected the lathe-fanucy config.
I homed it.
Changed to DRO view to see the tool offsets.
Then in the MDI tab issued the command T0106. I then saw the Z offset go to 0.5010, which is the sum of the 06 and 10001 offsets, so that seems to work exactly as it should.
Can you give the steps required to get the wrong behaviour?
Replied by andypugh on topic Tool offset
Just did, I'm on 2.6.7 but I set milestone as future-release by mistake.
I finally got round to this. (spare time in a hotel room working in Spain) and I have not yet seen the issue described.
What I did was compile master, then ran it, and selected the lathe-fanucy config.
I homed it.
Changed to DRO view to see the tool offsets.
Then in the MDI tab issued the command T0106. I then saw the Z offset go to 0.5010, which is the sum of the 06 and 10001 offsets, so that seems to work exactly as it should.
Can you give the steps required to get the wrong behaviour?
Please Log in or Create an account to join the conversation.
22 Jul 2015 03:44 #60808
by ReinaldoP
Replied by ReinaldoP on topic Tool offset
lathe-fanucy simulation works correctly on my computer also. The behavior only shows up when I run the actual machine. I double checked remap.py, toplevel.py , stdglue.py and toolchange.ngc. They are identical in latthe-fanucy and my configuration. The only difference between these are the hal files which of course are machine specific. Im handling the actual toolchange with a custom component, is it possible something in my hal files is interfering with the proper execution of the remap? Could the following iocontrol net connections in my hal file be causing me problems?
net tool_prep iocontrol.0.tool-prepare sl35TURRET.tool-prep
net tool_prepd sl35TURRET.tool-prepd iocontrol.0.tool-prepared
net tool_CMD iocontrol.0.tool-prep-number sl35TURRET.tool-cmd
net tool_change iocontrol.0.tool-change sl35TURRET.tool-change
net tool_done sl35TURRET.tool-changed iocontrol.0.tool-changed
net tool_prep iocontrol.0.tool-prepare sl35TURRET.tool-prep
net tool_prepd sl35TURRET.tool-prepd iocontrol.0.tool-prepared
net tool_CMD iocontrol.0.tool-prep-number sl35TURRET.tool-cmd
net tool_change iocontrol.0.tool-change sl35TURRET.tool-change
net tool_done sl35TURRET.tool-changed iocontrol.0.tool-changed
Please Log in or Create an account to join the conversation.
23 Jul 2015 15:53 - 23 Jul 2015 15:54 #60844
by andypugh
It is possible, but I am not clear how.
The remap.py code calculates the required offsets from the T-word in G-code if I recall correctly.
It is possible that the problem might be one of timing, that the system does not know that the tool is loaded at the point that the offset is applied.
Has a couple of (debug,) lines in it. Do they show the expected numbers or not?
Replied by andypugh on topic Tool offset
Could the following iocontrol net connections in my hal file be causing me problems?
It is possible, but I am not clear how.
The remap.py code calculates the required offsets from the T-word in G-code if I recall correctly.
It is possible that the problem might be one of timing, that the system does not know that the tool is loaded at the point that the offset is applied.
1 O<toolchange> sub
2 (debug, Tool requested = #<tool>)
3 #<wear> = [10000 + FIX[ #<tool> / 100]]
4 #<tool> = [#<tool> MOD 100]
5 M6 T#<tool>
6 G43 H#<tool>
7 O100 IF [#<wear> GT 10000]
8 G43.2 H#<wear>
9 O100 ENDIF
10 #<pocket> = #<tool>
11 (debug, tool = #<tool> wear = #<wear>)
12 O<toolchange> endsub [0]Has a couple of (debug,) lines in it. Do they show the expected numbers or not?
Last edit: 23 Jul 2015 15:54 by andypugh.
Please Log in or Create an account to join the conversation.
25 Jul 2015 03:09 #60897
by ReinaldoP
Replied by ReinaldoP on topic Tool offset
I tried the following:
When turret in position 3 with offset 3 I command T0505 in MDI,
Debug shows the following:
tool requested = 505.000000
tool = 5.0000 wear = 10005.0000
Turret moves to position 5 and offsets are the respective ones for T05 but wear component was not applied.
When turret in position 5 with offset 5 I command T0505 again in MDI,
Debug shows the following:
tool requested = 505.000000
tool = 5.0000 wear = 10005.0000
Now it applies wear.
Something I just noticed- when I first load linuxcnc and execute a Txxyy it works as intended(tool changes position and wear offset is applied), then all subsequent tool changes do not work as intended unless I command it twice or reboot linuxcnc.
When turret in position 3 with offset 3 I command T0505 in MDI,
Debug shows the following:
tool requested = 505.000000
tool = 5.0000 wear = 10005.0000
Turret moves to position 5 and offsets are the respective ones for T05 but wear component was not applied.
When turret in position 5 with offset 5 I command T0505 again in MDI,
Debug shows the following:
tool requested = 505.000000
tool = 5.0000 wear = 10005.0000
Now it applies wear.
Something I just noticed- when I first load linuxcnc and execute a Txxyy it works as intended(tool changes position and wear offset is applied), then all subsequent tool changes do not work as intended unless I command it twice or reboot linuxcnc.
Please Log in or Create an account to join the conversation.
25 Jul 2015 18:56 #60905
by andypugh
Replied by andypugh on topic Tool offset
Just out of interest, does the problem appear when running G-code from a file rather than MDI?
I am wondering if it is related to a strange MDI bug that I am seeing somewhere else.
I am wondering if it is related to a strange MDI bug that I am seeing somewhere else.
Please Log in or Create an account to join the conversation.
28 Jul 2015 02:48 #60969
by ReinaldoP
Replied by ReinaldoP on topic Tool offset
I was trying it out with MDI only before applying it to the programs I run in auto. And weirdly the offsets worked like a champ when running in auto mode (I had not tried it yet thinking it wouldnt work also).
So to answer your question YES the problem only happens in MDI mode apparently.
So to answer your question YES the problem only happens in MDI mode apparently.
Please Log in or Create an account to join the conversation.
28 Jul 2015 03:24 #60973
by andypugh
In that case I suggest seeing if it gets fixed when the other bug gets fixed. It sounds very simple, and probably(?) doesn't cause any problems when actually making parts?
Replied by andypugh on topic Tool offset
I was trying it out with MDI only before applying it to the programs I run in auto. And weirdly the offsets worked like a champ when running in auto mode (I had not tried it yet thinking it wouldnt work also).
So to answer your question YES the problem only happens in MDI mode apparently.
In that case I suggest seeing if it gets fixed when the other bug gets fixed. It sounds very simple, and probably(?) doesn't cause any problems when actually making parts?
Please Log in or Create an account to join the conversation.
Time to create page: 0.071 seconds