06-06-2007
02:40 PM
- last edited on
05-22-2025
03:25 PM
by
Content Cleaner
Hi scott_1970,
Like I said before, locating anything before FieldPoint 2.0 will be very difficult. Not many changes were made to the FieldPoint driver until version 4.0, so I think we may want to try to stick with FieldPoint Explorer 3.0.2.
Have you tried reinstalling FieldPoint Explorer 3.0.2 from the web? If not, please do so and see if that resolves the issue.
If you are still missing VI's, list those VI's on this forum, and maybe Nadim R. or I will be able to locate those VI's for you. That will most likely be the easiest course of action.
06-07-2007 01:58 PM
the files are in the feild point folder it is like labview just does not like them the attached picture is the folder they are in i have marked the ones that work and do not
what is the oldest version of fp explore you can get?
i can not think of anything else to try. i have reloaded labview and yes fp explorer from the link you provided no luck
the 1 thing i noticed is the label on 3 of the vi has (polymorhic) i do not remember that being ther on it before when i used it
06-08-2007 09:30 AM
06-11-2007 09:40 AM
12-02-2010 06:56 PM
I recently update the fieldpoint explorer driver from 2.0 to explorer 3.0.2 I have labview 5.0.1 and when I updated the driver it ask me if I wanted to use the old dll files. What should I have answered, (yes or no). I chose no and then went through the configuration of the new network module FP-1601 versus the 1600 which was in the rack. Updating the network module was the original reson to go from fp exp 2.0 to fp exp 3.0.2
Fieldpoint explorer 3.0.2 has support for the fp-1601.
The module configured fine and I could find devices fine. The problem is that it reset the counter modules to a default configuration. The tach signals would not read. Do you know why this happened.
Thank you
12-03-2010 05:25 PM
Hi asp4results,
It looks like this is a different question from what this thread was discussing back in '07. You might want to try starting a new thread specific to this issue.