|
|
The following sections list all supported RFID devices and describe the configuration properties for each device.
You need one or more RFID readers to use the WebLogic RFID Edge Server. All the supported makes and models of readers are shown in Table 2-1.
The reader models marked with an asterisk (*) have substantially similar command sets and capabilities as others in the same row, but they have not been as extensively tested.
Some readers models are identified as continuous readers or as on demand readers. On demand readers perform tag reads when directed to by the Edge Server. The Edge Server sends a read command to the reader, the command is executedContinuous read readers can be configured to read tags continuously.
| Note: | Supported read/write types are Read/Write (RW), Read Only (RO), and Write Only (WO). |
If you do not have a reader, you can use the reader simulator provided with the RFID Edge Server. Out of the box, it runs on any workstation and simulates a ThingMagic Mercury4 reader; with minor configuration it can simulate a Printronix reader. The reader simulator is useful for software evaluation, application development, and debugging. See Using the Reader Simulator.
Some readers may require specific configuration prior to use with WebLogic RFID Edge Server. You can configure the RFID Edge Server to communicate with supported readers in one of two ways:
RFID_EDGE_HOME/etc/edge.props file directly to configure these devices, where RFID_EDGE_HOME is the directory where you installed the RFID Edge Server software. (This is the default method for RFID Edge Server installations prior to version 1.3.) This file is a Java properties file used to configure the RFID Edge Server. For more information about the edge.props file, see
Configuring WebLogic RFID Edge Server.| Note: | Be aware that these two methods of configuring supported readers are mutually exclusive. All readers are defined either using the Administration Console or by editing the edge.props file. See
Two Approaches to Configuring Readers: edge.props or Administration Console in Installing WebLogic RFID Edge Server. |
Configuration properties consist of a name (shown in the Property Name column of the tables in this document) and a value (described in the Property Value and Description column). When written out in the edge.props file, they appear in the following format:
com.connecterra.ale.reader.<deviceID>.<prop1> = <prop1value>
If you are using the Administration Console to add and configure readers, you enter the configuration information in reader-specific fields. In this case, no reader configuration information will be written to the edge.props file; instead, the configuration information you enter will be saved in the persistence store kept by the RFID Edge Server.
Useful tips for configuring readers are included in reader-specific sections. For troubleshooting information that applies to all readers, see General Troubleshooting on page 2-113.
The following sections provide configuration information for all the supported makes and models of readers.
This section describes driver configuration information for the Accraply label printer. This device is capable of connecting to a reader (referred to as the Logical Reader Name for RFID Encoding property value) for tag write operations.
The Accraply reader uses the Easy Plug Label Scripting language. See Using the Easy Plug Label Scripting Language on page 2-30.
Table 2-2 lists the Accraply driver configuration properties.
The RFID Edge Server uses three Alien reader drivers:
This driver is used to interface the WebLogic RFID Edge Server with an Alien Technology ALR-9750 (Nanoscanner 915 MHz) RFID Reader. The reader driver implements the Alien text-based communications protocol for configuring and operating its RFID readers. This text-based reader/ host protocol is specified in the Nanoscanner Reader User Guide (Alien Doc # 8101024-000 Rev B).
Table 2-3 lists the Alien ALR-9750 reader driver configuration properties.
The user name the Edge Server will use for gaining access to the Alien reader. Must be the same as the user name you configured when setting up the Alien reader.
|
|||||
The password the Edge Server will use for gaining access to the Alien reader. Must be the same as the password you configured when setting up the Alien reader.
|
|||||
An optional Boolean property (allowed values are
true and false) specifying whether the driver disables the "check operation" (verification that there is a single tag in an antenna's field prior to conducting a tag programming operation). The default value is false, meaning the driver conducts the check operation.
|
|||||
The Alien reader obtains its IP network configuration dynamically via DHCP, or statically through one of the reader configuration interfaces. Refer to the Alien Nanoscanner Reader User Guide for further details.
The Edge Server Alien reader driver assumes that the Alien reader has also been configured, through the Alien Web interface or command-line interface, with the following configuration settings. These configuration settings must be saved to the reader's flash memory so that reader reboots do not result in their loss.
Alien>Set Username=<username>
Alien>Set Password=<password>This driver is used to interface the WebLogic RFID Edge Server with two models of Alien Technology readers: the ALR-9780 915 MHz RFID reader and the ALR-8780 866 MHz RFID reader.
The reader driver implements the Alien text-based communications protocol for configuring and operating its RFID readers. This text-based reader/host protocol is specified in the ALR-9780 Reader Interface Guide (Alien Doc # 8101938-000 Rev 01).
Table 2-4 lists the Alien ALR-9780 reader driver configuration properties.
The user name the Edge Server will use for gaining access to the Alien reader. Must be the same as the user name you configured when setting up the Alien reader.
|
|||||
The password the Edge Server will use for gaining access to the Alien reader. Must be the same as the password you configured when setting up the Alien reader.
|
|||||
An optional Boolean property (allowed values are
true and false) specifying whether the driver disables the "check operation" (verification that there is a single tag in an antenna's field prior to conducting a tag programming operation). The default value is false, meaning the driver conducts the check operation.
|
|||||
The number of acquisition cycles that are performed each time a logical reader conducts a read cycle (is issued a "Get TagList" command). Each logical reader operates with its own value. Integer property values range from 1 to 255. The default value is 1. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The number of RF wake commands the Alien reader issues at the start of each acquisition cycle. Each logical reader operates with its own value. Integer property values range from 0 to 255. The default value is 3. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The number of field reads (anti-collision searches) that are performed in each acquisition cycle. Each logical reader operates with its own value. Integer property values range from 1 to 255. The default value is 3. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The number of RF sleep commands the Alien reader issues after each field read. Each logical reader operates with its own value. Integer property values range from 0 to 255. The default value is 1. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The number of RF wake commands the Alien reader issues at the end of each acquisition cycle. Each logical reader operates with its own value. Integer property values range from 0 to 255. The default value imposed by the RFID Edge Server is 1. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The timeouts (in milliseconds) for field inventories (Alien Reader "Get TagList" commands). Each logical reader operates with its own timeout value. This configuration parameter, rather than the
socketTimeout property, will serve as the socket timeout value when the Edge Server is awaiting a response to a "Get TagList" command. The integer property value must be greater than or equal to 0. A timeout of 0 is interpreted as an infinite timeout. The default value is the value of the Socket Timeout property (or its default).
|
|||||
Alien ALR-9780 is a multi-protocol reader. To improve efficiency, the read operation will only attempt to collect tags encoded with the specified protocols. At present, valid values are:
|
The Alien reader obtains its IP network configuration dynamically via DHCP, or statically through one of the reader configuration interfaces. Refer to the Alien Reader Interface Guide for further details.
The Edge Server Alien reader driver assumes the Alien reader has also been configured, through the Alien Web interface or command-line interface, with the following configuration settings. These configuration settings must be saved to the reader's flash memory so that reader reboots do not result in their loss.
Alien>Set Username=<username>
Alien>Set Password=<password>
This driver is used to interface the WebLogic RFID Edge Server with the Alien Technology ALR-9800 continuous reader.
The ALR-9800 reader antennas must be used in pairs for all operations. For that reason, the driver configuration screen only allows configuration of two logical readers. Each logical reader corresponds to an antenna pair (0-1 or 2-3). Each antenna in the pair must point to the same tag location.
For more information, see the Alien Technology, Reader Interface Guide.
Alien offers an SDK (software development kit) for the ALR-9800 reader, which provides APIs for both Java and .Net. For more information about the SDK, visit the following URL: http://www.alientechnology.com/.
Table 2-5 lists the Alien ALR-9800 reader driver configuration properties.
The user name the Edge Server uses for gaining access to the Alien reader. Must be the same as the user name you configured when setting up the Alien reader.
|
|||||
The password the Edge Server uses for gaining access to the Alien reader. Must be the same as the password you configured when setting up the Alien reader.
|
|||||
The port on the Edge Server that is used by the reader to send notifications to. Valid range is 1-65535
|
|||||
Standard (default)—good for general purpose use and meets the EPCglobal Dense Reader Mode spectral mask requirements.
|
|||||
The Alien ALR-9800 reader has eight external output lines, numbered 0 through 7, and four external input lines, numbered 0 through 3. WebLogic RFID Edge Server lets you configure these GPIO like a PLC device. See
Configuring the Edge Server for PLC Communications on page 4-1. When configuring data items for the ALR-9800, use out0, out1, out2, ...out7 for outputs, and in0, ....in3 for inputs.
Listing 2-2 illustrates configuring the Alien ALR-9800 reader for controlling a 5-color stack light connected to the reader's external outputs 1 through 5.
#In edge.props file
#Define the PLC Transport `Reader'
com.connecterra.ale.plc.plcTransport.Alien9800GPIO.metaName = Reader
com.connecterra.ale.plc.plcTransport.Alien9800GPIO.pollInterval = 1000
#Define the message convention `Simple'
com.connecterra.ale.plc.plcMessageConvention.simple.metaName = Simple
com.connecterra.ale.plc.plcMessageConvention.simple.plcTransport = Alien9800GPIO
#Define the message convention `Multiple'
com.connecterra.ale.plc.plcMessageConvention.multiple.metaName = Multiple
com.connecterra.ale.plc.plcMessageConvention.multiple.plcTransport = Alien9800GPIO
#Define outboundMessage for left stack light
com.connecterra.ale.plc.outboundMessage.mystacklightleft.plcMessageConvention = multiple
com.connecterra.ale.plc.outboundMessage.mystacklightleft.items = out1 out2 out3 out4 out5
#Define inboundMessage
com.connecterra.ale.plc.inboundMessage.AlienInputs.plcMessageConvention = simple
com.connecterra.ale.plc.inboundMessage.AlienInputs.receiveItem = in1
com.connecterra.ale.plc.inboundMessage.AlienInputs.matchValues = false
#Define left stacklight. Alternatively, this can be done in the Administration
#Console by defining a PLC Stack Light device.
#See PLC Stack Light Example on page 4-4.
com.connecterra.ale.reader.stacklightleft.class = com.connecterra.ale.readertypes.PLCStackLightPhysicalReader
com.connecterra.ale.reader.stacklightleft.plcMessage = mystacklightleft
com.connecterra.ale.reader.stacklightleft.defaultRate = 0
com.connecterra.ale.reader.stacklightleft.stackLightLogicalReaderName = StackLightLeft
This driver is used to interface the WebLogic RFID Edge Server with the Alien Technology ALR-9800 on demand reader.
| Notes: | The ALR-9800 reader antennas must be used in pairs for all operations; for example, use antenna 0 and 1 together to read or write tags, likewise, antennas 2 and 3. |
| Note: | BEA recommends configuring the driver to use antennas pairs; for example, configure UHF Antenna 0 and UHF Antenna 1 with the same logical reader name. |
| Note: | With regard to antenna placement, the ALR-9800 reader antennas must be connected in pairs and each antenna in the pair must point to the same tag location. For example, you must connect both antenna 0 and antenna 1 when querying for information from either logical antenna 0 or 1. |
| Note: | For more information, see the Alien Technology, Reader Interface Guide (DOC. CONTROL# 8101938-000, REV E, Sept. 2005). |
| Note: | Table 2-6 lists the Alien ALR-9800 reader driver configuration properties. |
The user name the Edge Server will use for gaining access to the Alien reader. Must be the same as the user name you configured when setting up the Alien reader.
|
|||||
The password the Edge Server will use for gaining access to the Alien reader. Must be the same as the password you configured when setting up the Alien reader.
|
|||||
An optional Boolean property (allowed values are
true and false) specifying whether the driver disables the "check operation" (verification that there is a single tag in an antenna's field prior to conducting a tag programming operation). The default value is false, meaning the driver conducts the check operation.
|
|||||
The number of acquisition cycles that are performed each time a logical reader conducts a read cycle (is issued a "Get TagList" command). Each logical reader operates with its own value. Integer property values range from 1 to 255. The default value is 1. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The number of RF wake commands the Alien reader issues at the start of each acquisition cycle. Each logical reader operates with its own value. Integer property values range from 0 to 255. The default value is 3. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The number of field reads (anti-collision searches) that are performed in each acquisition cycle. Each logical reader operates with its own value. Integer property values range from 1 to 255. The default value is 3. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The number of RF sleep commands the Alien reader issues after each field read. Each logical reader operates with its own value. Integer property values range from 0 to 255. The default value is 1. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The number of RF wake commands the Alien reader issues at the end of each acquisition cycle. Each logical reader operates with its own value. Integer property values range from 0 to 255. The default value imposed by the RFID Edge Server is 1. See chapters 3 and 4 of the Alien Technology Reader Interface Guide for further information on this Acquire Parameter.
|
|||||
The timeouts (in milliseconds) for field inventories (Alien reader "Get TagList" commands). Each logical reader operates with its own timeout value. This configuration parameter, rather than the
socketTimeout property, will serve as the socket timeout value when the Edge Server is awaiting a response to a "Get TagList" command. The integer property value must be greater than or equal to 0. A timeout of 0 is interpreted as an infinite timeout. The default value is the value of the Socket Timeout property (or its default).
|
|||||
Standard (default)—good for general purpose use and meets the EPCglobal Dense Reader Mode spectral mask requirements.
|
|||||
A blank-separated list of RF protocols. Alien ALR-9800 is a multi-protocol reader. To improve efficiency, the read operation will only attempt to collect tags encoded with the specified protocols. At present, valid values are:
|
|||||
The Alien ALR-9800 reader has eight external output lines, numbered 0 through 7, and four external input lines, numbered 0 through 3. WebLogic RFID Edge Server lets you configure these GPIO like a PLC device. See
Configuring the Edge Server for PLC Communications on page 4-1. When configuring data items for the ALR-9800, use out0, out1, out2, ...out7 for outputs, and in0, ....in3 for inputs.
Listing 2-2 illustrates configuring the Alien ALR-9800 reader for controlling a 5-color stack light connected to the reader's external outputs 1 through 5.
#In edge.props file
#Define the PLC Transport `Reader'
com.connecterra.ale.plc.plcTransport.Alien9800GPIO.metaName = Reader
com.connecterra.ale.plc.plcTransport.Alien9800GPIO.pollInterval = 1000
#Define the message convention `Simple'
com.connecterra.ale.plc.plcMessageConvention.simple.metaName = Simple
com.connecterra.ale.plc.plcMessageConvention.simple.plcTransport = Alien9800GPIO
#Define the message convention `Multiple'
com.connecterra.ale.plc.plcMessageConvention.multiple.metaName = Multiple
com.connecterra.ale.plc.plcMessageConvention.multiple.plcTransport = Alien9800GPIO
#Define outboundMessage for left stack light
com.connecterra.ale.plc.outboundMessage.mystacklightleft.plcMessageConvention = multiple
com.connecterra.ale.plc.outboundMessage.mystacklightleft.items = out1 out2 out3 out4 out5
#Define inboundMessage
com.connecterra.ale.plc.inboundMessage.AlienInputs.plcMessageConvention = simple
com.connecterra.ale.plc.inboundMessage.AlienInputs.receiveItem = in1
com.connecterra.ale.plc.inboundMessage.AlienInputs.matchValues = false
#Define left stacklight. Alternatively, this can be done in the Administration
#Console by defining a PLC Stack Light device.
#See PLC Stack Light Example on page 4-4.
com.connecterra.ale.reader.stacklightleft.class = com.connecterra.ale.readertypes.PLCStackLightPhysicalReader
com.connecterra.ale.reader.stacklightleft.plcMessage = mystacklightleft
com.connecterra.ale.reader.stacklightleft.defaultRate = 0
com.connecterra.ale.reader.stacklightleft.stackLightLogicalReaderName = StackLightLeft
This section describes driver configuration information for the Avery 6405 RFID label printer. The printer supports the writing (programming) of Class 1 tags embedded within label stock ("smart labels") and the printing of those labels.
Table 2-7 lists the Avery 6405 reader driver configuration properties.
Specifies the pathname of a file containing Easy Plug commands defining a smart label form. Typically, the PCSpec
readerParameters attribute specifies Easy Plug-based label design. This property provides a mechanism for specifying a default label design in the event the PCSpec does not contain this parameter.
When present, the file name refers to a text file containing the set of Easy Plug commands specifying the smart label layout and dynamic (variable) content.
|
|||||
Easy Plug is a scripting language for specifying the layout and contents of printed labels. Easy Plug is described in detail in the Avery document, Manual Easy Plug, Release 3.00, 11/2003. Commands specific to the Avery 6405 are described in the document, How to RFID with Avery 6405.
The Avery 6405 and Accraply smart label printer drivers send their printers a separate collection of Easy Plug commands with each "smart label" (a printed label with an embedded RFID tag) to be printed and programmed. Users specify a smart label's Easy Plug commands when defining a PCSpec (see
Programming with the ALE and ALEPC APIs). A PCSpec readerParameters field carries the Easy Plug script as a String object; the corresponding reader parameter name is easyPlugScript (or one of easyPlugScript.accraply or easyPlugScript.avery if your WebLogic RFID Edge Server installation supports more than one device that uses EasyPlug).
As an alternative to specifying Easy Plug within a PCSpec, the Edge Server administrator may specify a default Easy Plug script using the reader driver Easy Plug Form property. This property provides a mechanism for specifying Easy Plug commands that serve as a default label design in the event the PCSpec readerParameters field does not carry a key/value pair containing an Easy Plug script.
The Easy Plug script, whether defined within the PCSpec or contained in a file identified by the easyPlugFilename property, must contain only Easy Plug commands. Here is an example script:
#!A1
#IMSR100/152.4//6/89/0V
#ER
#R000.00/000.00
#J100#T20.0
#M1/1
#YN100/0/100///THIS IS A TEST
#J50#T25.0
#YN100/0/58///[EPC_TAG_URI]
#Q1/
#!P1
Refer to Avery or Accraply documentation for additional information on Easy Plug.
This section describes driver configuration information for the AWID MPR-2010AN reader.
For the AWID MPR-3014 reader, the configuration properties are the same as for the AWID MPR-2010AN reader, plus the additional properties listed in Table 2-9.
Table 2-8 lists the AWID MPR-2010AN reader driver configuration properties.
When setting up AWID MPR-2010AN and MPR-3014 readers, follow the instructions provided in the MPRSetupGuide.pdf file (from the original CD).
When connecting to the reader for the first time, you need to set up a local network where the host computer is assigned an IP address in the 192.168.xxx space (the default address is 192.168.1.91).
| Note: | The reader comes with DHCP enabled by default. Disconnect from any external network where a DHCP server might be active while configuring the reader for the first time. |
If you do not know the IP address assigned to the reader, you may restore the factory defaults by pressing and holding a hidden button with a sharp object while rebooting the reader. Release the button when the reader powers up.
This reader supports up to four UHF antennas. At the present time, the reader cannot reliably detect which antenna ports have antennas attached. It relies on user input to enable and disable appropriate antenna ports. Therefore, when configuring logical readers, it is important that you do not attempt to configure antennas that are not physically attached; it is possible to damage the reader by doing this.
Unlike some readers, MPR-3014 can only support one antenna group. As always, the group is created by assigning the same logical reader name to several uhf antennas. The antenna group must be contiguous; for example, it must start with uhf1, and cannot skip antennas. If you assign the logical reader name "LR1" to uhf antenna 1 and uhf antenna 2, and then attempt to assign a different name to uhf antenna 3, the driver will interpret this as an attempt to create a second combined antenna group, and will generate an error: "AWID MPR-3014 allows only one combined antenna group".
For more information on antenna groups, see Combined Antenna Mode on page 2-78.
This section describes driver configuration information for the CAEN Technologies A928 RFID reader. Note that the RFID Edge Server requires the separate installation of the CAEN Java library to enable interoperation with the CAEN A928 RFID reader. Please contact your CAEN supplier for access to the file CAENRFIDLibrary.jar. This file should be copied into the lib subdirectory of your WebLogic RFID Edge Server installation before starting the software.
Table 2-10 lists the CAEN reader driver properties.
This section describes driver configuration information for the DataLogic DS6300-105-010 bar code reader. By default, the DataLogic bar code reader reads up to 12 alphanumeric digits (a-z, 0-9).
Table 2-11 lists the DataLogic reader driver configuration properties.
This section describes driver configuration information for the Escort Memory Systems (EMS) LRP820S and LRP2000 readers.
Table 2-12 lists the EMS reader driver configuration properties.
The WebLogic RFID Edge Server requires the use of a MOXA serial-to-Ethernet adapter for LAN access to EMS LRP readers.
The following section describes driver configuration information for a generic barcode reader. This driver supports most generic barcode readers.
This section describes the IER SmartController driver configurations. Table describes the driver configuration properties.
The following sections describe driver configuration information for the Impinj Speedway reader which uses the Mach1 protocol. The Impinj reader supports reading and writing of EPC Class 1 Gen 2 tags, including reading and writing tag memory, tag locking, and tag killing.
| Note: | Tag reading and programming operations are mutually exclusive. |
| Note: | For tag programming, only a single tag should be in the antenna RF field. If more than one tag is present, you cannot ensure programming the desired tag. |
| Caution: | Because the asynchronous read cycles of the Impinj reader can be very short, ECSpecs executed using the poll() or immediate() methods should avoid using a duration measured in read cycles. Otherwise, the reader may not be active for a long enough time to return accurate tag reads. |
Table 2-15 lists the Impinj Speedway reader configuration properties.
The EPC Gen2 reader inventory session number, as specified in the EPCglobal,
EPC Radio-Frequency Identity Protocols Class 1 Generation 2 UHF Air Interface Protocol Standard Version 1.0.9.
|
|||||
The power level for each UHF antenna. The range of valid values is from 15.0dBm to 30.0dBm, in 0.25 increments.The default power level is 30.0dBm.
|
|||||
The Impinj Speedway reader has eight external output pins, numbered 0 through 7, and four external input pins, numbered 0 through 3. WebLogic RFID Edge Server lets you configure these GPIO like a PLC device. See
Configuring the Edge Server for PLC Communications on page 4-1. When configuring GPIO pins for the Impinj reader, use GPO0, GPO1, GPO2, ...GPO7 for outputs, and GPI0, ....GPO3 for inputs.
| Note: | By default, the Impinj reader is configured to generate a GPI alert when the GPI status changes from Lo to HI only. |
The following sections describe driver configuration information for the Intermec Intellitag IF5 Reader and EasyCoder PM4i Printer:
Table 2-16 lists the Intermec Intellitag IF5 reader driver configuration properties.
Specifies the byte offset of the EPC within a tag's addressable memory. Values may range from 0 to the amount of available tag memory, minus the amount specified in the Byte Length property (below); the default value is 0. When writing ISO18000-6B tags, this value should be equal to or greater than 8. When the Class 1 Gen 2 protocol is selected, this value is ignored by the driver.
|
|||
An optional Boolean property (allowed values are
true and false) specifying whether the driver disables the "check operation" (verification that there is a single tag in an antenna's field prior to conducting a tag programming operation). The default value is false, meaning the driver conducts the check operation.
|
|||
The Intermec IF5 reader has four external output lines, numbered 1 through 4, and four external input lines, numbered 1 through 4. WebLogic RFID Edge Server lets you configure these GPIO like a PLC device. See
Configuring the Edge Server for PLC Communications on page 4-1. When configuring data items for the Intermec IF5, use out1, out2, ...out4 for outputs, and in1, ...in4 for inputs.
Listing 2-3 illustrates configuring the Intermec IF5 reader for controlling a 4-color stack light connected to the reader's external outputs 1 through 4. Note that while the reader only has 4 outputs, 5 data items must be defined in the PLC message (one for each color, White, Blue, Green, Amber, Red). Use NA for the unused light. In the following example, outputs are defined for White, Blue, Green, and Amber lights; Red is unused.
#In edge.props file
#Define the PLC Transport `Reader'
com.connecterra.ale.plc.plcTransport.IF5GPIO.metaName = Reader
com.connecterra.ale.plc.plcTransport.IF5GPIO.pollInterval = 1000
#Define the message convention `Simple'
com.connecterra.ale.plc.plcMessageConvention.simple.metaName = Simple
com.connecterra.ale.plc.plcMessageConvention.simple.plcTransport = IF5GPIO
#Define the message convention `Multiple'
com.connecterra.ale.plc.plcMessageConvention.multiple.metaName = Multiple
com.connecterra.ale.plc.plcMessageConvention.multiple.plcTransport = IF5GPIO
#Define outboundMessage for left stack light
com.connecterra.ale.plc.outboundMessage.mystacklightleft.plcMessageConvention = multiple
com.connecterra.ale.plc.outboundMessage.mystacklightleft.items = out1 out2 out3 out4 NA
#Define inboundMessage
com.connecterra.ale.plc.inboundMessage.IF5INPUTS.plcMessageConvention = simple
com.connecterra.ale.plc.inboundMessage.IF5INPUTS.receiveItem = in1
com.connecterra.ale.plc.inboundMessage.IF5INPUTS.matchValues = false
#Define left stacklight. Alternatively, this can be done in the Administration
#Console by defining a PLC Stack Light device.
#See PLC Stack Light Example on page 4-4.
com.connecterra.ale.reader.stacklightleft.class = com.connecterra.ale.readertypes.PLCStackLightPhysicalReader
com.connecterra.ale.reader.stacklightleft.plcMessage = mystacklightleft
com.connecterra.ale.reader.stacklightleft.defaultRate = 0
com.connecterra.ale.reader.stacklightleft.stackLightLogicalReaderName = StackLightLeft
Table 2-17 lists the Intermec PM4i label printer driver configuration properties.
Specifies the pathname of a file containing Intermec Fingerprint® commands defining a label form. Typically the Fingerprint script-based label design is specified within the PCSpec
readerParameters attribute; the reader parameter name is fpScript. This property provides a mechanism for specifying a default label design in the event the PCSpec does not contain PM4i reader parameters. When present, the PM4i reader parameter is a string containing the set of Fingerprint commands specifying a label layout.
|
|||
Intermec Fingerprint is a BASIC-inspired, printer-resident programming language for use with the Intermec EasyCoder bar code label printers. The Intermec Fingerprint programming language is described in detail in the Intermec Fingerprint v8.70.0/v10.0.0 Programmer´s Reference Manual (16 Jan. 2006).
The Intermec PM4i printer drivers send the printer a collection of Fingerprint commands with each label to be printed and programmed. Users specify a label's Fingerprint commands when defining a PCSpec (see
Programming with the ALE and ALEPC APIs). A PCSpec readerParameters field carries the Fingerprint script as a String object; the reader parameter name is fpScript.
As an alternative to specifying Fingerprint commands within a PCSpec, the Edge Server administrator may specify a default Fingerprint script using the Intermec reader driver Script File property. This property provides a mechanism for specifying Fingerprint commands that serve as a default label design in the event the PCSpec readerParameters field does not carry a key/value pair containing a template script.
The Fingerprint script, whether defined within the PCSpec or contained in a file identified by the Script File property, must only contain immediate mode commands, without the line numbers, should not contain a page feed (PF) command, and should contain no RFID commands and no "END" command. The following is an example Fingerprint script:
OPTIMIZE "BATCH" OFF
LTS& OFF
NASC -2:AN 7
CLIP ON
XORMODE OFF
MAG 1,1
BF "Monospace 821 BT",14,0,0,1,1 ON
'PP 59,208:DIR 1:BT "EAN128":BM 4:BH 160:PB "[EPC_HEX]"
PP 59,208:DIR 1:"[EPC_HEX]"
AN 8
MAG 1,1
PP 394,859:FT "Swiss 721 BT",14,0,100:NI:PT "As part of a test to improve
product"
PP 416,811:NI:PT " availability for consumers, packaging"
PP 406,763:NI:PT "contains an Electronic Product Code"
This section describes driver configuration information for the Paxar Monarch 9855 smart label printer. You will need to consult the Monarch® 9855™ RFID Printer Operator's Handbook and enable status polling to allow the printer to respond to status requests from the RFID Edge Server.
Table 2-18 lists the Paxar Monarch 9855 reader driver configuration properties.
Specifies the pathname of a file containing MPCL commands defining a smart label's form. Typically the MPCL-based label design will be specified within the PCSpec
readerParameters attribute. This property provides a mechanism for specifying a default label design in the event the PCSpec does not contain Monarch 9855 reader parameters. When present, the Monarch reader parameter is a string containing the set of MPCL commands specifying a smart label's layout.
|
This section describes driver configuration information for the Printronix SL5000r label printer with an integrated RFID UHF encoder. Although the Printronix device has a "reader driver," it does not support tag reading. Instead, it supports the writing (programming) of Class 1, Class 0+, and Class 1 Gen 2 tags embedded within label stock ("smart labels") and the printing of those labels.
Table 2-19 lists the Printronix SL5000r reader configuration properties.
Specifies the pathname of a file containing Printronix PGL commands defining a smart label form. Typically, the PCSpec
readerParameters attribute specifies PGL-based label design; the reader parameter name is pglScript. This property provides a mechanism for specifying a default label design in the event the PCSpec does not contain Printronix reader parameters.
|
|||||
The general-purpose I/O (GPIO) port used by the Edge Server to obtain printer status via the printer's Ethernet adapter. The default value is 3002.
|
|||||
The printer regularly sends "heartbeat" messages to the Edge Server to confirm connectivity. (Consult the manufacturer or printer documentation for information on how often these messages are sent.) This value defines how long, in milliseconds, the Edge Server will wait for a message before attempting to re-establish a connection with the printer. The default value is 11000. This property must be set to a value greater than the interval between heartbeat messages.
|
|||||
The Printronix Graphics Language (PGL) is a scripting language for specifying the layout and content of printed labels. PGL is described in detail in the Printronix document, IGP/PGL Emulation for Thermal Line Matrix, and Laser Printers: Printronix Graphics Language Programmer's Reference Manual.
The Printronix smart label printer drivers send the printer a separate collection of PGL commands with each "smart label" (a printed label with an embedded RFID tag) to be printed and programmed. Users specify a smart label's PGL commands when defining a PCSpec (see
Programming with the ALE and ALEPC APIs). A PCSpec readerParameters field carries the PGL script as a String object; the reader parameter name is pglScript.
As an alternative to specifying PGL within a PCSpec, the Edge Server administrator may specify a default PGL script using the Printronix reader driver PGL Form property. This property provides a mechanism for specifying PGL commands that serve as a default label design in the event the PCSpec readerParameters field does not carry a key/value pair containing a PGL script.
The PGL script, whether defined within the PCSpec or contained in a file identified by the PGL Form property, must only contain IGP/PGL Create Form mode commands. Below is an example PGL script:
SCALE;DOT;200;200
FONT;FACE 92250
ALPHA
POINT;60;50;8;8;*SHIP FROM:*
POINT;90;50;10;10;*ACME*
POINT;120;50;10;10;*Corporation*
POINT;150;50;10;10;*P.O. Box 1000*
POINT;180;50;10;10;*Dallas, TX75261*
POINT;60;365;8;8;*SHIP TO:*
POINT;90;365;10;10;*Retailer Distribution Center*
POINT;120;365;10;10;*200 Main Street*
POINT;150;365;10;10;*Springfield, MA01103*
STOP
HORZ
4;200;40;790
STOP
VERT
3;343;60;200
STOP
ALPHA
POINT;235;50;8;8;*(420)SHIP TO POSTAL CODE:*
POINT;285;100;12;12;*(420) 01103*
POINT;235;385;8;8;*CARRIER:*
POINT;285;400;12;12;*Acme Freightways*
POINT;330;400;10;10;*PRO: 1234*
POINT;370;400;10;10;*B/L: 5678*
STOP
BARCODE
C128C;XRD3:3:6:6:9:9:12:12;H7;283;75
*01103*
STOP
HORZ
4;425;40;790
STOP
VERT
3;374;200;425
STOP
ALPHA
POINT;465;50;12;12;*EPC:*
AF512;25;POINT;550;70;14;14
STOP
HORZ
4;625;40;779
STOP
ALPHA
POINT;665;50;12;12;*SKU:*
POINT;705;70;14;14;*ABC21270*
STOP
HORZ
4;750;40;779
STOP
ALPHA
POINT;790;50;12;12;*GTIN:*
POINT;840;270;12;12;*(01) 10036000212706*
STOP
BARCODE
C128C;XRD3:3:6:6:9:9:12:12;H7;850;250
*10036000212706*
STOP
The user-defined PGL script must not contain an RFWRITE Create Form mode command; the reader driver will insert the necessary RFWRITE command if it is called on to program a smart label's embedded RFID tag.
If the user wishes to print a specified EPC value on the smart label, the user-supplied PGL must use special substitution strings, indicating in what representation the tag values are to be printed. The RFID Edge Server recognizes the following substitution string values:
ALPHA
POINT;465;50;12;12;*EPC:*
POINT;550;70;14;14;*[EPC_ID_URI]*
STOP
Please refer to Printronix documentation for additional information on IGP/PGL.
The Printronix Device Management Language (PXML) is a printer device management protocol to control and monitor job and printer status. To use PXML, copy the following required JAR files from Printronix into the lib subdirectory of your WebLogic RFID Edge Server installation: pxml.jar, commonlib.jar, and jdom.jar.
PXML is an XML-based language that allows a client application to issue commands to a Printronix SL5000r printer and receive responses from the printer, including:
Responses can be either solicited (in response to a command) or autonomous (generated by events that occur during printer operation).
PNE is the Printronix proprietary device management protocol used by the Printronix PrintNet Enterprise software. PXML is the XML-based device management protocol to interface with third party software. Currently there is no auto switching between the two protocols and only one device management protocol can be active at any time. The printer factory default is PNE mode. Therefore, third party software must configure the printer for PXML before it can be used. This can be done either by sending the PTX_SETUP commands to the printer or setting the printer front panel menu.
Consult the Printronix documentation for detailed PXML setup information.
The RFID Edge Server uses two SAMSys reader drivers:
This section describes driver configuration information for the SAMSys MP9320 RFID reader. SAMSys MP9320 2.8 readers feature a single-color stack light, which requires no configuration.
The SAMSys MP9320 reader drivers use the following properties
A Boolean property (allowed values are
true and false) specifying whether the driver disables the Program Cycle Check (verification that there is exactly one programmable tag in an antenna's field prior to conducting a tag programming operation). The default value is false, meaning the driver conducts the check operation. Note that if the check operation is disabled (this property value is set to true) and multiple tags are present in the antenna's field when conducting a tag programming operation, then all tags in the field will be programmed with the same EPC.
|
|||||||||
A blank-separated list of RF protocols. SAMSys MP9320 is a multi-protocol reader. To improve efficiency, the read operation will only attempt to collect tags encoded with the specified protocols. At present, valid values are:
epcClass1 (includes epcClass1-64 and epcClass1-96)epcClass1-64 (EPC Class 1 Gen 1 64-bit)epcClass1-96 (EPC Class 1 Gen 1 96-bit)epcClass1Gen2 (includes epcClass1 and epcClass1Gen2.)
|
|||||||||
Indicates the behavior of the SAMSys reader in response to a request for data from an application. A value of
poll means that the reader is idle between requests, but performs a tag read when it receives a request for data. A value of autopoll means that the reader continuously reads tags and stores the data in memory between requests, and forwards all stored tag information when it receives a request from the application.
|
|||||||||
The RF power setting of the reader. The range of valid values is from RF power level 2 (34.7dBm (2.95W)) to RF power level 80 (16 dBm (40 mW)). The default value is RF power level 24 (1W).
|
To attain the maximum output from the SAMSys MP9320 2.7 and 2.8 readers, BEA Systems recommends setting the reader to 57600 bps. If you change the baud rate of the reader in the RFID Edge Server, you will need to perform these steps again to keep the baud rate settings the same throughout the hardware and software.
Use the following instructions set the baud rate:
The software should detect the reader connected to your computer serial port.
http://<IP.address.of.reader>/. This URL will launch a Java applet. You will need to enable Java in your Web browser to see the applet. If you would prefer to perform this configuration via Telnet, skip step 5 and follow the instructions in Appendix C of the MP9320 2.7 User's Guide.
57600, then click Save.}Cw,d:scw,b:00161616,f:1! to set the reader baud rate to 57600.Afterward, the reader external RS232 port and the external serial port on the Digi Connect ME Module are set to a baud rate of 57600.
| Note: | If the reader stops responding, use HyperTerminal to connect to the reader, power-cycle it, and press the Enter key three times. This will set the reader to the factory default. |
The SAMSys MP9210 reader driver requires the use of a MOXA serial-to-Ethernet adapter, available from Symbol Technologies.
Table 2-21 lists the SAMSys MP9210 reader configuration properties.
The SAMSys MP9210 reader will be connected to an IP network with a MOXA serial server. The serial configuration is shown below. If the reader's serial configuration is changed, adjust these settings accordingly.
A null modem is required if using a straight serial cable (DB9, female-to-male).
This section describes driver configuration information for the SATO RFID printer. SATO RFID printers support writing (programming) Class 1 Gen 2 tags embedded within label stock ("smart labels") and tags with embedded RFID transponders. For required printer setup information, see Configuring the SATO Printer on page 2-70.
Table 2-22 lists the SATO RFID printer driver configuration properties.
Specifies the pathname of the status message file. The status message file contains the status code description and severity classification. If not specified, a default status message file is used.
|
Use the operator panel located on the printer front to configure these SATO printer settings, shown in Table 2-23. For detailed SATO printer configuration information, see the printer model Operator Manual.
| Tip: | Upon initial connection to the printer, the Edge Server interrogates and displays the supported printer status protocol in the Edge Server console output and as an INFO level message in the RFID Device Alerts page in the Administration Console. |
The RFID Edge Server supports the following Motorola (Symbol or Matrics) reader drivers:
This section describes driver configuration information for the Motorola (Symbol) AR400 and XR400 readers in on-demand mode.
Table 2-24 lists the Motorola (Symbol) AR400 and XR400 readers configuration properties.
The frequency channel the AR400 reader will use to read tags. This property MUST ONLY be used with Symbol/Matrics FCC part 90 readers. Integer property values range from 0 to 13, corresponding to 914.25 MHz to 917.25 MHz, in 500 kHz steps. There is no default value. When not specified, the Set Frequency Channel command is not issued.
|
|||||
A Boolean property (allowed values are
true and false) specifying whether the driver disables the Program Cycle Check (verification that there is exactly one programmable tag in an antenna's field prior to conducting a tag programming operation). The default value is false, meaning the driver conducts the check operation. Note that if the check operation is disabled (this property value is set to true) and multiple tags are present in the antenna's field when conducting a tag programming operation, then all tags in the field will be programmed with the same EPC.
|
|||||
A set of properties specifying a logical reader name bound to each of the reader's UHF antennas. At least one logical reader name must be specified. (The AR400/XR400 readers support up to four logical readers.) If a property within this set is left undefined, there will be no logical reader associated with the corresponding antenna.
If multiple UHF antennas are assigned the same logical reader name, then the driver will treat them as a single combined antenna. The lowest-numbered antenna in the combined antenna grouping is checked to set antenna-specific properties and used for tag programming. If running in this combined antenna mode, see
Combined Antenna Mode on page 2-78.
|
|||||
A property controlling the length of time the AR400 reader gives itself when reading tags within a single antenna's field in response to a single "Read Full Field" Command. Integer property values range from 0 to 8, with full field read times lengthening with increasing environment variable property value. The default environment variable value is 3.
|
|||||
Specifies the protocol to use for stack light control. The default value is
Bytestream; valid values are:
|
|||||
To capture the reader GPIO input, you must enable GPIO mode by performing the following steps:
http://reader_ipaddressSee the Symbol Reader Manual, XR Series RFID Reader Integrator Guide (Part Number 72E-71773-03 Rev. A, February 2006), for login instructions.
edge.props file, set Enable Reader GPIO Mode (enableGPIO) to true.edge.props file (defined as myreadergpio in Listing 2-4
). Listing 2-4 illustrates configuring the XR400 reader for controlling a stack light and photo sensors connected to the reader's light indicator box (LIB).
######################################################
# Define the Reader's GPIO output for stack light use
########################################################
#In edge.props
#Define the PLC Transport 'Reader'
com.connecterra.ale.plc.plcTransport.myreadergpio.metaName = Reader
com.connecterra.ale.plc.plcTransport.myreadergpio.pollInterval = 500
#Define the message convention 'Multiple'
com.connecterra.ale.plc.plcMessageConvention.mymultiplemsg.metaName = Multiple
com.connecterra.ale.plc.plcMessageConvention.mymultiplemsg.plcTransport = myreadergpio
#Define outboundMessage message for left stack light
com.connecterra.ale.plc.outboundMessage.mystacklightleft.plcMessageConvention = mymultiplemsg
#(NA-not applicable, LG-left green, LY-left yellow, LR-left red)
com.connecterra.ale.plc.outboundMessage.mystacklightleft.items = NA NA LG LY LR
#Define left stacklight. Alternatively, this can be done in the Administration
#Console by defining a PLC Stack Light device.
#See PLC Stack Light Example on page 4-4.
com.connecterra.ale.reader.stacklightleft.class = com.connecterra.ale.readertypes.PLCStackLightPhysicalReader
com.connecterra.ale.reader.stacklightleft.plcMessage = mystacklightleft
com.connecterra.ale.reader.stacklightleft.defaultRate = 0
com.connecterra.ale.reader.stacklightleft.stackLightLogicalReaderName = StackLightLeft
#Define outboundMessage message for right stack light
com.connecterra.ale.plc.outboundMessage.mystacklightright.plcMessageConvention = mymultiplemsg
#(NA-not applicable, RG-right green, RY-right yellow, RR-right red)
com.connecterra.ale.plc.outboundMessage.mystacklightright.items = NA NA RG RY RR
#Define right stacklight. Alternatively, this can be done in the Administration
#Console by defining a PLC Stack Light device.
#See PLC Stack Light Example on page 4-4.
com.connecterra.ale.reader.stacklightRight.class = com.connecterra.ale.readertypes.PLCStackLightPhysicalReader
com.connecterra.ale.reader.stacklightRight.plcMessage = mystacklightright
com.connecterra.ale.reader.stacklightRight.defaultRate = 0
com.connecterra.ale.reader.stacklightRight.stackLightLogicalReaderName = StackLightRight
#########################################################
# Define the GPIO input for sensors/photoelectric eyes
###########################################################
#define the input trigger
com.connecterra.ale.triggerDriver.plcmessage.class=com.connecterra.ale.triggertypes.PLCTriggerDriver
#Define the message convention
com.connecterra.ale.plc.plcMessageConvention.mysimplemsg.metaName = Simple
com.connecterra.ale.plc.plcMessageConvention.mysimplemsg.plcTransport = myreadergpio
#Define inboundMessage message
com.connecterra.ale.plc.inboundMessage.photoeye1.plcMessageConvention = mysimplemsg
#Input pin 5 for photo eye1
com.connecterra.ale.plc.inboundMessage.photoeye1.receiveItem = input5
com.connecterra.ale.plc.inboundMessage.photoeye1.matchValues = true
com.connecterra.ale.plc.inboundMessage.photoeye2.plcMessageConvention = mysimplemsg
#Input pin 4 for photo eye2
com.connecterra.ale.plc.inboundMessage.photoeye2.receiveItem = input4
com.connecterra.ale.plc.inboundMessage.photoeye2.matchValues = true
#Define the direction trigger
com.connecterra.ale.triggerDriver.door1.class=com.connecterra.ale.triggertypes.DirectionTriggerDriver
com.connecterra.ale.triggerDriver.door1.timeout=10000
com.connecterra.ale.triggerDriver.door1.aTrigger=plcmessage:photoeye1
com.connecterra.ale.triggerDriver.door1.bTrigger=plcmessage:photoeye2
After defining these inputs, You can use the photo sensor as a trigger to start and stop your ECSpec. The trigger URI is plcmessage:photoeye1 for photoeye1 and plcmessage:photoeye2 for photoeye2.
The AR400 and XR400 reader drivers in the RFID Edge Server run a bytestream protocol. The bytestream protocol driver now supports combined antenna operations. To enable combined antenna operations, assign the same logical reader name to multiple physical antenna ports. All antennas combined within a single logical group must operate with the same set of antenna-specific configuration options (Power Level, Environment Variable). The driver will use the configuration properties assigned to the lowest numbered antenna port in a group for all antennas in that group. So, if two logical readers are combined into the same group, then the power level and environment variable properties specified for the first will also apply to the second.
The Motorola (Symbol of Matrics) RDR-001 reader driver requires the use of a serial-to-Ethernet adapter.
Table 2-25 lists the RDR-001 reader configuration properties.
This driver provides support for the Motorola XR400 and XR480 readers. The driver uses the reader's HTTP interface and sets the operation mode to continuous.
Table 2-26 lists the XR4xx reader configuration properties.
The mode specifies how the Edge Server communicates with the reader for tags. The driver supports the following operation modes:
periodically_when_tags_in_field - the edge server polls the reader periodically for tags, but if there is no tag movement in front of the reader (no notification from the reader), the poll may be skipped.
|
|||
Specifies the antenna is an individual antenna, or a member of a combined antenna group. The following values are valid:
AREA - specifies an individual antenna. COMB1 - specifies combined antenna group 1. COMB2 - specifies combined antenna group 2. |
|||
|
motion_sensor_inventory_control - input is connected to the motion sensors, which are used by the reader to control tag inventory. photo_sensor_GPIO - input is connected to photo sensors. Photo sensor status is forwarded to the edge server. |
|||
To capture the reader GPIO input, you must enable GPIO mode by performing the following steps:
http://reader_ipaddressSee the Symbol Reader Manual, XR Series RFID Reader Integrator Guide, for login instructions.
edge.props file, set Enable Reader GPIO Mode (enableGPIO) to true.The following steps describe how to configure the stack light and photo sensors connected to the Light Indicator Box (LIB).
#In edge.props
#Define the PLC Transport 'Reader'
com.connecterra.ale.plc.plcTransport.myreadergpio.metaName = Reader#Define the message convention 'Multiple' for output
com.connecterra.ale.plc.plcMessageConvention.mymultiplemsg.metaName = Multiplecom.connecterra.ale.plc.plcMessageConvention.mymultiplemsg.plcTransport = myreadergpio#Define outboundMessage message for left stack light
com.connecterra.ale.plc.outboundMessage.mystacklightleft.plcMessageConvention = mymultiplemsg#(NA-not applicable, LG-left green, LY-left yellow, LR-left red)
com.connecterra.ale.plc.outboundMessage.mystacklightleft.items = NA NA LG LY LR#Define outboundMessage message for right stack light
com.connecterra.ale.plc.outboundMessage.mystacklightright.plcMessageConvention = mymultiplemsg
#(NA-not applicable, RG-right green, RY-right yellow, RR-right red)
com.connecterra.ale.plc.outboundMessage.mystacklightright.items = NA NA RG RY RRUse the following steps to configure the photo_sensor_GPIO connected to the reader's LIB:
######################################################
# Define the Reader's GPIO output for stack light use
########################################################
#In edge.props
#Define the PLC Transport 'Reader'
com.connecterra.ale.plc.plcTransport.myreadergpio.metaName = Reader#########################################################
# Define the GPIO input for sensors/photoelectric eyes
###########################################################
#Define the message convention for input
com.connecterra.ale.plc.plcMessageConvention.mysimplemsg.metaName = Simplecom.connecterra.ale.plc.plcMessageConvention.mysimplemsg.plcTransport = myreadergpio#Define inboundMessage message
com.connecterra.ale.plc.inboundMessage.photoeye1.plcMessageConvention = mysimplemsg
#Input pin 5 for photo eye1
com.connecterra.ale.plc.inboundMessage.photoeye1.receiveItem = input5com.connecterra.ale.plc.inboundMessage.photoeye1.matchValues = truecom.connecterra.ale.plc.inboundMessage.photoeye2.plcMessageConvention = mysimplemsg#Input pin 4 for photo eye2
com.connecterra.ale.plc.inboundMessage.photoeye2.receiveItem = input4com.connecterra.ale.plc.inboundMessage.photoeye2.matchValues = true#define the PLC trigger driver
com.connecterra.ale.triggerDriver.plcmessage.class=com.connecterra.ale.triggertypes.PLCTriggerDriver
This section describes driver configuration information for the Tagsys Medio L100 and L200 RFID readers. Note that the RFID Edge Server requires the separate installation of the Tagsys Java library to enable interoperation with the Tagsys RFID readers. Please contact your Tagsys supplier for access to the file com.tagsys.jar. This file should be copied into the lib subdirectory of your WebLogic RFID Edge Server installation before starting the software.
The Tagsys Medio L100 and L200 reader drivers require the use of a MOXA serial-to-Ethernet adapter, available from Symbol Technologies.
Table 2-27 lists the Tagsys Medio L100 and L200 reader configuration properties.
Indicates the behavior of the Tagsys reader in response to a request for data from an application. A value of
poll means that the reader is idle between requests, but performs a tag read when it receives a request for data. A value of autopoll means that the reader continuously reads tags and stores the data in memory between requests, and forwards all stored tag information when it receives a request from the application.
|
|||||
The Tagsys Medio L100 and L200 readers support combined antenna operations and can manage up to four antennas, organized into two pairs of antennas. Each antenna is able to transmit an RF field, but only one antenna in the pair can receive at a single time. This means that each antenna can transmit an RF field used to read tags, but tag contents can only be read by one antenna of the pair at a given time.
Configuring Tagsys readers to perform read operations on both antennas (or antenna pair) one after the other enhances tag reading performance. The multiplexing mode implements several antenna combinations that are applied one after the other in a loop.
Antenna multiplexing information is organized into patterns. A pattern contains information about which antennas are enabled at the same time as well as the phase shift angle values between the enabled antennas.
If antenna pairs are used, the multiplexing patterns are shown in Table 2-28.
If no antenna pairs are used, the multiplexing patters are shown in Table 2-29.
For more information on combined antenna operations, see Combined Antenna Mode on page 2-78. For detailed multiplexing configuration information, see Lx00 Platform Firmware Reference Guide (Tagsys Document Reference 10958D0).
The Tagsys reader will be connected to an IP network with a MOXA serial server. The serial configuration is shown below. If the reader's serial configuration is changed, adjust these settings accordingly.
A null modem is required if using a straight serial cable (DB9, female-to-male).
The RFID Edge Server uses two ThingMagic reader drivers:
Table 2-30 lists the ThingMagic Mercury3 reader configuration properties.
An optional Boolean property (allowed values are
true and false) specifying whether the driver disables the "check operation" (verification that there is a single tag in an antenna's field prior to conducting a tag programming operation). The default value is false, meaning the driver conducts the check operation.
|
|||
Specifies the logical reader name for each UHF (915 MHz) antenna. At least one logical reader name must be specified.
|
|||
Table 2-31 lists the ThingMagic Mercury4 reader configuration properties.
An optional Boolean property (allowed values are
true and false) specifying whether the driver disables the "check operation" (verification that there is a single tag in an antenna's field prior to conducting a tag programming operation). The default value is false, meaning the driver conducts the check operation.
|
|||
Specifies the logical reader name for each UHF (915 MHz) antenna. At least one logical reader name must be specified.
|
|||
The ThingMagic reader obtains its IP network configuration dynamically via DHCP, or statically through one of the reader configuration interfaces. Refer to the ThingMagic User Guide for further details.
This section describes driver configuration information for the Wavetrend L-RX900 reader. This reader supports reading Wavetrend active tags.
The Wavetrend L-RX900 reader has two external output lines, numbered 0 and 1.WebLogic RFID Edge Server lets you configure these GPIO like a PLC device. See
Configuring the Edge Server for PLC Communications on page 4-1. When configuring data items for the L-RX900, use out0 and out1 for outputs. The following provides an example of programming the L-RX900 GPIO.
#In edge.props file
#Define the PLC Transport `Reader'
com.connecterra.ale.plc.plcTransport.wtgpio.metaName = Reader
com.connecterra.ale.plc.plcTransport. wtgpio.pollInterval = 1000
#Define the message convention `Simple'
com.connecterra.ale.plc.plcMessageConvention.simple.metaName = Simple
com.connecterra.ale.plc.plcMessageConvention.simple.plcTransport = wtgpio
#Define the message convention `Multiple'
com.connecterra.ale.plc.plcMessageConvention.multiple.metaName = Multiple
com.connecterra.ale.plc.plcMessageConvention.multiple.plcTransport = wtgpio
#Define outboundMessage for left stack light
com.connecterra.ale.plc.outboundMessage.mystacklightleft.plcMessageConvention = multiple
com.connecterra.ale.plc.outboundMessage.mystacklightleft.items = out0 out1 NA NA NA
#Define inboundMessage
com.connecterra.ale.plc.inboundMessage.wtinputs.plcMessageConvention = simple
com.connecterra.ale.plc.inboundMessage. wtinputs.receiveItem = in0
com.connecterra.ale.plc.inboundMessage. wtinputs.matchValues = false
#Define left stacklight. Alternatively, this can be done in the Administration
#Console by defining a PLC Stack Light device.
#See PLC Stack Light Example on page 4-4.
com.connecterra.ale.reader.stacklightleft.class = com.connecterra.ale.readertypes.PLCStackLightPhysicalReader
com.connecterra.ale.reader.stacklightleft.plcMessage = mystacklightleft
com.connecterra.ale.reader.stacklightleft.defaultRate = 0
com.connecterra.ale.reader.stacklightleft.stackLightLogicalReaderName = StackLightLeft
Starting with the Edge Server version 2.3 release, memory can be configured so that memory banks are designated for each data item in an ECSpec. Table 2-33 shows the relationship of memory banks to the vendor-specific data items:
Use the following syntax to specify a memory bank region in the API:
urn:connecterra:tagmem:@<mem_bank>.<bit_length>.<bit_offset>
A memory bank region representing 8 bits at offset 16 of memory bank 10002 (3rd byte of the age value) would be specified as follows:
urn:connecterra:tagmem:@10002.8.16
The following PCSpec example shows how to specify a memory bank for an RSSI value:
<?xml version="1.0" encoding="UTF-8"?>
<ale:ECSpec includeSpecInReports="false" xmlns:ale="urn:epcglobal:ale:xsd:1" xmlns:aleext="http://schemas.connecterra.com/EPCglobal-extensions/ale">
<logicalReaders>
<logicalReader>wavetrend</logicalReader>
</logicalReaders>
<boundarySpec>
<duration unit="MS">2000</duration>
</boundarySpec>
<reportSpecs>
<reportSpec reportIfEmpty="false" reportName="Report_0" reportOnlyOnChange="false">
<reportSet set="CURRENT"/>
<output includeCount="false" includeEPC="true" includeRawDecimal="false" includeRawHex="false" includeTag="false">
<aleext:includeMemory aleext:field="urn:connecterra:tagmem:@10004.8"/>
</output>
<aleext:applicationData></aleext:applicationData>
<aleext:essential>false</aleext:essential>
</reportSpec>
</reportSpecs>
</ale:ECSpec>
This section describes driver configuration information for the Zebra R110XiIIIPlus, R110Xi and R4MPlus label printers.
The Zebra R110XiIIIPlus, R110Xi and R4MPlus printer drivers share all the same properties except class, as shown in the following table
|
Typically, the PCSpec
readerParameters attribute specifies ZPL-based label design; the reader parameter name is zplScript. This property provides a mechanism for specifying a default label design in the event the PCSpec does not contain ZPL reader parameters. When present, the ZPL Form refers to a text file (label.zpl) containing the set of ZPL commands specifying the smart label layout and dynamic (variable) content. See
Using the Zebra Printing Language (ZPL II) on page 2-109.
|
|||||
Specifies the pathname of a file containing a table of all known status codes, descriptions, and severity levels. The file can be edited by the end user (commonly editing the severity levels). The file must be present for the driver to work, but the field can be left blank. A blank field is interpreted as the default file: etc/ZebraPrintStatus.props
|
|||||
ZPL is a scripting language for specifying the layout and contents of printed labels. ZPL is described in detail in the Zebra document, ZPLII Programming Guide (Zebra Document 45541LB-R3).
The Zebra printer driver sends its printer a separate collection of ZPL commands with each "smart label" (a printed label with an embedded RFID tag) to be printed and programmed. Users specify smart label ZPL commands when defining a PCSpec (see
Programming with the ALE and ALEPC APIs). A PCSpec readerParameters field carries the ZPL script as a String object; the reader parameter name is zplScript. As an alternative to specifying ZPL within a PCSpec, the Edge Server administrator may specify a default ZPL script using the Zebra reader driver ZPL Form property. This property provides a mechanism for specifying ZPL commands that serve as a default label design in the event the PCSpec readerParameters field does not carry a key/value pair containing a ZPL script.
Below is an example ZPL script:
^XA
^FX *** NOTE: Lines, beginning with ^FX are comments ***^FS
^FX Set home position ^FS
^LH30,35
^FX Write EPC HEX ^FS
^WT,,,,1^FD[EPC_HEX]^FS
^FX "Ship From" text ^FS
^FO20,15^A0N,18,,^FDSHIP FROM:^FS
^FO20,40^A0N,26,,^FDAcme^FS
^FO20,65^A0N,26,,^FDCorporation^FS
^FO20,90^A0N,26,,^FDP.O. Box 61900^FS
^FO20,115^A0N,26,,^FDDallas, TX 75261^FS
^FX Draw vertical line ^FS
^FO300,0^GB0,180,2^FS
^FX "Ship to" text ^FS
^FO320,15^A0N,18,,^FDSHIP TO:^FS
^FO320,40^A0N,26,,^FDRetailer Distribution Center^FS
^FO320,65^A0N,26,,^FD200 Main Street^FS
^FO320,90^A0N,26,,^FDSpringfield, MA01103^FS
^FX Draw horizontal line ^FS
^FO0,180^GB720,0,4^FS
^FX Postal code text ^FS
^FO20,195^A0N,18,,^FDSHIP TO POSTAL CODE:^FS
^FO30,275^A0N,32,,^BC,90,,Y,^FD(420) 01103^FS
^FX Draw vertical line ^FS
^FO340,180^GB0,270,2^FS
^FX Carrier text ^FS
^FO360,195^A0N,18,,^FDCARRIER:^FS
^FO360,245^A0N,36,,^FDAcme Freightways^FS
^FO360,295^A0N,30,,^FDPRO: 1234^FS
^FO360,345^A0N,30,,^FDB/L: 5678^FS
^FX Draw horizontal line ^FS
^FO0,450^GB720,0,4^FS
^FX EPC text ^FS
^FO0,465^A0N,32,,^FDEPC:^FS
^FO20,575^A0N,32,,^FD[EPC_TAG_URI]^FS
^FX Draw horizontal line ^FS
^FO0,670^GB720,0,4^FS
^FX SKU text ^FS
^FO0,685^A0N,32,,^FDSKU:^FS
^FO15,724^A0N,36,,^FDABC21270^FS
^FX Draw hoarizontal line ^FS
^FO0,785^GB720,0,4^FS
^FX GTIN text ^FS
^FO0,800^A0N,32,,^FDGTIN^FS
^FO100,890^A0N,32,,^BC,90,,Y,^FD>; (01) 10036000212706 ^FS
^XZ
If you want to print a specified EPC value on the smart label, the user-supplied ZPL must include special substitution strings, indicating in what representation the tag values are to be printed. The RFID Edge Server recognizes the following pre-programmed substitution string values:
^XA
^FO20,575^A0N,32,,^FD[EPC_TAG_URI]^FS
^XZ
The RFID Edge Server also recognizes user-defined substitution strings. User-defined parameters are specified in square brackets, but the substitution values must be provided in the PC spec in reader parameters as in the following example:
<readerParameters>
parameter map. Note that all of the [CT_..] fields should be either keys or replaced -->
<readerParameter name="MY_CUSTOM_PARAMETER1">parameterValue1 </readerParameter>
<readerParameter name="MY_CUSTOM_PARAMETER2">parameterValue2 </readerParameter>
...
</readerParameters>
The Zebra110 driver supports host status polling and RFID log processing.
Host status is polled at the interval defined by the deviceStatusUpdateInterval property in the edge.props file. Note that this value applies to all drivers.
An RFID log entry is returned for each job that contains an RFID operation (Enable RFID Encoding is set to true). The status code extracted from the log is matched against the customizeable status file (by default, etc/ZebraPrintStatus.props) for description and severity level and then processed according to severity level.
The section applies to all readers.
Problem: While an active subscription is running, the reader frequently displays a failed connection message.
Possible reason: Verify that the socketTimeout field is blank (the default setting is 15000 ms). You can change this value, but it is impractical to set it lower than 5000.
Problem: You see unusually high CPU utilization when running an active subscription.
Possible reason: Verify that the defaultRate value is a non-zero positive number.
|