FieldPoint Family

cancel
Showing results for 
Search instead for 
Did you mean: 

cFP2120 has differnt time stamps

I have a cFP-2120 with one AI-110 module.  The timestamp is different on differnet channels in LabVIEW 7.1; several hours dfferent.  They are also different in MAX.  I set the time server in Remote Systems Network Settings Tab on the IP address in MAX to be the development PC that is on the same subnet, etc.  This doesn't work wither.  I have rebooted, reformatted and toggled power on the cFP-2120.  Why can't I make the cFP-2120 take the development PC timestamp?  Why does the same cFP-2120 give dofferent timestamps in LV?
 
I am using LV 7.1 and have both FP version 4 and version 5.  MAX v4.1.  The development PC is a Dell P4 with 1GB; garden variety stuff.
 
I should mention that there are three cFP-2120 + AI-110 systems on the network.  They all have the same behavior.
 
Thanks in advance for your help.
 
BW,
Jim
0 Kudos
Message 1 of 7
(4,308 Views)
Hi Jim,

You commented that the timestamp is off by "several hours," so I will assume this means "hours different" and not "hours, minutes, and second different." In this case it sounds like there is a time zone difference between the host computer and the cFP controllers. I'll also assume your host computer is set up correctly, so here's how to fix the cFP.

To change the time zone on a cFP controller, select it in the Measurement & Automation Explorer (MAX), switch to the system settings tab and adjust the time zone (and daylight savings check) as necessary. It's worth checking the Time Zone settings on your host computer (double click your date/time icon in the taskbar and switch to the Time Zone tab).

Cheers.

Michael K.

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

0 Kudos
Message 2 of 7
(4,293 Views)
Hi Michael,
 
Thanks for your response.  No, it is off my hours, minutes and seconds.  I have already gone into the sytem tab in MAX to set the time zone  Should this not matter if I am using the PC as the time server?
 
best wishes,
Jim
0 Kudos
Message 3 of 7
(4,293 Views)
Hi Jim,

Sorry for the misunderstanding, sometimes you hope for the best and expect the worst. There's a wealth of information on setting/correcting the timestamp on a [compact]FieldPoint controller.

cFP-2xxx Controller Synchronization Problems with the National Instruments Time Server

Setting the Date and Time On My FP-160x or FP-20xx (still somewhat relevant)

Setting Date and Time on a LabVIEW Real-TIme Target Using Network Time Protocol (NTP) Server from NI...

Cheers.

Michael K.

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

0 Kudos
Message 4 of 7
(4,285 Views)

Hello Michael,

Thanks for the links.  I think I already have a firewall exception for lktsrv; but I'll double-check.

Also, none of the links shed any light on why the same controller would have differnet channels (AI-110) on its backplane at drastically different hours, minutes and seconds.

Thanks again.

Best wishes,

Jim

0 Kudos
Message 5 of 7
(4,282 Views)
Hi Jim,

I guess I'm still not understanding the situation. Do you have several cFP-2120 controllers showing a different timestamp when reading from an AI-110 or one 2120 controller showing different timestamps when reading from several AI-110?

In either case you should be able to use the KnowledgeBase How Do I Set the Date and Time on My Real-Time Controller?

This describes how to set the date/time on the controller using Real-Time VIs. It is still worth investigating why the Time Server isn't updating the timestamps as expected. Let me know how this goes

Michael K.

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

0 Kudos
Message 6 of 7
(4,275 Views)
I think Jim is saying that he has several channels (all on the same AI module, all on the same backplane of a single 2120) that are returning timestamps that are all very different times.  This can happen because over a remote connection, the timestamp is only going to change if the value is different from the last value read.  So if you have some inputs changing often, but some are never changing, then you are going to get really old timestamps for the input channels that are never changing, but updated timestamps for input channels that change often.  Could this be what you are seeing, Jim?

-Tommy

0 Kudos
Message 7 of 7
(4,262 Views)