RFID RCP

Overview

Purpose of the device

Industry, services, commerce, and logistics are just some of the industries where the reader can be used. It can be used as a tool for logging into a machine, access to a room (warehouse), an element of a loyalty system, a time recorder, etc. Using its own application or protocols supported by the reader, the user can control practically every element of the reader - display, buzzer, inputs, outputs. Thanks to the built-in memory, he also has access to the list of logs stored in it.

The user can integrate the reader into his system using the protocols Modbus TCP/RTU, HTTP client/server (HTTPS supported), SNMP.

Due to the built-in memory, the reader can operate autonomously without an external server.

Changelog

1.1 2nd of April 2025

• Firmware revision v0.86,
• Added support of enter command.

1.0 25th of March 2025

• Firmware revision v0.81

Device construction

Technical characteristics

Because of different installation needs, the device does not have any mounting openings in the enclosure. Openings should be made by the customer anywhere in the rear section of the housing - this does not void warranty. Remember to use a proper cable gland in order to maintain the declared ingress protection.

Dimensions

• Version with a numerical keypad:

Connector description

1. RESET – Pressing and holding the button for 10-15 seconds restores the device to factory settings,
2. Power jumpers – Passive PoE power jumpers: Remove the jumpers if using the screw terminal power! (Only in Passive PoE version),
3. LAN – LAN connection socket,
4. RS485 – RS485 connector – Modbus RTU connector (option),
5. RelayMode – Relay mode jumpers. In position 1-2 - NO relay output, position 2-3 - PWR output voltage is supplied from the power input (12-24VDC),
6. REL1 – Relay 1 connector,
7. REL2 – Relay 2 connector,
8. IN1 – General purpose input No. 1,
9. IN2 – General purpose input No. 2,
10. +12V- – 12-24V DC module power supply input.

REL1 and REL2 outputs can operate in two modes:

• PWR mode – Configuration jumpers set in position 2-3 (as shown in the image below). In this mode, an activated relay will provide the output with the power supply voltage eg. 12V DC. If the reader is powered with 24V DC, 24V DC will be provided.

• Normally Open mode – Jumpers set in position 1-2 (as shown in the image below). In this mode an external power source is necessary.

Communication channels and general characteristics

RFID RCP general view

RFID RCP with buttons general view

RFID RCP with numerical keypad general view

The module communicates by using LAN or RS-485.

The following methods can be used to access the read RFID tag:

• Built-in WWW server, available from a standard web browser,
• HTTP/HTTPS in server mode,
• HTTP/HTTPS in client mode,
• Modbus TCP,
• Modbus RTU (RS-485) (option),
• SNMP.

The module is equipped with an LCD display or LED indicators, informing about power supply and current device state.

Network configuration

After the initial power-up, it's needed to configure the device. It can be done in two ways, the simplest method is to use the Inveo Discoverer programme.

Changing the device's IP address - Discoverer programme

After running the Discoverer programme and searching for the appropriate device:

1. Right-click the device,
2. Click the Change settings button.

After the dialogue window is opened you can:

• Set the IP address, mask, gateway, DNS1/DNS2,
• Change the Host name.

If Remote Config is disabled (enabled by default), the device needs to be configured by changing the computer's subnet:

To enable remote configuration:

1. Go to the Administration tab,
2. In the Access configuration window, select Enable Remote Config.

Changing the computer's subnet address for configuration

During configuration without Discoverer programme, it's needed to change the subnet address of the computer on the same network.

To access the computer's network configuration, do one of the following:

• Press Win + R, type in ncpa.cpl, and then press Enter,
• Alternatively, go to:
  Start → Control Panel → Network and Internet → Network and sharing center → Change adapter settings.

Then:

1. Select the network connection,
2. Right-click it and select Properties,
3. After selecting this option, network connection configuration screen will appear,

Select Internet protocol version 4 (TCP/IPv4) and type in the following parameters:

Network settings configuration

To customise the device's network settings, go to the Network tab. Parameters such as the IP address, subnet mask, gateway, DNS, and other network-specific options can be configured here.

• DHCP – Enable/disable DHCP server,
• IP – Device IP address,
• Netmask – IP subnet mask,
• Gateway – Network gateway,
• DNS1, DNS2 – DNS server addresses.

Communication with the module from an external network

If the module is located in a different LAN, port forwarding is required. Depending on the communication method utilized, contact with the network administrator and forwarding of certain ports is needed.

WWW webpage and HTTP protocol:

• TCP/IP port 80

MODBUS TCP:

• TCP/IP port 502

SNMP protocol:

• UDP port 161

Device configuration

Device status – home tab

Device status is available via the www page (default 192.168.111.15).

After the tab is selected, the Status table will be displayed:

• Input 1 – Current input No. 1 state (binary input),
• Input 2 – Current input No. 2 state (binary input),
• Relay 1 – Current relay output No. 1 state,
• Relay 2 – Current relay output No. 2 state,
• Last read ID – Last read tag in HEX,
• ID known as – Read tag type (unknown/user),
• Number of read ID – Number of tags read since last device restart,
• Active Groups – Currently active group numbers,
• Other info – This field informs about server response timeout ()Protocol Timeout!).

Reader operation modes

The device allows for operating mode selection. Extensive control options enable stand-alone operation and program control.

Autonomous mode

The device operates in stand-alone mode, the reader compares the tags with internal memory, opens the door in response to application of a saved card etc.

Program control mode

The module can be controlled with protocols. In this setting, the communication timeout time can be defined, after which the reader switches back to autonomous mode. It should be noted that the reader will return to program control mode after connection is restored.

Advanced operation mode settings

• ID Compare Length – ID length will be compared with the card database,
• Swap ID – ID bytes swap function,
• Variable ID length – Set UID length (only in Mifare version),
• Read Delay – Subsequent tags read delay (0,1s; 150=15s),
• Continuous reading – Hotel mode – During protocol control operation, the card is visible only while it is applied to the reader, its ID is replaced with zeros after it's removed.

Additionally, Pulse output mode can be set in the I/O Settings / Output Relay 1 table. This means that the output will still be activated for a specified period of time (eg. 40*0.1s=4s) after a card is removed.

This function is most commonly used to provide power to a machine that should be active only when an authorized worker inserts a card into the reader. Similar to hotel systems – Room power is on after the card is inserted into the reader (special purpose enclosures),

• Prevent auto IO control – Forces program control of outputs, LED's and the LCD display when the reader is controlled via a protocol. This option is useful in conjunction with communication timeout, after the reader switches to autonomous mode. In result, the server/controller must control interaction with the user. After communication is lost and the reader automatically enters autonomous mode, the reader will react according to the I/O Settings,
• HTTPClient IO control by code – In HTTP Client mode, the LED's and sound signal will depend on the response codes (eg. 200, 401, 404).

Managing cards

The reader allows for managing cards both via implemented communication protocols and external software.

Adding and removing cards using a web browser

Tags can be assigned manually in the Cards tab.

To add a new user's card, click Add User by reader in the Cards tab, then apply the card to the reader. Card assignment will be indicated by an appropriate sound signal. If the user doesn't physically hold the tag, but it's needed to add a new user, click Add User manual.

In the window, assign a user name, input the card ID and specify group membership. Apply the data using Add Card. A new record will appear in the List of cards after a successful card add operation. The table allows for card data editing. The Active field activates or deactivates the selected card. Thanks to this, a blocked user will not be recognized after his card is applied. The Group option is responsible for activating the card on a specified time.

The button saves the current settings.
deletes the card from memory.

Download of all reader card data is available by recalling cardList.xml (eg. http://192.168.111.15/cardList.xml).

Sample card data file:

<cardList>
    <cardItem>
        <no>7</no>
        <name>John</name>
        <active>1</active>
        <group>1111</group>
        <cardId>00000000000000</cardId>
    </cardItem>
    <cardItem>
        <no>8</no>
        <name>Alice</name>
        <active>1</active>
        <group>1111</group>
        <cardId>00111111111111</cardId>
    </cardItem>
</cardList>

The card can also be added by using the RfidIndManager PC programme. To save the cards to the reader's memory, select a CSV file with a card number, user name, and card ID. RfidIndManager will initiate communication with the module and save the cards to the device's memory.

Adding cards by using Modbus

The module is equipped with Modbus protocol. Card ID and user name can be saved to the memory by using this protocol. In the following example, the values are sent to the Holding Registers in decimal.

Mifare card example

• Card number: 8,
• Card ID: 4923267D,

• User name: John.

• Enable Modbus TCP or RTU in the module,

• Connect the module to the PC using a USB to RS485 converter or TCP to make Modbus communication possible,
• Run the Modbus service programme and set the PC as a Master. For easier configuration, set the display option for Holding Registers from 1100 to 1149 (50 records),
• After configuration is complete, open the address edition window. To save the card number, send a value minus 1 to Holding Register 1100. For number 8, send 7,
• The next step is to select the card settings (such as: card activation, group membership) by sending an appropriate value to Holding Register 1101.

Dividing card ID to bytes and converting it to decimal:

49 (hex)=73 (dec)
23 (hex)=35 (dec)
26 (hex)=38 (dec)
7D (hex)=125 (dec)

4 bytes for Mifare cards, 5 bytes for Unique cards

Sending of card IDs happens by sending subsequent bytes to Holding Registers 1102-1105.

1. Assign a user name by converting it to ASCII code:

J=74
o=111
h=104
n=110

After the user name is converted to ASCII, send the code values to Holding Registers starting from 1110 (1110-1113 in this example). The name must end with NULL – after the last character, send a 0 to the next address (1114 in this example).

The following screenshot features the Holding Registers with values from the example:

Own API (http GET)

A card can be added to the reader's memory by using HTTP GET commands.

To add a card, type one of the following addresses into a web browser:

• In HEX: "IP_address"/msg.php?addId="card_ID"

• In decimal: "IP_address"/msg.php?addDecId="card_ID"

The device returns a number, under which the card was saved: Return: 8

Using this number, assign a user name by typing: IP_address/msg.php?changeName=”card_ID!”username

A card can also be added by using the command: IP_address/msg.php?addCard

Read the card first, and then type the above command in to the browser. The device saves the last read tag. After using this command, the card number will be returned. To assign a name, use the command: „IP_address”/msg.php?changeName=”card_ID!”username”

More HTTP GET commands are described in the HTTP GET – control chapter.

Saving data to Mifare and ICODE cards – HTTP GET command

The reader can save Mifare Classic 1k/4k and ICODE card blocks. Data can be saved to any memory block.

Saving data to an ICODE card

ICODE cards are equipped with an EEPROM. Data can both be written and read. The tag memory is divided into blocks, 4 bytes each.

The user can write and read the card contents. Using relevant parameters, 16 bytes of tag memory (4 data blocks) can be written at a time. If writing less bytes than a multiple of 4 (length of a single ICODE block), the remaining bytes will be overwritten with zeros. – example 1

Syntax: IP_address/block.xml?block=block_no&data=data

• block – Block to be written/read,
• data – Up to 16 bytes of data in HEX format.

After the command is sent, apply the card to the reader. The reader will respond in the following way:

<cardContent>
    <result>0</result>
    <uid>9D720004000004E0</uid>
    <block>33333333444444445555555566666666</block>
</cardContent>

If the result value is different than 0 – the write operation failed.

<cardContent>
    <result>0</result>
    <uid>9D720004000004E0</uid>
    <block>1A999999</block>
</cardContent>

<cardContent>
    <result>10</result>
    <uid>0000001CC60D0D</uid>
    <block>ABA00D00000000000000000000000000</block>
</cardContent>

Reading Mifare and ICODE blocks

The reader can read the memory blocks of Mifare Classic 1k/4k and ICODE cards.
Any block can be read from the memory. The read data is available via HTTPClient and Modbus (from Holding Register 100). In HTTP Client, a "block" field is added to the HTTP GET request, containing the hex value of data read (16 bytes). Additionally, the read block can be assigned as a card UID. In this case, the number of copied block bytes corresponds to the length of the card UID (eg. 8 bytes for ICODE tags).

Reading ICODE block contents – Block Reader

In the RFID Settings tab, ICODE Block Reader table, ICODE card blocks readout can be configured – HTTP Client, Modbus, autonomous operation.

• Enable – Enable the block reading function,
• Block address,
• Override UID – Override card ID with read data,
• Offset for UID – Number of the byte in a block the data read operation starts from,
• Add data to HTTPClient – Read block will be added to a GET request in HTTP Client mode.

Read block using Modbus – data contain Holding Registers 100 - 115:

Reading ICODE tag contents – HTTP GET command

ICODE cards are equipped with EEPROM. They can both be read and written. 1024 memory bits (128B) divided into 32 blocks 4 bytes each, are available to the user.

The user can write and read tag contents. To read the card, use the command: IP_address/block.xml?block=block_no.

After the command is sent, apply the card to the reader. The reader will respond in the following way:

<cardContent>
    <result>0</result>
    <uid>9D720004000004E0</uid>
    <block>33333333444444445555555566666666</block>
</cardContent>

If the result value is different than 0 – the write operation failed.

Reading Mifare Classic 1k/4k blocks – Block Reader

In the RFID Settings tab, Mifare Block Reader table, Mifare card block readout can be configured – HTTP Client, Modbus, autonomous operation.

• Enable – Enable the block reading function,
• Block address,
• Auth key – Authentication key in HEX format - the key is saved in secure memory (write only). The key should be written only when a change is required. Default key: 6xff (FFFFFFFFFFFF),
• Auth key B – Key selection. By default, key "A". If key "B" must be used, select this option,
• Override UID – Override card ID with read data,
• Offset for UID – Number of the byte in a block the data read operation starts from,
• Add data to HTTPClient – Read block will be added to a GET request in HTTP Client mode.

Example block read using HTTPClient:

GET?mac=000000000000&ip=192.168.0.236&name=&id=697C0004000004E0&inout=0&block=99999911112842376AAAFFFAFAFA1122&io=0&put=1

Block read via Modbus – data contains the Holding Registers 100 – 115.

Reading Mifare Classic 1k/4k data – HTTP GET command

The user can write and read tag contents. 16 bytes can be read at one time by sending appropriate parameters (1 memory block of the tag).

Syntax:
IP_address/block.xml?block=block_no&keyType=AlubB&keyIdx=0-7

• block – Number of block to read data from,
• keyType – Authorization type: key A or key B,
• keyIdx – Memory key index (0-7) – described below.

After the command is sent, apply the card to the reader.

The reader will respond in the following way:

<cardContent>
    <result>0</result>
    <uid>0000001CC60D0D</uid>
    <block>ABA00D00000000000000000000000000</block>
</cardContent>

If the result value is different than 0 – the write operation failed.

The user can set up to 8 Mifare keys. Specific key should be reacalled by keyIdx. By default, all keys (0-7) have the value of FFFFFFFFFFFF.
We suggest that the key ‘0’ remains unchanged. Mifare tags have default keys A and B set to FFFFFFFFFFFF.

To set a Mifare key, send 2 parameters:

• keyIdx – Location number,
• key – Key in HEX format (6 bytes → 12 hex characters).

Syntax:
IP_address/block.xml?keyIdx=location_no&key=key

After the command is sent, apply the card to the reader.

<cardContent>
    <result>12</result>
    <uid>00000000000000</uid>
    <block>00000000000000000000000000000000</block>
</cardContent>

Warning! (for writing a key) - If result is equal to 12 – key write operation was successful. - If result is equal to 11 – key write operation has failed.

<cardContent>
    <result>0</result>
    <uid>0000001CC60D0D</uid>
    <block>99000000000000000000000000000000</block>
</cardContent>

<cardContent>
    <result>10</result>
    <uid>0000001CC60D0D</uid>
    <block>00000000000000000000000000000000</block>
</cardContent>

Access – card groups

The reader allows activation of select cards at a specified time.
This means that you need to set the card activation time from which the user will be recognized in the system.
Group configuration can be done in the Access tab.

In the Access Groups table, 4 conditions can be defined that can be assigned to 4 groups. The table fields have the following meaning:

• Enable rule – Enable selected comdition,
• Start time – The time from which the respective groups are activated and the previous ones deactivated (at 21:00, groups No. 1 and No. 2 are deactivated, and groups No. 3 and No. 4 are activated),
• Group 1-4 – Assignment of condition to groups.

Save the configuration of each condition.

Events logging

The reader can log tag application events.

For the reader to register RFID tag application to its memory, select an appropriate Log mode in RFID Settings → Logger.

Event preview is available via:

• www page (Logs tab).
• XML file,
• Modbus - read from appropriate addresses,
• raw file.

Events configuration

• Log mode:
  • Disabled,
  • Enabled.
• Log a card removal – Selecting this option will additionally register a card removal event after it was held for longer than 5 seconds. Option available only in 'Continuous reading' mode,
• Log when control by protocol – This option allows logging of events even when the reader is controlled by a protocol. By default, when protocol control is enabled, the reader does not store events.

Events preview via a www page

The Log table contains the card read history.

The marked flag indicates an attempt to read a card that is not present in the device's memory or is set as inactive.

Clicking Remove logs will remove all logs from the device's memory.

Events preview using an XML file

The user can download all device logs by recalling the IP_address/logList.xml resource or by clicking XML in the Logs tab:

<logList>
    <logItem>
        <no>1</no>
        <id>8</id>
        <name>Rex</name>
        <cardId>00000061F3911B</cardId>
        <state>10000000</state>
        <time>1743501257</time>
    </logItem>
    <logItem>
        <no>2</no>
        <id>7</id>
        <name>John</name>
        <cardId>00000031C19E1B</cardId>
        <state>10000000</state>
        <time>1743501259</time>
    </logItem>
    <logItem>
        <no>3</no>
        <id>0</id>
        <name/>
        <cardId>000000D57E2014</cardId>
        <state>11000000</state>
        <time>1743501263</time>
    </logItem>
</logList>

• no – Reading No.,
• id – Card number defined in Cards minus 1,
• name – Name assigned to the user. For unknown or inactive cards, this tag is empty,
• cardID – Card UID number,
• state – Applies only to RFID RCP with buttons – flag specifying which function keys have been selected:

• time – Unix timestamp.

Downloading logs in the form of a CSV file

The option to download logs in CSV formati is available by clicking CSV in the Logs tab.

The CSV file contains event records, such as a subsequent number, card user ID (if identified), card ID number, card user name (if defined), date and time of the event, and card mode flag. Additionally, it contains a Unix timestamp for precision. The following table explaining the card mode flags can be used to interpret the data:

For example, if the flag value is 128, this indicates that a card has been applied. Flag 1024 indicates the current output 1 state. Adding those values (for a flag 1152), we can assume that the card application caused the output 1 state to change.
Thanks to this option, the user can easily download and interpret the logs registered by the device in CSV format, enabling further analysis and data management.

LCD text

In the Text Message tab, it's possible to configure the device's display settings.

Time table

In this table, the display language of the time shown in the first row of the display can be configured.

LCD Message table In this table, displaying of notifications on the LCD screen can be activated and a Large font size enabled.

Prompt Message, Enter Accept Message and Enter Rejest Message tables

In the tables, it's possible to configure the texts displayed on the screen during various events: application of a known card, application of an inactive card, hold time.

Reaction for events (inputs / outputs) – I/O Settings

The reader can autonomously control sound and optical signaling, door bolt relay, and alarm state. Functions are described in the tables below.

Selecting Door unlock in the Input 1 table forces automatic activation of relay 1 (door bolt) after input 1 is activated (shorted):

The Input 2 table allows the user to set a reaction for the opening of input No, 2:

Selecting Open Timeout Alarm will activate the function of automatic activation of relay 2 in the event input 2 remains open for a time longer than Max Time.

By using this function, an open door sensor can be connected to input 1 and an alarm siren to output 2. Thanks to this, if someone opens the door and it is not shut within the defined time or remains partially open, an alarm will sound.

Remember to Save all changes.

In the Output Relay 1, Output Relay 2 tables, module outputs can be configured independently.

• Mode:
  • Disabled – Disable relay control,
  • Pulse – After activation, the relay remains on for a specified period of time (eg. door control),
  • Toggle – Tag read event causes the output to invert its state.
• Time-on – Relay activation time in Pulse mode. In 0,1s units (20 means 2 seconds),
• Action – Action that causes the output to activate:
  • None – Control via HTTP, SMNP, Modbus,
  • All Cards – Output is activated after any RFID tag application (doesn't matter whether it's saved to the module's memory or not),
  • Known Cards – Output is activated only after an active tag is applied,
  • Unknown Cards – Output is activated only after an unknown/inactive tag is applied.
• Invert output – Inverts the output type from NO to NC,
• Long Open – Output is activated for a time period defined in this field after a card has been applied to more than 5 seconds:

Function available only for output No. 1, allowing its activation for a longer period of time, up to 38912s.

Function activation:

• Option operates only when the output is set to Pulse mode,
• User's card must be active and assigned to group 4,
• Group 4 does not need to be active, but the card must be assigned to it.

After the User2 card is applied to the reader, output 1 is activated for 4 seconds (0,1*40). If the card remains in the read field for more than 5 seconds, the output will be activated for additional 10 seconds: - Output No. 1 is activated for 4 seconds, - Output is deactivated for 1 second, - Output is activated again for 10 seconds.

Sound signaling  
- The user will hear the stadard read sound while applying the card,
- If the card is held in the read field form more than 5 seconds, the device will emit single-tone sounds,
- The last high tone signals the Long Open function activation.

Thanks to this option, relay output No. 1 can be configured for a longer time, which may be useful in various applications that need a longer opening time.

Relay activation on a different Inveo device – I/O Settings

The function Bridge Output Relay 1 to external Inveo device allows sending of a request to change the output state of another Inveo device. This allows, for example, to open a door bolt that isn't connected to the reader directly. Communication is carried over a LAN.

• Enable – Enable the relay state forwarding function,
• Server IP – IP address of the Inveo device that operates the output be controlled by the reader,
• Port – Port, on which the remote device listens – default 9761 (UDP),
• Channel – Number of the channel in the remote device that will be controlled.

The service forwards the state of relay output 1 to a remote device (eg. LanTick). The relay in the remote device is activated when output 1 is activated in the relay, that's why the settings from Output relay 1 table are important.

Remote module configuration

To enable the service, go to the Administration tab and select Enable Program Access, then Save Config.

Audio/visual signaling – I/O Settings

The reader has 3 kinds of sound signal:

• Accept sound – Two consecutive tones: first one low, second one higher and longer. Positive sound,
• Reject sound – Two consecutive tones: first tone like in accept (short tone), second tone lower and longer. Negative sound,
• Short beep – Only the short tone from accept/reject.

In the Events table, reader behaviour after and RFID tag application can be programmed.

• Sound action – Action that triggers the sound signal:
  • None,
  • All Cards (Accept tone) – Module emits the accept sound after an RFID tag is applied (known or unknown),
  • All Cards (Short beep) – Short signal for all tags*,
  • Known Cards – Emits the positive sound for known and negative for unknown tags.
• LED/LCD Backlight Action – Action that triggers LCD or LED activation:
  • None – Control by HTTP, SMNP, Modbus,
  • All Cards,
  • Known Cards.

* the short sound signal can be used for communication between the reader and server. In this case, the reader indicates tag readout with a short sound, but it's up to the server to signal the processed information.

LCD screen backlight can be controlled by the reader.

Setting a value of 255 will make the backlight glow constantly.
Setting a value of 0 will disable the backlight. Setting a value of eg. 5 will cause the display to light up for 5 seconds after tag application.

Real Time Clock (RTC)

The readers are equipped with a built-in Real Time Clock (RTC).

The time can be set manually in the Time settings tab, Time status section, using the Update time button. The time will be taken off the system. The time zone can be configured with the list. Selecting Daylight saving forces the use of summer and winter time.

The module can also synchronize the internal clock with a time server utilizing SNTP. The settings can be configured in Network → SNTP.

To enable SNTP sychronization, input the SNTP server's address into the Server field. Typing in 0.0.0.0 disables time sychronization.

SNMP server configuration

The module is equipped with an SNMP v2c server. To enable this function, go to Administration → Services and Enable SNMP.

SNMP allows for:

• Downloading of input state,
• Setting output states,
• Downloading read RFID tag ID's.

MIB file describing the SNMP structure can be downloaded from the SNMP tab by clicking Download MIB file.

Communication protocols and administration

The Administration menu enables configuration of active services and password change.

Module name

Each reader can be assigned with a unique name used for identification.

Change password

To change the password:

1. Input the Current Password,
2. Input the New Password an Re-type Password,
3. Save Config.

Services settings

• Autonomic – Autonomous reader mode,
• Enable Modbus TCP,
• Enable Modbus RTU,
• Enable SNMP,
• Enable HTTP GET,
• Enable HTTP Client,
• Timeout – Time, after which the module will enter autonomous mode if it doesn't receive information from a server,
• Enable Remote Network Config – Enable remote module configuration (Discoverer programme),
• Enable TFTP Bootloader.

Communication protocols

HTTP

HTTP GET – read state

RFID modules can be controlled via HTTP on port 80. To read the current state of the module, complete the following steps:

1. Open a web browser,
2. Enter the address: http://IP_address/status.xml.
   • Replace IP_address with a real device IP.

An XML resource with basic reader information will display in the browser.

Example XML result

<status>
    <model>RFID IND-LCD Mif</model>
    <name/>
    <mac>00:00:00:00:00:00</mac>
    <id>000000D57E2014</id>
    <newId>0</newId>
    <known>1</known>
    <cnt>14</cnt>
    <out0>Off</out0>
    <out1>Off</out1>
    <in0>Off</in0>
    <in1>Off</in1>
    <resetFlag>1</resetFlag>
    <enable>1</enable>
    <group>1234</group>
    <httpClientStatus>0</httpClientStatus>
    <n_logs>4</n_logs>
    <timeout>0</timeout>
    <fw>0.86</fw>
    <hw>1.0</hw>
</status>

HTTP GET – control

Controlling the module in Enable HTTP GET mode involves sending appropriate commands to the reader using HTTP.

http://IP_address/status.xml?

http://IP_address/msg.php?

Editing cards via HTTP POST

The reader allows editing of cards via HTTP POST method. The data structure is located in edit.xml:

id: 6
card: 00
name: User2
act: 1
grp: 0100

• id – Card number from Cards minus 1,
• card – TAG,
• name – User name,
• act – Specifies whether the card is Active (0 or 1),
• grp – Card group assignment (0 means a card is not assigned, 1 means card assigned to a group):

0001 – card assigned to group No. 4,
0111 – card assigned to groups No. 2, 3 and 4.

The POST method data structure has the following form:
id=value&card=00&name=value&act=value&grp=value

Card can be edited by changing appropriate parameters. HTTP POST allows the user to add a new card by using id=-1. The reader will add the card to the first available position.

Card amendment example:

To edit the card, use the cURL programme. cURL enables sending of HTTP requests from the Windows command line. Syntax:

curl -u admin:admin00 -d "id=6&card=00&name=John&act=1&grp=0111" -X POST http://192.168.0.222/edit.html

• -u admin:admin00 – User authorization, user:password,
• -d "id=6&card=00&name=John&act=1&grp=0111" -X POST – Card edit request:
  • id=6 – Card No. 7,
  • card=0 – Card UID can't be changed,
  • name=John – Assign new user name,
  • act=1 – Force new card activation,
  • grp=0111 – Assign card to groups No. 2, 3 i 4,
  • http://192.168.0.222/edit.html – IP address of the module and the resource that should be recalled.

Add card example:

To add a card to the reader's memory, use the cURL programme. Syntax:

curl -u admin:admin00 -d "id=-1&card=0600A4638D&name=Ahr&act=1&grp=1001" -X POST http://192.168.0.222/edit.html

The request shown above will add a new card to the first available position in the reader's memory.

• id=-1 – Force add new card.

HTTP Client

Module control in HTTP Client mode is possible after selecting Enable HTTP Client inAdministration. If the reader has Enable HTTP Client mode activated, configure the address the data will be sent to. To do that, use the Network → HTTP Client Configuration table.

• Server IP – IP address the reader will send data to,
• Server name – Domain address name – if it's registered on a DNS. If the domain address is inputted ino Server IP, fill this field with 0.0.0.0,
• Port – Port, the server is listening on,
• Resource – Resource the reader recalls, eg. /somefile.php,
• Poll time:
  • Poll time=0 - data is sent only when an RFID tag is applied,
  • Poll time>0 - data is sent periodically and after an RFID tag is applied. eg. Poll time=50 - data will be sent every 5 seconds and after an RFID tag is applied.

Sending data to the server

The module sends data to the corresponding server resource depending on whether the reader has read the TAG or because of periodic information exchange.

If the reader has read an RFID tag, the data will be sent in the following format:

• A – MAC address,
• B – IP address,
• C – Reader name (assigned in the Administration tab),
• D – UID of the applied RFID card,
• E – Applies only to RFID RCP with buttons – function key flag (private/official entry/exit),
• F – Timestamp,
• G – Active inputs/outputs information,
• H – Card application or removal flag.

mac=A&ip=B&name=C&id=D&inout=E&ts=F&io=G&H=1

During periodic information exchange, the data is sent to the server in the following format:

• A – MAC address,
• B – IP address,
• C – Reader name (assigned in the Adminsitration tab),
• F – Timestamp,
• G – Active inputs/outputs information.

mac=A&ip=B&name=C&ts=F&io=G

• E – Flag specifying which function keys have been selected (private/official entry/exit) The value is sent as a sum of the components:

• G – State of activated inputs and outputs sent as a sum of the components:

• H – Card application or removal state:

• put=1 – Card applied,

• away=1 – Card removed (only in Continuous reading mode),
• put=1&away=1 – Card applied and instantly removed (only in Continuous reading mode).

Only for Mifare RFID readers:

If the module has block readout enabled, read block information can be added: block=1234567890ABCDEF1234567890ABCDEF.

In response, the server can send nothing or reply with a XML resource:

When operating the reader in HTTP Client mode, the HTTP Response code can be used to control interaction with the user. In the RFID Settings tab, automatic reaction to the 3 basic HTTP response codes (200, 401, 404) can be set – HTTPClient IO control by code

In this configuration, the reader will react depending on the code number that it receives:

• Code 200: generate the „accept” sound and blink the green LED,
• Code 401: generate the „reject” sound and blink the red LED,
• Code 404: generate the „reject” sound an blink both LEDs.

The XML file can contain the following fields (the example sounds the accept sound, opens the door and displays text on the LCD)

<buzz>1</buzz>
<clear>0</clear>
<text>Enter please</text>
<open>1</open>

Activate the green LED for 2 seconds:

<ledg>20,0,1</ledg>

Blink the red LED 2 times with a time of 0.5/0.5 seconds:

<ledr>5,5,2</ledr>

The XML file syntax is not checked. Only information between the known tags is browsed.

Php server support example:

<?php
if( $_GET["id"] ) // module send id and MAC - $_GET["mac"]
{
    $who=$_GET["id"];
    // you can check id in DB and do some action
    echo "<buzz>1</buzz>"; // sound signal
    echo "<clear>1</clear>"; // clear LCD
    echo "<text>Card ID: $who</text>" // print ID on LCD
    echo "<open>1</open>"; // door open
}
else // no id - default state polling
{
    echo "<clear>1</clear>"; // clear LCD
    echo "<text>Hello</text>"; //print prompt text
}

Modbus

Modbus is available via RS-485 (Modbus RTU) or TCP (Modbus TCP). RS-485 port settings are located in the Administration tab.

• PDU – Device's Modbus address,
• Baudrate – Transmission speed:
  • 1200,
  • 2400,
  • 4800,
  • 9600,
  • 19200,
  • 38400,
  • 57600,
  • 115200.
• Parity:
  • None,
  • None and 2 stop,
  • Even,
  • Odd,
  • Mark,
  • Space.

After all parameters have been set, enable the Modbus RTU service and Save the configuration.

The device supports the following Modbus RTU functions:

• 0x01 Read Coils
• 0x03 Read Holding Register
• 0x05 Write Single Coil
• 0x06 Write Single Register
• 0x0F Write Multiple Coils
• 0x10 Write Multiple Registers

RFID control

The Holding Registers 1000-1007 addresses have been distributed this way for backwards compatibility.

Card records amendment

Card settings (1101 Holding Registers):

If the user card is modified, 1101 Holding Register is responsible for storing the card in reader's memory, its activation and the groups that are assigned to this card.

Example of values with explanation:

• Delete card from reader's memory – value 0,
• Simultaneous card deactivation and assignment to group No. 1 – value 5,
• Asignment of card to all groups – value 63.

Log records

Read card control

LCD

2 characters should be sent to one Holding Register address. To write "John" from the beginning of the second display row, convert the characters using an ASCII table:

• J = hex 4A,
• o = hex 6F,
• h = hex 68,
• n = hex 6E.

After that, send 4A6F to address 2020 and 686E to address 2021. Space character is represented by 0x1E.

Input/Output IO

Integration with own software

Inveo RFID readers can be integrated with own software, operating in server mode (Administration > Enable HTTP GET) or client mode (Administration > Enable HTTP Client)

Server mode (HTTP Server)

In this mode, the reader operates as a server. A remote host (client) connects with the module and manages it using HTTP GET. To enable this mode, select Administration → Enable HTTP GET

• Read status: the client periodically reads the status.xml file, decodes the XML tag it's interested in and returns commands to the reader when needed. The status.xml tag contains all required information that can be saved to a database, such as the reader's MAC address, input and output state, and card ID.
• User interaction: After using the data, the client can send commands to the reader, such as accept/reject sound, LED blink, door bolt release or LCD text. The reader blocks the readout of subsequent tags until the client recalls releaseId=1.
• Sound signal: If the communication isn't happening in real-time, the reader can emit a short sound after a tag has been read, informing the user about the fact. The user does not need to hold the card in the read field indefinitely – only until they hear a sound effect.

Client mode (HTTP Client)

In this mode, the reader operates similarly to a web browser. It sends requests to the server and awaits replies. The server awaits requests, processes them and sends an appropriate answer. To activate this mode, go to Administration → Enable HTTP Client.

• Sending data: the module automatically connects with the server and sends the read tag information via HTTP GET. The server processes the request and sends a reply in the form of an XML file containing commands that define module operation: LED control, sound signal, LCD screen.
• Direct integration: The module sends a code to the server or a controlling application by itself right after a card is read. The client-server mode enables easy integration with PHP, Node JS, MySQL servers.

Factory settings, backup

Restoring factory settings

To restore the factory settings:

• Power up the device,
• Short the jumper (RFID IND) or press the RESET button (RFID RCP) for a time period between 10 and 15 seconds,
• Remove the jumper or release the button during the sound signal.

Once the above steps have been completed, the device will be set to the following parameters:

• IP address: 192.168.111.15
• IP mask: 255.255.255.0
• User: admin
• Password: admin00

Warranty and manufacturer's liability

The manufacturer undertakes to respect the warranty agreement, if the following conditions are met:

• All repairs, changes, expansions and device calibrations are carried out by the manufacturer or an authorized service center,
• The power supply system meets the applicable standards,
• The device is operated in accordance with the suggestions presented in this manual,
• The device is operated in accordance with its intended purpose.

The manufacturer assumes no responsibility for consequences resulting from improper installation, improper use of the device, failure to comply with the instruction manual, and repairs made by unauthorized personnel.

Storage, operation and transport conditions

The device should be stored in enclosed rooms, where the atmosphere is free from vapours and corrosive substances:

• Environment temperature from -30°C to +60°C (-22°F - 140°F),
• Humidity from 25% to 90% (condensation unacceptable),
• Atmospheric pressure from 700 to 1060 hPa.

The device is intended to operate in the following conditions:

• Environment temperature from -10°C do +55°C (14°F - 131°F),
• Humidity from 30% to 75%,
• Atmospheric pressure from 700 to 1060 hPa.

Recommended transport conditions:

• Environment temperature from -40°C do +85°C (-40°F - 185°F),
• Humidity from 5% to 95%,
• Atmospheric pressure from 700 to 1060 hPa.

Installation and device operation:

• The module should be operated in accordance with recommendations provided later in this manual.

Disposal and decommissioning

In an event the device needs to be decommissioned (eg. after its intended life period is surpassed), it is recommended to contact the manufacturer or his representative, who are responsible to respond appropriately, i.e., to collect the device from the user. The user can alternatively contact companies specializing in electronic device or computer equipment disposal and/or decommissioning. Under no condition should the device be placed with other waste.