M61 Qn Remap loaded tool mixup
31 Dec 2020 11:16 #193627
by MaHa
M61 Qn Remap loaded tool mixup was created by MaHa
Having manual toolchange, for my safety and tools like a probe, it is compulsory the spindle is always set to ´S0 M5´ for toolchange. I enter this in the ´change.ngc´ and ´settool.ngc´. I have remaped M6 anyway and now M61 also.
But with M61, the Tool changed in, is the order number in tooltable. Maybe T6 is at line 2, an T44 at line 6, M61 Q6 loads T44, same M61 Q2 loads T6.
I have found a virtualmachine in my backups with 2.7.15 installed, and there the Remap of M61 is working. It seems in Version 2.81 something changed.
I have checked the stdglue.py used, and until the line in epilog with emccanon.... i printed tool and pocket parameter, they are correct.
But with M61, the Tool changed in, is the order number in tooltable. Maybe T6 is at line 2, an T44 at line 6, M61 Q6 loads T44, same M61 Q2 loads T6.
I have found a virtualmachine in my backups with 2.7.15 installed, and there the Remap of M61 is working. It seems in Version 2.81 something changed.
I have checked the stdglue.py used, and until the line in epilog with emccanon.... i printed tool and pocket parameter, they are correct.
Attachments:
Please Log in or Create an account to join the conversation.
31 Dec 2020 13:19 #193647
by cmorley
Replied by cmorley on topic M61 Qn Remap loaded tool mixup
Are you saying something changed from 2.8 to 2.8.1 or from 2.7.15 to 2.8?
Please Log in or Create an account to join the conversation.
31 Dec 2020 13:29 #193648
by MaHa
Replied by MaHa on topic M61 Qn Remap loaded tool mixup
In 2.7.15 it works as expected. My machine is updated to 2.81, the error occurs. On a laptop for simulation with Mint19.3 and Ver.2.8 the error occurs also.
Please Log in or Create an account to join the conversation.
31 Dec 2020 13:42 #193649
by cmorley
Replied by cmorley on topic M61 Qn Remap loaded tool mixup
yes there was work on tool changing.
if you using git:
git commit hash# 278a980 and around that seems to be the big change.
Chris
if you using git:
git commit hash# 278a980 and around that seems to be the big change.
Chris
The following user(s) said Thank You: MaHa
Please Log in or Create an account to join the conversation.
Time to create page: 0.074 seconds