I am using version 7 of CC and exporting g-code for use on a OneFinity Elite with Masso G3 controller.
I have it setup so it asks me to change/confirm the first bit, and then on the change M6. That all works. However, I notice on the Masso that the message asks me to add a different bit number than what the G-Code has listed. For example, in attached photo the code has a M6T1 so I am expected the message to say to load tool 1. However as you can see, it asks for Tool number 2.
After some experimentation with four bits, I found that if G-Code loads bits 1, 3, 8, 7 in that order, the messages tell me to load bits 7, 8, 3, and then 1. So these are reversed. Anyone have any ideas why this might be?
I wonder if it’s actually expecting the tool change to be T1M6, instead of M6T1. That would cause it to be looking for the prior tool at each tool change.
Can you try flipping that in the G-code to confirm?
On a two tool gcode file I flipped it to T1M6 format and it appeared to work. I will test tomorrow on a file with a few more changes to confirm. Curious if there is a way for CC to export it in this order from the start?
If I understand correctly, changing line #203 from:
writeBlock("M6", state.tval.format(tnum));
to:
writeBlock(state.tval.format(tnum), "M6");
will do what is wanted (but I haven’t yet had occasion to program in Javascript beyond an initial/aborted experimentation in tplang and Maker.js, and beginning to read a book on it and some ECMAscript/js programming in Flash and Adobe InDesign).
