rightfinance.blogg.se

Id3 editor save template
Id3 editor save template






id3 editor save template

Note: Note: I/O element’s “Movement sensor” Averaging constant is interpreted as Start Move Timeout in seconds (from 1 to 59). In Deep Sleep mode there is no Averaging. 1 Averaging constant value equals about 30 miliseconds. If I/O value is entering or leaving predefined range, it must have same value for Averaging constant time. Averaging constant allows setting I/O event delay (averaging). Sometimes it is necessary to wait some time interval before event generating. In some applications there is no need to generate events on every I/O range enter/exit immediately.

id3 editor save template

“Generate event” parameter defines when to generate event – when value enters defined range, exits it or both.Īveraging constant – it is an I/O event delay parameter. If I/O value enters or exits this range, FM3612 generates event. High and Low levels – define I/O value range. Panic priority triggers same actions as high priority, but if GPRS fails, it sends AVL packet using SMS mode if SMS is enabled in SMS settings.

id3 editor save template

When High priority is selected, module makes additional record with high priority flag and sends event packet immediately to the server by GPRS. When low priority event is triggered, FM3612 makes additional record with indication that the reason for that was I/O element change. Regular packets are sent as Low priority records. Priority (AVL packet priority) can be low, high or panic. By default all I/O element are disabled and FM3612 records only GNSS coordinates. I/O settings allow defining I/O event criteria.Įnabled or disabled field – allows enabling I/O element so it is added to the data packet and is sent to the server. Event generating method is used when additional AVL packet is needed when current value of I/O exceeds predefined High and Low levels. Monitoring method is used when current I/O information needed with regular GNSS coordinates. Note: There are two types of operations with Permanent I/O elements: simple monitoring and event generating. Value range: 0- 99999999 liters* “Total Fuel Used” is sent to server multiplied by 10.Įxample: if value was 150.5 liters, “1505” will be sent to server. It provides unique number which assigned to a set of base GSM stations.ġ0 * Degrees (☌), -55 - +115, if 3000 – Dallas errorĭistance which device has been traveled with ignition ON: mġst connected dallas temperature sensor IDĢnd connected dallas temperature sensor IDģrd connected dallas temperature sensor IDĤrd connected dallas temperature sensor IDĮventual I/O elements (generate and send record to server only if appropriate conditions are met)Įvent: 0 – target left zone, 1 – target entered zoneġ – harsh acceleration, 2 – harsh braking, 3 – harsh corneringĭepending on green driving type: if harsh acceleration or braking – g*100 (value 123 -> 1.23g), if harsh cornering – degrees (value in radians)Īt over speeding start km/h, at over speeding end km/h

#Id3 editor save template code#

Location Area code (LAC), it depends on GSM operator. Permanent I/O elements (are always sent to server if enabled)Ģ – GPS ready (antenna is working, but with no GPS fix)ģ – GPS working (antenna is working and has GPS fix)Ĥ – GPS sleep (when device is in GPS sleep mode)ĥ – Overcurrent (The only condition to get value 5, then antenna is damaged and short circuit)Ġ – home on stop, 1 – home on move, 2 – roaming on stop, 3 – roaming on move, 4 – unknown on stop, 5 – unknown on moveĠ – not deep sleep mode, 1 – deep sleep mode After enabling I/O element(s) AVL packet along with GNSS information contains current value(s) of enabled I/O element. When no I/O element is enabled, AVL packet comes with GNSS information only.








Id3 editor save template