FieldPoint Family

cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot control the FP-PG-522 module via software.

Has anyone programmed the "On Time" and "Off Time" of a FP-PG-522 with Measurement Studio?  I used Measurement and Automation Explorer to create the two items in the Data Neighborhood.  I have successfully used Measurement Studio for Visual Basic with FP-AO-200, FP-AI-110, FP-RLY-420, FP-DO-410 and other modules, but not the FP-PG-522..
0 Kudos
Message 1 of 9
(8,311 Views)
I am not directly familiar with how to configure these settings in Visual Basic. I imagine that the programming will be very similar to that which you've already coded for your other modules.
Thus, is there any particular issue that is preventing you from configuring these settings? Are you able to configure similar settings for the other modules? If so, what differs in this case?
I'd like to see if I can help.
Cheers,
Emilie K | Applications Engineer | National Instruments
0 Kudos
Message 2 of 9
(8,300 Views)
Sorry, I haven't responded to your questions sooner, but iIn order to invetigate the problem, I need to shut down the equipment connected to the module.  The same Visual Basic program I successfully use for the FP-AO-200, I am using for the FP-PG-522, just a different URLs and values.
 
Here's what I have learned:
 
I have reverted back to default module and channel names, but I'll abreviate in this discussion.  I created items for Off Time and On Time in MAX for channels 0 through 3.  The resulotion is 100 microseconds and the Pulse Mode is Continuous.
 
If I try to write a value to the Off Time or On Time for channel 0, the values display in MAX are not changed even though the status messages and quality attributes say everthing is okay.  For channel 1, if I wriite to the Off Time or the On Time, the On Time is changed.  For channel 2, I cannot write to the On Time or Off Time.  The status message says I have a good connection, but he quality attribute says "Can't write data.".  For channel 3, both the Off Time and On Time write to the Off Time item.
0 Kudos
Message 3 of 9
(8,266 Views)
It seems like we should determine whether this is a hardware or software issue. From the behavior you describe in MAX, I'm leaning towards hardware.
I've also found that you are no working directly with an AE via phone support, which is great. If we can find a solution for you, we'll make sure to update this post to let others know what resolved your issue.
Until then,
Emilie K
0 Kudos
Message 4 of 9
(8,246 Views)
I am leaning toward a hardware problem also, but you just never know until problem is identified.  I decided to post the problem for a quick and easy solution from the NI Forum, but it didn't happen.
 
Thanks.
0 Kudos
Message 5 of 9
(8,243 Views)
I am having this exact problem right now.  Has there been a solution found yet, or has the root cause of the problem been identified?  I am using Windows XP OS and a VB6 interface to OPC.  The OPC server explorer won't even set the values.  The only way I can set the pulse parameters is through Measurement & Automation Explorer.
0 Kudos
Message 6 of 9
(7,972 Views)
 

Hello rwbacon,

First things first, let's make sure you've got the appropriate literature for using the FieldPoint Optomux commands. It's located in the FieldPoint Optomux Programming Reference Help Manual.

I'm not sure what was the exact solution for DrWisch, since I did not handle his direct support call but from the notes in our database, it looks like instead of naming the items himself in MAX, he tried using the default names. You might try this yourself if you haven't already.

Beyond that, if it indeed was a hardware issue, it's most likely something you'll need to handle directly with an Applications Engineer. Call in and we can conduct one-on-one troubleshooting to determine whether your unit requires repair.

Good luck!

Emilie K
National Instruments

0 Kudos
Message 7 of 9
(7,954 Views)
Thanks, I found the answer here: http://forums.ni.com/ni/board/message?board.id=110&message.id=6649&query.id=101591#M6649

Installing the update solved all my problems.  Guess it was an NI bug.

0 Kudos
Message 8 of 9
(7,936 Views)
 

Indeed, it looks like upon installing the latest FieldPoint driver (version 6.0), the problems were eliminated. We currently only provide version 5.0.1 of the FieldPoint driver on our website but you can certainly find FieldPoint 6.0 on the Device Drivers distribution CD that is shipped with LabVIEW 8.5.

Thanks for following up and letting us know what solved your issue!

Cheers,
Emilie
National Instruments

0 Kudos
Message 9 of 9
(7,912 Views)