Jump to content
  • EN

Test-AC: Difference between revisions

From Teltonika Telematics Wiki
← Older editNewer edit →
VisualWikitext
No edit summary
No edit summary
Line 1: Line 1:
https://wiki.teltonika-gps.com/view/Template:FTX_Features
==Camera request command==
=SECO Scenario=
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="2" 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 the connection is tried to be made. <br>If <b><domain></b> and <b><port></b> parameters are included, the device will send footage of the command to that address.<br>
If <b><resolution></b> parameter is included when requesting a photo, the device will send the photo with the selected resolution.
<br><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.
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |icam_req:
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |
''<camera_type><br>
''<peripheral><br>
''<file_type><br>
''<timestamp><br>
''<duration><br>
''<resolution><br>
''<domain><br>
''<port><br>
|}
The arguments are as follows:


===<u>Introduction</u>===
*<file_type>
[[File:FTX SECO.png|right|500px]]
**0 - Video
**1 - Photo


The purpose of Secure Engine Cut Off (SECO) is to bring a vehicle to a stop, in order to prevent unauthorized use. SECO disables the fuel pump, which would prevent the engine from continuing to run and stop the vehicle from being driven. For safety reasons, the system is designed to slow the vehicle down gradually in a controlled manner, ensuring that security measures do not compromise the driver’s or passengers’ safety. It is typically triggered by remote commands (SMS or GPRS) and is used for security or immobilization purposes.
*<file_source>
**1 - Front camera
**2 - Rear camera
**3 - Both cameras


===<u>Prerequisites</u>===
*<timestamp>
*At least one '''DOUT''' is available.
**Unix timestamps in decimal (not required for photo download)
*'''SECO functionality''' should have DOUT control priority higher than '''Immobilizer''' scenario.


===<u>How It Works</u>===
*<duration>
Firstly, in order to safely slow down vehicle the systems toggles the relay, which is connected to fuel pump ('''GNSS Available'''). Secondly, at a safe speed, the system tuns on DOUT permanently in order to stop the vehicle ('''Speed Pulse'''). Last mode is activated in case no GNSS fix is available ('''GNSS Unavailable''').
**Video duration in seconds from provided timestamps (not required for photo download), (max 30 sec)


'''Speed Pulse'''
*<resolution> (<b>Only applied to photos</b>)
**0 – Use the resolution provided in the configuration
**1 – 160x120
**2 – 320x240
**3 – 640x480
**4 – 1280x720
**5 – 1920x1080


DOUT control starts when the vehicle speed goes below a configured speed threshold and remains below this threshold for a specified speed check period. As soon as that happens DOUT is activated.
*<type>
**0-DSM
**1-MDAS
**2-DualCam front
**3-DualCam rear
**4-DashCam


The timer will be reset if the vehicle speed increases above the configured speed threshold.
*<Peripheral>
**1-COM1
**2-COM2
'''''camreq:'' Structure examples:'''


'''GNSS Available'''
'''camreq:<file type>,<file source>(if video, add ",<timestamp>,<duration>)'''


This mode requires a GNSS fix to be present before DOUT control begins.  
However, if there is a need to send to the specific server without configuring, you can add two extra parameters.  
The complete structure:


DOUT pulsing starts when the vehicle speed drops below a configured speed pulse threshold and the speed remains below this threshold for a specified speed check period.
'''camreq:<file type>,<file source>(if video, add ",<timestamp>,<duration>),<domain>,port'''


'''GNSS Unavailable'''
For example: camreq:0,1,1624960616,5,212.59.13.226,7160


This mode is used when a GNSS fix is not available.
'''camreq:1,<file source>,<domain>,<port>,<resolution>'''


In this mode, the system initiates DOUT control only if the vehicle is stationary, location data is unavailable, and the movement timeout condition is met.
Upload with domain, port, and resolution provided by a request. Example: camreq:1,1,192.168.1.1,12345,4


'''Note:''' If there is no GNSS fix available and “secoon” command is sent, the system waits for the movement timeout to be reached before activating the configured DOUT. This approach ensures that the vehicle is stationary prior to disabling the fuel supply.
'''''icam_req:''  Structure examples:'''


=== <u> Parameters list </u>===
'''icam_req:<camera_type>,<peripheral>,<file_type>,<resolution>,<domain>,<port>
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>


<td style="vertical-align: middle; text-align: center;"> SECO DOUT status </td>
Usage example: 1,2,0,1,server.com,1234
<td style="vertical-align: middle; text-align: center;"> 396</td>
<td style="vertical-align: middle; text-align: center;"> SECO DOUT status. </td>
<td style="vertical-align: middle; text-align: left;">'''0''' = SECO DOUT is '''OFF''' <br> '''1''' = SECO DOUT is '''pulsing''' <br> '''2''' = SECO DOUT is '''ON''' </td>


</tr>  
'''icam_req:<camera_type>,<peripheral>,<file_type>,<timestamp>,<domain>,<port>
<tr>


<td style="vertical-align: middle; text-align: center;"> Priority </td>
Usage example: 1,2,1,1609459200000,server2.com,5678
<td style="vertical-align: middle; text-align: center;"> 1039600 </td>
<td style="vertical-align: middle; text-align: center;"> Priority of how events are being sent to a server. For example, events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur. </td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = SECO  scenario is '''disabled''' <br> '''1''' = SECO scenario is '''low''' <br> '''2''' = SECO scenario is '''high''' <br>
</td>


</tr>  
'''icam_req:<camera_type>,<peripheral>,<file_type>,<timestamp>,<duration>
<tr>


<td style="vertical-align: middle; text-align: center;"> Speed </td>
Usage example: 1,2,2,1609459200000,10
<td style="vertical-align: middle; text-align: center;"> 12254 </td>
{| class="wikitable"
<td style="vertical-align: middle; text-align: center;"> Speed threshold at which the configured digital output (DOUT) will be activated. </td>
|+
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''255''' <br> Default value = '''10''' </td>
! 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>.


</tr>
'''(If  photo request)'''
<tr>


<td style="vertical-align: middle; text-align: center;"> Speed pulse scenario </td>
<td style="vertical-align: middle; text-align: center;"> 12259 </td>
<td style="vertical-align: middle; text-align: center;">
Speed threshold at which the configured digital output (DOUT) will be toggled. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''255''' <br>Default value = '''10''' </td>


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


<td style="vertical-align: middle; text-align: center;">
'''(If  video request)'''
Speed check period </td>
| colspan="2" |Preparing to send file  from timestamp <timestamp of the file>
<td style="vertical-align: middle; text-align: center;"> 12255 </td>
|-
<td style="vertical-align: middle; text-align: center;"> Time span during which speed must be lower than configured for output to activate (GNSS on). </td>
| 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
<td style="vertical-align: middle; text-align: left;">  Minimum value = '''0'''<br> Maximum value = '''65535''' <br>Default value = '''10''' </td>
| colspan="2" |Already connected. Preparing to send file from timestamp <timestamp of the file>
 
|-
</tr>
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Request received but the capture  failed
<tr>
| colspan="2" |Error: capture failed
 
|-
<td style="vertical-align: middle; text-align: center;">
|Request received but the device  cannot proceed with the capture and sending because ignition is off
Movement timeout</td>
| colspan="2" |Error: Cannot capture  because ignition is off
<td style="vertical-align: middle; text-align: center;"> 12256 </td>
|-
<td style="vertical-align: middle; text-align: center;"> Duration after which the DOUT will be activated if no movement is detected and GNSS is off. </td>
|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
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''65535''' <br>Default value = '''30''' </td>
| colspan="2" |Warning: Photo / Video  already captured previously, trying to send it
 
|-
</tr>
|Request received but the device was already connected to the server. New media is not captured. The device is ready to send previous capture
<tr>
| colspan="2" |Already connected. Warning: Photo / Video already captured previously, trying to send it
 
|-
<td style="vertical-align: middle; text-align: center;">Eventual records</td>
|Request received but the camera doesn’t acknowledge sent command. Nothing will be sent
<td style="vertical-align: middle; text-align: center;"> 1039604</td>
| colspan="2" |Error: DualCam NAK
<td style="vertical-align: middle; text-align: center;">Enables feature status sending only when the event happens (an eventual record). When disabled, feature status will be sent with both eventual and periodical records.</td>
|-
<td style="vertical-align: middle; text-align: left;"> '''0''' = SECO status will be sent with both eventual and periodical records. <br> '''1''' = SECO status will be sent only when the event happens (an eventual record).</td>
|Request received but the camera is  not connected or not working
 
| colspan="2" |Error: DualCam not  present
</tr>
|-
<tr>
|Request received but the camera is  not connected or not working
 
| colspan="2" |Error: requested file  does not exist
<td style="vertical-align: middle; text-align: center;">Output control</td>
|-
<td style="vertical-align: middle; text-align: center;">12252</td>
|Request received but the device  cannot connect to the server
<td style="vertical-align: middle; text-align: center;">
| colspan="2" |Error: connect to  server
Digital output used for connection to fuel pump to gradually stop the vehicle. </td>
|-
<td style="vertical-align: middle; text-align: left;"> '''0''' = DOUT control is disabled <br> '''1''' = DOUT1 is controlled <br> '''2''' = DOUT2 is controlled <br> '''3''' = DOUT3 is controlled <br> '''4''' = DOUT4 is controlled</td>
|Request received but the modem is  not ready for operation (network or modem issue)
 
| colspan="2" |Error: modem not ready  to start send
</tr>
|-
<tr>
|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
<td style="vertical-align: middle; text-align: center;">Output pulse</td>
|-
<td style="vertical-align: middle; text-align: center;">12253</td>
|Request received but file capture time was exceeded.
<td style="vertical-align: middle; text-align: center;">Pulse functionality adds additional output control which helps to slow down vehicle before fully disabling fuel pump.</td>
| colspan="2" |Error: Media request  timeout
<td style="vertical-align: middle; text-align: left;"> '''0''' = Disabled <br> '''1''' = Enabled </td>
|-
 
|Request received but capture  completed incorrectly
</tr>
| colspan="2" |Error: Media request problem
<tr>
|-
 
|File type parameter incorrect in the  request command
<td style="vertical-align: middle; text-align: center;">
| rowspan="4" |Error: Invalid
DOUT on duration</td>
|File Type
<td style="vertical-align: middle; text-align: center;">12257</td>
| rowspan="4" |argument  in camera request cmd!
<td style="vertical-align: middle; text-align: center;"> Duration for how long DOUT should be active.</td>
|-
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''10'''<br> Maximum value = '''5000''' <br>Default value = '''1000''' </td>
|File Source parameter incorrect in  the request command
 
|File Source
</tr>
|-
<tr>
|Timestamp parameter incorrect in the request command
 
|Timestamp
<td style="vertical-align: middle; text-align: center;">DOUT off duration</td>
<td style="vertical-align: middle; text-align: center;">12258</td>
<td style="vertical-align: middle; text-align: center;"> A value in milliseconds, for how long DOUT should be inactive. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''10'''<br> Maximum value = '''5000''' <br>Default value = '''1000''' </td>
 
</tr>
</table>
 
<!---For Template:FTX SMS/GPRS Commands--->
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}}{{FTX Pin Support List|model={{{model}}}|pin=DOUT2}}{{FTX Pin Support List|model={{{model}}}|pin=DOUT3}}
|
===SECO Commands===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:20%; vertical-align: middle; text-align: left;">COMMAND</th>
<th style="width:45%; vertical-align: middle; text-align: left;">DESCRIPTION</th>
<th style="width:35%; vertical-align: middle; text-align: left;">SYNTAX EXAMPLE</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">[[SMS/GPRS command - secooff|secooff]]</td>
<td style="vertical-align: middle; text-align: left;">Deactivate SECO scenario.</td>
<td style="vertical-align: middle; text-align: left;"><code>secooff</code></td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">[[SMS/GPRS command - secoon|secoon]]</td>
<td style="vertical-align: middle; text-align: left;">Activate SECO scenario.</td>
<td style="vertical-align: middle; text-align: left;"><code>secoon</code></td>
</tr>
</table>
}}
 
----
https://wiki.teltonika-gps.com/index.php?title=Template:FTX_Mobile_network
 
==Server settings== 
[[File:FTX server settings.png|right|500x800px]]
===Primary server settings===
'''Domain'''
*Server or Domain address, either IP address or Domain can be written.
'''Port'''
*Server Port.
'''Data protocol'''
*TCP (Transmission control protocol) or UDP (User datagram protocol). Changing this parameter will alter how the device communicates. From the device side, TCP and UDP work almost the same, the only difference is that UDP doesn't need additional confirmation from the server side, that the data packet was received. TCP has that and uses more network data for the confirmation. The desired data transfer protocol can be selected through the configurator. For more information on the protocol differences of Teltonika devices, refer here [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols]
----
'''New description added''' <br>
<span style="color:#00FF00;">'''Encryption'''
*TLS/DTLS are security protocols that protect information sent over a network by encrypting the data so only the intended recipient can read it. These Protocols help authenticate devices communicating with the server and ensure data integrity during transmission. TLS/DTLS encryption creates a secure, private connection so sensitive data can travel safely across networks.</span>
 
*In order to utilize TLS/DTLS encryption, server certificates must be uploaded via '''Teltonika Configurator Tool (TCT)''' or '''FOTA Web''' using '''Upload user TLS certificate''' task. For more information please reference [[{{{model}}} Device status]].
 
*'''Note:''' Currently Encryption is supported only if TCP/UDP data protocol is used. MQTT + TLS is not supported in '''Firmware version 3.7.0''' at this time.
 
----
===Secondary server settings===
'''Mode'''
*Backup - Records are sent to second server while main server is not available.
*Duplicate - records are sent to both servers (main and second), records are deleted from Flash storage only if both servers confirmed that the records were received from device.
 
{| class="wikitable"
|+ Secondary server parameters
|-
|-
! Parameter !! Parameter ID !! Values
|Duration parameter incorrect in the  request command
|Duration
|-
|-
| Second server type || 2010 || 0 - Disable, 1 - Backup, 2 - Duplicate
|Cannot proceed with the request,  ignition is off
| colspan="3" |Error: Ignition not  detected!
|-
|-
| Secondary server IP or DNS address || 2007 || String
|Request command structure incorrect
| colspan="3" |Error: Invalid camera  request command!
|-
|-
| Secondary server port || 2008 || Integer
|RS232 and DualCam mode is not  enabled
| colspan="3" |Error: DualCam is not  configured!
|-
|-
| Secondary server protocol || 2009 || 0 - TCP, 1 - UDP
|Front or rear camera not found
| colspan="3" |Error: Front / Rear  Camera not present
|}
|}
 
<br>
https://wiki.teltonika-gps.com/view/Template:FTX_Features
=GNSS Fuel Counter=
[[File:FTX GNSS fuel counter.png|right|500px]]
 
===<u>Introduction</u>===
The Fuel Counter GNSS scenario provides fuel consumption estimation using GNSS-derived distance and user-configured fuel rate. It calculates the amount of fuel used by multiplying traveled distance by the average fuel rate and converting it to appropriate units. It is a software-based alternative when fuel flow sensors are not available.
===<u>How It Works</u>===
The scenario monitors GNSS data and updates fuel usage whenever valid  GNSS PVT(Position, Velocity, Time) messages are received and movement is detected. It also supports runtime reconfiguration to keep fuel usage parameters in sync with user changes.
 
*On device startup, the scenario:
**Checks for a retained value of previously used fuel.
**If found, it restores this value and updates the corresponding I/O element.
**If no retained value is found, the system uses the current configuration parameter (user-defined or default), stores it in retained RAM for future startups, and updates the I/O element.
 
When GNSS messages are received, the scenario determines whether they represent a GNSS source event or position data, and, if valid movement is detected, updates both distance traveled and fuel consumption.
 
If the scenario is enabled and the user modifies the average fuel usage parameter, it automatically detects any deviation between the configuration and the current I/O value and synchronizes them.
=== <u> Parameters list </u>===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Scenario priority </td>
<td style="vertical-align: middle; text-align: center;"> 1001200<br>(12)</td>
<td style="vertical-align: middle; text-align: center;">Priority of how events are being sent to a server. For example, events with low priority are added to the periodical record, and events with high priority are sent immediately after they occur.</td>
<td style="vertical-align: middle; text-align: left;">  '''0'''=Disable <br>  '''1'''=Low priority <br>  '''2'''=High priority </td>
 
</tr> 
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Average consumption </td>
<td style="vertical-align: middle; text-align: center;"> 11902 </td>
<td style="vertical-align: middle; text-align: center;">Average consumption presented in the technical documentation of the vehicle.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''50.0''' <br> Default value = '''0.0''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">
Fuel counter value</td>
<td style="vertical-align: middle; text-align: center;"> 11910 </td>
<td style="vertical-align: middle; text-align: center;">The initial fuel counter value in litres. Can be used to set the starting value or reset the current one.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''4294967.2''' <br> Default value = '''0.0''' </td>
 
</tr>
</table>

Revision as of 10:59, 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, them files immediately become available for download. If not, then the connection is tried to be made.
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>

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

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>

Usage example: 1,2,0,1,server.com,1234

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

Usage example: 1,2,1,1609459200000,server2.com,5678

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

Usage example: 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


Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Test-AC&oldid=111856"