2020 Timestamp Not Correct

[Dancharris]

I am running the cFP 2020 and get a timestamp from the read vi that indicates 1970. The lookout time server process is running on the computer that is running the .vi s and both this computer and the cFP have static i.p. addresses. The computer and the cFP are connected via a 5-port switch from a newtwork drop of the main network.

I reviewed some of the other posts regarding this type of problem and seem to have no luck with solutions. I have tried switching the time server function to another computer on the network with no luck.

Thanks


Dan H

[Matthew_Williams]

What versions of software are you using? We have seen issues with
RT 6.1.1 on the cFP and FieldPoint Explorer 3.0.2 on the pc. Don't
have pertinent experience yet with newer versions. Also have to ask
the obvious question; is the cFP module configured to talk to one of
the PCs configured as a time server? FieldPoint Explorer or MAX will
let you set/confirm the timeserver setting. You can also check it
by ftp'ing in and looking in the ni-rt.ini file in the root of the
module. I think the entry is something like 'timeserver=192.168.0.1'.

We wound up setting the cFP time explicetly within our application and
disabling the native stuff.

Matt

[Dancharris]

We are using LV 7.1 full (currently without the LV RT module) and MAX for windows XP.

I checked the ni-rt.ini file and the timeserver i.p info is correct. Also I know the lookout process is running because it errors that the process is already running when I try to restart it.

All the other data aquisition functions, with several different I/O modules are running fine. The computer and cFP2020 know each other exist and communicate well.

We have worked around by just using the "get current timpstamp" vi. Our process is very slow acting and the difference between the read time and the computer time is not enough to make a difference but I fear that when to go to embed the vi on the 2020 the work around will fail.

How did you set the cFP time explicitly? Maybe that will work for us.

Dan H

[Dancharris]

#include Thank you for your help

Forgot to say this.

Dan H

[Matthew_Williams]

See the attached for a mechanism to programatically set the time on the cFP.
I forget whether this compensates for GMT; just make sure to check that it
does what you need one way or the other. Hope it is useful.

Matt

[LYu]

Hi Dan,

What version of the FieldPoint driver are you using? I'm assuming that you're reading using the FP Read VI? Is the timestamp value consistently showing only "1970"? When the Lookout TimeService is not running, do you get the same result? Have you tried connecting with a different host computer?

If you change the format and precision of the output indicator (right click indicator and choose "Format and Precision") by increasing the digits of precision and data type, do you see a difference in the result?

Also, does the situation described here apply?

Incorrect Timestamping When Logging Data On a FP-20xx

Thanks,
Lesley Y.