Support Home Portal Log in
Open navigation

G120 - Wiegand Driver ID Readers and Keypads

Driver ID Options and Reading 3rd Party Driver ID Tags with DM Devices

For a complete discussion of device compatibility with various card/tag types, and options across our entire device range, see here - Driver ID Reader Options

Wiegand on the G120.

The G120 has a Wiegand interface. Wiegand is a common interfaced used by RFID readers. So it means many readers can be simply connected to the G120, and read cards that the DM RFID reader may not be able to read. 

Why does this matter?:

Many worksites will already have a particular type of access/ID card in use. If we are able to have our telematics devices read these cards, the complexity of managing and an entire new type of fob/card - just for the telematics devices is removed. We can simply use the cards which are already in rotation. 

 Driver ID Options for Fleet Tracking

Read more about this on our site!

Most Wiegand ID cards use IDs which are 26 bits in length. But other lengths are possible. The G120 and Telematics Guru are able to support IDs up to 40 bits in length.

How do I source the right reader for use with the G120?

In short, you need to find a reader that reads the type of card/fob in use, and outputs Wiegand. Check the specification, that it has a Wiegand Interface and check the card types it reads. That is pretty much all there is to it. Though sometimes keypads like to do weird things, but often it is hard to know until you have it in your hands.

The other considerations are:

  • Cost
  • Form Factor
  • Mounting
  • How it is powered.

There is 4V available on pin 3 on the wiring harness (purple wire of 4 way driver ID connector on G120 harness). But most Wiegand readers will require a higher voltage to operate i.e. 12V, so they will need to be powered separately. It is generally easiest just to connect to where you are powering the G120 from. 

What are some common pitfalls?

These can be hard to spot beforehand, but a few issues or areas to consider that have cropped up in testing keypads

  • We have seen some keypads that send through data for every key press (and don't wait for the complete code). So trying to enter "12345" sends through each in sequence i.e. 1, 2, 3, 4, 5. This means they won't work without firmware modification - best to look for another keypad if possible.


  • Wiegand encoding must be accounted for. "12345" when pressed on the keypad won't turn up as this.
    E.g on one keypad we have tested, an entry of "111111" will appear as 1A00D903C0 in Telemetry. So this is the Driver ID TG will be working with, and 1A00D903C0 must be what is entered in the Driver List. This is easy to work around by:
    • Simply enter the desired code - i.e. 12345 - then check the Telemetry in TG for the driver code. Paste what comes through into the driver list, and add a comment for the actual entered code against the driver.
    • We have worked out the encoding for some keypads we have tested and code converters are attached to the article. Keypad/reader manufacturers may be able to provide Excel spreadsheets to do a conversion.
  • It is difficult to work out a card format without being informed by the supplier/manufacturer. Test multiple different cards when checking readers - sometimes they are a different format than expected - so it appears the reader isn't working, but the card just can't be read since the reader can't read that type of card.

How do I connect and test a reader?


The Wiegand interface uses 4 wires. 

Wire ColourFunction
(Usually) GreenData 0
(Usually) WhiteData 1

These can be connected to the relevant pins on the G120 Harness.The pins used are terminated with the 4 way molex connector which is used for the DM RFID reader - so you will need to cut this off and solder/crimp the wires. Connections are as follows:

Ground (reader)
Connect to any G120 ground, but Pin 15 (black) is convenient
Power (reader)
Typically connect this to your power supply - check the voltage range on your reader before making connections.

If you wish to power from the harness you can use G120 Pin 3 (purple on 4 way connector) - with some caveats. This power rail is generally used to supply the DM RFID reader. So it will only output approximately 4V. It is also only remains powered by default when the unit is awake (but this can be changed to stay on in settings) Most Wiegand RFID readers require >4V to operate however - so most connections will be to external power.

Data 0 (reader)
Connect to G120 Pin 14, TTL RX (Green on 4 way connector)
Data 1 (reader)
Connect to Pin 13, TTL TX (Brown on 4 way connector)


Some readers and keypads have an internal buzzer, and a certain wire controls this buzzer. The G120 can be connected and configured such that the reader will buzz on when no driver ID is entered at the start of a trip. 

If the buzzer is activated when the reader's buzzer control wire is given a path to ground, connect this wire to the G120 Switched Ground (Yellow, Pin 11).
If it is activated when the reader's buzzer control wire is given 5V (or theareabouts), we can use the switched power output on the G120 (Orange, Pin 9).
Then we must set up either of these outputs' function to Buzzer in System Parameters. 

System Parameters

Be sure to set the 4 Wire Plug Function in system parameters to Wiegand.
If you are using pin 3 to power your reader;
set Keep Peripherals On - Yes to keep that line at 4V always.

3rd Party Keypads/Readers and set-up specifics

Below are some Wiegand readers we have seen in use and/or tested. Not all have been extensively tested. Toggle between tabs to view set up instructions specific to each keypad.

Hikvision DS-K1107 Keypad LA5351 RFID Reader LA5353 KeypadHID Proxpoint Plus

Product information - Hikvision DSK1107 Web Page, User Manual

Australian Supplier - Security Wholesalers

IP65 keypad. Good form factor - easily mounted with 2 x screws. The keypad also has a built in buzzer, which can be made to buzz in the same way as DM RFID readers with the correct wiring setup. 

Warning - 12V Keypad

This keypad has an input voltage of 12V - ensure you do not exceed this!

This keypad sends each key press as soon as it is sent - but we have integrated it into the G120 firmware, so that when a certain parameter is enabled, the G120 store each key press and only send through a completed code once the # key is pressed.

Note - there are 2 variants

DS-K1107 - EK
This has both a Keypad for PIN input, and will read 125kHz EM4001 cards and fobs - which is the format used by our RFID readers
DS-K11078 - MK
Has a keypad and reads MiFare cards.


This a guide, consult the manual for full details. 

Hikvision Keypad Wire
Connect to
Red wire (PWR)12V DC power
Black (GND)To ground - pin 15 (Black) on 4 way driver ID connector on the G120 is easiest
Green (W0)G120 pin 14 - Green on 4 way driver ID connector
White (W1)G120 pin 13 - Brown on 4 way driver ID connector
Optional - Purple (Beep Control)G120 pin 9 - Orange - Switched Power Output

Parameter Setup

Ensure the 4 Wire Plug function is set to Wiegand as shown in the previous section. 


In OEM server, ensure Interpret DS-K1107 Key Presses is set to Yes under the Wiegand Parameters

If we have wired up the buzzer control and want to enable buzzing, we need to set up this parameter:

Then, buzzing on no driver ID is set up as usual - see Driver ID & Immobilisation methods with Powered Devices for more information. 

Operation and Usage

  • The # key is "Enter" and * is clear. So to enter the code "1234" press 1234#
  • If a few keys are pressed and are not followed by # - after 30 seconds whatever keys have been pressed will be sent as the code.
  • The very first tag scan/entry after power on is ignored. This is not a problem in practice as the keypad should remain powered once installed as it requires 12V power, which would be supplied from a constant source.
  • Number 6 on the DIP switches on the rear of the device must be on (this sets the keypad to output codes via the Wiegand interface) - the rest can be off. 
  • DIP switch 7 toggles between 34 and 26 bit Wiegand codes - default position (off) is 34 bit.
  • Ensure you are on FW 2.7 or above.
  • Consult the manual for further information. 

Driver ID Encoding

Driver ID Encoding Example

Wiegand IDs are typically made up of 2 bits to indicate the length of the data, 8 bits for a site code, then some data bits and finally a couple of check bits for error correction. So 12345# - i.e. entering the code 12345, is not sent by the G120 in this form. We can use the attached DS-K1107 input code -> end code converter. 

An example:

To give out this ID for the DS-K1107 keypad.

  • Driver Name: Peter
  • ID - PIN code 12345

We would set up this keypad as per the instructions above.

Then we enter the code into the converter

1 - PIN code we wish to use

2 - Wiegand binary representation

3 - Hex representation for use in TG

We then copy (3) into TG. This is what will be sent as the driver ID.

It is worth testing a few codes to ensure the values returned by the converter are correct.
We can use the Driver Code Field to provide a reference to what their PIN code is

Then it will display in the driver list for easy reference. 

The 10 digits available on the keypad mean a Licence number can be used as the PIN.

Driver ID Calculator - Keypad Pin

Driver ID Calculator - Fob ID

Testing and basic troubleshooting

To test for reads, it is best to keep the process simple. Various driver ID settings can mean that if a tag is not in the devices driver list - when it is scanned it is rejected on the device and not uploaded to the server. So it is hard to see if the reads work.

To test:

  1. Reset all parameters to default (remove the tabs)
  2. Only apply the 4 wire plug function = Wiegand parameter, for simplicity.
  3. Connect the reader to the G120 as above
  4. Scan your tags - the reader should give some indication
  5. Tag scans don't cause an immediate upload - so to test it is good to put the device in trip by providing over 5V to the ignition line (this is how it will work in practice) - so scans will be immediately uploaded.
  6. Either Turn on Data Capture in OEM, or check the Driver ID column in Telemetry in Telematics Guru (Assets -> Telemetry) Successful reads will appear here. 

If you don't get any reads here

  • Try swapping the W0 and W1 connections in case they are mixed up
  • Check all connections are OK, including power supply to the reader
  • Try other cards - maybe the one you are testing isn't the format you think it is or is dead
  • If all else fails, further debugging is difficult, contact DM and the end result be you will need to send us a card and reader to test.
  • Increase the maximum bit length in parameters to 40.
    37 is the default and is the longest we expect to receive. This provides some error correction, extremely long codes are probably errors and are ignored. However some readers may send longer codes - the maximum that can be read by the G120 is 40 bits.

DS-K1107 Keypad

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.