Why my custom device break only when VeriStand trying to run it?

Hello

I have a custom device, he worked for some time now, today, I made a few changes to add some features more and now VeriStand tells me the RT pilot is more executable.

I have not change my build configuration or add any functionas that could bring in an external DLL, or something that could link incorrectly.

Any ideas of how I could go on this shrinking.  The problem is that when running in VeriStand.  Built LLB has no problem, the source of the development has no problem, it's only when VeriStand tries to deploy there is a problem, so there must be something that is not bound correctly Yes?

The system isn't RT, it's just deploy on Windows using a SMU.

I am not sure the exact cause, but I ended up simply remove parts of the code piece by piece pilot to refine what was causing the problem. It turned to be a VI of debugging I used several times before in various projects, but which contains the string "call" LabVIEW primitive, but set apart from that, it's just a simple string manipulation.  So I don't know if it was just a few cases of random edge that occurred when running under code basic LabVIEW VeriStand clean, but for some reason, he broke the driver VI.

So, solved the problem, but the cause, I can't really say.

Tags: NI Products

Similar Questions

Maybe you are looking for