Difference between revisions of "DashCam Data Sending Parameters ID"
| (8 intermediate revisions by the same user not shown) | |||
| Line 142: | Line 142: | ||
{| class="wikitable" style="text-align:center;" | {| class="wikitable" style="text-align:center;" | ||
|- style="text-align:left; background-color:#ffffff;" | |- style="text-align:left; background-color:#ffffff;" | ||
| − | ! | + | ! |
| − | ! | + | ! style="font-weight:bold; color:#333333;" | Parameter ID for FMX650 device |
| − | |||
|- | |- | ||
| Camera Resolution Picture | | Camera Resolution Picture | ||
| COM1 DashCam - 1011000<br />COM2 DashCam - 1012000 | | COM1 DashCam - 1011000<br />COM2 DashCam - 1012000 | ||
| − | |||
|- | |- | ||
| Camera Picture Compression | | Camera Picture Compression | ||
| COM1 DashCam - 1011001<br />COM2 DashCam - 1012001 | | COM1 DashCam - 1011001<br />COM2 DashCam - 1012001 | ||
| − | |||
|- | |- | ||
| OSD Display | | OSD Display | ||
| COM1 DashCam - 1011002<br />COM2 DashCam - 1012002 | | COM1 DashCam - 1011002<br />COM2 DashCam - 1012002 | ||
| − | |||
|- | |- | ||
| Video Frame Rate | | Video Frame Rate | ||
| COM1 DashCam - 1011003<br />COM2 DashCam - 1012003 | | COM1 DashCam - 1011003<br />COM2 DashCam - 1012003 | ||
| − | |||
|- | |- | ||
| File Transfer Priority | | File Transfer Priority | ||
| COM1 DashCam - 1011025<br />COM2 DashCam - 1012025 | | COM1 DashCam - 1011025<br />COM2 DashCam - 1012025 | ||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| Camera Time Zone | | Camera Time Zone | ||
| COM1 DashCam - 1011024<br />COM2 DashCam - 1012024 | | COM1 DashCam - 1011024<br />COM2 DashCam - 1012024 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
| Line 385: | Line 272: | ||
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<br> | <br> | ||
| − | |||
==Video sending by trigger parameters ID== | ==Video sending by trigger parameters ID== | ||
Video sending by trigger camera scenario monitors the selected trigger (video sending trigger parameter) and captures video from the camera 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 the camera 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. | ||
| Line 501: | Line 328: | ||
==Camera ping transmission and TF status checking parameters ID== | ==Camera ping transmission and TF status checking parameters ID== | ||
Camera pinging was implemented to periodically check if a camera is connected to a device. This is done via “Get TF status” command for camera every 20 seconds when ignition is on. The received result from this command is stored in the corresponding AVL element “Front camera state”. The following do not only store TF status, but also if response from the camera was received or not. | Camera pinging was implemented to periodically check if a camera is connected to a device. This is done via “Get TF status” command for camera every 20 seconds when ignition is on. The received result from this command is stored in the corresponding AVL element “Front camera state”. The following do not only store TF status, but also if response from the camera was received or not. | ||
| − | + | {| class="wikitable" | |
| − | {| class="wikitable | + | |+ |
| − | | | + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name''' |
| − | ! rowspan="1" style="width: | + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter AVL ID''' |
| − | ! rowspan="1" style="width: | + | ! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter values''' |
| − | ! rowspan="1" style="width: | + | |- |
| − | + | | rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |Front camera state: | |
| + | | rowspan="5" style="text-align: center; style=" width: 150px; background: white; color: black;" |498 | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0 - Camera not detected | ||
| + | |- | ||
| + | |- | ||
| + | |- | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1 - No card | ||
| + | |- | ||
| + | |- | ||
| + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |2 - Card mount failed | ||
| + | |- | ||
|- | |- | ||
| − | | rowspan=" | + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |3 - Card mounted |
| − | |||
| − | |||
| − | |||
|- | |- | ||
| − | | style="text-align: | + | | rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |4 - Card faulty |
|- | |- | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
<br> | <br> | ||
[[Category:Teltonika DashCam]] | [[Category:Teltonika DashCam]] | ||
Revision as of 14:23, 4 January 2024
Main Page > Video Solutions > Teltonika DashCam > DashCam Data Sending Parameters IDDashCam/DualCam RS232 camera support
DashCam camera support was introduced from firmware version 03.27.13.Rev.662. A new RS232 mode "DashCam" 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 | Parameter description |
|---|---|---|---|
| RS232 Mode | 151 | 18 | DualCam |
| RS232 Mode | 151 | 26 | DashCam |
Configuration version 8.19.5.0 has to be used if the configuration is being made in offline mode.
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 |
| File transfer priority | 66025 | 0 - Picture | 2 |
| 1 - Video | |||
| 2 - Alternating | |||
| Camera Time Zone | 66024 |
-720 – UTC-12:00 |
UTC+00:00 |
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.
Camera Feature Settings Parameters ID (for FMx650 devices)
| Parameter ID for FMX650 device | |
|---|---|
| Camera Resolution Picture | COM1 DashCam - 1011000 COM2 DashCam - 1012000 |
| Camera Picture Compression | COM1 DashCam - 1011001 COM2 DashCam - 1012001 |
| OSD Display | COM1 DashCam - 1011002 COM2 DashCam - 1012002 |
| Video Frame Rate | COM1 DashCam - 1011003 COM2 DashCam - 1012003 |
| File Transfer Priority | COM1 DashCam - 1011025 COM2 DashCam - 1012025 |
| Camera Time Zone | COM1 DashCam - 1011024 COM2 DashCam - 1012024 |
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 | |||
| 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 | |||
| Video source for trigger DIN2 | 66041 | ||
| 0 - None | 0 | ||
| 1 - Front | |||
| Video source for trigger Crash | 66042 | ||
| 0 - None | 0 | ||
| 1 - Front |
Video sending by trigger parameters ID
Video sending by trigger camera scenario monitors the selected trigger (video sending trigger parameter) and captures video from the camera 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 parameters ID
Added Image sending trigger option (works the same way as Video sending trigger just triggers image sending).
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 ping transmission and TF status checking parameters ID
Camera pinging was implemented to periodically check if a camera is connected to a device. This is done via “Get TF status” command for camera every 20 seconds when ignition is on. The received result from this command is stored in the corresponding AVL element “Front camera state”. The following do not only store TF status, but also if response from the camera was received or not.
| Parameter name | Parameter AVL ID | Parameter values |
|---|---|---|
| Front camera state: | 498 | 0 - Camera not detected |
| 1 - No card | ||
| 2 - Card mount failed | ||
| 3 - Card mounted | ||
| 4 - Card faulty |
