CFP Channel browsing gives problem in exe

[I_I]

We have configuration screen in which user can assign CFP channels for specific data acquisition. For browse purpose we are using "FieldPoint IO Point" control.

In VI everything works fine. But if I create Exe, if I select "bwowse" option then brows window doesn't pop up.

We found it is searching for "rtd_getdevice.vi".

If anybody knows solution ,please let me know.

[Hillary_C_E]

Hello Iqbal,

This is a known issue (#41273). This has been fixed for a future version of the FieldPoint drivers. In the meantime, the preferred workaround is below.

event_ctrls.llb is found in this folder: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib

- Make a copy of the <vi.lib>\eventctls.llb\eventvkey.ctl and rename it to rtd_eventvkey.ctl, place the renamed copy into the fplvmgr.rsc LLB
- Close LabVIEW
- Move (don't copy) event_ctls.llb to your desktop so LabVIEW won't be able to find it
- launch LV and open the rtd_getdevice.vi
- you will get a dialog saying it can't find event_ctls.llb - point it to your renamed copy of the ctl
- save the rtd_getdevice.vi

The line "showSystemVIs =True" must be added to the LabVIEW.ini, otherwise LV will not prompt that eventvkey.ctl could not be found.

[Englund]

This solution doesn't work for me.
When I open LV it searches for the "eventvkey.ctl" and I can't point it to the "FPLVMgr.rsc" because otherwise I get an error

LabVIEW: Resource not found
An error occured loading VI 'FPLVMgr.rsc'.
LabVIEW load error code 8: Could not load VI resource

If i rename it to "FPLVMgr.rsc.llb" it will work, but that's not really the same?

Well if I choose ignore the loading of the file. LabVIEW will hang when trying to open any VI the LV will hang and not respond to anything but a shutdown via taskmanager.

I really need the FieldPoint browse function and all projects at the organization relys on the program to work.

[Hillary_C_E]

Hi Englund,

Can you provide me with more details on what you are doing? Are you creating an executable or simply opening a VI that has the FieldPoint I/O Point?

If you are using an executable, what error do you receive when you run your executable? What behavior are you seeing?

If you're just using a VI, what behavior do you see? What version of LabVIEW and the FieldPoint drivers do you have installed? You can check in Measurement and Automation Explorer under My Computer » Software.

[Englund]

I hope you will get what I'm trying to explain.

• I have build my application based on configuration files (ini files) which include the Fieldpoint address.
• Now when I launch the application it works as it should, but no signals from or to the Fieldpoint devices are working
• I want to check/change the fieldpoint devices (I've made a page where I can change the ini files), but I get an error which complains about that some component doesn't exist and should be reinstalled.
  
• If I try an old version of the program which uses RunTime Engine 8.2 i will get an error about a shared Fieldpoint rsc fil

I'm sure the problem is the same that you described above. If the problem isn't described accurately I will write more later, because I'm not on the LV computer at the moment.

[Englund]

The error appears when I press the browse button on the Fieldpoint browse tool in the executable mode.

[Hillary_C_E]

Hi Englund,

Can you provide the exact text or a screenshot of the error you are receiving about missing components?

So, I'm assuming you are using LabVIEW 8.5. Have you installed the FieldPoint drivers on your computer that you are running the executable on?

[Joseph_Loo]

Did you use MAX to configure the fieldpoint devices on your target machine? If so how does the names compare with your development version?

[Englund]

The FP file is a copy of what i have on my computer. I also have used the "network" version of the file. The problem occurs when pressing the Browse button and works fine as long as it's not an executable.

[Englund]

The newest FP drivers 6.0.1 and LV 8.5 and along it installed 8.2

The VI and whole program works when using them in VI mode. It's only the application mode that's not working. Browse function is also working. I suspect that the current RTe for FP's are somehow in a buggy state....