Jiji
Well-Known Member
- First Name
- Rick
- Joined
- Jul 26, 2021
- Threads
- 24
- Messages
- 493
- Reaction score
- 641
- Location
- Finger Lakes
- Vehicles
- 2022 Mustang Mach-E GT 2024 F-150 Lightning
- Thread starter
- #1
I have been digging into the variables available from the OBDII port and am stumped by not finding a DID (Read Data Identifier, UDS service 0x22) that returns the current time (using FORScan Lite, they call it Global Time which is misleading).
There are lots of modules that respond to DID 0xDD00 but this returns a time value that I can make no sense of unless it is the time when the MME was born which means everybody gets a different value reported back.
This value returned is a 32-bits but it is a tenths of seconds time, last night (2022-01-08 22:17 local) my MME returned 185304671, which is 18530467.1 seconds. Digging in with a little Python datetime queries I can find time t=0:
>>> import datetime
>>> dt = datetime.datetime(2022, 1, 8, 22, 17)
>>> dt.timestamp()
1641698220.0
>>> dt.timestamp()-18530467
1623167753.0
>>> datetime.datetime.fromtimestamp(1623167753)
datetime.datetime(2021, 6, 8, 11, 55, 53)
Of course this is meaningless unless I look at my build date and it happens to say 06/2021.
I would suspect the TCU or the APIM modules might report a time (TCU has the GPS module and GPS time would be perfect, APIM of course displays the time so got it somewhere). Hoping that someone with different ODBII software, perhaps Torque or other high-end ODBII package, might have a DID that returns local or GMT time.
And while I am at it, I would love to get precision GPS, the GPS data returned by the APIM module reading DID 0x8012 has limited lat/long precision making it useless for mapping trip data. With accurate GPS I won't need a phone except to use as hotspot to connect the MME remotely.
There are lots of modules that respond to DID 0xDD00 but this returns a time value that I can make no sense of unless it is the time when the MME was born which means everybody gets a different value reported back.
This value returned is a 32-bits but it is a tenths of seconds time, last night (2022-01-08 22:17 local) my MME returned 185304671, which is 18530467.1 seconds. Digging in with a little Python datetime queries I can find time t=0:
>>> import datetime
>>> dt = datetime.datetime(2022, 1, 8, 22, 17)
>>> dt.timestamp()
1641698220.0
>>> dt.timestamp()-18530467
1623167753.0
>>> datetime.datetime.fromtimestamp(1623167753)
datetime.datetime(2021, 6, 8, 11, 55, 53)
Of course this is meaningless unless I look at my build date and it happens to say 06/2021.
I would suspect the TCU or the APIM modules might report a time (TCU has the GPS module and GPS time would be perfect, APIM of course displays the time so got it somewhere). Hoping that someone with different ODBII software, perhaps Torque or other high-end ODBII package, might have a DID that returns local or GMT time.
And while I am at it, I would love to get precision GPS, the GPS data returned by the APIM module reading DID 0x8012 has limited lat/long precision making it useless for mapping trip data. With accurate GPS I won't need a phone except to use as hotspot to connect the MME remotely.
Sponsored
