FieldPoint Advise vi triggers out of range read when exiting application

[lgk]

I recently upgraded a LV v6.1 application to LV v8.20.

After doing so and getting the application to run, I found that upon exiting the application an error was triggered due to the FPLVMgr.dll attempting to read memory that was no longer there.

By the process of elimination, I found that the offending code was the FieldPoint Advise VIs used in two locations in the application.

I replaced the Advise VIs with FieldPoint Read VIs and then added a timer to the loop. So now I have the same functionality, but I think I read in one of the Help files that the timer in the loop is not as efficient as the Advise in the loop.

Is there a fix for the FP Advise VIs?

[Steven_T]

Hello lgk,

The FP Advise vi is performing its own loop as well.  If you look at the Advise, you will notice that it just calls some DLLs inside a loop.  Perhaps these functions that the original VI was calling has changed in the latest version of FieldPoint.  I would recommend trying to put down the new Advise VIs.  They could fix your problem.

I have used the Advise VIs in the latest version of FieldPoint and they seem to work fine.  Let us know what happens.

I hope this helps.

Steven T.