Jump to content

Test-AC: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
No edit summary
(46 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Country Blocking Service==
==Camera request command==
Device is blocked when it connects to an operator with restricted '''Mobile Country Code (MCC)''' it saves blocking timestamp (current timestamp + 28 days) and starts the counter. The counter tracks the cumulative number of days the device spends connected to an operator with restricted MCC.
A new camera request has been added, which allows the server to request files from a camera. It is also possible to to have two identical cameras connected at once. 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> <br>
''<file_source> <br>
''<timestamp> <br>
''<duration> <br>
''<domain> <br>
''<port> <br>
<u>''<resolution>''<br>(Only applied to photos)</u>
| 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, the files immediately become available for download. If not, then connection is attempted.  


If the device reaches '''28 cumulative days''' of connection to to an operator with restricted '''MCC''', it will be '''automatically blocked'''.
*If <b><domain></b> and <b><port></b> parameters are included, the device will send footage of the command to that address.


===Blacklisted Countries===
*If <b><resolution></b> parameter is included when requesting a photo, the device will send the photo with the selected resolution.


The below table provides blacklisted '''Mobile Country Codes'''.
<b>Please note,</b> that if the resolution parameter is not included in the SMS/GPRS command, the device will request a photo with configured resolution.
<table class="nd-othertables_2" style="width:30%; border-collapse: collapse;">
|-
<tr>
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |icam_req:
<th style="width:1%; vertical-align: middle; text-align: center;">MCC</th>
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |
<th style="width:1%; vertical-align: middle; text-align: center;">Country</th>
''<camera_type><br>
</tr>
''<peripheral><br>
<tr>
''<file_type><br>
<td style="vertical-align: middle; text-align: center;">250</td>
''<timestamp><br>
<td style="vertical-align: middle; text-align: center;">Russia</td>
''<duration><br>
</tr>
''<resolution><br>
<tr>
''<domain><br>
<td style="vertical-align: middle; text-align: center;">257</td>
''<port><br>  
<td style="vertical-align: middle; text-align: center;">Belarus</td>
|
</tr>
This command is used '''ONLY''' when both of the connected cameras are of the same type. It works only on DualCam or DashCam devices.
<tr>
|}
<td style="vertical-align: middle; text-align: center;">368</td>
The arguments are as follows:
<td style="vertical-align: middle; text-align: center;">Cuba</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">438</td>
<td style="vertical-align: middle; text-align: center;">Iran</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">467</td>
<td style="vertical-align: middle; text-align: center;">North Korea</td>
</tr>
</table>


===Resetting the Counter===
*<camera_type>
**0-DSM
**1-MDAS
**2-DualCam front
**3-DualCam rear
**4-DashCam


To reset the counter and timestamp, the device must connect to a non-restricted '''MCC''' continuously for '''7 uninterrupted days'''.
*<peripheral>
If the device disconnects from operator with a '''non-restricted MCC''' or connects to operator with a restricted MCC during this 7-day reset period, the reset process fails, and the 28-day counter continues accumulating.
**1-COM1
**2-COM2


===Unblocking Conditions===
*<file_type>
**0- Video
**1 - Photo


In order for device to be unblocked it must maintain a continuous connection to operators with non-restricted '''MCCs for a full 7 days'''. Additionally, the device must have an active time synchronization and an inserted SIM card. If the device connects to a restricted operator MCC during this period, the unblocking counter resets.
*<file_source>
**1 - Front camera
**2 - Rear camera
**3 - Both cameras


===Blocked Actions===
*<timestamp>
**Unix timestamps in decimal (not required for photo download)


While device is in a blocked state the following services are restricted:
*<duration>
<table class="nd-othertables_2" style="width:50%; border-collapse: collapse;">
**Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec)
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">Service</th>
<th style="width:1%; vertical-align: middle; text-align: center;">Status</th>
</tr>


<tr>
*<resolution> (<b>Only applied to photos</b>)
<td style="vertical-align: middle; text-align: center;"> Record Saving</td>
**0 – Use the resolution provided in the configuration
<td style="vertical-align: middle; text-align: center;">Stopped</td>
**1 – 160x120
</tr>
**2 – 320x240
**3 – 640x480
**4 – 1280x720
**5 – 1920x1080


<tr>
<td style="vertical-align: middle; text-align: center;"> Record Sending</td>
<td style="vertical-align: middle; text-align: center;">Stopped</td>
</tr>


<tr>
'''''camreq:'' Structure examples:'''
<td style="vertical-align: middle; text-align: center;">DOUT</td>
<td style="vertical-align: middle; text-align: center;">Disabled</td>
</tr>


<tr>
'''camreq:<file type>,<file source>(if video, add ",<timestamp>,<duration>)'''
<td style="vertical-align: middle; text-align: center;"><nowiki>*</nowiki>SMS/GPRS Commands</td>
<td style="vertical-align: middle; text-align: center;">Disabled</td>
</tr>


<tr>
However, if there is a need to send to the specific server without configuring, you can add two extra parameters.
<td style="vertical-align: middle; text-align: center;">Sleep Modes</td>
The complete structure:
<td style="vertical-align: middle; text-align: center;">Disabled</td>
</tr>


<tr>
'''camreq:<file type>,<file source>(if video, add ",<timestamp>,<duration>),<domain>,port'''
<td style="vertical-align: middle; text-align: center;">Features</td>
 
<td style="vertical-align: middle; text-align: center;">Disabled</td>
For example: camreq:0,1,1624960616,5,212.59.13.226,7160
</tr>
 
<tr>
'''camreq:1,<file source>,<domain>,<port>,<resolution>'''
<td style="vertical-align: middle; text-align: center;">Bluetooth</td>
 
<td style="vertical-align: middle; text-align: center;">Disabled</td>
Upload with domain, port, and resolution provided by a request. Example: camreq:1,1,192.168.1.1,12345,4
</tr>
 
<tr>
'''''icam_req:''  Structure examples:'''
<td style="vertical-align: middle; text-align: center;">CAN/OBD</td>
 
<td style="vertical-align: middle; text-align: center;">Disabled</td>
'''icam_req:<camera_type>,<peripheral>,<file_type>,<resolution>,<domain>,<port>
</tr>
 
</table>
Example: icam_req:1,2,0,1,192.168.1.1,1234
<nowiki>*</nowiki>'''Note:''' ''getgps'' command can be sent every 10 minutes to get location of the device
 
===Firmware Considerations===
'''icam_req:<camera_type>,<peripheral>,<file_type>,<timestamp>,<domain>,<port>
Firmware can not be downgraded below '''3.7.0''' where Country Blocking Service was introduced.
 
Example: icam_req:1,2,1,1609459200000,192.168.1.1,5678
 
'''icam_req:<camera_type>,<peripheral>,<file_type>,<timestamp>,<duration>
 
Example: icam_req:1,2,2,1609459200000,10
{| 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-30> 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>

Revision as of 13:33, 17 March 2026

Camera request command

A new camera request has been added, which allows the server to request files from a camera. It is also possible to to have two identical cameras connected at once. The format is as provided below in the table:

Command Arguments Explanation
camreq:

<file_type>
<file_source>
<timestamp>
<duration>
<domain>
<port>
<resolution>
(Only applied to photos)

Captures appropriate file with the provided details.
  • If the connection to server is opened, the files immediately become available for download. If not, then connection is attempted.
  • If <domain> and <port> parameters are included, the device will send footage of the command to that address.
  • If <resolution> parameter is included when requesting a photo, the device will send the photo with the selected resolution.

Please note, that if the resolution parameter is not included in the SMS/GPRS command, the device will request a photo with configured resolution.

icam_req:

<camera_type>
<peripheral>
<file_type>
<timestamp>
<duration>
<resolution>
<domain>
<port>

This command is used ONLY when both of the connected cameras are of the same type. It works only on DualCam or DashCam devices.

The arguments are as follows:

  • <camera_type>
    • 0-DSM
    • 1-MDAS
    • 2-DualCam front
    • 3-DualCam rear
    • 4-DashCam
  • <peripheral>
    • 1-COM1
    • 2-COM2
  • <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)
  • <resolution> (Only applied to photos)
    • 0 – Use the resolution provided in the configuration
    • 1 – 160x120
    • 2 – 320x240
    • 3 – 640x480
    • 4 – 1280x720
    • 5 – 1920x1080


camreq: 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

camreq:1,<file source>,<domain>,<port>,<resolution>

Upload with domain, port, and resolution provided by a request. Example: camreq:1,1,192.168.1.1,12345,4

icam_req: Structure examples:

icam_req:<camera_type>,<peripheral>,<file_type>,<resolution>,<domain>,<port>

Example: icam_req:1,2,0,1,192.168.1.1,1234

icam_req:<camera_type>,<peripheral>,<file_type>,<timestamp>,<domain>,<port>

Example: icam_req:1,2,1,1609459200000,192.168.1.1,5678

icam_req:<camera_type>,<peripheral>,<file_type>,<timestamp>,<duration>

Example: icam_req:1,2,2,1609459200000,10

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)


Video request from source <1-3> for <1-30> seconds since YYYY-MM-DD HH:MM:SS.

(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