Changes

DualCam Communication Protocol (view source)

Revision as of 15:40, 16 September 2024

652 bytes added , 16 September

Added Trigger Timestamp to the response command table.

Line 302: Line 302:

! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Latitude (8 bytes)'''

! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Longitude (8 bytes)'''

+

! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Trigger Timestamp (8 bytes)'''

|-

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0x000B

Line 312: Line 313:

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0xFF

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0xFFFF

+

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0xFFFFFFFFFFFFFFFF

Line 318: Line 320:

'''Note: 0x000B command was added since 03.27.04.Rev.104 firmware version and would not work with older versions.'''

+

'''Note: The Trigger Timestamp was made available since 03.29.00.Rev.534 firmware version and would not work with older versions.'''

Response command meta data:

Line 325: Line 329:

! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Description'''

|-

−

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Command version

+

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" | Command version

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Iteration of the command itself to determine to parse of the data

|-

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |File type

−

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Media type for confirming which file’s metadata is received. Byte structure is the same as byte 3 in the initialization packet settings data

+

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Media type for confirming which file’s metadata is received. Byte structure is the same as byte 3 in the initialization packet settings data

|-

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Timestamp

−

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Timestamp at the time of the ~~trigger~~. ~~Same used in a corresponding SOS record~~

+

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Timestamp at the time of the video file being finalized.

|-

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Trigger

−

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Trigger values. Same values as video sending trigger in SOS record.

+

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" | Trigger values. Same values as video sending trigger in SOS record.

|-

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Video length

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Duration of the video in seconds. If the file type is a photo, this value is 0x0000.

+

|-

+

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Trigger Timestamp

+

| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Timestamp at the time of the trigger. The same value is used in the corresponding event record.

|-

|}

−

==Converting Latitude and Longitude values to decimal==

+

==Converting Latitude and Longitude values to decimal ==

Latitude and Longitude values are being sent in HEX format, but to correctly parse them conversation from HEX to Double. Example:

The received value in HEX is 404B59A74E8E028D

Line 359: Line 366:

[[File:HexToDecimal.png]]

−

==CRC-16 calculation==

+

== CRC-16 calculation ==

CRC is calculated with using 3 input variables:

Line 472: Line 479:

==Video files and conversion==

Videos downloaded from the camera are in the raw h265 format. By default, they could be viewed using the ZMVideoPlayer program in the h265 format. If the videos are needed in a more common format, they can be converted.

−

[[Category:Teltonika DualCam]]

SimonasM

Administrators

17

edits