Difference between revisions of "Template:FMB I/O settings"
From Wiki Knowledge Base | Teltonika GPS
Atabasnikov (talk | contribs) |
|||
| (38 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | When no I/O element is enabled, AVL packet comes with GNSS information only. After enabling I/O element(s) AVL packet along with GNSS information contains current value(s) of enabled I/O element.<br/>Current value – if device is connected to configurator all current I/O values are displayed in this column.<br/>Priority field – allows enabling I/O element and set them priority so it is added to the data packet and is sent to the server. By default 12 I/O elements with low priority are enabled: Ignition, Movement, Data Mode, GSM Signal, Sleep mode, GNSS Status, GNSS PDOP, GNSS HDOP, External Voltage, Speed, Battery Voltage and Battery Current. Priority (AVL packet priority) can be Low, High or Panic. All records made by FMB120 are regular. Regular packets are sent as Low priority records. When low priority event is triggered, FMB120 makes additional record with indication that the reason for that was I/O element change (depends from Operand configuration). When High priority is selected, module makes additional record with high priority flag and sends event packet immediately to the server by GPRS. Panic priority triggers same actions as high priority, but if GPRS fails, it sends AVL packet using SMS data sending mode if SMS data sending is enabled and data send number is written in SMS/Call Settings.<br/>High and Low levels – define I/O value range. If I/O value enters or exits this range, FMB120 generates event. “Operand” parameter defines when to generate event: On Exit, On Entrance, On Both, On Hysteresis and On Delta Change.<br/>Event only - when selected NO, I/O element status value will be appeared in each AVL record, and when selected YES, I/O element status value will be appended only to eventual records. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Operands== | ==Operands== | ||
| − | + | ||
===Operand On Exit=== | ===Operand On Exit=== | ||
| − | Record is generated when input | + | Record is generated when actual value input increases and becomes higher than high level or decreases and become lower than low level. |
| − | [[Image:Fmb120_on_exit.png|x150px| | + | [[Image:Fmb120_on_exit.png|x150px|center]] |
| + | |||
===Operand On Entrance=== | ===Operand On Entrance=== | ||
| − | + | Record is generated when actual value input increases or decreases and becomes between high and low level values. | |
| − | Record is generated when input | + | [[Image:Fmb120_on_entrance.png|x150px|center]] |
| − | [[Image:Fmb120_on_entrance.png|x150px| | + | |
===Operand On Both=== | ===Operand On Both=== | ||
| − | + | Record is generated by both (On Exit and On Entrance) operands logic at same time. | |
| − | Record is generated by both | + | [[Image:Fmb120_on_both.png|x150px|center]] |
| − | [[Image:Fmb120_on_both.png|x150px| | + | |
===Operand Monitoring=== | ===Operand Monitoring=== | ||
| − | + | No event at all. Values are recorded only when other trigger have worked. | |
| − | No event at all. Values are recorded only when other | + | [[Image:Fmb120_operand_monitoring.png|x150px|center]] |
| − | [[Image:Fmb120_operand_monitoring.png|x150px| | + | |
===Operand On Hysteresis=== | ===Operand On Hysteresis=== | ||
| − | + | Record is generated when actual value input inceases from lower than low value to higher | |
| − | Record is generated when input value | + | than high level value or decreasing from higher than high level to lower than low level. |
| − | [[Image:Fmb120_on_hysteresis.png|350px| | + | [[Image:Fmb120_on_hysteresis.png|350px|center]] |
| + | |||
===Operand On Change=== | ===Operand On Change=== | ||
| − | + | Record is generated when value changes. | |
| − | Record is generated when | + | [[Image:Fmb120_on_change.png|x150px|center]] |
| − | [[Image:Fmb120_on_change.png|x150px| | + | |
===Operand On Delta Change=== | ===Operand On Delta Change=== | ||
| − | + | Record is generated when value changes and absolute value of last value minus actual input value becomes equal or higher than high level value. | |
| − | Record is generated when | + | [[Image:Fmb120_on_delta_change.png|x150px|center]] |
| − | [[Image:Fmb120_on_delta_change.png|x150px| | + | |
==Avg Const== | ==Avg Const== | ||
| − | If | + | If avg const value is 10, new value must be present for 1 second to register change to new value. Internally sampling is done every 40ms, so 25 samples are taken in second. To configure 5 seconds averaging multiply 10 by 5 yielding 50. The same logic works even if device is in deep sleep mode.<br/>Averaging follows RC exponential curves, see image below: |
| − | [[Image:Fmb120_avg_const.png|300px| | + | [[Image:Fmb120_avg_const.png|300px|center]] |
| − | For Boolean values | + | For Boolean values 5τ, values is used, that means value change is taken when new values is averaged to more then 99.3%. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ==OBD II (Bluetooth) and LVCAN I/O elements== | |
| − | + | In OBD II (Bluetooth) column are shown I/O elements which information can be obtained from OBD II Bluetooth dongle connected to FMB120 device and in LVCAN column are shown I/O elements whitch information can be obtained from LV-CAN200 or ALL-CAN300 connected to FMB120 device. All I/O configuration is the same as described in [[FMB120 I/O settings|I/O settings]] section, except OBD II (Bluetooth) I/O element don’t have averaging constant parameter.<br/>Detailed description about LVCAN I/O element configuration described in [[FMB120 CAN adapters|FMB120 with LV-CAN200 and ALL-CAN300 CAN adapters]]. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 14:05, 11 April 2018
When no I/O element is enabled, AVL packet comes with GNSS information only. After enabling I/O element(s) AVL packet along with GNSS information contains current value(s) of enabled I/O element.
Current value – if device is connected to configurator all current I/O values are displayed in this column.
Priority field – allows enabling I/O element and set them priority so it is added to the data packet and is sent to the server. By default 12 I/O elements with low priority are enabled: Ignition, Movement, Data Mode, GSM Signal, Sleep mode, GNSS Status, GNSS PDOP, GNSS HDOP, External Voltage, Speed, Battery Voltage and Battery Current. Priority (AVL packet priority) can be Low, High or Panic. All records made by FMB120 are regular. Regular packets are sent as Low priority records. When low priority event is triggered, FMB120 makes additional record with indication that the reason for that was I/O element change (depends from Operand configuration). When High priority is selected, module makes additional record with high priority flag and sends event packet immediately to the server by GPRS. Panic priority triggers same actions as high priority, but if GPRS fails, it sends AVL packet using SMS data sending mode if SMS data sending is enabled and data send number is written in SMS/Call Settings.
High and Low levels – define I/O value range. If I/O value enters or exits this range, FMB120 generates event. “Operand” parameter defines when to generate event: On Exit, On Entrance, On Both, On Hysteresis and On Delta Change.
Event only - when selected NO, I/O element status value will be appeared in each AVL record, and when selected YES, I/O element status value will be appended only to eventual records.
Operands
Operand On Exit
Record is generated when actual value input increases and becomes higher than high level or decreases and become lower than low level.
Operand On Entrance
Record is generated when actual value input increases or decreases and becomes between high and low level values.
Operand On Both
Record is generated by both (On Exit and On Entrance) operands logic at same time.
Operand Monitoring
No event at all. Values are recorded only when other trigger have worked.
Operand On Hysteresis
Record is generated when actual value input inceases from lower than low value to higher than high level value or decreasing from higher than high level to lower than low level.
Operand On Change
Record is generated when value changes.
Operand On Delta Change
Record is generated when value changes and absolute value of last value minus actual input value becomes equal or higher than high level value.
Avg Const
If avg const value is 10, new value must be present for 1 second to register change to new value. Internally sampling is done every 40ms, so 25 samples are taken in second. To configure 5 seconds averaging multiply 10 by 5 yielding 50. The same logic works even if device is in deep sleep mode.
Averaging follows RC exponential curves, see image below:
For Boolean values 5τ, values is used, that means value change is taken when new values is averaged to more then 99.3%.
OBD II (Bluetooth) and LVCAN I/O elements
In OBD II (Bluetooth) column are shown I/O elements which information can be obtained from OBD II Bluetooth dongle connected to FMB120 device and in LVCAN column are shown I/O elements whitch information can be obtained from LV-CAN200 or ALL-CAN300 connected to FMB120 device. All I/O configuration is the same as described in I/O settings section, except OBD II (Bluetooth) I/O element don’t have averaging constant parameter.
Detailed description about LVCAN I/O element configuration described in FMB120 with LV-CAN200 and ALL-CAN300 CAN adapters.
