Supported readers
This document is dedicated to AspireRFID users in charge of using the following readers:
Tagsys Medio L100 and L200
TAGSYS MedioTM L100 and Medio L200 are robust, long range and multiread HF RFID readers. Packaged in rugged casings, they are both ideal for use in industrial applications where 3D volume detection is required, such as production and distribution sites.
TAGSYS Medio L100 and Medio L200 are powerful and long range readers, designed for challenging environments. They are multi-protocols, ISO 15693 compatible and operate at 13.56MHz. Each reader offers 4 configurable I/O ports enabling end-users to connect a wide choice of RFID antenna to detect several RFID-tagged items simultaneously.
The Medio L100 reader has 2 RF channels,while the Medio L200 has 4.
Requirements
Hardware
- Reader : Medio L100/L200 long Range HF RFID Reader
- Antenna : Tagsys Aero LB Antenna, optimized to operate with Tagsys mid and long-range Medio readers + its coaxial cable and BNC connector.
- Tag : HF tag that can be decoded by the reader, must be one of the supported protocols : C210, C240, C270, C370 (ISO15693).
Software
- Tomcat Apache server installed (Tomcat 6 or later version)
- AspireRfidIDE executable tool can be downloaded here
- AspireRFID ALE war file here
Preliminary configurations
AspireRfidIDE configurationThis tool provides means of configuration of the underlying ASPIRE infrastructure. The user can describe his requirements to the IDE, which provides all the configuration options, and translates them into configuration messages by which it will supply all the appropriate modules.
After downloading the repository, unzip it and lunch the executable file.
The tool can be configured through the IDE's preferences window (Window>Preferences).
Choose the Ale Server Configurator from the list appearing at the left see the picture below.
From there you can configure the :
- ALE client end point: Set the end point to the filtering and collection server's by giving the name of the ALE war file (fc-server-version.war) with the right version (1.2.2). This file must be set to : http:// localhost:8080/fc-server-1.2.2-SNAPSHOT/services/ALEService
- ALE client end point: must be set to :
http:// localhost:8080/fc-server-1.2.2-SNAPSHOT/services/ALELRService
- RP LRSpecs Directory : The directory where LRSpecs1 for RP readers will be stored.
- EC Specs Directory: The directory where ECSpecs2 will be stored which will be used to configure the server?s filtering function.
- Reader name: Add the reader name (Tagsys Reader for example).
Push Apply to save the new configurations, then Ok to close the window.
Create LRSpec
LRSpec is the Logical Reader Specifications, it is an xml file understandable by AspireRfid core used to define a reader. This file is provided for AspireRfidIDE tool to specify the reader settings : the class that will be called to create the reader, the used media (serial), the tag types that can be read…
This LRSpec must be saved under the RP directory.
To make the LRSpec, create a text file, copy the content of the box below and save it as an xml file in the RP directory (C:Documents and SettingsuserAspireRFIDIDELRSpecsRP).
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns3:LRSpec xmlns:ns2="urn:epcglobal:ale:wsdl:1" xmlns:ns3="urn:epcglobal:ale:xsd:1">
<isComposite>false</isComposite>
<readers/>
<properties>
<property>
<name>ReaderType</name>
<value>org.fosstrak.ale.server.readers.medio.MedioAdaptor</value>
</property>
<property>
<name>Description</name>
<value>This Intermec Logical Reader consists of Antenna1</value>
</property>
<property>
<name>PhysicalReaderName</name>
<value>TagsysReader</value>
</property>
<property>
<name>PhysicalReaderSource</name>
<value>Antenna1</value>
</property>
<property>
<name>tagsys.mediolx00.settings.iMediaType</name>
<value>serial</value>
</property>
<property>
<name>tagsys.mediolx00.settings.strSerialName</name>
<value>COM1</value>
</property>
<property>
<name>tagsys.mediolx00.settings.iSerialSpeed</name>
<value>38400</value>
</property>
<property>
<name>tagsys.mediolx00.settings.iPower</name>
<value>1</value>
</property> <!-- 0 is off and channels could be 1,2,3,4 -->
<property>
<name>tagsys.mediolx00.settings.iChannel</name>
<value>1</value>
</property> <!--values are TAG_C210, TAG_C240, TAG_C270, TAG_ISO15693-->
<property>
<name>tagsys.mediolx00.settings.strTagType</name>
<value>TAG_ISO15693</value>
</property>
<property>
<name>tagsys.mediolx00.settings.boCont</name>
<value>true</value>
</property> <property>
<name>tagsys.mediolx00.settings.boSort</name>
<value>false</value>
</property> <!-- timer between 2 reads (in millisec) -->
<property>
<name>tagsys.mediolx00.settings.iTimer</name>
<value>250</value>
</property> </properties>
</ns3:LRSpec>
Event Cycle Specification (ECSpec) is an xml file describing filtering and collection behavior. This tells the Middleware how the RFID tag reads ariving from the reader should be filtered and aggregated, for example : added, current or deleted tags.
This file must be created (same method as the LRSpec) and saved under the EC Spec directory (C:Documents and SettingsuserAspireRFIDIDEECSpecs)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:ECSpec xmlns:ns2="urn:epcglobal:ale:xsd:1">
<logicalReaders>
<logicalReader>TagsysReader</logicalReader>
</logicalReaders>
<boundarySpec>
<repeatPeriod unit="MS">10000</repeatPeriod>
<duration unit="MS">9500</duration>
<stableSetInterval unit="MS">0</stableSetInterval>
</boundarySpec>
<reportSpecs>
<reportSpec>
<reportSet set="CURRENT"/>
<output includeRawHex="true" includeRawDecimal="true" includeEPC="true" includeTag="true"/>
</reportSpec>
</reportSpecs>
</ns2:ECSpec>
Tomcat is used in order to deploy the Filtering and Collection server.
Copy the two WAR file (fc-server-version.war) into the Tomcat's webapps directory and start Tomcat. The war file will be deployed into a new folder.
You will usually find the webapps folder inside the tomcat installation directory (C:Program FilesApache Software FoundationTomcatwebapps).
Deployment
Now that all configurations are done, the reader can be tested.
- Plug-in the reader's power supply,
- Connect the reader into the RS232 connector and check which serial port is used (make sure that it is the same as LRSpec file),
- Connect the antenna to the reader,
- Put the tag in the antenna range,
- Make sure that Tomcat server is started (if you are using windows check the graphic interface on the task bar, if your using Linux check with the command line : service tomcat7 status)
- Go to AspireRfidIDE and push the Get vendor version in LRSpecConfiguratorView. A version number should be returned in the console tab (if not check again the configurations).
- To define the new reader as shown in the picture below, push Define button and select the LRSpec already defined and press Execute.
A dialog box will appear with the message : Lrspec successfully defined!
Now define the ECSpec for the same reader.
A text file will be created with the read tags under C:Documents and SettingsuserScans.
For example, for a tag ISO15693 reading, the generated report is :
E00401000E197F26 (DSFID:00),ISO15693
TagSys Medio TR-P101 and P101
The Medio TR-P101 and P101 readers are a low cost of ownership RFID solution that are ideal for applications requiring a single antenna. The rugged design provides long-lasting performance in harsh environments, and the remote upgradability feature offers an efficient method for maintaining an RFID infrastructure without leveraging valuable resources. High performance features such as dual operating modes and 1W power output make the Medio TR-P101 an effective RFID solution for textile service applications, and the Medio P101 a good RFID reader for a multitude of applications and settings ranging from manufacturing to library checkout stations.
Requirements
Hardware
- Reader : Medio TR-P101 Mid-Range HF RFID Reader (delivered with 1 SMA/BNC Adaptor, 1 RS232 cable and 1 Universal Power Supply).
- Antenna : Tagsys Aero LB Antenna, optimized to operate with Tagsys? mid and long-range Medio? readers + its coaxial cable and BNC connector.
- Tag : Tag : HF tag that can be decoded by the reader, must be one of these protocols : C210, C240, C270, C370 (ISO15693).
Software
- Tomcat Apache server installed (Tomcat 6 or later version)
- AspireRfidIDE executable tool can be downloaded here
- AspireRFID ALE war file here
Preliminary configurations
AspireRfidIDE configurationThis tool provides means of configuration of the underlying ASPIRE infrastructure. The user can describe his requirements to the IDE, which provides all the configuration options, and translates them into configuration messages by which it will supply all the appropriate modules.
After downloading the repository, unzip it and lunch the executable file.
The tool can be configured through the IDE's preferences window (Window>Preferences).
Choose the Ale Server Configurator from the list appearing at the left see the picture below.
From there you can configure the :
- ALE client end point: Set the end point to the filtering and collection server's by giving the name of the ALE war file (fc-server-version.war) with the right version (1.2.2). This file must be set to : http:// localhost:8080/fc-server-1.2.2-SNAPSHOT/services/ALEService
- ALE client end point: must be set to :
http:// localhost:8080/fc-server-1.2.2-SNAPSHOT/services/ALELRService
- RP LRSpecs Directory : The directory where LRSpecs1 for RP readers will be stored.
- EC Specs Directory: The directory where ECSpecs2 will be stored which will be used to configure the server?s filtering function.
- Reader name: Add the reader name (Tagsys Reader for example).
Push Apply to save the new configurations, then Ok to close the window.
Create LRSpec
LRSpec is the Logical Reader Specifications, it is an xml file understandable by AspireRfid core used to define a reader. This file is provided for AspireRfidIDE tool to specify the reader settings : the class that will be called to create the reader, the used media (serial), the tag types that can be read…
This LRSpec must be saved under the RP directory.
To make the LRSpec, create a text file, copy the content of the box below and save it as an xml file in the RP directory (C:Documents and SettingsuserAspireRFIDIDELRSpecsRP).
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns3:LRSpec xmlns:ns2="urn:epcglobal:ale:wsdl:1" xmlns:ns3="urn:epcglobal:ale:xsd:1">
<isComposite>false</isComposite>
<readers/>
<properties>
<property>
<name>ReaderType</name>
<value>org.fosstrak.ale.server.readers.tagsys.Trp101Adaptor</value>
</property>
<property>
<name>Description</name>
<value>This Intermec Logical Reader consists of Antenna1</value>
</property>
<property>
<name>ConnectionPoint</name>
<value>http://localhost:8000</value>
</property>
<property>
<name>NotificationPoint</name>
<value>http://localhost:9090</value>
</property>
<property>
<name>ReadTimeInterval</name>
<value>1500</value>
</property>
<!--property>
<name>AdaptorClass</name>
<value>org.fosstrak.ale.server.readers.tagsys.Trp101Adaptor</value>
</property>
<property>
<name>ImplementationClass</name>
<value>org.fosstrak.ale.server.readers.tagsys.Trp101Adaptor</value>
</property-->
<property>
<name>PhysicalReaderName</name>
<value>TagsysReader</value>
</property>
<property>
<name>PhysicalReaderSource</name>
<value>Antenna1</value>
</property>
<property>
<name>tagsys.mediolx00.settings.iMediaType</name>
<value>serial</value>
</property>
<property>
<name>tagsys.mediolx00.settings.strSerialName</name>
<value>COM1</value>
</property>
<property>
<name>tagsys.mediolx00.settings.iSerialSpeed</name>
<value>38400</value>
</property>
<property>
<name>tagsys.mediolx00.settings.iPower</name>
<value>1</value>
</property> <!-- 0 is off and channels could be 1,2,3,4 -->
<property>
<name>tagsys.mediolx00.settings.iChannel</name>
<value>1</value>
</property> <!--values are TAG_C210, TAG_C240, TAG_C270, TAG_ISO15693-->
<property>
<name>tagsys.mediolx00.settings.strTagType</name>
<value>TAG_ISO15693</value>
</property>
<property>
<name>tagsys.mediolx00.settings.boCont</name>
<value>true</value>
</property> <property>
<name>tagsys.mediolx00.settings.boSort</name>
<value>false</value>
</property> <!-- timer between 2 reads (in millisec) -->
<property>
<name>tagsys.mediolx00.settings.iTimer</name>
<value>250</value>
</property> </properties>
</ns3:LRSpec>
Event Cycle Specification (ECSpec) is an xml file describing filtering and collection behavior. This tells the Middleware how the RFID tag reads ariving from the reader should be filtered and aggregated, for example : added, current or deleted tags.
This file must be created (same method as the LRSpec) and saved under the EC Spec directory (C:Documents and SettingsuserAspireRFIDIDEECSpecs)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:ECSpec xmlns:ns2="urn:epcglobal:ale:xsd:1">
<logicalReaders>
<logicalReader>TagsysReader</logicalReader>
</logicalReaders>
<boundarySpec>
<repeatPeriod unit="MS">10000</repeatPeriod>
<duration unit="MS">9500</duration>
<stableSetInterval unit="MS">0</stableSetInterval>
</boundarySpec>
<reportSpecs>
<reportSpec>
<reportSet set="CURRENT"/>
<output includeRawHex="true" includeRawDecimal="true" includeEPC="true" includeTag="true"/>
</reportSpec>
</reportSpecs>
</ns2:ECSpec>
Tomcat is used in order to deploy the Filtering and Collection server.
Copy the two WAR file (fc-server-version.war) into the Tomcat's webapps directory and start Tomcat. The war file will be deployed into a new folder.
You will usually find the webapps folder inside the tomcat installation directory (C:Program FilesApache Software FoundationTomcatwebapps).
Deployment
Now that all configurations are done, the reader can be tested.
- Plug-in the reader's power supply,
- Connect the reader into the RS232 connector and check which serial port is used (make sure that it is the same as LRSpec file),
- Connect the antenna to the reader,
- Put the tag in the antenna range,
- Make sure that Tomcat server is started (if you are using windows check the graphic interface on the task bar, if your using Linux check with the command line : service tomcat7 status)
- Go to AspireRfidIDE and push the Get vendor version in LRSpecConfiguratorView. A version number should be returned in the console tab (if not check again the configurations).
- To define the new reader as shown in the picture below, push Define button and select the LRSpec already defined and press Execute.
A dialog box will appear with the message : Lrspec successfully defined!
Now define the ECSpec for the same reader.
A text file will be created with the read tags under C:Documents and SettingsuserScans.
For example, for a tag ISO15693 reading, the generated report is :
E00401000E197F26 (DSFID:00),ISO15693
PDF
History
