Heh. It hasn't been so long since I've driven down dirt roads in Quebec that still had speed limits in miles per hour. There be rebels up there in the PQ.
I'll keep my U.S. customary units, thank you.
The drill bits kill me: 15/64ths 3/32ths 9/64ths. Maybe I’m a simpleton, but why not just 1mm 2mm 3mm 4mm? 
At least you don’t have to memorise what fractions are larger than others, you just need to know how to count. I do find it a bit strange that you guys haven’t adopted it, and I mean no office by this, but your language has been simplified (removing ‘u’ from words [colour, labour], removing words altogether [cheque]), why not go that one step further by simplifying your units?
You just better watch your language mister! While some of us may live here, that doesn’t mean we are one of them 
But given that both by parents were crow eaters, I’ll forgive you this time 
The drill bits make perfect sense to me–they’re binary compatible. (:
Yes, but most of us here aren’t computers like you, Phil 
1 Like
Hah! I don’t believe that for a moment. We’re all geeks here.
3 Likes
I tried that and ran into issues. I was communicating with a WES system and spent a month troubleshooting my code only to realize there was no issue, only my timestamps were off. I don't know for sure if it was from the 1 second frequency or the Ignition GW timestamp, but once I removed this and used the Rockwell SNTP AOI we saw expected results.
I have a scheduled gateway script that sets the date and time on every PLC that is connected to the gateway to the gateway's time every day at the same time, using SSV with the DINT[7] tags required to set the time.
I highly recommend running an NTP server anywhere on your network. If you have Windows domain controllers there's one already running on them. The SNMP/NTP AOI for Rockwell works well and will be more accurate and efficient than using a gateway script.
3 Likes