USB Rockwell RA style readers can be configured to Enroll, use Single Factor Login, or Dual Factor Login. While the reader comes pre-configured for all three, you will need to configure the reader (using our configuration utility) based on which function will be used, in order to match your Factory Talk screens.   Please see this example of the different prompts used for each type of function here:

 No. Mounting a reader to metal can result in failure to read cards or a significantly reduced read range. 

The card analyzer only works with certain products that we offer. It was designed to work specifically with the pcProx Plus card readers with a USB interface. These models typically end in "AKU ".  Examples of a model number would be: RDR-805X1AKU, RDR-800X1AKU. RDR-805X2AKU & RDR-800X2AKU If you are receiving this error message when trying to run the analyzer, you have an unsupported model connected.   Please refer to the list of supported readers at the bottom of the error message.

DISINFECTANTS AND CLEANSERS TESTED ON DESKTOP/SURFACE MOUNT READERS BLEACH 5.25% - Poured on and rubbed vigorously with paper towel, sit1 min rinse & wipe dry HYDROGEN PEROXIDE 3% - Poured on and rubbed vigorously with paper towel, sit 1 min rinse & wipe dry ISOPROPYL ALCOHOL 70% - Poured on and rubbed vigorously with paper towel, sit 1 min rinse & wipe dry CLOROX WIPES - Rubbed vigorously ESD WIPES - Rubbed vigorously SUPER SANI-CLOTH - per recommended application SANI-CLOTH AF3 - per recommended application CHLOROX DISPATCH WIPES - per recommended application CAVIWIPES - per recommended application SONO ULTRASOUND WIPES - per recommended application

We only make Low Frequency, 125 kHz, and High Frequency, 13.56 MHz, readers. We do not offer any readers that will support Ultra High Frequency credentials.

The AKU model readers do not require a driver download. AKU model readers are generic USB devices and should be plug and play. They will utilize the generic USB driver from Windows. Windows should identify the device as a keyboard.

Our current generation of pcProx plus model readers, number RDR-800xxAKx, will support HID Seos cards. Our older generation does not. The easiest way to determine if your reader will support Seos cards or not is to look at the label on the back of the reader and check the firmware. If your firmware begins with PLC it does not support Seos cards. If your firmware begins with LNC it does support Seos cards.

Using pcSwipe in a Papercut environment and receiving the error “Attached USB device will not be used because it is not supported” Solution: Model (MS3-00M1AKU) mag stripe reader using the config key ext-device.hp-oxpd.additional-card-readers.vid-pid.hex needs to be 0x0c27:0x1000 otherwise they will get the reader not supported error message, IF you neglect to add the “0x” in the VID/PID.  See this example: Try the following device config key, this would be accessed from the

If you need to add or remove delimiters from the output of your reader it can be done using the WAVE ID® Configuration Utility 1. Go to the Format tab 2. Go to the Delimiters sub tab 3. Make any desired to changes to the delimiters 4. Click the Write Active / Write Settings button 

The readers by default will only output the ID number. If you need to output the facility code as well, you will need to configure the reader via the WAVE ID® Configuration Utility  1. Go to the Format tab 2. Check the "Send FAC" box 3. Click the Write Active / Write Settings button If the correct facility code is not shown, your format may be different than the default format.

If your card has a number such as 00068, by default the reader will only output 68. If you need the leading zeroes, you will have to enable the fix length feature in the WAVE ID® Configuration Utility 1. Go to the Format tab 2. Check the "Fix length FAC / ID fields" box 3. Set the ID digits to the total number of digits you want your output to be

At the very top of the WAVE ID® Configuration Utility is text that says "Device" Click on device and you're given several options including "Reset to Factory Defaults" Click on reset to defaults and the reader will go back to factory settings. 

The OEM Wiegand Converter requires a regulated power source of 5 VDC or 8-16 VDC, 100mA for internal operation. On the J4 Terminal block you would need to connect power (VH or V5), data 0 (W0), data 1 (W1), and ground (Gnd). VH - INPUT: Voltage (High), Power supply input from your power supply. The supply must be 8 – 16 VDC @100ma maximum. The on-board 5V regulator handles 1A combined consumption so external consumers connected to the 5V bus are limited to 900mA 

 As long as there is a continuous 5 Volt DC input to the Wiegand Splitter there should be no limit on the number that can be linked together. 

While the reader may connect to the utility locally, it may not connect through a VMware session unless you redirect the USB port.   An USB interface reader appears locally, by default, as a Human Interface Device (HID). On both Windows and Linux-based thin clients this defaulted connection can be fully redirected with some configuration changes. The steps for these configuration changes are below. Step 1: Add the following lines to the .

You can download the AK0 driver from our website under Support > Support Tools > Software Downloads. You can also download it directly here.

 The serial reader sends the card and delimiter data in ASCII Hex format. The reader will send the card data using ASCII characters 0 – 9 when the reader is in decimal mode and ASCII characters 0 – 9 and A – F when the reader is in hexadecimal mode. The delimiters supported are ASCII characters 00 – 7F when entered using the virtual keyboard in the rf IDEAS configuration utility.

We currently offer 3 Mobile credential readers. WAVE ID® Mobile Reader for HID Mobile Access® WAVE ID® Mobile Reader for Orange Business Services Pack ID  WAVE ID® Mobile Reader for Safetrust Wallet

Supported card types will be based on the model number you have. However, you can find a list of all supported card types for our readers at the link below: https://www.rfideas.com/support/tools/supported-card-types 

The easiest way to determine the frequency your reader supports is by looking at the model number.   Model numbers beginning with a 6, for example RDR-6081AKU, are Low Frequency, 125kHz readers. Model numbers beginning with a 7, for example RDR-7081BKU, are High Frequency, 13.56MHz readers Model numbers beginning with an 8, for example RDR-80581AKU, are dual frequency readers and will support both Low 125kHz and High 13.56MHz frequencies.

0x0c27:0x1000 Device USB\VID0C27&PID_1000

VID - 0C27 PID - 3BFA

The most important thing to note when looking at the differnece between Proximity, iClass, and Seos is the frequency at which they operate. HID Proximity operates at the 125 kHz low frequency while both HID iClass and HID Seos operate at the 13.56 MHz high frequency. HID Seos cards are similar to iClass cards but they are secured a step higher. When it comes to readers, we have two main groups of plus readers.

 The difference between a 81 series reader and an 82 series reader, for example, RDR-6081AKU vs RDR-6082AKU or RDR-80581AKU vs RDR-80582AKU Is that the 81 series readers are designed to visibly output data. When you scan a card, it will send the data via its method of communication: USB keystrokes, Serial, or Ethernet depending on the model. An 82 series reader is what we would call one of our SDK readers.

Both AKU and AK0 readers have a USB cable, the difference is in how they communicate. AKU readers function as a keyboard and will output to any text field. Simply click your cursor into a text area such as word, scan a card, and you should get an output. AK0 readers on the other hand are virtual COM port readers and communicate with serial data. You would need to use a program that supports a serial connection like pcProx Config or a terminal application like Putty to see the card scan.

Please note that we carry two variations of Ethernet PoE readers, the AKE-P and AKB-P. The biggest difference is the AKB-P reader has the built in EIP protocol to connect to Rockwell PLCs. The AKE-P is simply an Ethernet PoE enabled reader. So if you need to connect to a Rockwell PLC, please ensure that the Ethernet reader ends in AKB-P. Please see this link for the PoE manual:

 The maximum recommended distance is 500 feet from the Wiegand Splitter.  

You can download a list of available pinouts here. 

Our PoE models, those ending in AKB-P or AKE-P, follow the IEEE 802.3af standard which is 48 VDC. Any PoE injectors or equipment that follow that standard will work.

Typical read range is 1–4 inches; however, this can vary based on how the card was manufactured and how the reader is mounted. Typically a low frequency, 125 kHz card, will have a shorter read range then a high frequency, 13.56 MHz card. Additionally, the range between different form factors like fobs, stick on tags, and cards can vary. 

To purchase the SDK, send a request by email to sales@rfideas.com. 

The pcProx API is a purchased item. In order to purchase our software developers kit please contact our sales team at sales@rfideas.com

The pinout on the Ethernet connector is considered an IEEE 802.3af standard PoE pinout. And, we support both modes A & B. Please see a description in the link here: https://en.wikipedia.org/wiki/Power_over_Ethernet#Pinouts  An example pinout from Wikipedia for the IEEE802.3af standard can be found here:

Please see this link for the MODBus manual:  Link: https://www.rfideas.com/sites/default/files/2021-01/Modbus-pcProx_PoE_Configuration_Utility_User_Manual_199009230A.pdf    

You can find the BLE driver on the software downloads section of our website or linked below. https://www.rfideas.com/sites/default/files/2020-02/BLE-Driver.exe_.zip If you are going to be developing, you may also want the Bluegigga Bluetooth SDK from Silicon Labs found here. https://www.silabs.com/products/development-tools/software/bluegiga-bluetooth-smart-software-stack 

Our current generation of pcProx plus model readers will support 4 card configurations. Our older generation does not. The easiest way to determine if your reader will support 4 configurations or not is to look at the label on the back of the reader and check the firmware. If your firmware begins with PLC it will only support 2 configurations. If your firmware begins with LNC it supports 4 configurations.

Any reader models that end in AK0 or BK0 are considered to be our virtual com readers. These readers require a specific driver that can be found here. If you would like to see a training video on how to load the driver, please click here: https://www.rfideas.com/resource/rf-ideas-ak0bk0-driver-training-video 

Our AKB-P model readers are designed specifically for use with Rockwell PLC's. They are designed to output in hexadecimal with preset delimiters for communication wit the PLC. Anytime the reader power cycles, it will reset to its default settings to ensure the proper output for communication. Other then selecting the correct card type, no other settings should need to be changed.

If you are using the WAVE ID® Plus card reader, you will need to configure the reader to read the correct card type. This reader holds 2–4 configurations and can read over 50 types of cards. If you are using the AKU standard USB version of the card reader, please try using the card analyzer to be sure your reader is configured to the proper card type.  If you are using a single-band, single-configuration reader, these readers are only able to read one card type at a time and your card may not be supported.

Be sure you choose the correct interface type on the Connect tab. There are options for USB, serial and ethernet. **If using an ethernet reader, you must connect using port 10001. **AK0 readers must connect using the “Use Com Port” option.  If the above tips do not work, please try running the utility as ADMIN and try again. 

 If your reader is not outputting to notepad or other text fields, the most common cause would be that it is not a keystroking reader. Only readers where the model number ends in 1AKU or 1BKU will output to a text field. If your model does end in either of those, and is not outputting, it is possible the keystrokes have been disabled. You will want to use our configuration utility, pcProx Config, and do the following,