Tool table scanning
- kalev
- Offline
- New Member
-
Less
More
- Posts: 4
- Thank you received: 0
24 Sep 2019 07:50 #146046
by kalev
Tool table scanning was created by kalev
Hello
I have the lathe with horizontal tool turret. During the tool setup I measure the tooltip X,Z distance from rotational center of the turret
and save values into tool table V and W. Before each tool change ( maybe on tool table update ) I want to calculate maximum distance from turret's center ( combining V and W ) of tools loaded in turret. I want to estimate is tool crash into workpiece possible during turret rotation. For that I have to scan tooltable entries. Is scanning possible in O-code or it needs python stuff.
Thanks
I have the lathe with horizontal tool turret. During the tool setup I measure the tooltip X,Z distance from rotational center of the turret
and save values into tool table V and W. Before each tool change ( maybe on tool table update ) I want to calculate maximum distance from turret's center ( combining V and W ) of tools loaded in turret. I want to estimate is tool crash into workpiece possible during turret rotation. For that I have to scan tooltable entries. Is scanning possible in O-code or it needs python stuff.
Thanks
Please Log in or Create an account to join the conversation.
- pl7i92
-
- Offline
- Platinum Member
-
Less
More
- Posts: 1875
- Thank you received: 354
24 Sep 2019 13:40 #146068
by pl7i92
Replied by pl7i92 on topic Tool table scanning
hi most postprocessor CAM programms will let you load a External tooltable
so you can put the TXT file to your CAM like Fusion360
you can read the tooltable values of the loaded tool
so you can put the TXT file to your CAM like Fusion360
you can read the tooltable values of the loaded tool
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 23178
- Thank you received: 4862
02 Oct 2019 02:09 #146846
by andypugh
Why not use X and Y? (Tool X and Y are separate from coordinate system X and Y, so as long as you are consistent that might be better)
You can read the offsets of the loaded tool in G-code, #5401-5409 linuxcnc.org/docs/2.7/html/gcode/overview.html#gcode:parameters
Replied by andypugh on topic Tool table scanning
During the tool setup I measure the tooltip X,Z distance from rotational center of the turret
and save values into tool table V and W.
Why not use X and Y? (Tool X and Y are separate from coordinate system X and Y, so as long as you are consistent that might be better)
Before each tool change ( maybe on tool table update ) I want to calculate maximum distance from turret's center ( combining V and W ) of tools loaded in turret. I want to estimate is tool crash into workpiece possible during turret rotation. For that I have to scan tooltable entries. Is scanning possible in O-code or it needs python stuff.
You can read the offsets of the loaded tool in G-code, #5401-5409 linuxcnc.org/docs/2.7/html/gcode/overview.html#gcode:parameters
Please Log in or Create an account to join the conversation.
- pl7i92
-
- Offline
- Platinum Member
-
Less
More
- Posts: 1875
- Thank you received: 354
02 Oct 2019 08:50 #146867
by pl7i92
Replied by pl7i92 on topic Tool table scanning
@_Andreas_ Andy
this is only for the alredy loaded tool
There shoudt be a Component
thatt reads the entirer tootable
and gives back a wanted tool info
so someone can make dicitions on a prepared tool
this is only for the alredy loaded tool
There shoudt be a Component
thatt reads the entirer tootable
and gives back a wanted tool info
so someone can make dicitions on a prepared tool
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 23178
- Thank you received: 4862
03 Oct 2019 05:07 #146949
by andypugh
It isn't that simple in all cases. As G-code can change offsets in parts of the system that components can't see.
Replied by andypugh on topic Tool table scanning
@_Andreas_ Andy
this is only for the alredy loaded tool
There shoudt be a Component
thatt reads the entirer tootable
and gives back a wanted tool info
so someone can make dicitions on a prepared tool
It isn't that simple in all cases. As G-code can change offsets in parts of the system that components can't see.
Please Log in or Create an account to join the conversation.
- kalev
- Offline
- New Member
-
Less
More
- Posts: 4
- Thank you received: 0
03 Oct 2019 06:11 #146955
by kalev
Replied by kalev on topic Tool table scanning
Hello and thank for your replies
I think I found solution. I had to use M6 remapping adding to ini
REMAP=M6 modalgroup=6 prolog=my_change_prolog ngc=m6_my
and adding to stdglue.py ( standard change script ) my_change_prolog function ( see attachment ).
Compare standard change_prolog with my_change_prolog to see changes.
Now I have all needed parameters on O-code level.
Next step I need to write m6_my o-code script to prevent turret crash.
I think I found solution. I had to use M6 remapping adding to ini
REMAP=M6 modalgroup=6 prolog=my_change_prolog ngc=m6_my
and adding to stdglue.py ( standard change script ) my_change_prolog function ( see attachment ).
Compare standard change_prolog with my_change_prolog to see changes.
Now I have all needed parameters on O-code level.
Next step I need to write m6_my o-code script to prevent turret crash.
Please Log in or Create an account to join the conversation.
- pl7i92
-
- Offline
- Platinum Member
-
Less
More
- Posts: 1875
- Thank you received: 354
03 Oct 2019 08:23 #146960
by pl7i92
Replied by pl7i92 on topic Tool table scanning
nice effert to takel this problem
also as it is only nessasary in the tool change it is the best solution
never the less the turret shudt know all tool length
also as it is only nessasary in the tool change it is the best solution
never the less the turret shudt know all tool length
Please Log in or Create an account to join the conversation.
Time to create page: 0.066 seconds