DateTime tag with Omron NJ Driver

I was wondering if it is possible to read in an Omron NJ “TIME” datatype tag into Ignition using the Omron NJ Driver.

I noticed that it seems to be compatible with Ignition because i was able to import it into the Omron NJ Driver tag table without issue, and is given the DataType “UINT_BCD” on Ignition side.

What is the best way to create a tag in Ignition to read this from the Driver? I’ve tried Integer, Dataset, Date and they all do not seem to work.

The only date/time datatype supported right now is the “DATE_AND_TIME_NSEC” datatype.

Neither the Omron documentation nor the engineers we had contact with were able to tell us the byte format of the other datatypes. As soon as we get this information the driver should gain support these additional datatypes.

Just having a look into this again for a different application.

I don’t seem to have this datatype available in Sysmac Studio. I have “TIME”, “DATE”, “TIME_OF_DAY”, “DATE_AND_TIME”.

Do you know what version of Omron software you were using to get that datatype?

Not trying to put words in Kevin’s mouth, but I think he meant "The only date/time datatype supported by Ignition’s OPC/UA infrastructure right now is the “DATE_AND_TIME_NSEC” datatype. Omron doesn’t have that, so Dates & Times don’t convert.

Ah ok thanks.
I have decided to use the Omron function “DTToSec” to provide a LONG INT variable which represents UNIX time in seconds. This is then read by Ignition OPC Server and written to SQL using a transaction group. In order to have timestamp data in a chart/table i need to make convert the INTEGER into a date time format with my SQL Query.

We’ll be meeting with an Omron engineer next month; I’ll see if we can get some more information on this.

Is it now possible to link datetime from sysmac directly within ignition?
| The variable in the iport list is placed as unit_BCD data type.

Only within the designer> tagbrowser this variable will not be available

Is it now possible to link datetime from sysmac directly within ignition?
The variable in the iport list is placed as unit_BCD data type.

Only within the designer> tagbrowser this variable will not be available

Ignition 8.0.15 has support for the date/time datatypes.

Our best effort at finding documentation on these datatypes suggests that DATE_AND_TIME is the number of nanoseconds since the epoch (1970-01-01T00:00:00). I can only imagine this is supposed to be Zulu/UTC-0/GMT.

Currently our driver reads the same values for DATE_AND_TIME as Kepware does over OPC UA. We’ve had one customer argue that this is somehow incorrect but I’m not sure how else the value could possibly be interpreted, so if any of you have insight it would be appreciated.

2 Likes