Difference between revisions of "Next Calibration Date Parasing"
From Wiki Knowledge Base | Teltonika GPS
(Created page with "__TOC__ ==Next calibration date parsing== The value is received as 4 byte Hexadecimal value. Example how to parse it to Human readable date is provided in the table below: {...") |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
==Next calibration date parsing== | ==Next calibration date parsing== | ||
| − | The value is received as 4 byte | + | The value is received as 4 byte hexadecimal value. Example how to parse it to a human readable date is provided in the table below: |
{| class="wikitable" | {| class="wikitable" | ||
Latest revision as of 12:27, 9 September 2022
Next calibration date parsing
The value is received as 4 byte hexadecimal value. Example how to parse it to a human readable date is provided in the table below:
| Step | Next Calibration Date (AVL ID:10503) | Format |
|---|---|---|
| 1. Received value | 66-64-F0-80 | HEX |
| 2. Converted to DEC | 1717891200 | DEC |
| 3. Converted to Human readable date | Sunday, June 9, 2024 12:00:00 AM, GMT+00:00 | Human readable date |
Converting whole 4 byte Hexadecimal - 66-64-F0-80 value to decimal value as it is equivalent of Unix timestamp in seconds - 1717891200. Convert epoch to human-readable date: https://www.epochconverter.com/
