LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why doesn't the advanced fieldpoint vi's/functions subpalette appear

I cannot get the fieldpoint Advanced VI's and Functions subpalette (FP Advise etc..) does not show up in the fieldpoint functions palette using Labview 8.5.
0 Kudos
Message 1 of 11
(4,242 Views)

I notice this is an old post....but there are no replies. 

 

I can't find this subpaltte either.   

 

Bueler?  Bueluer?

---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 2 of 11
(3,920 Views)
The location in my palette (LV2009sp1)
Message 3 of 11
(3,915 Views)

Thanks for the reply,

 

Using 8.6.1 here at the moment.  Here's my shot of the same palette. 

 

I looked all over for it and still don't see it.  However, I know they are...somewhere.  I can find all of the VIs on the disk here:  C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\FieldPoint   I just don't see the subpalette. 

 

I fired up my Virtual Machine where I have LV 2009 installed, and sure enough it was there.  

 

 

...at least I know where to find the VIs.  

 

 

 

 

Message Edited by pallen on 02-22-2010 12:17 PM
---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 4 of 11
(3,904 Views)

Patrick,

 

If you bring up Quick Drop (Ctrl + Spacebar) and search for a specific VI in the Advanced palette do you get a hit?

 

It sounds like this file exists on your system (replace 2009 for 8.x):

C:\Program Files\National Instruments\LabVIEW 2009\menus\Categories\Measurement\fieldpoint.mnu

 

What you may be missing is this folder:

C:\Program Files\National Instruments\LabVIEW 2009\menus\Categories\Measurement\_FIELDPOINT

 

I attached the contents of my folder, try saving this in the above location. A repair or upgrade of the NI-FieldPoint driver should also fix this.

Message Edited by pflores on 02-23-2010 06:58 PM
---

Peter Flores
Applications Engineer
Message 5 of 11
(3,881 Views)

Hi Peter,

 

Thanks for your reply and your attachment. 

 

The VIs were not showing up in the Quick Drop menu either.  

 

However, when I replaced the contents of my _Fieldpoint folder with files in your attachment the Advanced menu was added to my palette.  The VIs are also now showing up in the Quick Drop menu as well.  

 

Thanks again. 

 

*edit*  I tried to mark your post as the solution to this problem.  I'm not the original poster though, so this is probably why I'm not presented with this option.

Message Edited by pallen on 02-24-2010 10:21 AM
---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 6 of 11
(3,867 Views)

Thread revival.  Having a similar issue.  Have tried the above _FIELDPOINT contents, but no luck.  Have also uninstalled the FieldPoint (6.1) drivers and re-installed (first having tried a repair of the drivers).  I'm running LabView 8.6.

 

Thanks.

0 Kudos
Message 7 of 11
(3,182 Views)

Hello,

 

You are most likely unable to view the FieldPoint palette because the FiledPoint 6.1 Driver is not supported with LabVIEW 8.6.  The latest FP driver supported back to 8.6 is FieldPoint 6.0.10.  For more information on the different drivers check out the FieldPoint Readme.

 

Regards,

M. Whitaker
ni.com/support
0 Kudos
Message 8 of 11
(3,159 Views)

Hello M. Whitaker,

 

Please take a look back at this thread http://forums.ni.com/t5/FieldPoint-Family/FieldPoint-IO-Point-In-via-control-rather-than-constant/m-... where jdpeters originally posted.

 

What you are saying seems to conflict with the information in Software Installation Compatibility for FieldPoint Real-Time Controllers.  It says that 8.6 uses fieldpoint drivers 6.0.3+.

 

To me, the plus means that driver and higher  (i.e. later).  If 8.6 doesn't work with drivers 6.1, then that document needs to be updated to reflect that.

0 Kudos
Message 9 of 11
(3,155 Views)

I concur with RavensFan.  The driver compatibility document, as written, implies that 6.1 is acceptable.  I'll try 6.0.10.  If that works, I'll be quite disappointed in the fact that the NI document caused quite a bit of delay in resolving this issue.

0 Kudos
Message 10 of 11
(3,151 Views)