I've been chasing my tail all day on a similar issue w/ allen bradly's date time type. I have the plc data structure as follows:
I was having trouble getting the date time to read properly so I pivoted to just pulling the Raw Lint and then FromMillis() it back into a datetime. Now here's the interesting part, when i try to pull in that raw unix timestamp LINT this is what i get
Notice from the first screenshot that that 11 million number is the exact same as the Time32 and in fact not the lint I was trying to pull.
Has anyone seen this before? Any thoughts?
Thank you!
Possible bug. You should open a support ticket.
You might also want to try my alternate driver--different implementation:
Automation Professionals is pleased to announce its latest EtherNet/IP Communications Suite driver module, a major upgrade to its EtherNet/IP Class1 Communications module, as a Public Beta.
As of April 15, 2023, this is now a Production Release.
The primary new feature is its new Generic EtherNet/IP Client Driver, a drop-in replacement for IA's Logix V21+ driver and its Omron NJ/NX driver. It does work with older Logix processors, and also works with Rockwell's MicroLogix 8xx family (ethernet…
What are you seeing when you just use the regular DT tag? What version of Ignition are you using?
The Proper DT tag (as a Long)
As a Date/Time
We are using v8.1.45
Activated without the Client Option? (Most users have that.)
If you have the client option, just create a "Generic EtherNet/IP Client" to replace the IA Logix device. (Use the same name.)
Phil, we are using the client option only and what @ethan.lewis is speaking to is the "Generic Ethernet/IP Client" and the results we are getting from Allen-Bradley DT type
So, not Kevin's problem at all. Please send an email to support@automation-pros.com so we can start evaluating this.
1 Like
