- Edited
Ruptela protocol updated: ident parsing fixed. Now idents always consist of 15 digits (IMEI of device).
[Changelog] ruptela protocol
5 days later
IO_ID 481: CAN Fuel level 2 is supported for ruptela protocol.
10 days later
- Edited
IO_ID 626: CAN DTC Indication lights is supported for ruptela protocol
10 days later
IO_ID 141: ECO normal speed distance is supported as segment.normal.speed.distance parameter
IO_ID 142: ECO cruise control distance is supported as segment.cruise.control.distance parameter
IO_ID 143: ECO cornering counter is supported as segment.cruise.control.distance parameter
for ruptela protocol
7 days later
The following IO_IDs are supported for ruptela protocol:
IO_ID 584: G Peak X - max.x.acceleration
IO_ID 585: G Peak Y - max.y.acceleration
IO_ID 586: G Peak Z - max.z.acceleration
5 days later
Ruptela protocol updated: parameter can.liquid.sensor.fuel.volume (IO_ID 205) is renamed to can.fuel.volume
For backward compatibility both parameters are registered for now. Old parameter will be removed 25 Nov 2019.
Settings added:
secondary server for connectivity card
Eco-driving over speeding limit (as a wrapper for setcfg/getcfg ParameterID 400)
- Edited
Settings added:
econnect - to force device for a single connection to specified IP:port
data_sending - Enable/Disable, Min records, Period, Link timeout - configuration group
data_collection - Enable/Disable, Logging interval, Time without engine, Engine detection - configuration group
coefficients - for Distance, Time with engine and Radial - configuration group
3 months later
Constant link, keep-alive and heartbeat setting added for connection profiles
Parsing of IO IDs 104 - 106, 123 - 125, 152 - 154 for vehicle.vin corrected. Contact us if you note some misparsing for vehicle.vin parameter.
4 months later
- Edited
Next Monday, 2020-07-20 we are planning to install an update for Ruptela protocol, that introduces the following changes in channel commands:
- custom command will have new schema
{
"address": [
"connection"
],
"description": "Send command over GPRS",
"name": "custom",
"schema": {
"additionalProperties": false,
"description": "Send command over GPRS",
"properties": {
"command_id": {
"maximum": 256,
"minimum": 100,
"title": "Command ID",
"type": "integer"
},
"hex": {
"default": false,
"title": "Command payload is encoded as HEX string",
"type": "boolean"
},
"payload": {
"maxLength": 1000,
"minLength": 0,
"title": "Command payload",
"type": "string"
}
},
"required": [
"command_id",
"payload"
],
"title": "Custom Command",
"type": "object",
"x-view-order": [
"command_id",
"payload",
"hex"
]
},
"title": "Custom Command"
}- commands garmin_data, garmin_status, dtc_codes will be removed (custom command may be used instead now)
You may contact us with any concerns or suggestions on this matter.
7 days later
15 days later
Ruptela protocol updated - new IO_IDs added:
- 538: CAN door lock state - is registered as can.central.lock.status
- 573: CAN LCV configuration - is registered as can.lvc.module.control.bitmask
- 574: CAN Interface configuration - is registered as can.configuration.bitmask
a month later
Ruptela protocol updated: Command 14/114 Transparent Channel data suppored.
The following parameters are registered in channel message for Command 14 packet:
- port.id - port ID, possible values: 0 – port A, 1 – port B, 2 – port C (4th generation).
- timestamp - timestamp of the payload data.
- payload.hex - raw data from port
- Edited
Ruptela protocol allows transparently send data to the external devices connected through RS232 interface.
Command 114 is used for this purpose.
Below is a curl example showing how such command can be send to the device connected to flespi channel:
curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: FlespiToken <XXXX>' \
-d '[{"address":{"ident":"<IDENT>","type":"connection"},"name":"custom","properties":{"command_id":114,"payload":"01000068656C6C6F2066726F6D20666C65737069","hex":true},"ttl":86400}]' \
'https://flespi.io/gw/channels/<CHANNEL_ID>/commands-queue'
Command payload 01000068656C6C6F2066726F6D20666C65737069 consist of:
01 - Port ID
0000 - Reserved bytes
68656C6C6F2066726F6D20666C65737069 - Payload data to be transmitted to RS232 device's port.
6 months later
The list of supported Ruptela devices is enhanced with the following ones:
Several new IO IDs are supported for Ruptela protocol:
- 722 OBD Electric vehicle battery level - flespi parameter can.vehicle.battery.level
- 723 OBD Electric vehicle remaining distance - flespi parameter can.vehicle.remaining.distance
- 739 Autogeofence alert - flespi parameter auto.geofence.alert
Ruptela protocol updated: parsing of can.fuel.level is corrected according to the protocol documentation: multiplier 0.4 is applied to calculate the fuel level percentage.
16 days later
The following IO IDs are supported for Ruptela protocol:
- 717 Last snapshot info - if non-zero value is present, parameters adas.alert.id, adas.snapshot.source, adas.snapshot.timestamp are registered
- 718 Fatigue sensor snapshot on SD card - parameter adas.snapshots.count
7 days later
setlock action setting added for Ruptela FM-Tco4 LCV, Ruptela LCV5, Ruptela Trace5
Setting format may slightly change after live tests
