YAHOO I got it working!!!!! No more crashes!
I figured out what you meant about re-zeroing the work co-ordinance after a run and yes I was having the same problem. But now it is solved along with my original problem. This controller does NOT like going from work co-ordinance
to Machine co-ordinance and back again!!! To solve the problem I add G90 after every G53 (G28) and to solve your problem at the end of acycle, you need to add one at the end of the code after the final G53.
Here is the test code that came from fusion i'll highlight the lines that I hand edited.
(1001)
(T17 D=19. CR=0. - ZMIN=-15. - FLAT END MILL)
G90 G94 G91.1 G40 G49 G17
G21
(WHEN USING FUSION 360 FOR PERSONAL USE, THE FEEDRATE OF )
(RAPID MOVES IS REDUCED TO MATCH THE FEEDRATE OF CUTTING )
(MOVES, WHICH CAN INCREASE MACHINING TIME. UNRESTRICTED )
(RAPID MOVES ARE AVAILABLE WITH A FUSION 360 SUBSCRIPTION. )
G90 --------------
G53 G0 Z0.
G90 -------------
(TRACE1)
M5
T17 M6
S16000 M3
G54
G0 X10.447 Y12.749
G1 Z5. F2000.
Z-15. F1000.
Y87.749 F2000.
X85.447
Y12.749
X10.447
Z5. F1000.
Z15. F2000.
G53 G0 Z0.
G53 G0 X0. Y0.
G90 ----------
M30
I hand removed the G43 line too
here is a handy video
Editing Post Processors & G-Code with Visual Studio Code
Glen