1,645
edits
Changes
Created page with "==Camera firmware version== Additional SMS/GPRS command for cameras’ firmware checking. Since both cameras are separate, there are two versions returned. {| class="wikitab..."
==Camera firmware version==
Additional SMS/GPRS command for cameras’ firmware checking. Since both cameras are separate, there are two versions returned.
{| 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;" |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>
Additional SMS/GPRS command for cameras’ firmware checking. Since both cameras are separate, there are two versions returned.
{| 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;" |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>
