Shared Variable Timestamp fixed on TPC-2012

[dbtestcon]

My code running on a TPC-2012 reads from a shared variable that is hosted on a CRio.  Reading the timestamp of the shared variable gives me the same 5AM time in 1903.

If I read that same shared variable using software running on a PC vs the TPC, I get a timestamp that corresponds to the correct time on the CRio. Therefore, the CRio is publishing and updating the variable as required.

What is up with the TPC?  I am guessing that reading the timestamp is not supported on the TPC?  Yes/No?

[dbtestcon · Accepted solution]

Fixed.

You must read the timestamp AND the actual variable output.  Just reading the timestamp will not give you anything meaningful.

I didn't care about the data in the Shared Variable, I just wanted the tmie it was written.....

[Jennifer_R]

Hi dbtestcon,

This was reported to R&D (#162395) for further investigation.  Thank you for posting your workaround.