top of page
GC-2673 keypad and NFC cards with fleet vans on a black and gold Wialon Driver ID troubleshooting cover

Driver ID Not Showing in Wialon? Keypad, iButton and RFID Troubleshooting

Nov 11
5 min read

If driver ID is not showing in Wialon, start with one controlled login and trace it from the reader or keypad to the tracker, then into the platform. A successful beep is only one part of that chain. Replacing hardware before locating the missing step can leave the original fault unresolved.

This guide focuses on diagnosing an installed system in Wialon Hosting. Screen names and behaviour can differ in Wialon Local or other editions. For choosing equipment, use our Driver Identification Kits guide and tracker/keypad compatibility guide.

Start with one vehicle and one test credential

Record the tracker model, firmware, keypad or reader model, connection method and Wialon edition. Use a test credential assigned to a known test driver, with the vehicle parked. Note the exact login time and timezone. Keep the original configuration so each change can be reversed.

Define the symptom before changing anything: no identifier received, an identifier received without a driver name, the wrong driver, or an old driver remaining after a handover. Change one setting at a time and repeat the same test. A fleet-wide change is a poor starting point for an isolated installation fault.

Quick diagnosis table

What you see

First check

Next useful test

Keypad responds, but no ID reaches the tracker

Power, ground, data connection and supported input

Compare tracker input diagnostics before and after a test login

Tracker records an ID, but Wialon has no matching event

Reporting configuration and the message sent at the test time

Compare the tracker event with the received message

ID appears in Wialon, but no driver name

Sensor mapping, driver Code and assignment list

Follow the platform checks below

The wrong driver appears

Credential allocation and the received ID

Retest with two clearly labelled test credentials

Driver stays assigned after leaving

Agreed logout or handover behaviour

Test the intended end-of-shift event separately

Live display works, but a report looks wrong

Report interval and event timestamps

Compare one short test journey with the recorded events

1. Check what Wialon actually receives

Open Messages for the correct unit and select a short interval around the test. Wialon's Raw data view exposes received parameters; Sensor values shows their interpreted results. Compare both views instead of relying only on a driver label on the map. The Time and Registration time columns distinguish when the device generated a message from when the server received it. See Wialon's data-message reference.

Write down the parameter name and observed value exactly. Do not assume that a PIN entered on a keypad, a number printed on a token and the transmitted identifier will all look identical. If there is no relevant message, work backwards with the installer: can the tracker see the credential, and is that event configured to be reported?

A useful handover to support contains the test time, model and firmware, expected result and a redacted message sample. Remove operational PINs, personal details and vehicle location before sharing diagnostic material. Avoid changing report templates while the basic event is still missing.

2. Check the Wialon assignment path

For automatic assignment, configure a Driver assignment sensor on the unit and include the unit in the driver's resource's automatic assignment list. Use the parameter actually supplied by your equipment; avl_driver is an example, not a universal setting. Wialon does not allow a previous-message parameter for this sensor or its validator. Follow the official assignment instructions for your edition.

The driver's Code must exactly match the sensor value, including letter case. If the sensor applies a conversion, use the resulting value. For example, a test sensor value of 000b142c must not be shortened to b142c or replaced with an unrelated printed card number. Check the stored credential against the current message, not a screenshot from another vehicle. Wialon's driver-property documentation explains Code and Exclusive settings.

3. Test the end of the assignment

In Wialon Hosting, automatic separation can use an empty value, a configured separation code or a notification action. Ignition-off alone is not a universal logout rule. A manually assigned driver must be separated manually. Stored messages arriving late can distort assignment history; use a live test when assessing handovers.

Choose the intended operational rule with the fleet manager: should the assignment end at ignition-off, at a deliberate logout, or when another driver takes over? Then test that rule independently. A successful login does not demonstrate a successful logout.

For single-driver operation, review Exclusive on the driver profiles. Wialon documents resource and real-time limitations: enabling it for one driver does not make every later driver exclusive. Check both test profiles and confirm the actual result. Our van driver identification guide covers the wider shared-vehicle workflow.

4. Recheck hardware only where the evidence points

Before ordering a replacement, compare the exact interface and reporting capability. A tracker being supported by Wialon does not establish that a particular keypad, reader and firmware combination supports the required driver-ID workflow.

For example, the GC-2673 PIN and NFC keypad sends identifiers to a supported tracker through 1-Wire/iButton. NFC is the card-to-keypad connection; it does not replace the wired tracker connection. Validate PIN and card operation separately if the deployment uses both. The GC-2673 application guide explains that dual-method approach.

For token-based installations, review the iButton reader range or RFID readers against the tracker specification. Driver logging and immobiliser control are separate functions. This diagnostic process does not authorise remote immobilisation or changes to vehicle-start circuits.

A small acceptance test before rollout

Use two test drivers and one parked vehicle. Record a successful login for each, the intended separation event, and a login with an unassigned test credential. Then repeat after an ignition cycle. For every step, record expected driver, observed driver, message time and pass/fail.

Do not mark the installation complete simply because a name appeared once. The useful outcome is a repeatable match between credential, vehicle and assignment interval. Retain the test record with the installation configuration so future changes have a baseline.

Frequently asked questions

Does a keypad beep prove Wialon received the driver ID?

No. Treat it as local feedback and confirm the tracker event and received message separately.

Should I buy a different keypad if the driver name is missing?

First locate the missing step. A reader replacement will not correct a platform mapping or credential-allocation problem. Buy replacement hardware when the interface, condition or supported workflow is the issue.

Can the same instructions be copied to every Teltonika or Queclink tracker?

No. Check the exact model, firmware, accessory interface and decoded parameter. Use the platform documentation alongside the equipment-specific configuration instructions.

Need help choosing a compatible Driver ID kit?

Send Tracking Hardware UK your tracker model and firmware, Wialon edition, required login method and the result of the controlled test. We can help check the hardware fit before you order. Compare our driver identification keypads and request a quote.

Comments


bottom of page