Old FP-1000 app developed with LabVIEW 5.1.1, not running correctly since updating to MAX 4.5/FP6.0.2

[DavidBoyd]

I have an old application built under LabVIEW 5.1.1 which opens an .iak file (the file path is embedded in the app) and reads/writes to modules attached to an FP-1000.  Recently I was forced to move the setup onto a new PC and now I'm unable to get the app to communicate with the FP hardware.  The new PC has recent drivers installed (MAX 4.5, FP drivers 6.0.2).  From MAX, I can open the .iak file and communicate with the FP hardware, so I'm unsure of where the problem lies.  Are there version limitations with such old LabVIEW code and new FieldPoint drivers?  Sorry, I haven't visited this setup for  a long time (nor did I create it originally), so I'm a bit rusty on FieldPoint setups.  Any guidance would be much appreciated - I'm trying to avoid having to redevelop the app.

Thanks,

Dave

[DavidBoyd]

(Replying to my own message since I can't seem to edit it)

Does the version of FPLVMgr.dll used by the application need to match the FP driver release, or the application LV version?  The app is still referencing a copy of FPLVMgr which Windows identifies as 3.0.something;  on my own PC (which also has FP 6.0.2 support installed), the version of the .dll (found under Program Files\National Instruments\LabVIEW 8.5\vi.lib\FieldPoint\SubVIs, and also under LabVIEW 8.6) is 6.0.0.

Anyone?

Dave

[Bakk_Diagram]

Hi David,  LabVIEW 5.1 is no longer supported, so we do not test to see whether the latest versions of MAX and drivers work with it.  Do you have LabVIEW version 8.2 or lower?  You can use any of those programs to upconvert your LabVIEW VI to a newer version.  LabVIEW 8.5 and higher can only open and upconvert VI's that are already version 7 or higher.  If you have multiple versions LabVIEW you can daisy chain convert to the latest version.

[DavidBoyd]

Thanks, Chris, for replying.

I have every version of LabVIEW from 5.0 through 2009 beta available, though not presently installed.  I was trying to avoid having to bring this app back into the development environment.

Since I posted last, I experimented and fixed the issue.  I took a current copy of FPLVMgr.dll (version 6.0.0) and dropped it into the support directory for the app, replacing the old (3.0.0) DLL which was there.  So, the answer to my question seems to be, an old LV executable can use a new FP DLL, and apparently must do so if the MAX/FP driver installation is updated.

Hope this info is useful to others.

Dave