FMB130 external voltage event activated by limits

Hi everyone,

I’m working with a Teltonika FMB130 and I have a question regarding external voltage detection and voltage limits.

Scenario

When the external power is unplugged, the device generates a Power Cut event only when the voltage drops below ~4 V.
Additionally, the event is generated about 10 seconds after the power is disconnected.

What I’m trying to achieve

I need to generate a faster alert, triggered at a higher voltage level, instead of waiting until the voltage drops to ~4 V.

Configuration applied

In Teltonika Configurator, I configured the External Voltage I/O with:

  • Low limit: 10 V

  • High limit: 12 V

  • Operand: Hysteresis

The intention is to generate an alert when the voltage drops below 10 V, and recover above 12 V.

Issue

Despite this configuration:

  • The device ignores the configured low/high limits

  • The alert is still generated only when the voltage drops below ~4 V

  • The behavior matches the default External Power Cut event, not the configured voltage limits

Question

How can I configure the FMB130 to generate a faster power-related event using voltage limits, instead of relying on the default power cut detection at ~4 V?

Any clarification on whether this behavior is firmware-limited or if there is a correct way to achieve this using I/O voltage events would be greatly appreciated.

Thank you in advance.

Hello,

It seems that hysteresis is not suitable if you need an alert bellow 10v and above 12v.

The operand that should be used is On Exit

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

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

Source: FMB130 I/O settings - Teltonika Telematics Wiki

Also take note of how Avg constant works since that also adds to the delay. 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.

This topic was automatically closed after 60 days. New replies are no longer allowed.