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. The DM RFID reader reads 125kHz EM4001 cards and fobs. Other common access cards that sites/business may use are HID(common) or MiFare. So if a customer already has allocated access cards to their staff, they can still be used if a suitable reader is found.
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?
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:
- Form Factor
- 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 FW modification - best to look for another keypad.
- 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?
Connections are as follows
The Wiegand interface uses 4 wires.
- Data 0
- Usually Green
- Data 1
- usually white
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)
Instructions for wiring and parameter setup
Other integrated readers require other parameters set in addition to the above linked article, these are indicated below.
|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.
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.
- Reset all parameters to default (remove the tabs)
- Only apply the 4 wire plug function = Wiegand parameter, for simplicity.
- Connect the reader to the G120 as above
- Scan your tags - the reader should give some indication
- 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.
- 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.
Recommended 3rd Party Keypads/Readers?
Below are some Wiegand readers we have seen in use and/or tested. Not all have been extensively tested.
IP65 keypad. Good form factor - easily mounted with 2 x screws.
This keypad sends each key press as soon as it is sent - but we have integrated it into the G120 firmware, so that the G120 will 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.
- 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 - the rest can be off.
- Ensure you are on FW 2.7 or above.
- RFID Access Card Reader
- Tested by DM, works and reads HID cards.
- (Jaycar Australia)
- Digital Keypad with RFID
- (Jaycar Australia) - LA5353
- HID Compatible Reader
- This reader will read HID cards - which are commonly used on sites.
- HID ProxPoint Plus
- One caveat is the maximum bit length must be extended from 37 for some cards as they may use 38 bit codes.
- Driver Name: Peter
- ID - PIN code 12345
Installation and Use
Consult the manual available on the manufacturers website.
Key points for use with the G120 as a Wiegand Keypad
Two DS-K1107 PIN -> Driver ID converters are attached for use.
To give out this ID for the DS-K1107 keypad.
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.
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.