Datron Neo not Posting

[infoQHYQM]

I've had to very recently change some of our programs that, over the last year, were running fine on a Datron Neo2.

I've been unable to post anything that runs.  I've modified old programs to test.  I've made new models (very simple programs to test machine alignment with 2 OP/side-to-side of a plate) on a vacuum chuck.

The Neo doesn't output a simulation when I load the file.  It fails on the WCS call line if I try to run the programs anyway.

I've uninstalled and reinstalled Fusion360 4 times in the past few days.  I've checked the post processor each time, to be sure it's the most up to date version (including today's most recent release #43695 3/15/22)  I've checked the post settings (that the WCS matches the program output), and traced the post processor call location, to try and verify that it's not calling some out of date version somewhere on my computer.

Anyone else having this issue, or have a direction for me to attempt?  I'm currently at a loss as to what else to check.

[engineguy]

@infoQHYQM 

Hmmm, it may well be your Post Processor, it is possible thet the PP that you used in the past had been edited for some reason then what can happen during Fusion Updates and/or if you have the Automatic Post and Machines updates enabled in your preferences then the PP will be overwritten with the new updates but any edits will be lost.

Not always best to have the latest PP 😞 😞

[AchimN]

What is the error message you get on the machine?

This is the line which calls the WCS, we never changed the syntax for that:
LoadWcs name="NUMBER"
Did you try to remove that line from the nc file? Does simulation then work?

[infoQHYQM]

Thank you for the replies!  If it's not already obvious, I'm very much an amateur in the machining space, so changing the code directly is something I've not had any exposure to/need to do.  I'm sure my attempts are just incorrect in the syntax somehow.  To be fair, I have done some searching around on my own to try and figure it out, as well as chatting with Datron.  While they're very helpful, it appears to be a change in Fusion that's causing the difference though, so I thought to post here as well.

The error is:

SimPL runtime error

Cause of fault: Invalid value for an argument

Then lists the program calls that cause the error, which are lines that call the WCS.

I did not try to simply remove the line.. I did try re-assigning it in various ways, but wasn't able to get it to work correctly (all after posting) without directly exchanging the "1" with "last measured WCS".  That did work.  Our WCS is/has been "last measured WCS" which Fusion doesn't allow (in stock/operation setup; and hand editing that in for every call on every posted program will take too much time.)

I did try assigning a variable WCS 1 to last measured in the program, as well as setting up WCS 1 on the machine directly, to be equal to the function of last measured, but it doesn't update every time we measure a new plate, it only substitutes the current values then remains static.  We'd like it to remain dynamic, as there are tolerances in the stock we receive, so they vary a bit.

I'll try removing it altogether on a very simple program, thank you.  However, editing every call manually (hundreds and hundreds per program) will be onerous which ultimately will leave me with the same issue.  I suppose there is probably a way to replace each one automatically, but I am uncertain how to do that.

I suppose I can also do as @engineguy suggests (thanks for your reply as well), and go back to an earlier Post, but with live software, I imagine this may become an issue in the future anyway, so I'd rather fix our process to future-proof it a bit.  And, it's an opportunity for me to learn more about this fascinating process.

[AchimN]

I did double check this now, there were no changes made to the syntax of the WCS output in the program.
There was an update recently for WCS definitions, but that also did not change the syntax of the output.

Could you please share such a program which errors out on your machine?
I´ll then chat with Datron to find out what the issue is.

[infoQHYQM · Accepted solution]

Thanks for your offer to assist.

Today, we figured out if we delete the machine assignment within each OP's CAM in the "Setups" tree, we could then assign WCS 0 in the setups, which then forces the machine to go with the last known configuration.  Posting those out works as it used to; not sure if it was a change in Fusion then, or if I bumbled my program changes (probably the latter, right?  pebcak)

If there was a machine selected in the setups, it would force a non-zero numeral for WCS, wherein on the machine itself we had no numeral assigned WCS, creating the error.

[boopathi.sivakumar]

Hi @infoQHYQM 

Yes you where right! without the machine config you would able to post the code with zero offset. It seems like while updating to the new wcs definition it doesn't take care for the zero offset.
Sorry for the inconvenience caused I have made a ticket to resolve that  issue.
Time being to resolve that edit the post and find for the 

// wcs defintion  and change the definition as shown below

wcsDefinitions = {
  useZeroOffset: true,
  wcs          : [
    {name:"Zero Offset", format:"", range:[0, 0]},
    {name:"Standard", format:"LoadWcs name=\"#\"", range:[1, 999]}
  ]
};

Now if you load that post with machine config it will allow you to specify the Zero Offset.

[AchimN · Accepted solution]

This makes sense then now, using WCS 0 was not possible anymore.

The issue is fixed already and the updated post processor is already available online.
https://cam.autodesk.com/hsmposts?p=datron_next

Now when a machine is selected in Fusion you can choose "Zero offset":