machine definitions - feed units to post processor

[Rob_Lockwood]

Having multiple machines, that work in different units, i'm frequently annoyed with posting to the wrong units. I use machine definitions, which does a good job of selecting the proper post processor, but post units either matches the file, or has a selection. Is there anything on the roadmap, or can it be put there, to drive/connect the machine definition to the post units, or even a method to force the post units in the post processor itself? Or is this possible? Currently my posts are setup to fail if I post the wrong units, which works well as a failsafe to avoid any damage or issues, but it's still pretty annoying.

[Laurens-3DTechDraw]

Dear Mister Level 72 Machinist,

Have you tried adding the following line as the first line in onOpen(){}

unit = IN;

Or respectively

unit = MM;

Same part with only that change gives these outputs:

INCH:

20 * - Face1
21 TOOL CALL 10 Z S1314
22 TOOL DEF 16
23 L Z+0 R0 FMAX M91
24 M126
25 M3
26 LBL 1
27 CYCL DEF 247 DATUM SETTING ~
  Q339=4 ; DATUM NUMBER
28 LBL 0
29 PLANE RESET TURN FMAX
30 L X+1.7061 Y+1.221 R0 FMAX
31 L Z+0.5906 R0 FMAX
32 M9
33 M17
34 CYCL DEF 32.0 TOLERANCE
35 CYCL DEF 32.1 T+0.0004
36 CYCL DEF 32.2 HSC-MODE:1 TA0.01
37 FN0: Q50=64.65 ; Cutting
38 FN0: Q52=64.65 ; Finish
39 FN0: Q53=64.65 ; Entry
40 FN0: Q54=64.65 ; Exit
41 L Z+0.2126 FMAX
42 L Z+0.2087 FQ53
43 L Y+1.2209 Z+0.2047
44 L X+1.706 Y+1.2207 Z+0.2008
45 L Y+1.2205 Z+0.1969
46 L X+1.7059 Y+1.2203 Z+0.1929
47 L X+1.7057 Y+1.22 Z+0.189

MM:

20 * - Face1
21 TOOL CALL 10 Z S1314
22 TOOL DEF 16
23 L Z+0 R0 FMAX M91
24 M126
25 M3
26 LBL 1
27 CYCL DEF 247 DATUM SETTING ~
  Q339=4 ; DATUM NUMBER
28 LBL 0
29 PLANE RESET TURN FMAX
30 L X+43.3356 Y+31.0136 R0 FMAX
31 L Z+15 R0 FMAX
32 M9
33 M17
34 CYCL DEF 32.0 TOLERANCE
35 CYCL DEF 32.1 T+0.01
36 CYCL DEF 32.2 HSC-MODE:1 TA0.01
37 FN0: Q50=1642.07 ; Cutting
38 FN0: Q52=1642.07 ; Finish
39 FN0: Q53=1642.07 ; Entry
40 FN0: Q54=1642.07 ; Exit
41 L Z+5.4 FMAX
42 L X+43.3353 Y+31.0128 Z+5.3 FQ53
43 L X+43.3345 Y+31.0106 Z+5.2001
44 L X+43.3332 Y+31.0068 Z+5.1002
45 L X+43.3313 Y+31.0016 Z+5.0004
46 L X+43.3288 Y+30.9949 Z+4.9007
47 L X+43.3259 Y+30.9867 Z+4.8011

The only setback to this is that that it doesn't yet load your formats in that unit. (So as you see less decimals in the examples)

If you want those to be correct as well you need a to add the 

unit = IN;

Also in the Collected State. 

[Rob_Lockwood]

@Laurens-3DTechDraw nope - I pestered one of them autodesk employees not too long ago, and was told there wasn't a good solution, and I didn't see any reason to not believe him 🙂

I'll take a look and see if that has any ill effects, or if it solves the issue. Thanks.

[Laurens-3DTechDraw]

@Rob_Lockwood

Pfff, Autodesk employee's like they are the smart one's here.

Pretty sure we did something like that to Brad from TacticalKeyChains RoboDrill post: https://forums.autodesk.com/t5/hsm-post-processor-forum/post-process-unit-default/m-p/6089156/highli...

Next time I talk to Achim I'll ask him. He's probably seen/done this before.

But doing some checks is not all that hard of course since you can just post out in the correct unit without the edits to the post.

And then do the changes, set the post window to the wrong unit and see if there are differences in the output.

If not, party hardy all night long, if yes cry, stamp & call for mama.