Is there a VI that will download the configuration to the Fieldpoint controller, so we don't have to use MAX?

[wd8ivl]

I recently upgraded to Fieldpoint 5.0 so that I can use cFP-2020s. 

What I now notice is that if I build an EXE for a FP-2010, I can't talk to it...I've included the proper FPLMVgr.dll in the data folder of the EXE, but it still doesn't communicate.

If I put the older version of FPLMVgr.dll (from MAX3.02), it works. 

So I'm guessing the problem is because the controllers configuration file was saved to it with MAX 3.02, and the MAX 4.0 FPLMVgr.dll won't talk to it.

So, if I could include a vi in my EXE that would take the configuration file (the IAK file) that MAX saves to the controller, then the controller's configuration would always match the proper version of FPLMVgr.dll. 

Mike

[Charlie S.]

Hello Mike,

I'd like to help out, but I think I might be having some trouble understanding your issue here. What do you mean by "it doesn't communicate?" Are you attempting to target it from LabVIEW directly or do you have a separate host VI that communicates through TCP/IP or Shared Variables? You said you upgraded to FieldPoint 5.0 on your development machine -- did you also update the driver on the real-time (RT) cFP-2020 controller? The host and target drivers have to match. That could explain why the older version of the FPLVMgr.dll works, while the new one does not.

Also, is there a reason you need to avoid MAX? You will have to use it to update the driver on the RT target. What version of LabVIEW are you using? When you build and deploy the .exe it should download the data folder with the correct FPLVMgr.dll for you.

I apologize for all the questions -- let me know what you have and we can proceed from there!

[wd8ivl]

Charlie,

Sorry I didn't respond sooner - I was on vacation...

First, I'm using LV7.0 on machines running Win2K.  I had to upgrade from MAX 3.0.2 (?) to Max 4.0 to get the proper Fieldpoint drivers (FP5.0) that would let me use a cFP-2020 in my latest project.

The company has standardized on using FP2010 & cFP2020 controlers here, even though my projects don't run the FP code in the processor in RT...it's run on as an EXE on a locally connected PC.     

For one of my previous projects, (before the upgrade to MAX 4.0 with FP 5.0 drivers), I built an EXE for use as above & it works fine.  Since the upgrade to MAX 4.0 with FP5.0 drivers, if I build an EXE from the same sourcecode, the EXE will not communicate with the Fieldpoint I/O.  If I go back to the old EXE, it works fine.  All I can think of is that the Item Names were downloaded to the FP-2010 with the previous version of MAX.  (in MAX, Tools->Fieldpoint->Download Item Names on Save).

The locally connected PC's that are connected to the Fieldpoint systems are also connected to the plantwide network via a seperate NIC.  I store the EXEs they run on the plant server.  I program the LV code & build the EXEs on my desk.  To do a  "Tools->Fieldpoint->Download Item Names on Save" I'd have to be at the PC on the shop floor, since MAX on my desktop won't "see through" the PC that's locally connected to the FP installation to the FP processor.

So, if I could add something to my LV code that would do a "Download Item Names on Save" when the EXE was run, it would save trips to the shop, as well as assuring that everything was running with compatable versions. 

Another thing that would help is if there was something I could put in my code that would commision a new FP controller...that way if one failed, our Mainetnance department could put in a fresh one,  start the EXE, and not have to call me.

Thanks,

Mike

[bburress]

Hey Mike,
        Have you downloaded the new Fieldpoint drivers to the controllers by using MAX?  The IAK file is created by MAX, so you should be able to import the saved iak file into MAX and run your code using it.  If not, then you should be able to find devices again to create a new iak file, then use that one for your EXE to reference.  The iak file stored on the controller itself only matters if you are running the EXE embedded on the controller.  If you are running the EXE on a PC, the only iak file that matters is the one saved on that PC.