postprocessor DMG 70-5

[jan.van.gent]

Hi,

At our facility we have a Sauer ultrasonic 70-5 5-axis milling centre. It's the same as the DMG 70-5, but it is also capable of ultrasonic milling.

I'm having troubles making a postprocessor. I'm using the NX postbuilder. The Sauer uses heidenhain software.

7230 L Z10. F885. 7240 L X70.626 Y45.813 7250 L X71.495 Y46.039 F983. 7260 L X72.297 Y46.444 7270 L X72.995 Y47.008 7280 L X73.558 Y47.707 7290 L X73.962 Y48.508 7300 L X74.187 Y49.377 7310 L X72.167 Y50.542 7320 L Z13. 7330 L Z65. FMAX 7340 L Z0.0 B0.0 C0.0 7350 L X0.0 Y0.0 7360 M129 7370 L Z0.0 M91 7380 B65.53 C-65.53 7390 L M128 7400 L X46. Y12.798 Z45.03 FMAX M3 7410 L Y28.072 Z29.756 FMAX 7420 L Y36.414 Z21.414 F2654. 7430 L X50. 7440 L X78. F2949. 7450 L Y37.163 Z21.355 B62.054 C-66.959 7460 L Y37.911 Z21.295 B58.613 C-68.351 7470 L Y38.66 Z21.235 B55.206 C-69.71 7480 L Y39.409 Z21.176 B51.827 C-71.039

Above a part of the generated code.

Line 7380 is causing trouble, what can i do about it? Any tips?

[850T3]

That's easy: You are missing the "L"
Try this:
7380 L B65.53 C-65.53

[jan.van.gent]

Hi,

Maybe i should give some more information.

I'm using NX 7.5 software with the NX postbuilder. Its for the DMG 70-evo with heidenhain iTNC530 control.

A part of code:

0130 M129
0140 Z+400.000 B+.000 C+.000 FMAX M91
0150 L M128
0160 L X-22.315 Y+16.071 FMAX M3
0170 L Z+13.000
0180 L Z+3.000 FMAX
0190 L X-22.315 Y+16.071 Z+.000 B+.000 C+.000 F250. M8
0200 L X-15.747 Y+16.071 Z+.000 B+.000 C+.000 F250.
0210 L X+15.747 Y+16.071 Z+.000 B+.000 C+.000 F250.
0220 L X+22.315 Y+16.071 Z+.000 B+.000 C+.000 F250.
0230 L X+22.315 Y+16.071 Z+3.000 B+.000 C+.000 F250.
0240 L Z+13.000 FMAX
0250 L X-25.754 Y+9.643 FMAX
....
9000 L X+49.277 Z-8.815 FMAX
9010 L Z+3.661 FMAX
9020 M129
9030 Z+200.000 B+.000 C+.000 M91
9040 C-172.799
9050 L M128
9060 L X+11.531 Z+3.661 FMAX
9070 L Z-20.392 FMAX
9080 L X+15.490 Y+50.931 Z-24.352 B+.000 C-172.799 F1517.
9090 L X+8.574 Y+50.931 Z-24.352 B+.000 C-172.799 F1685.
9100 L X+.000 Y+50.931 Z-24.352 B+.000 C-172.799 F1685.
9110 L X+.000 Y+50.053 Z-24.352 B+.000 C-172.799 F1685.
9120 L X+8.574 Y+50.053 Z-24.352 B+.000 C-172.799 F1685.
9130 L X+13.079 Y+50.053 Z-24.352 B+.000 C-172.799 F1685.
9140 L X+13.079 Y+50.053 Z-17.352 B+.000 C-172.799 F1685.
9150 L Z-10.352 FMAX
9160 L Z+3.661 FMAX
9170 M129
9180 Z+200.000 C+.000 M91
9190 B+22.140 C-172.123
9200 L M128
9210 L X+53.597 Z+3.661 FMAX
9220 L Z-3.517 FMAX
9230 L X+57.364 Z-17.001 FMAX
9240 L X+54.614 Y+50.053 Z-21.879 B+22.140 C-172.123 F1517.
9250 L X+54.644 Y+50.053 Z-21.871 B+22.170 C-172.112 F1685.
...


You clearly see the problem... Some lines don't have the L in front.
The home position is set up at x+200 y:0 z:0 b:0 c:0 so I guess the problem is with the coming home block.
But when I check this in the post builder:


The L is present so it should generate code with L in front i guess.

When I delete the lines with M91 and the line without L in front (just remove them manualy) the NC code run just fine. But if I make a 5-axis program and post process it, 100+ of these lines are present and it's stupid to delete all those lines manually.

Anone has an idea what to do about this?

[850T3]

Unfortunately I only have my mac available which doesn't run postbuilder NX8. And I already opened my heidenhain post with NX8...
For quick and dirty solutions, just to not be held up with 1 problem to solve another, I would put a text box with "L" in front. I do remember having a similar problem, but I don't remember how I solved it. Well, not with a literal "L".

Maybe there is a relation with the M129, that doesn't have an L in front while the M128 afterwards does have an "L"......
You know, I think it is in the L definition, that is under "WORD", G_motion. I guess it is set to modal. Change it to non modal. Pretty sure that's it.


Are you going to the Siemens NX8 CAM event, 25th januari? Only 's Hertogenbosch, AFAIK.

[jan.van.gent]

850T3, thanks for the suggestion. I'll try this tomorow.

Yes I'm going to the CAM event in the Netherlands.
Maybee I'll bump into you there.

[jelmerra]

there is a couple of options:
* make it text that will work because text is not set to modal
* uncheck the modal button for the L field
* write a script with MOM_force always G_motion in it