After going through troubleshooting and problem solving I am confident the issues we discussed in this thread
https://forums.autodesk.com/t5/fusion-manufacture/issues-with-heidenhain-manualplus-post-processor-a...
Should be considered bugs in the post processor. Or if the way it is now works for some Heidenhain machines perhaps it needs to be branched to create a version that works for our Glidemeister manual plus machine.
I will attach a post as generated by version 44057 and an edited post with the edits I had to make just to get the machine to run them. Also recognizing I have also had to disable canned cycles to get an output our machine would run.
I also have made changes to the post processor to get it to work with our machine. The most obvious you will see is it duplicates tool callouts. This is required on our machine but I believe this is a problem with our machine we haven't yet been able to diagnose or resolve. This issue isn't just with Gcode. If we are using the user interface and call a tool it makes a clicking noise but doesn't do the toolchange. The interface does however show it has moved to the current tool.
Likely not necessary to the discussion of post processor I will explain the process in the UI here.
If tool 3308 is loaded and I want to change to tool 101 I have to enter any other valid tool position so say 202, it will click, and the UI will show tool 202 but the turret is still in tool 8 position. Then I can enter 101 and it will properly do the toolchange and move to turret position 1 and display tool 101 on the UI.
If anyone has any ideas on this let me know.
In Gcode having one TXXX callout will do the same thing. It will click and display the new tool number has been loaded but the turret has not actually moved. However having
TXXX
TXXX
Will then load the correct tool.
I don't remember all other edits but you can compare. I think one other was changing the precision of some units which were causing an issue with the default setting so in a previous thread I was told to change post processor settings to change that precision and it worked.
Regarding the unedited and edited post it is probably easiest to just load them in compare mode, then just reference the following explanation if you need more info on why I changed what I did. I don't know if all my changes were right, best, or necessary to do in the way I did but they did result in being able to run the program successfully.
1001 is the unedited post. 1001-edited is the manually edited version that would run correctly on our machine.
heidenhain turning-05-13-2024 is the post processor I am using with edits I have made.
https://www.facebook.com/groups/1229995573786339/
Fusion
