Difference between revisions of "Template:FMB640 SMS/GPRS command list"
Marius Bakas (talk | contribs) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 57: | Line 57: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| − | <td style="text-align: center;">''[[ | + | <td style="text-align: center;">''[[FMX6 getinfo|getinfo]]''</td> |
<td style="text-align: left;">Device runtime system information</td> | <td style="text-align: left;">Device runtime system information</td> | ||
<td style="text-align: center;">Yes</td> | <td style="text-align: center;">Yes</td> | ||
| Line 109: | Line 109: | ||
<td style="text-align: center;">''resetlimits''</td> | <td style="text-align: center;">''resetlimits''</td> | ||
<td style="text-align: left;">Resets data counters</td> | <td style="text-align: left;">Resets data counters</td> | ||
| + | <td style="text-align: center;">Yes</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td style="text-align: center;">''getlimits''</td> | ||
| + | <td style="text-align: left;">Gets home/roaming uploaded data information</td> | ||
<td style="text-align: center;">Yes</td> | <td style="text-align: center;">Yes</td> | ||
</tr> | </tr> | ||
| Line 121: | Line 126: | ||
<td style="text-align: center;">Yes</td> | <td style="text-align: center;">Yes</td> | ||
</tr> | </tr> | ||
| + | |||
| + | |||
| + | |||
<tr> | <tr> | ||
<td style="text-align: center;">{{{cmd_setdigout|''[[FMB setdigout|setdigout]] XXXX Y1 Y2 Y3 Y4''}}}</td> | <td style="text-align: center;">{{{cmd_setdigout|''[[FMB setdigout|setdigout]] XXXX Y1 Y2 Y3 Y4''}}}</td> | ||
| Line 190: | Line 198: | ||
<td style="text-align: center;">Yes</td> | <td style="text-align: center;">Yes</td> | ||
</tr> | </tr> | ||
| + | <tr> | ||
| + | <td style="text-align: center;">''[[Tracking_on_Demand|on_demand_trackingX]]''</td> | ||
| + | <td style="text-align: left;"> | ||
| + | X=0 – Stops Tracking on Demand functionality.<br /> | ||
| + | X=1 – Starts Tracking on Demand functionality.<br /> | ||
| + | X=2 – Generates one high priority record and inititates data sending to server.<br /> | ||
| + | </td> | ||
| + | <td style="text-align: center;">Yes</td> | ||
| + | </tr> | ||
</table> | </table> | ||
{{{sect_can|{{Template:FMB640 CAN SMS/GRPS commands}}}}} | {{{sect_can|{{Template:FMB640 CAN SMS/GRPS commands}}}}} | ||
Latest revision as of 17:05, 28 November 2022
All commands are case sensitive. When user tries to send SMS/GPRS message to FMB640 that operates in Deep Sleep mode, it cannot arrive to FMB640 device because the GSM/GPRS module is disabled most of the time. FMB640 will receive the SMS/GPRS message when it exits Deep Sleep mode.
If FMB640 is in GPS Sleep or Online Deep Sleep mode, sent SMS/GPRS message will arrive to the device.
SMS command structure:
<SMS login><space><SMS password><space><command><space><value>
SMS command getinfo example:
- If you have set SMS login and password:
login pass getinfo - If SMS login and password are not set leave two spaces before command:
getinfo
Common commands
| Command | Description | Response |
|---|---|---|
| getstatus | Modem Status information | Yes |
| getrecord | SMS command initiates saving and sending of high priority record | No |
| getcfgtime | Date and Time of last successful configuration | Yes |
| getgps | Current GPS data and time | Yes |
| getnmeainfo | NMEA error debug SMS | Yes |
| cpureset | Reset CPU | No |
| defaultcfg | Reset configuration to default | Yes |
| getver | Device / Modem / Code version information | Yes |
| getinfo | Device runtime system information | Yes |
| tacho_connect | Connect to Web Tacho immediately | Yes |
| web_connect | Connect to Fota WEB immediately | Yes |
| deleterecords | Delete all records saved on FLASH | Yes |
| getio | Readout digital inputs and outputs, analog inputs | Yes |
| banlist | Banlist information | Yes |
| crashlog | Crash log information | Yes |
| delete_all_sms | Delete all read SMS | Yes |
| braminfo | BatRam info | Yes |
| getgnss | Current GNSS information | Yes |
| resetlimits | Resets data counters | Yes |
| getlimits | Gets home/roaming uploaded data information | Yes |
| scanfms | Shows FMS elements that can be read from vehicle | Yes |
| readio # | Returns IO status, # AVL ID | Yes |
| setdigout XXXX Y1 Y2 Y3 Y4 | Set digital output 1. # – 0; 1 or ? (0 - OFF, 1 – ON or ? – Ignore) for DOUT1 |
Yes |
| getparam # | Readout parameter value according entered ID. # - ID value |
Yes |
| setparam #:# | Sets selected parameter value 1.# - first ID value |
Yes |
| setparam #:#;#:#;… | ||
| flush #,#,#,#,#,#,# | Redirects device to other server 1.# - IMEI |
Yes |
| Command | Description | Response |
|---|---|---|
| odoset:# | Set total odometer value # - new odometer value in m |
Yes |
| odoget | Display current odometer value | Yes |
| odinfo | Odometer Debug info | Yes |
| on_demand_trackingX |
X=0 – Stops Tracking on Demand functionality. |
Yes |
| Command | Description | Response |
|---|---|---|
| lvcansetprog # | Set program number to LV-CAN200/ ALL-CAN300 that is connected to FMx640. # - three digit number that identity vehicle | Yes |
| lvcansimpletacho # | Add or remove simpletacho start byte. # - 0 or 1 (0 – don’t add start byte, 1 – add start byte) | No |
| lvcangetprog | Get program number from LV-CAN200/ ALL-CAN300 that is connected to FMx640 | Yes |
| lvcangetinfo | Get information about connected LV-CAN200/ALL-CAN300 | Yes |
| lvcanclear # | Clear Total Mileage (counted), Engine Work Time (counted), Fuel Consumed (counted) parameters values. # - parameter (0 – Engine work time (counted), 1 – Fuel Consumed (counted), 2 – Vehicle Mileage (counted)) | Yes |
