OLIMEX MOD-RFID1356 User manual

MOD-RFID1356
User Manual
All boards produced by Olimex are ROHS compliant
Rev.A, May 2008
Copyr ght(c) 2008, OLIMEX Ltd, All r ghts reserved
Downloaded from Elcodis.com electronic components distributor

INTRODUCTION:
MOD-RFID1356 is an RFID station, able to interact with ISO15 93
compliant VICC transponders. All the complexity of RFID tag detection,
verification and decoding are handled by MOD-RFID135 . Custom
command requests can be initiated to facilitate VICC EEPROM read and
write operations.
MOD-RFID135 supports two distinctive modes of operation, easily
switched by a single button press. It can emulate USB HID keyboard and
input the read TAG ID directly to any Windows application, including the
venerable Notepad. Or it can emulate USB CDC serial port for easy access
from custom user applications using standard code for COM port access.
FEATURES:
- Supports ISO15 93 compliant VICC transponders like EM4034.
- Base RFID frequency 13,5 MHz;
- USB port connection to PC;
- Two modes of operation, easily changed by pressing the button;
- USB HID keyboard emulation mode;
- USB CDC serial port emulation mode;
- Simple command-line interface in USB CDC mode for configuration,
data acquisition and initiation of custom command requests;
- Two LEDs indicating device status and tag presence;
- Support for continuous and periodic RF scanning to better suit user
power requirements;
- Ships with default mode USB HID and default configuration:
continuous read, scan always, LEDs activated;
ELECTROSTATIC WARNING:
The MOD-RFID135 board is shipped in protective anti-static packaging.
The board must not be subject to high electrostatic potentials. General
practice for working with static sensitive devices should be applied when
working with this board.
REQUIREMENTS:
Cables: 1.8 meter USB A-B cable.
Software:
Software needed for USB HID keyboard mode:
- Notepad or other text editor.
Software needed for USB CDC mode:
- HyperTerminal or other terminal program.
Downloaded from Elcodis.com electronic components distributor

SUPPORTED RFID TAGS/VICC:
MOD-RFID135 supports RFID transponder tags with the following
characteristics:
- ISO15 93 compliant transponders;
- 13,5 MHz carrier frequency;
-1 out of 4 transmission encoding (VCD to VICC);
- High data rate (2 ,48kbit/s) reception encoding using one sub-
carrier frequency.
CAVEAT: MOD-RFID135 does not support reliably the anticollision
algorithm as defined in the ISO15 93 standard. It w ll work reliably only if
there is a single VICC in the vicinity or if there is no RF collision. If there is
an RF collision, supposedly because of two VICCs with almost identical
UIDs, it might not detect both of them.
POWER SUPPLY:
Normally the device is supplied from USB.
LEDS:
In normal mode the GREEN LED is on whenever the RF antenna circuit is
active and scanning for RFID tags. The RED LED switches on whenever a
valid RF TAG ID is being scanned and decoded successfully.
The LEDs can be switched off to save power consumption. See the
“Command Line Interface” section for more information.
In boot loader mode the LEDs have other meaning. See the “Firmware
Upgrade” section for more information.
PC DRIVER INSTALLATION:
Drivers for the USB HID mode are integrated in Windows XP/Vista.
The driver for USB CDC mode is available from our website. Windows
installation steps are the following:
1. Download and unzip the file “MOD-RFID135 -drivers.zip” in a
temporary directory.
2. Plug the programmer in the USB port.
3. Point the Device Wizard to the temporary directory.
4. Windows will complain that drivers are not signed. Click “Continue”.
5. Click finish.
Screen shots of the steps are shown below:
Downloaded from Elcodis.com electronic components distributor

Downloaded from Elcodis.com electronic components distributor

Linux distributions normally include drivers both for USB HID and USB
CDC classes. Depending on which driver is loaded in the kernel, user
should look either for
/dev/ttyACMn
or
/dev/ttyUSBn
where "n" is a number, assigned by the kernel to the plugged device.
USB HID MODE:
When device is connected via USB to a host PC it will represent itself as
USB HID keyboard. When an RFID transponder is detected in the vicinity,
the module will type the HEX-representation of the transponder ID.
To use the device in this mode:
1. Open Notepad.
2. Plug in the device in the USB port of the PC.
3. Put an RFID tag in front of the device. The TAG ID will be entered in
the currently opened text file.
There is no need for OS driver because all major operating systems include
USB HID drivers.
NOTE: This mode does not allow configuration of device parameters. MOD-
RFID135 is shipped with default configuration for continuous read. If this
Downloaded from Elcodis.com electronic components distributor

must be changed then device must be switched to USB CDC mode and
configured using the serial command line interface.
USB CDC MODE:
In this mode the device represents itself as USB CDC virtual serial port. It
provides a simple shell-like command line interface for configuring and
interacting with the module. The device echoes back the typed characters
and waits for Carriage Return (Enter) before processing the line input. See
“Command Line Interface” for more information on the supported
commands.
Any terminal software can be used to open the COM port, assigned by the
OS, and type in commands.
SWITCHING OPERATING MODES:
The current mode of operation can be selected by pressing and holding the
button of the device. After two seconds the LEDs will start to blink and will
show the code for the next selected mode. When button is released, the
device will reboot and enter the selected mode. Selected mode is
remembered between power downs. The assigned codes are:
LED Status Descr pt on
Red Green Prev ous State State After Button Is
Released
blinks off USB CDC USB HID
off blinks USB HID USB CDC
COMMAND LINE INTERFACE (USB CDC mode):
The command line interface, available in USB CDC mode, allows device
configuration and reading of successfully decoded TAG IDs. Just open the
serial port assigned to MOD-RFID135 using HyperTerminal or similar
terminal program, and start typing commands.
For the impatient: type '?' and press enter to see a short help for the
supported commands. Any typed character will be echoed back; 'enter' will
force the module to process the input command line.
1. Command ?
This command prints a short help message, describing the available
commands and their arguments.
2. Command
This command prints a short information about firmware version,
hardware board revision, and currently selected configuration.
3. Command b
This command forces the device to enter boot loader mode. After
executing this command the device will disconnect itself from USB,
switch to boot loader mode, and reconnect itself in anticipation of
Downloaded from Elcodis.com electronic components distributor

receiving a firmware upgrade image. See the section “Firmware
Upgrade” for more information.
4. Command r
This command is only valid if device is in single read mode (see
below). It will trigger a single TAG read. If TAG ID is successfully
read, it will be printed. Otherwise if operation timeouts, zeros will be
printed.
5. Command msXX
Set single read mode. The XX parameter must be a decimal value,
indicating the TAG read timeout in seconds.
Example – setting single read mode with 15 seconds timeout:
ms15
6. Command mcFR
Set continuous read mode with frequency F (Hz). R is for
compatibility with other Olimex products and is otherwise ignored if
present. Both F and R must be single digit decimal numbers.
If F is 0 then RF antenna is constantly switched on and the device
scans continuously for tags. Otherwise if F is 1-5, the device will
switch the antenna on F times per second.
Example – continuous scanning:
mc0
Example – scan once per second:
mc1
7. Command mlE
Set LED mode. If E is 0, LEDs will be disabled. Otherwise if E is 1,
LEDs will be enabled.
Example – enabling LEDs:
ml1
Example – disabling LEDs to conserve power:
ml0
8. Command cT1,T2,FFCCDD...DD
Issue custom command request. T1 and T2 are timeouts in
milliseconds. T1 shows how much to wait in RF silence before
issuing timeout. T2 defines the total reception timeout, no matter
what is decoded from the RF field. Typical values for both are 50 to
100ms. After them is the hexadecimal representation of the request
which will be issued. FF is the request flags byte, CC is the comand
code, followed by zero or more data bytes. CRC is automatically
handled by MOD-RFID135 .
If answer was correctly received and decoded the response format
would be:
<FFAA...
where FF is the response flags byte, followed by one or more
response data bytes.
On error the following is returned:
!eXX
Downloaded from Elcodis.com electronic components distributor

where XX is a decimal number code of the occurred error. In general
the VICC error code bytes are propagated, along with some
additional MOD-RFID135 specific error codes. See the table below
for error code definitions.
Error
code
Descr pt on
1 Command code request not supported.
2 Request format not recognized.
3 Command option is not supported.
14 Generic error.
1 Specified block does not exist.
18 Specified block is locked.
19 Block write error.
20 Block lock error.
1 0 Power check failed.
25 VICC response timeout.
257 MOD-RFID135 does not posses enough memory
to complete the requested operation.
258 VICC response has incorrect CRC.
Please consult the ISO15 93 standard and your VICC datasheet for
more information about request and answer formats.
Example – read four 32-bit EEPROM words starting from word
number 2, addressed version, both timeouts set to 100ms,
addressing VICC UID with 7B8C0016010416E0 :
c100,100,20237B8C0016010416E00204
Example – read four 32-bit EEPROM words starting from word
number 2, non-addressed version:
c100,100,00230204
Example – write EEPROM word at address 0xA with value
0x11223344, addressed version, addressing VICC UID with
7B8C0016010416E0 :
c100,100,20217B8C0016010416E00A11223344
Example – write EEPROM word at address 0xA with value
0x11223344, non-addressed version:
c100,100,00210A11223344
Below is a screen shot of command line session using HyperTerminal:
Downloaded from Elcodis.com electronic components distributor

FIRMWARE UPGRADE:
MOD-RFID135 contains a built-in boot loader for easy firmware upgrade.
Device enters boot loader mode if the application FLASH section is
corrupted. To force the device to enter boot loader mode for manual
firmware update do the following:
1. Disconnect the device from USB.
2. Press and hold the button.
3. Power up the device by connecting it to USB.
4. Device now must be in boot loader mode, indicated by the LED light
sequence:
a. RED on, GREEN off.
b. RED off, GREEN on.
c. RED off, GREEN off.
Button can now be released. The device will stay in boot loader mode until
it is power cycled.
Boot loader implements the standard protocol XMODEM with CRC1 for
firmware update. User is free to use his favorite terminal client
(HyperTerminal, minicom, etc) to upload the firmware images taken from
our website. Boot loader uses an USB virtual serial port that is baudrate
agnostic.
As an alternative we provide a simple Windows GUI application for users
who don’t want to or cannot use terminal software.
After the firmware image is uploaded the target will blink the GREEN LED if
update was successful, otherwise it will blink the RED LED if firmware
image was invalid or update was unsuccessful. Device stays in this state
until it is power cycled.
Downloaded from Elcodis.com electronic components distributor

ELECTRICAL CHARACTERISTICS:
Symbol Descr pt on Cond t on M n Typ Max Un
ts
VCC Power Supply Voltage. V
ICC,NOLED Power Supply Current
with deactivated
LEDs.
Idle (RF scanning not active) mA
Continuous scanning mA
Scanning 2 times per second mA
ICC Power Supply Current
with activated LEDs.
Continuous scanning mA
Scanning 2 times per second mA
Downloaded from Elcodis.com electronic components distributor