RFID Configuration Support in FMB125 – Immediate Data Send & Card Validation

Hello team,

I have an RRHFOEM07 RFID reader connected to a Teltonika FMB125 over RS232 (Mode: RFID HID, Baud 9600). The device correctly reports the RFID UID as a hex value (e.g. 0x0000002A1F9C9D34) when a tag is swiped (Data acquisition = On Change).

My requirement: I want the device itself to accept only pre-configured RFID card IDs (stored on the device) and reject others, so that only allowed card(s) (e.g. S1) will trigger the digital output (DOUT) and other cards (S2) are ignored.

To accept only pre-configured RFID card IDs and trigger DOUT only for allowed cards, you need to enable the Immobilizer scenario with iButton List Check feature on your FMB125. This will validate scanned RFID cards against a stored whitelist and control DOUT1 accordingly.

FMB125 Features settings - Teltonika Telematics Wiki

  1. Configure the RFID/iButton whitelist on the device

  2. Enable the Immobilizer scenario with list checking

  3. Enable DOUT control for authorized cards

Important Note: In Teltonika terminology, RFID cards and iButtons use the same authentication mechanism. The “iButton List Check” feature works for both iButton IDs and RFID card UIDs.

Configuration Steps

Step 1: Add Authorized RFID Cards to the Device List

You need to configure your allowed RFID card UIDs in the device’s iButton/RFID list.

How to add RFID cards to the list:

  • Use the Teltonika Configurator software

  • Navigate to the iButton/RFID List section

  • Add your authorized RFID card UIDs (e.g., 0x0000002A1F9C9D34)

  • Save the configuration to the device

For detailed instructions on listing RFID cards in FMB devices, refer to the device’s iButton List configuration guide in the Teltonika Wiki.

How It Works

Authorization Logic

When iButton List Check (Parameter 11703) is enabled (Value: 1):

  1. Card Scanned: When an RFID card is swiped on the reader

  2. List Validation: The device checks if the card UID exists in the configured RFID/iButton list

  3. Authorization Result:

    • :white_check_mark: Card in list (S1): Authorization successful → DOUT1 can be controlled

    • :cross_mark: Card NOT in list (S2): Authorization fails → DOUT1 remains unchanged

DOUT Control Behavior

With DOUT Control (Parameter 11702) enabled:

    • DOUT1 turns ON when ignition turns ON

    • DOUT1 turns OFF after any authorized RFID card is attached

    • If ignition is turned OFF and back ON within the timeout period, re-authorization is not required

If more support is required, please raise query in partner portal.

Thanks