Full disclosure — we make these keypads at Tracking Hardware UK, so we know the wiring well. Following on from our FMB130 keypad guide, this one covers the setup we get asked about most: a PIN keypad on the FMC130’s 1-Wire interface driving the Immobilizer scenario, so the engine will only start after a valid PIN.
What you’ll need
- FMC130 on reasonably recent firmware, plus the Teltonika Configurator
- A 1-Wire PIN keypad that emulates a Dallas iButton (ours is the EC-19521, but the steps are identical for any iButton-emulating keypad)
- A standard 5-pin automotive changeover relay (coil voltage to match the vehicle) and an inline fuse
Wiring — keypad
Pin numbers are from the FMC130 pinout on the Teltonika wiki — double-check against your harness before crimping anything.
- Keypad yellow → vehicle power, 8–36 V (12 V and 24 V both fine)
- Keypad brown → ground, on the same ground point as the FMC130’s GND (pin 7). A shared ground is not optional on 1-Wire
- Keypad white → FMC130 1-Wire DATA (pin 11). It is easy to land this on a regular DIN by mistake — count twice
- Do not power the keypad from pin 10 (1WIRE POWER). That pin is a +3.8 V output meant for iButton readers; the keypad takes vehicle power on its yellow wire instead
Wiring — immobiliser relay
DOUT1 (pin 8) is an open-collector output rated 0.5 A — it switches to ground rather than sourcing power, so it can’t interrupt a starter circuit on its own. Hence the relay:
- Relay terminal 85 → FMC130 DOUT1 (pin 8)
- Relay terminal 86 → ignition-switched +12 V, fused
- Run the starter solenoid feed through terminals 30 and 87a (the normally closed pair). While the scenario holds DOUT1 active the relay is energised and the circuit is broken; once a valid PIN is entered DOUT1 releases and the circuit closes again
For safety, always interrupt the starter motor circuit rather than fuel or ignition — that way nothing can cut power while the vehicle is moving.
Configurator settings
- System: confirm your ignition source. DIN1 (pin 5) is the usual choice
- Features → Immobilizer: enable the scenario, set the controlled output to DOUT1, and set the authorization ID list checking to 1-Wire (on current firmware at least one checking method must be selected)
- Ignition Off Timeout (default 25 s) sets how long authorisation survives after ignition-off before the driver must re-enter a PIN. One side effect worth knowing: if it’s longer than your sleep timeout, the device may never sleep
- iButton List: this is your whitelist. To capture each keypad ID, wire everything up, have the driver enter their PIN and press *, then read the ID from Status → I/O info in the Configurator and add it to the list. Important: an empty list means any ID authorises, so the immobiliser isn’t protecting anything until this is filled in
- I/O: set the iButton element priority to Low or higher so driver IDs reach your platform in records (note these records are only generated while ignition is on)
Testing
- Ignition on, no PIN → the vehicle should refuse to crank
- Enter a whitelisted PIN and press * → the keypad transmits, DOUT1 releases, and the vehicle cranks normally
- Ignition off, wait past the Ignition Off Timeout, ignition on again → blocked until a fresh PIN
Common problems & fixes
- If a setting here doesn’t match what you see, your firmware may differ — the current field names are always in the Configurator itself and on the wiki: FMC130 Features settings. For the full pinout, search “FMC130 First Start” on the same wiki
Happy to answer follow-ups here — we support these units directly.