I am at my wits end. The number of hoops I have to jump through to develop RT applications is insane. The number of times I have seen some form of this error is crazy.
Then I'll lose connection to the cRIO so I'll spend another minute waiting for that.
I'm already using a direct usb / ethernet (neither make a difference) connection, with no switches to go through, and the problem persists.
It's every. Single. Time.
I've read the many threads discussing the same issue, and they all suggest the same things:
- Clear compiled cache
- Mass recompile
- Deploy the built application instead.
And yes, they do - rarely - work. But at this point I'm spending hours trying to test single changes. I've attempted to make as much of the code runnable on the host computer for testing, but I'm at a point where I need to test on hardware. I'm using EtherCAT devices so deterministic code is essential.
Then some other suggestions are on the lines of:
- Don't use classes.
- Don't use Networked Variables.
- Don't use the scan engine.
Well that's great and all, but if I'm not going to use any of the advantages LabVIEW gives me, then why use it? I'd still likely have half the deployment errors.
Apologies for the rant, but please, can someone suggest some more material ways I can improve my deployment process.