My LV program can't find the iak file when the program is loaded from a different PC.

[wd8ivl]

Hello all,

My LV vi with Fieldpoint I/O and it's IAK file are stored on the company network.  If I load and run the LV vi from the PC it was developed on, everything is fine.  If I load and run on a different PC (that has an identical install of LV), the LV vi can't find the IAK file (all of the I/O pointers to the file are grayed out.) 

Also, if I make an EXE out of the vi on the machine that can find the IAK, it won't find it if it's run from the other machine.

It is not related to whether one machine has different "rights", as they are identical.  It's not related to different installs of LV, as they are identical.   

I have found that this is related to the network login name/password, and to the machine's network name.  If I login on the second machine and try to run the program, it won't find the IAK.  If I point it to the IAK it will run.  If I save it and log out, and then login as a different user with the same rights on the second machine, it won't find the IAK again, until I re-point it there when I re-run it.  This is true for both the vi and the EXE.

This problem makes deploying the EXE difficult to different machines, as the first time it's run, the EXE has to be pointed to the IAK.  Pointing the EXE to the IAK is difficult as these installations have no keyboard or mouse.

Does anyone have any ideas on how to fix this so the LV vi or it's EXE finds the IAK from no matter where it's loaded from?

Thanks,

Mike

[Laura F.]

Hello Mike,

Unfortunately, from what I can find I do not know that there is an easy solution to this problem you are seeing.  Please take a look at this KnowledgeBase.  The only other solution I can think of would be to save the iak file locally to the same directory on each computer. 

Regards,

Laura

[wd8ivl]

Laura,

Thank you for the responce.

Putting the IAK locally is not an option.  The programs and support files (IAKs, DLLs, etc) have to be up on the network where they can be used by multiple PC's knowing that each PC is running the same version, and they are backed-up regularly. 

After further investigation, from what I have found is that for the Vi to find the IAK file the first time the Vi loads, the person logging into the PC has to have local Admin rights (at least for Win2K) on the PC.

This is possibly somthing that should be addressed by the LV folks - if the person logging in has rights to open the Vi, then that Vi should be able to open all of it's support files with those rights.

Mike   

[Laura F.]

Hello Mike,

The best way to bring attention to issues such as this is to submit feedback at ni.com/contact.  We value all feedback we receive on our products and strive to make them even more useful for our customers with each release.

Regards,

Laura 

[wd8ivl]

Laura,

I figured I'd continue this thread because it's along he same line..

I have two Fieldpoint systems. They are identical, except for one thing...one has an AI-110 in position 7...the other has nothing. Both have the same IP address, etc and I swap the ethernet cable between them when I want to select which one I use.  I use a dedicated ethernet card to the FP processor...and it's not the company net.

There are two IAK files...one for the system with the AI-110, one for the system without the AI-110. The two IAKs are in different paths.

Before I had the system and the IAK without the AI-110, I made an EXE of the code that woked with the AI-110, and it worked fine.

But now if I run the EXE after I've used MAX and opened the IAK without the AI-110, the EXE won't read the AI-110!  I have to go back into MAX and open the IAK that has the AI-110 in it, close MAX and restart the EXE for the EXE to see the AI-110.  (Max is NOT SET to "Download Items on Save")

I looks like the EXE is looking at MAX to get the IAK or a pointer to the IAK.

Did I build my EXE incorrectly?  Shouldn't an EXE completely ignore MAX once it's made?

Thanks,

Mike

[Thaison_V]

Hi Mike,

If you are embedding your executable file onto your FieldPoint controller, it should have all the configuration information it needs on the controller itself.  Are you using one of the real-time FieldPoint controllers (FP-2XXX series?) or the Network controller (FP-1600)?  The FP-1600 will still need to reference an IAK file even if you create an executable since it doesn't actually store any information on the controller itself.  In the VI executable for a FP-1600, you can explicitly point to the IAK file you want to use as well.  That way it does not need to reference MAX for this information.  If you could divulge some more details about what controller, and what version of software you are using to create the executable, I'll try to give you more specific suggestions.  Thanks!

Thaison V

[wd8ivl]

Thaison,

Thanks for the reply.

I am using a FP-2010, but using it as a FP-1600, with the EXE on the PC and not in the FP processor.

I understand that the EXE still needs the IAK file. 

And now that I've looked at it, I think I see the problem...I built my VI with Polymorphic VIs, and defined the FieldPoint IO Point I/O with constants...what I think I should have done is used an FP Open and then created tags for each of my IO Points, as the open will point back to the IAK directly.

Always learning....

Mike