Default values changes since FMB firmware version 03.18.16.rev.00

We are always improving our solutions according Your feedback. The most important task for us is to make our provided IoT solutions as understandable as possible and improve performance from first usage. We understand how to achieve full potential of our products as fast as possible even for new clients. That’s why we are changing some of default configuration parameters values to make devices more efficient. For more information about changes, see the table below. You will find all changed parameters listed there along with explanation, why they were changed.

Default values changes

Name	Param ID	Old Value	New Value	Change explanation
Sleep Mode Time out, min	103	10	1440	Sleep time out set to 1440 min to avoid lost data when device wakes up from sleep mode. Which may be caused by GPS signal reacquisition time. As a result after short stops during the day device will not go to sleep. But when vehicle is stationary longer than 24 hours (1440 minutes), device will go to deep sleep, to preserve car battery.
Record saving/sending	107	After Position Fix	After Time Sync	Record saving and sending is now allowed with no valid GPS fix, most importantly the time must be synchronized. Records with synchronized time, but without GPS fix, will have zero coordinates.
Eco score allowed events	700	10	100	Eco score allowed events value was increased to 100 for more accurate evaluation.
NTP resync, h	901	0	3	Network Time resynchronization was previously disabled. Now it will occur every 3 hours, to improve internal clock reliability.
Open link timeout, s	1000	30	300	Records open link timeout between FMB device and AVL server extended to 300s. This will help to minimize GSM operator charges for link activation.
Sort by	1002	Newest	Oldest	Records sending sequence changed: Oldest records will be sent first. So the records sequence on server would be chronological.
Green Driving Max acceleration	11004	2.2	2.5	Values adjusted to get more accurate readings and avoid falsely triggering harsh acceleration event in Green driving scenario.
Green Driving Max braking	11005	2.5	2.7	Values adjusted to get more accurate readings and avoid falsely triggering harsh braking event in Green driving scenario.
Green Driving Max cornering	11006	2.1	3.4	Values adjusted to get more accurate readings and avoid falsely triggering harsh cornering event in Green driving scenario.
Crash Duration, ms	11401	5	20	Crash detection duration value altered to avoid generation of fake crash events.
Crash Threshold, mG	11402	1500	2500	Crash detection threshold value altered to avoid fake crash events.
Towing detection Event timeout, s	11603	0	10	Towing detection timeout set to 10 seconds to avoid fake towing events while entering the car. If Ignition is not turned on during this time, Towing event may be generated, because of vehicle vibrations caused by door opening and closing.
Movement start delay, s	19001	1	5	Movement start delay time extended to 5 seconds to eliminate fake events when vehicle is stationary.
Movement I/O element Averaging constant	50015	1	10	Movement I/O element state change is now registered only after 1 second (10 avg = 1 sec). Change is made in order to eliminate fake events.
Data mode I/O element Priority	50020	Low	None	Data mode I/O element is now disabled by default.
Speed I/O element Priority	50090	Low	None	Speed I/O element is now disabled by default. Speed element is always received along with GNSS information.
Active GSM operator I/O element	50140	None	Low	Operator code I/O element is now enabled by default and set to low priority.
Total odometer I/O element	50160	None	Low	Total odometer I/O element is now enabled by default and set to low priority.
Battery level % I/O element Event only parameter	50694	Yes	No	In case enabled, Battery level % I/O element value will be appended to every record, not just eventual records.
Blue-tooth status I/O element	50720	Low	None	Blue-tooth status I/O element is now disabled by default.
Blue-tooth status I/O element Event only parameter	50724	Yes	No	In case enabled, Blue-tooth status I/O element value will be appended to every record, not just eventual records.

Link back to FMB firmware errata