Fusion 360 / Tormach Post Processor Work Offset

[sidetrak06]

Has anyone else been bothered that the Fusion 360 post processor for Tormach always outputs G54 as the work offset in the first line of code after the tooling comments regardless of the work offset selected in the Setup.

(A - 3x10 Back)
(T10 D=3.15 CR=0. TAPER=45deg - ZMIN=0.735 - face mill)
(T50 D=0.375 CR=0.005 - ZMIN=0.11 - bullnose end mill)
(T71 D=0.375 CR=0.1875 - ZMIN=0.3594 - ball end mill)
(T72 D=0.3125 CR=0.1563 - ZMIN=0.555 - ball end mill)
(T100 D=0.375 CR=0. TAPER=45deg - ZMIN=0.69 - chamfer mill)
(T160 D=0.266 CR=0. TAPER=135deg - ZMIN=0.01 - drill)
G90 G54 G64 G50 G17 G40 G80 G94 G91.1 G49
G20 (Inch)

If you put the correct work offset in the Fusion 360 Setup it will write that into the G-Code at each tool path as seen below:

N10(Face3)
T10 G43 H10 M6
(Shell Mill 45 deg x 3.15)
S2500 M3 M8
G59.1

There isn't a problem with running this G-Code file but I find myself manually typing over the G54 at the beginning with the correct offset so that it doesn't confuse my CNC operator. I often write programs that he runs and he always checks the beginning of the program to know which tools and offset is to be used. He then zeros his work piece based on the offset listed which is defaulted to G54 unless I change it manually.

I am guessing I could modify the post processor but this just seems like a bug that should be fixed on a higher level. Is anyone else annoyed by this?

Thanks,
Ben

Similar Threads:

• Can Fusion 360 do full 4th axis work on Tormach?
• Fusion 360 Post Processor
• fusion 360 post processor
• Fusion 360 Post Processor for Tormach PCNC1100
• Tormach Post and Fusion 360

[syscore]

Removing the default work offset (or changing it to something else) is easy enough, it is in the following line (the gFormat.format(54) call) ...

writeBlock(gAbsIncModal.format(90), gFormat.format(54), gFormat.format(64), gFormat.format(50), gPlaneModal.format(17), gFormat.format(40), gFormat.format(80), gFeedModeModal.format(94), gFormat.format(91.1), gFormat.format(49));

That line is in the onOpen() bock.


Making it output the correct work offset will be a little more tricky. You will have to get the first section (containing the first work offset) and then convert it to gcode. This is how it is done in the onSection() block ...

var workOffset = currentSection.workOffset;
if (workOffset == 0) {
warningOnce(localize("Work offset has not been specified. Using G54 as WCS."), WARNING_WORK_OFFSET);
workOffset = 1;
}
if (workOffset > 0) {
if (workOffset > 6) {
var p = workOffset; // 1->... // G59 P1 is the same as G54 and so on
if (p > 9) {
error(localize("Work offset out of range."));
} else {
if (workOffset != currentWorkOffset) {
p = 59 + ((p - 6)/10.0);
writeBlock(gFormat.format(p)); // G59.x
currentWorkOffset = workOffset;
}
}
} else {
if (workOffset != currentWorkOffset) {
writeBlock(gFormat.format(53 + workOffset)); // G54->G59
currentWorkOffset = workOffset;
}
}
}


But you probably only need to do something like the following (right before that long line) ...

var firstSection = getSection(0);
var firstWorkOffset = firstSection.workOffset;

and then (in that long line) replace gFormat.format(54) with gFormat.format(59 + firstWorkOffset / 10.0);

[mountaindew]

The post for Sprutcam does the same thing and does make me look twice at times. When running multisided part code, I never use g54 as first offset because of a pp bug I run into years ago. I developed a habit of looking at the code lines just before first op when locating the first offset used in that program.

[syscore]

Btw, there is an option (under properties when you post) that says "Force Work Offset" which will output the work offset before each section, regardless of whether it is needed or not. That will not remove the default G54, but if you alter the post to remove the G54, it will force a work offset block at the beginning of each section, even if it is G54.

[sidetrak06]

I am hesitant to modify the post processor because then I have to manually check for updates and make this revision every time. Does anyone know if Tormach provides the post processor for Fusion 360 to implement or if it is derived directly from Fusion 360? I am going to submit a feature revision but I want to submit to the correct people.

Thanks!

[syscore]

https://forums.autodesk.com/t5/hsm-p...forum/bd-p/218

You might also want to mention it to Tormach (maybe they have some pull) but the post processor is maintained by Autodesk.

[sidetrak06]

Done and done, now we wait...

[daniellyall]

you could add a switch to it so you can just turn it off then after a few people have tested it and the HSM guys no about this thread they may just add it in.

[sidetrak06]

Not sure what you mean, can you elaborate please?

you could add a switch to it so you can just turn it off then after a few people have tested it and the HSM guys no about this thread they may just add it in.

[daniellyall]

you could just remove that if you don't wont it there theirs nothing in the manual to say it needs to be there