Difference between revisions of "DualCam Data Sending Parameters ID"
From Wiki Knowledge Base | Teltonika GPS
(Created page with "==DualCam RS232 camera support== DualCam camera support was introduced from firmware version 03.27.06.Rev.360. A new RS232 mode "DualCam" was added with parameters for setting...") |
|||
| (25 intermediate revisions by 4 users not shown) | |||
| Line 16: | Line 16: | ||
<br> | <br> | ||
<br> | <br> | ||
| + | <be> | ||
==Camera Feature Settings Parameters ID== | ==Camera Feature Settings Parameters ID== | ||
| Line 59: | Line 60: | ||
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |20, 25 and 30 (frames per second) | | colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |20, 25 and 30 (frames per second) | ||
| colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |30 | | colspan="1" rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |30 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
'''OSD display''' - On Screen Display feature displays date and time in the upper left corner of the photo. This feature can be enabled or disabled. | '''OSD display''' - On Screen Display feature displays date and time in the upper left corner of the photo. This feature can be enabled or disabled. | ||
| − | < | + | <be> |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Camera Scenario Settings Parameters ID== | ==Camera Scenario Settings Parameters ID== | ||
| Line 392: | Line 186: | ||
|} | |} | ||
<br> | <br> | ||
| − | + | ===Video sending by trigger=== | |
| − | = | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ==Video sending by trigger | ||
Video sending by trigger camera scenario monitors the selected trigger (video sending trigger parameter) and captures video from front, rear or both cameras before and after the event (video duration before trigger and video duration after trigger parameters). If the previously captured video has not finished downloading, then a new video capture is skipped until the old one has been sent. When this scenario is triggered, high priority eventual record is generated with the value corresponding to what triggered the scenario. See the table below. | Video sending by trigger camera scenario monitors the selected trigger (video sending trigger parameter) and captures video from front, rear or both cameras before and after the event (video duration before trigger and video duration after trigger parameters). If the previously captured video has not finished downloading, then a new video capture is skipped until the old one has been sent. When this scenario is triggered, high priority eventual record is generated with the value corresponding to what triggered the scenario. See the table below. | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 471: | Line 206: | ||
|} | |} | ||
| − | ==Image sending trigger | + | ===Image sending trigger=== |
| + | |||
'''Added''' Image sending trigger option (works the same way as Video sending trigger just triggers image sending). Both front and rear images will be sent. | '''Added''' Image sending trigger option (works the same way as Video sending trigger just triggers image sending). Both front and rear images will be sent. | ||
| Line 504: | Line 240: | ||
|} | |} | ||
| − | ==Camera | + | ===Camera firmware version=== |
| − | |||
| − | {| class="wikitable" style="text-align:center;" | + | Additional SMS/GPRS command for cameras’ firmware checking. Since both cameras are separate, there are two versions returned. |
| − | |- style="background-color:# | + | |
| − | ! rowspan="1" style="width: | + | {| class="wikitable" |
| − | ! rowspan="1" style="width: | + | |+ |
| − | ! rowspan="1" style="width: | + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command''' |
| − | ! rowspan="1" style="width: | + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Arguments''' |
| + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Explanation''' | ||
| + | |- | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |camgetver | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |None | ||
| + | | rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Used to check firmware versions. | ||
| + | Returns version in the format: '''V<major>.<minor>.<revision>.''' | ||
| + | For example, '''V1.9.3.''' | ||
| + | |||
| + | Because there are two cameras, two versions are returned. | ||
| + | The complete response would look like this: | ||
| + | '''Front camera V1.9.3. Rear camera V1.9.3.''' | ||
| + | |||
| + | If there are problems reading the version or if the camera is not responding/connected, the return would be this: | ||
| + | '''The front camera camgetver failed. The rear camera camgetver failed.''' | ||
| + | |||
| + | |} | ||
| + | |||
| + | ===Camera request command=== | ||
| + | A new camera request has been added, which allows the server to request files from a camera. The format is as provided below in the table: | ||
| + | {| class="wikitable" | ||
| + | |+ | ||
| + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Command''' | ||
| + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Arguments''' | ||
| + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Explanation''' | ||
| + | |- | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |camreq: | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |<file_type>,<file_source>,<timestamp>,<duration> | ||
| + | ,<domain>,<port> | ||
| + | | rowspan="1" style="text-align: left; style=" width: 150px; background: white; color: black;" |Captures appropriate file with the provided details. If the connection to server is opened, them files immediately become available for download. If not, then connection is tried to be made. If <domain> and <port> parameters are included, the device will send footage of the command to that address. | ||
| + | |} | ||
| + | The arguments are as follows: | ||
| + | |||
| + | *<file_type> | ||
| + | **0 - Video | ||
| + | **1 - Photo | ||
| + | *<file_source> | ||
| + | **1 - Front camera | ||
| + | **2 - Rear camera | ||
| + | **3 - Both cameras | ||
| + | *<timestamp> | ||
| + | **Unix timestamps in decimal (not required for photo download) | ||
| + | *<duration> | ||
| + | **Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec) | ||
| + | |||
| + | '''Structure examples:''' | ||
| + | |||
| + | '''camreq:<file type>,<file source>(if video, add ",<timestamp>,<duration>)''' | ||
| + | |||
| + | However, if there is a need to send to the specific server without configuring, you can add two extra parameters. | ||
| + | The complete structure: | ||
| + | |||
| + | '''camreq:<file type>,<file source>(if video, add ",<timestamp>,<duration>),<domain>,port''' | ||
| + | |||
| + | For example: camreq:0,1,1624960616,5,212.59.13.226,7160 | ||
| + | |||
| + | |||
| + | {| class="wikitable" | ||
| + | |+ | ||
| + | ! rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Conditions''' | ||
| + | ! colspan="3" rowspan="1" style="width: 600px; background: #0054A6; color: white;" |'''Command response''' | ||
| + | |- | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Request successful and server connection successful. Device is ready to send selected file | ||
| + | | rowspan="14" style="text-align: left; style=" width: 150px; background: white; color: black;" |Photo request from source <1-3>. | ||
| + | |||
| + | '''(If photo request)''' | ||
| + | |||
| + | |||
| + | Video request from source <1-3> for <1-255> seconds since YYYY-MM-DD HH:MM:SS. | ||
| + | |||
| + | '''(If video request)''' | ||
| + | | colspan="2" |Preparing to send file from timestamp <timestamp of the file> | ||
| + | |- | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Request successful but the device was already connected to the server. Device is ready to send selected file | ||
| + | | colspan="2" |Already connected. Preparing to send file from timestamp <timestamp of the file> | ||
| + | |- | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Request received but the capture failed | ||
| + | | colspan="2" |Error: capture failed | ||
| + | |- | ||
| + | |Request received but the device cannot proceed with the capture and sending because ignition is off | ||
| + | | colspan="2" |Error: Cannot capture because ignition is off | ||
| + | |- | ||
| + | |Request received but the previously captured and prepared photo/video was not sent. New media is not captured. The device is ready to send the previous capture | ||
| + | | colspan="2" |Warning: Photo / Video already captured previously, trying to send it | ||
| + | |- | ||
| + | |Request received but the device was already connected to the server. New media is not captured. The device is ready to send previous capture | ||
| + | | colspan="2" |Already connected. Warning: Photo / Video already captured previously, trying to send it | ||
| + | |- | ||
| + | |Request received but the camera doesn’t acknowledge sent command. Nothing will be sent | ||
| + | | colspan="2" |Error: DualCam NAK | ||
| + | |- | ||
| + | |Request received but the camera is not connected or not working | ||
| + | | colspan="2" |Error: DualCam not present | ||
| + | |- | ||
| + | |Request received but the camera is not connected or not working | ||
| + | | colspan="2" |Error: requested file does not exist | ||
| + | |- | ||
| + | |Request received but the device cannot connect to the server | ||
| + | | colspan="2" |Error: connect to server | ||
| + | |- | ||
| + | |Request received but the modem is not ready for operation (network or modem issue) | ||
| + | | colspan="2" |Error: modem not ready to start send | ||
| + | |- | ||
| + | |Request received but the device cannot proceed with the capture and sending because the camera is being reconfigured | ||
| + | | colspan="2" |Cannot send, DualCam configuration is in progress | ||
| + | |- | ||
| + | |Request received but file capture time was exceeded. | ||
| + | | colspan="2" |Error: Media request timeout | ||
| + | |- | ||
| + | |Request received but capture completed incorrectly | ||
| + | | colspan="2" |Error: Media request problem | ||
| + | |- | ||
| + | |File type parameter incorrect in the request command | ||
| + | | rowspan="4" |Error: Invalid | ||
| + | |File Type | ||
| + | | rowspan="4" |argument in camera request cmd! | ||
| + | |- | ||
| + | |File Source parameter incorrect in the request command | ||
| + | |File Source | ||
| + | |- | ||
| + | |Timestamp parameter incorrect in the request command | ||
| + | |Timestamp | ||
| + | |- | ||
| + | |Duration parameter incorrect in the request command | ||
| + | |Duration | ||
| + | |- | ||
| + | |Cannot proceed with the request, ignition is off | ||
| + | | colspan="3" |Error: Ignition not detected! | ||
|- | |- | ||
| − | | | + | |Request command structure incorrect |
| − | | | + | | colspan="3" |Error: Invalid camera request command! |
| − | |||
| − | |||
|- | |- | ||
| − | | | + | |RS232 and DualCam mode is not enabled |
| + | | colspan="3" |Error: DualCam is not configured! | ||
|- | |- | ||
| − | | | + | |Front or rear camera not found |
| − | | | + | | colspan="3" |Error: Front / Rear Camera not present |
| − | | | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
<br> | <br> | ||
| − | |||
| − | |||
Revision as of 09:51, 14 July 2022
Main Page > Video Solutions > Teltonika DualCam > DualCam Data Sending Parameters IDDualCam RS232 camera support
DualCam camera support was introduced from firmware version 03.27.06.Rev.360. A new RS232 mode "DualCam" was added with parameters for setting control. The details of the RS232 mode parameter are provided in the table below.
| Parameter name | Parameter ID | Parameter value |
|---|---|---|
| RS232 Mode | 151 | 18 |
Configuration version 8.14.1.0 has to be used if configuration is being made in offline mode.
<be>
Camera Feature Settings Parameters ID
Once this mode is enabled, new tab “Camera Settings” appears on the left sidebar. This will contain the main parameters for configuring the camera settings The parameter IDs and values are provided in the table below. Once configuration is
saved to device, these parameters are updated.
| Parameter name | Parameter ID | Parameter values | Default values |
|---|---|---|---|
| Camera Picture Resolution | 66000 | ||
| 0 - 160 x 120 | 3 | ||
| 1 - 320 x 240 | |||
| 2 - 640 x 480 | |||
| 3 - 1280 x 720 | |||
| 4 - 1920 x 1080 | |||
| Camera Picture Compression | 66001 | [0 - 100] (%) | 50 |
| OSD Display | 66002 | 0 - Disabled | 0 |
| 1 - Enabled | |||
| Video Frame Rate | 66003 | 20, 25 and 30 (frames per second) | 30 |
OSD display - On Screen Display feature displays date and time in the upper left corner of the photo. This feature can be enabled or disabled. <be>
Camera Scenario Settings Parameters ID
"Camera settings" tab also contains scenario settings that trigger camera video/photo capture when specific condition is met.
| Parameter name | Parameter ID | Parameter values | Default values |
|---|---|---|---|
| Periodic Image sending | 66006 | 0 - Disabled | 0 |
| 1 - Front Camera | |||
| 2 - Rear Camera | |||
| 3 - Both Cameras | |||
| Sending interval | 66007 | [10-1800] (seconds) | 600 |
| Image Sending Trigger | 66022 | ||
| 0 - None | 0 | ||
| 2 - DIN1 | |||
| 4 - DIN2 | |||
| 8 - Crash | |||
| 16 - Towing | |||
| 32 - Idling | |||
| 64 - Geofence | |||
| 128 - Unplug | |||
| 256 - Green Driving | |||
| Video sending trigger | 66023 | ||
| 0 - None | 0 | ||
| 2 - DIN1 | |||
| 4 - DIN2 | |||
| 8 - Crash | |||
| Video duration before trigger | 66009 | [1-10] (seconds) | 5 |
| Video duration after trigger | 66010 | [1-10] (seconds) | 5 |
| Camera Scenario Mode | 66020 | ||
| 0 - On Ignition | 0 | ||
| 1 - Always | |||
| Video source for trigger DIN1 | 66040 | ||
| 0 - None | 0 | ||
| 1 - Front | |||
| 2 - Rear | |||
| 3 - Front and Rear | |||
| Video source for trigger DIN2 | 66041 | ||
| 0 - None | 0 | ||
| 1 - Front | |||
| 2 - Rear | |||
| 3 - Front and Rear | |||
| Video source for trigger Crash | 66042 | ||
| 0 - None | 0 | ||
| 1 - Front | |||
| 2 - Rear | |||
| 3 - Front and Rear |
Video sending by trigger
Video sending by trigger camera scenario monitors the selected trigger (video sending trigger parameter) and captures video from front, rear or both cameras before and after the event (video duration before trigger and video duration after trigger parameters). If the previously captured video has not finished downloading, then a new video capture is skipped until the old one has been sent. When this scenario is triggered, high priority eventual record is generated with the value corresponding to what triggered the scenario. See the table below.
| Parameter name | Parameter AVL ID | Parameter value |
|---|---|---|
| SOS trigger | 499 | 0 - Server request |
| 1 - DIN1 | ||
| 2 - DIN2 | ||
| 3 - Crash |
Image sending trigger
Added Image sending trigger option (works the same way as Video sending trigger just triggers image sending). Both front and rear images will be sent.
For selecting multiple options using SMS/GPRS commands, add values of every option and set that value for this parameter.
For example, to set DIN1 (2), Crash (8), and Unplug (128) scenarios as triggers, add their values (2 + 4 + 128 = 138) and set the sum as the parameter value
| Parameter name | Parameter AVL ID | Parameter value |
|---|---|---|
| SOS trigger | 499 | 0 - Server request |
| 1 - DIN1 | ||
| 2 - DIN2 | ||
| 3 - Crash | ||
| 4 - Towing | ||
| 5 - Idling | ||
| 6 - Geofence | ||
| 7 - Unplug | ||
| 8 - Green Driving |
Camera firmware version
Additional SMS/GPRS command for cameras’ firmware checking. Since both cameras are separate, there are two versions returned.
| Command | Arguments | Explanation |
|---|---|---|
| camgetver | None | Used to check firmware versions.
Returns version in the format: V<major>.<minor>.<revision>. For example, V1.9.3. Because there are two cameras, two versions are returned. The complete response would look like this: Front camera V1.9.3. Rear camera V1.9.3. If there are problems reading the version or if the camera is not responding/connected, the return would be this: The front camera camgetver failed. The rear camera camgetver failed. |
Camera request command
A new camera request has been added, which allows the server to request files from a camera. The format is as provided below in the table:
| Command | Arguments | Explanation |
|---|---|---|
| camreq: | <file_type>,<file_source>,<timestamp>,<duration>
,<domain>,<port> |
Captures appropriate file with the provided details. If the connection to server is opened, them files immediately become available for download. If not, then connection is tried to be made. If <domain> and <port> parameters are included, the device will send footage of the command to that address. |
The arguments are as follows:
- <file_type>
- 0 - Video
- 1 - Photo
- <file_source>
- 1 - Front camera
- 2 - Rear camera
- 3 - Both cameras
- <timestamp>
- Unix timestamps in decimal (not required for photo download)
- <duration>
- Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec)
Structure examples:
camreq:<file type>,<file source>(if video, add ",<timestamp>,<duration>)
However, if there is a need to send to the specific server without configuring, you can add two extra parameters. The complete structure:
camreq:<file type>,<file source>(if video, add ",<timestamp>,<duration>),<domain>,port
For example: camreq:0,1,1624960616,5,212.59.13.226,7160
| Conditions | Command response | ||
|---|---|---|---|
| Request successful and server connection successful. Device is ready to send selected file | Photo request from source <1-3>.
(If photo request)
(If video request) |
Preparing to send file from timestamp <timestamp of the file> | |
| Request successful but the device was already connected to the server. Device is ready to send selected file | Already connected. Preparing to send file from timestamp <timestamp of the file> | ||
| Request received but the capture failed | Error: capture failed | ||
| Request received but the device cannot proceed with the capture and sending because ignition is off | Error: Cannot capture because ignition is off | ||
| Request received but the previously captured and prepared photo/video was not sent. New media is not captured. The device is ready to send the previous capture | Warning: Photo / Video already captured previously, trying to send it | ||
| Request received but the device was already connected to the server. New media is not captured. The device is ready to send previous capture | Already connected. Warning: Photo / Video already captured previously, trying to send it | ||
| Request received but the camera doesn’t acknowledge sent command. Nothing will be sent | Error: DualCam NAK | ||
| Request received but the camera is not connected or not working | Error: DualCam not present | ||
| Request received but the camera is not connected or not working | Error: requested file does not exist | ||
| Request received but the device cannot connect to the server | Error: connect to server | ||
| Request received but the modem is not ready for operation (network or modem issue) | Error: modem not ready to start send | ||
| Request received but the device cannot proceed with the capture and sending because the camera is being reconfigured | Cannot send, DualCam configuration is in progress | ||
| Request received but file capture time was exceeded. | Error: Media request timeout | ||
| Request received but capture completed incorrectly | Error: Media request problem | ||
| File type parameter incorrect in the request command | Error: Invalid | File Type | argument in camera request cmd! |
| File Source parameter incorrect in the request command | File Source | ||
| Timestamp parameter incorrect in the request command | Timestamp | ||
| Duration parameter incorrect in the request command | Duration | ||
| Cannot proceed with the request, ignition is off | Error: Ignition not detected! | ||
| Request command structure incorrect | Error: Invalid camera request command! | ||
| RS232 and DualCam mode is not enabled | Error: DualCam is not configured! | ||
| Front or rear camera not found | Error: Front / Rear Camera not present | ||
