Some of Teltonika Routers can send position data using Codec 8. The devices added:
Teltonika RUT850
Teltonika RUT955
[Changelog] teltonika protocol
8 days later
- Edited
There is an error in parameter acceleration.array parsing: device sends accelerometer values in mG units, while flespi converts it to G with division by 100 and not by 1000.
Fix will be installed today (Feb 17) at 17-00 UTC
8 days later
New scheme is applied to setdigout action setting for all device types for 1, 2, 3 and 4 outputs. Old format is marked as deprecated and will be removed in 2 weeks.
We have added a TLS support for the teltonika protocol.
Now you can generate your own PKI, then build a server certificate plus private key and use them in the channel configuration as shown on the screenshot below:
18 days later
Teltonika protocol updated - new CAN Adapter parameters are supported for FMB140 and other devices. The following parameters are registered:
- 232 CNG status - can.cng.status
- 233 CNG used - can.cng.consumed
- 234 CNG level - can.cng.level
- 388 Module ID 17B - can.module.id.hex
- 517 SecurityStateFlags_P4 - can.security.state.flags.bitmask
10 days later
- Edited
Teltonika protocol updated, added parsing of one more parameter for FMB devices:
- 636 UMTS/LTE Cell ID - gsm.cellid
FMB devices parameter bug fixes:
AVL ID 152 is stored as can.vehicle.battery.level. Was in conflict with AVL ID 113 battey.level
AVL ID 105 is stored as can.tracker.counted.mileage. Was in conflict with AVL ID 87
FMB640 devices update: AVL ID 143 Door status parsing updated with precise parsing scheme for each door: can.driver.door.status, can.passenger.door.status, can.rear.left.door, can.rear.right.door, can.hood.status, can.trunk.status, door.open.status
Some more of Teltonika Routers can send position data using Codec 8. The devices added:
Teltonika RUTX09
Teltonika RUTX10
Teltonika RUTX11
Teltonika RUTX12
- Edited
Bitwise parsing of security state flags is supported in flespi. This is a replacement for the parameter lvc.security.state.bitmask that will be removed in a week, 05-Apr-2021.
The mapping into flespi parameters is the following:
- Byte 0
CAN1-CAN3 connected states - can.connection.state.1 - can.connection.state.3 - Byte 2
0x04 – Battery charging - battery.charging.status
0x08 – Charging cable connected - cable.connected.status
0x10 – Vehicle working mode, 1-business mode, 0-private mode - private.status
0x20 – Bit appears when any operate button in car was put. This bit is reset if the button is released - button.pressed.status
0x40 – Bit appears when immobilizer is in service mode - immobilizer.service.status
0x80 – Immobiliser, bit appears during introduction of a programmed sequence of keys in the car - immobilizer.keys.status - Byte 3
0x01 – The key is in ignition lock - can.ignition.key.status
0x02 – Ignition on - can.engine.ignition.status
0x04 – Dynamic ignition on - can.dynamic.ignition.status
0x08 – Webasto - can.webasto.status
0x10 – Car closed - can.car.closed.status
0x20 – Car closed by factory's remote control - can.car.closed.remote.status
0x40 – Factory-installed alarm system is actuated (is in panic mode) - factory.alarm.actuated.status
0x80 – Factory-installed alarm system is emulated by module - factory.alarm.emulated.status - Byte 4
0x01 – Parking activated (automatic gearbox) - can.parking.status
0x10 – Handbrake is actuated (information available only with ignition on) - can.handbrake.status
0x20 – Footbrake is actuated (information available only with ignition on) - can.pedal.brake.status
0x40 – Engine is working (information available only when the ignition on) - can.engine.working.status
0x80 – Reverse is on - can.reverse.gear.status - Byte 5
0x01 – Front left door opened - can.driver.door.status
0x02 – Front right door opened - can.passenger.door.status
0x04 – Rear left door opened - can.rear.left.door.status
0x08 – Rear right door opened - can.rear.right.door.status
0x10 – Engine cover opened - can.hood.status
0x20 – Trunk door opened - can.trunk.status - Byte 6
0x01-0x05 – Different remote control states - car.remove.control.state
0x80 – CAN module goes to sleep mode - can.module.sleep.mode
a month later
- Edited
To resolve parameter names collision, parameter ID 303 Instant Movement now is stored into flespi parameter instant.movement.status.
Before the update Param ID 303 was registered as movement.status parameter, which was already taken by Param ID 240 Movement.
List of Teltonika Param IDs with affected device types can be found here.
a month later
Teltonika devices now can be configured over UDP connection
This update had been installed with some minor bug fixes in Teltonika device settings.
20 days later
15 days later
geofence AVL IDs parsing bug fixed.
previous logic was that number of geofence had been stored into geofence.id parameter, while its state was parsed as
0=false, 1=true ==> geofence.status
2=false, 3=true ==> overspeeding.status
The problem was when 1 message contained several geofence AVL IDs, so the parsing of the last AVL ID erased previously parsed geofence parameters.
The solution is - migrate geofence id to parameter index. So the new logic is
- geofence.id parameter will be removed
- value is parsed to
0=false, 1=true ==> geofence.status.INDEX_OF_GEOFENCE
2=false, 3=true ==> overspeeding.status.INDEX_OF_GEOFENCE
old logic and new logic are now working in parallel. Old logic will be removed July 21st
7 days later
FMB640 series added parsing of IDs:
16 to can.tracker.counted.mileage
216 to vehicle.mileage
New setting of Crash counter implemented for FMB series:
TST100 device parsing updated: 242 ==> mandown.alarm.status, 386 ==> position.fix.age
FMB640 series odoset setting added
a month later
Parameter ID=248 Immobilizer is supported for Teltonika FMB devices.
The following parameters are registered in flespi depending on Param ID=248 value:
- if immobilizer value is 0: ibutton.connected.status=false parameter is registered
- if immobilizer value is 1: ibutton.connected.status=true parameter is registered
- if immobilizer value is 2: both parameters ibutton.connected.status=true and ibutton.authorized.status=true are registered
20 days later
Bugfix in Setting for tst100 and tft100 device types:
motion_detection_sas setting was working not correctly: starting from the firmware 55.00.04++ it works the same way as for FMB series, thus setting motion_detection_sas moved to motion_detection with bitmask as sources.
2 months later
Minor updates:
- Dallas temperature sensor parsing suppression added for values 850, 2000, 3000, 4000, 5000 (it was enabled for 3000 only)
- Bugfix: the response from the device is added to command result for all commands
TLS setting added
11 days later
Minor updates:
- manual CAN elements parsing added for FMB640 series as manual.can.ID and manual.can.extended
- several bugfixes in parsing for telmetry data and command responses
