FMB962 I/O settings

From Wiki Knowledge Base | Teltonika GPS
Revision as of 14:32, 26 October 2018 by Mariusandruska (talk | contribs) (Created page with "{{ Template:FMB964_I/O_settings |model=FMB962 |section_fmb0= ==OBD II (Blue-tooth) I/O elements== ''OBD II (Blue-tooth)'' section show I/O elements that can be obtained accord...")

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)
Main Page > EOL Products > FMB962 > FMB962 Configuration > FMB962 I/O settings

When no I/O element is enabled, AVL packet comes with GNSS information only. After enabling I/O element(s) AVL packet contains current value(s) of enabled I/O element(s) along with GNSS information.
If the device is connected to configurator all current I/O values are displayed in Current Value column.
Priority field allows enabling I/O elements and setting them a priority so they are added to the data packet, which 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 Current and Battery Voltage. Priority level (AVL packet priority) can be Low, High or Panic. All records made by FMB962 are regular, and regular packets are sent as low priority records. When Low priority event is triggered, FMB962 makes an additional record with an indication that the event was caused by an I/O element change (depending on Operand configuration). When High priority is selected, module makes an additional record with high priority flag and sends event packet immediately to the server using GPRS. Panic priority triggers same actions as High priority, but if GPRS fails, it sends an AVL packet using SMS data if SMS data sending is enabled and the number is provided in SMS/Call Settings.
High and Low levels define I/O value range. If I/O value enters or exits this range, FMB962 generates an event. Operand parameter defines when to generate event: On Exit, On Entrance, On Both, On Hysteresis or On Delta Change.
When Event Only is selected, I/O element status value will be appended only to eventual records, otherwise I/O element status value will appear in each AVL record.

Operands

Operand On Exit

Record is generated when input value leaves a range between low and high level limits.

Fmb120 on exit.png

Operand On Entrance


Record is generated when input value enters a range between low and high level limits.

Fmb120 on entrance.png

Operand On Both


Record is generated by both On Exit and On Entrance operands' logic at same time.

Fmb120 on both.png

Operand Monitoring


No event at all. Values are recorded only when other triggers worked.

Fmb120 operand monitoring.png

Operand On Hysteresis


Record is generated when input value crosses the high limit value from below the low limit value or vice versa.

Fmb120 on hysteresis.png

Operand On Change


Record is generated when input value changes.

Fmb120 on change.png

Operand On Delta Change


Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value.

Fmb120 on delta change.png

Avg Const

If Avg Const value is 10, new value must be present for 1 second to register the change to a new value. Internal sampling is done every 40 ms, so 25 samples are taken per second. To configure 5 seconds of averaging multiply 10 by 5 yielding 50 as Avg Const value. The same logic works if the device is in Deep Sleep mode.
Averaging follows RC exponential curve, see image below:

Fmb120 avg const.png

For Boolean values of 5τ, values is used, that means value change is taken when new values is averaged to more than 99.3%.

OBD II (Blue-tooth) I/O elements

OBD II (Blue-tooth) section show I/O elements that can be obtained accordingly from OBD II Blue-tooth dongle connected to FMB964 device. All I/O configuration is as described in FMB964 I/O settings section, except OBD II (Blue-tooth) I/O elements does not have an averaging constant parameter.