A P P E N D I X A

Reader Adapter Reference

This appendix describes the Device Profiles (also known as reader-adapters) and their properties for the RFID readers that are supported in this release. This information can be seen and modified using the RFID Configuration Manager. See Managing Device Profiles for procedures.

The following tables list the properties (also known as attributes), a description and the valid values. Additional descriptive information for some properties follows the table where necessary to expand on the property usage. The properties that are common to all Device Profiles are described in detail in the section Supported Device Profiles. The complete list of supported readers and other devices described in TABLE 2-3 found in Chapter 2

AWID2010Adapter

The AWID2010Adapter is used to communicate with the AWID MPR-2010 reader. The attributes are defined in TABLE A-1.

TABLE A-1 AWID2010Adapter Properties
Property Name	Description	Values
Name	Unique name identifying this adapter	Sample value = AWIDAdapter
classname	java classname	com.sun.autoid.adapter.awid.AWID2010Adapter
Common Properties	See TABLE 2-4 for general description and values
`LogLevel` `hostname` `port` `readerepc` `autoread` `communicationTimeout` `scanDuration`		`hostname -` must be static IP address or specified to boot from DHCP and obtain the IP address specified by the value of this property `port` - default value=80
Additional Properties
readCommandType	The AWID Reader can read tags in multiple modes.	PORTAL_IDs IDs IDs_WITH_SELECT SINGLE_TAG_METER READ_SINGLE_TAGID READ_SINGLE_TAGID_TIMEOUT
tagType	The Reader can read different type of tags. Specifying more than one property would set it to Multi-Protocol mode	one or comma-separated list of the following values: EPC_CLASS_0 EPC_CLASS_1 INTERMEC EM EPC_CLASS_1.19 MULTI_PROTOCOL
EM_Version	required when reading in IDs mode for tagType set to EM	EM_4022 - default EM_4222
writeEPCRetry	Number of tries to write before returning	1 - default is 1 0 - write until complete
sleeptime	The sleep time between reads in milliseconds.	default is 250 msecs
gatherUserData	If true, read the User Data in the transponder and associate it with the Identifier during the inventory round. This information is then passed along the processing chain to filters and connectors which in turn interpret the User Data appropriately. default is false	false - default true

ISCMR100Adapter

The ISCMR100Adapter is used to communicate with the Feig Electronic ID ISC MR.100 and Feig Electronic ID ISC PR.100 readers. The attributes are shown in TABLE A-2.

TABLE A-2 ISCMR100Adapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	Sample value = ISCMR100FeigReader
classname	java classname	com.sun.autoid.adapter.feig.obidiscan.ISCMR100Adapter
Common Properties	See TABLE 2-4 for general description and values
`LogLevel`
`hostname`		must be configured with a static IP address, or to boot from DHCP and obtain the IP address specified in this property.
`port`
`readerepc`
`autoread`
communicationTimeout
`scanDuration`

PMLAdapter

The PMLAdapter is used to communicate with the Software PMLCore Reader . The PMLReader typically listens for connection on one or multiple ports. The attributes are shown in TABLE A-3.

TABLE A-3 PMLAdapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	Sample value = `PMLReader`
classname	java classname	`com.sun.autoid.adapter.pml.PMLAdapter`
Common Properties	See TABLE 2-4 for general description and values
`LogLevel`
`hostname`	IP address or hostname of the Reader where the Software PMLCore Reader is executing
`port`		Must match the corresponding entry in the `Simulator.properties` of the PMLCore Reader.
`readerepc`		must match the corresponding entry in the `Simulator.properties` of the PMLCore Reader
`autoread`	PMLCore reader supports autoread mode.	Setting this property to true causes the Software PMLCore reader to begin generating simulated RFID Events. See TABLE 2-4.
`scanDuration`

NanoScanner Adapter

The NanoScannerAdapter communicates with the Alien ALR-9780 or Alien NanoScanner 915 RFID readers. The attributes are shown in TABLE A-4.

TABLE A-4 NanoScannerAdapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	Sample value = AlienReader
classname	java classname	`com.sun.autoid.adapter.alien.NanoScannerAdapte`r
Common Properties	See TABLE 2-4 for general description and values
`LogLevel`
`hostname`		must be configured with a static IP address, or to boot from DHCP and obtain the IP address specified in this property.
`port`		default is port 23
`readerepc` `autoread` communicationTimeout `scanDuration`
Additional Properties	Also see Additional Properties Information - NanoScannerAdapter.
`readerepcANT0, readerepcANT1,`etc	the EPC identifier associated with antenna 0, 1, 2 or 3 of the reader.
`antennaSequence`	Specifies the order in which antennae are pulsed. This property must be set to enable the various antennae.	This is a comma separated list of antenna identifiers: 0, 1, 2, 3, depending on the number of antennae supported by the reader. An example value = 0,1, - the reader would pulse antenna 0, followed by antenna 1. Also refer to the Alien Reader documentation.
`username`	Specifies the username that the Event Manager uses to communicate with the reader.	Sample value = `alien`
`password`	Specifies the password that the Event Manager uses to communicate with the Alien reader.	Sample value = `password`
`persisttime`	Specifies the number of seconds the reader should persist the tag list in its internal tag list buffer.	Sample value = 2, which tells the Alien reader to remember tags for up to 2 seconds before it stops reporting them.
`AcquireMode`	Specifies the mode to be used for collection of tags. Refer to the Alien Reader documentation.	`Inventory` or `GlobalScroll` - `Inventory` mode is recommended for applications that expect multiple tags to be detected by the reader at once.

Additional Properties Information - NanoScannerAdapter

1. readerepcANT0, readerepcANT1 - This value overrides the value specified by readerepc for this particular antenna. (The property readerepc applies to the entire system as long as an EPC has not been specified for a particular antenna.) This property enables the events from two or more antennae from a single reader to be handled by two or more separate processing chains of filters and connectors. Setting the EPC Identifier for the antenna tells the RFID Event Manager to discriminate between the antennae if they're enabled, but enabling the antenna is done through the use of the antennaSequence property.

2. persisttime - This should not be confused with the functionality provided by the Smoother Filter. The persisttime property is managed by the Alien RFID reader, not the RFID Event Manager. Refer to the Alien Reader documentation.

Mercury3Adapter

The Mercury3Adapter communicates with the ThingMagic Mercury3 and the Sensormatic SensorID Agile 1 RFID Reader. The attributes are shown in TABLE A-5.

TABLE A-5 Mercury3Adapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	Sample value = ThingMagicReader
classname	java classname	com.sun.autoid.adapter.tyco.Mercury3Adapter
Common Properties	See TABLE 2-4 for general description and values
`LogLevel`
`hostname`		must be configured with a static IP address, or to boot from DHCP and obtain the IP address specified in this property.
`port`		default is port 80
`readerepc` `autoread` communicationTimeout scanDuration
Additional Properties	Also see Additional Properties Information- Mercury3Adapter.
`protocol`	Use this property to specify the protocol to be used during data capture. At this time, only one protocol can be active at a time.	This reader supports two RF protocols, `CC915` for UHF, and `CC1356` for HF. The default value = `CC915`.
`readerepcUHF1,` `readerepcUHF2,` etc	`readerepcUHF1` specifies the EPC for Antenna UHF1. This is the EPC reader value associated with the UHF1, UHF2, HF1, and HF2 antennae of the reader. Replace UHF1 with UHF2, HF1, or HF2 for the other antennae.	A sample value = `urn:epc:tag:gid-96:1.2.1` See Additional Properties Information- Mercury3Adapter
`antenna`	This reader supports 2 antennae for each protocol: UHF1, UHF2 and HF1, HF2. This property specifies the antenna from which to read.	The default is to enable all the antennae for the RF `protocol` that has been enabled (see `protocol`). For example, if CC915 (the default) is selected, both antennae UHF1 and UHF2 will be active. See Additional Properties Information- Mercury3Adapter

Additional Properties Information- Mercury3Adapter

1. readerepcUHF1 - where UHF1 can be UHF1, UHF2, HF1, or HF2. This is the EPC reader value associated with the UHF1, UHF2, HF1, and HF2 antennae of the reader. This property overrides the value specified by readerepc for this particular antenna. The property readerepc applies to the entire system as long as an EPC has not been specified for a particular antenna. This is useful for handling the events from two or more antennae from a single reader by two or more separate processing chains of filters and connectors.

2. antenna - This reader supports 2 antennae for each protocol: UHF1, UHF2 and HF1, HF2. Use the antenna property to specify the antenna from which to read. The default is to enable all the antennae for the RF protocol that has been selected (see protocol). For example, if CC915 (the default) is selected, both antennae UHF1 and UHF2 will be active.

Note - It is not necessary to set the antenna property to enable the various antennae. Setting the EPC Identifier for the antenna tells the RFID Event Manager to discriminate between the antennae if they're enabled. Enabling a specific antenna is done through the use of the antenna property.

To activate only UHF1, use the following antenna property:

	<ems:properties>

		<ems:property>antenna</ems:property>

		<ems:value>1</ems:value>

	</ems:properties>

Note - Programming (writing to) an RFID tag can only be done from antenna 1 (UHF1) at this time.

Mercury4Adapter

The Mercury4Adapter is used to communicate with the ThingMagic Mercury4 and the Sensormatic Agile2 RFID Reader. The attributes are shown in TABLE A-6.

TABLE A-6 Mercury4Adapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	Sample value = ThingMagicReader
classname	java classname	com.sun.autoid.adapter.tyco.Mercury4Adapter
Common Properties	See TABLE 2-4 for general description and values
`LogLevel`
`hostname`		must be configured with a static IP address, or to boot from DHCP and obtain the IP address specified in this property.
`port` readerepc autoread communicationTimeout scanDuration		default is port 80
Additional Properties	Also see Additional Properties Information- Mercury3Adapter.
`protocol`	Use this property to specify the protocol to be used during data capture.	This reader supports three data capture protocols: `EPC0`, `EPC1` and `ISO18000-6B`. The default is ALL.
`readerepcUHF1, readerepcUHF2,` etc	`readerepcUHF1` specifies the EPC for Antenna UHF1.This is the EPC reader value associated with the UHF1, UHF2, UHF3, UHF4, UHF5, UHF6, UHF7 and UHF8 antennae. Replace UHF1 with UHF2, UHF3 and so on for the other antennae.	A sample value = urn:epc:tag:gid-96:1.2.1 See Additional Properties Information- Mercury3Adapter
`antenna`	This reader supports 2 antennae for each protocol: UHF1, UHF2 and HF1, HF2. This property specifies the antenna from which to read.	The default is to enable all the antennae for the RF `protocol` that has been enabled (see `protocol`). For example, if `CC915` (the default) is selected, both antennae `UHF1` and `UHF2` will be active. See Additional Properties Information- Mercury3Adapter

MatricsReader Adapter

The MatricsReaderAdapter is used to communicate with the Matrics RDR-001 and Matrics AR-400 RFID readers. The attributes are shown in TABLE A-7.

Note - The use of a serial to network (Ethernet) adapter is required.

TABLE A-7 MatricsAdapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	Sample name = MatricsReader
classname	java classname	com.sun.autoid.adapter.matrics.MatricsReaderAdapter
Common Properties	See TABLE 2-4 for general description and values
`LogLevel`
`hostname`	IP address for the network-facing interface of the Serial to Ethernet Convertor Port which interfaces to the Matrics RDR-001. Future Matrics readers will have this built in.	example value = 192.168.2.150
`port`	IP port for the network- facing interface of the Serial to Ethernet Convertor Port which interfaces to the Matrics RDR-001. Future Matrics readers will have this built in.
`readerepc` autoread communicationTimeout `scanDuration -`not used by this reader

Additional Properties	Also see Additional Properties Information- MatricsReader Adapter.
`ConnectionType`	Specifies the type of network being used to connect to the reader.	`network`: indicates IP connection `serial`: not currently used
`readerepcANT`x	Specifies an EPC value associated with one of the specific multiple antennae on the reader, where the variable x is an EPC value associated with antenna 1, 2, 3, and 4 of the reader.	urn:epc:tag:gid-96:1.1.1
Node	See Additional Properties Information- MatricsReader Adapter
Antennan	Specifies whether a particular antenna is to be used where n, indicates the number of the antenna. This readers supports antenna 1-4.	A value of 1 means it is to used. A value of zero means it is to be inhibited. For example, to enable Antenna 1, the following is used: <ems:properties> <ems:property>Antenna1</ems:property> <ems:value>1</ems:value> </ems:properties>
`Power`	Controls the power level transmitted during a given read or write interval	The minimum value is `01hex`. The maximum value is FFhex which specifies a full power condition (in this case 4 watts). The power level is logarithmic. For the RDR-001 reader, the maximum power is about `30dBm`. The value `C0hex` is about 50 percent and `80hex` about 25 percent of the maximum power.
`Environment`
`CombinedAntenna`
`FilterLength`	not currently used - for future expansion
`Filter`	not currently used - for future expansion
`Wait`	used by the underlying adapter framework to pause between read cycles.
`debugflags`	not currently used - for future expansion

Additional Properties Information- MatricsReader Adapter

1. readerepcANTn - the reader antenna EPC identifier, an EPC value associated with antenna 1, 2, 3, and 4 of the reader where the variable n is the number of the antenna. It overrides the value specified by readerepc for this particular antenna, readerepc applies to the entire system as long as an EPC has not been specified for a particular antenna. This is useful for handling the events from two or more antennae from a single reader by two or more separate processing chains (filters and connectors). See readerepc. The following example specifies the EPC for antenna 1. Replace 0 with 1, 2, or 3 for the other antennae.

	<ems:properties>

		<ems:property>readerepcANT0</ems:property>

		<ems:value>urn:epc:tag:gid-96:1.1.1</ems:value>

	</ems:properties>

Note that readerepcANT0 corresponds to physical antenna 1, readerepcANT1 corresponds to antenna 2, readerepcANT2 corresponds to antenna 3, and readerepcANT3 corresponds to antenna 4.

Note - It is necessary to set the antennan (where n is the number of the antenna) property to 1 in order to enable the use of antenna 1. Setting the EPC Identifier for antenna 1 tells the RFID Event Manager to discriminate between the antennae if they're enabled, but enabling the antenna is done through the use of the Antennan property.

2. Node - The Matrics reader sits on a RS 485 (a form of serial bus where multiple serial devices can operate unlike RS 232 where only operate at the same time) bus. Each node on a 485 bus must have an address. The serial to network adapter relays commands to the reader based on this address. If there are additional readers present then they have other addresses. For normal operation, no more than one reader will be on the 485 bus. Each reader will have its own serial to network adapter port interface and will be directly IP addressable. The 485 address below must be the same for all reader.

	<ems:properties>

		<ems:property>Node</ems:property>

		<ems:value>4</ems:value>

	</ems:properties>

3. Power - This parameter controls the power level transmitted during a given read or write interval. The normal transmit power of a North American Matrics RDR-001 reader is 4 watts. In other locales, this value may be less. The actual value is to be considered as a percentage value. The minimum value is 01hex. The maximum value is FFhex which specifies a full power condition (in our case 4 watts). The `Power level' is logarithmic. In case of the reader RDR-001 the maximum power is about 30dBm. The value C0hex is about 50 percent and 80hex about 25 percent of the maximum power.

	<ems:properties>

		<ems:property>Power</ems:property>

		<ems:value>C0</ems:value>

	</ems:properties>

4. Environment - This property determines how long the reader tries to read tags during a `Read Full' command. A larger number means longer, more intense reading (more frequencies in a FCC part 15 reader are used). This is useful for applications where tagged items are not moving (stationary), such as in a shelf application, to overcome issues with interference and RF-Null's on a fixed pool of tags.

In an environment where tags moving in and out of the read field of a reader it is important to read as fast as possible to be able to start negotiating with new tags coming into the read field. That's the reason that in dynamic environments the variable is usually small. The environment property is dependent on the location of the system. Generally it is safe to start with the smallest value (00 for dynamic, 04 for static) to evaluate the performance. To improve reads it might be necessary to adjust the property up or down.

Practically, this value should remain at 4. There are few benefits to changing it unless you are sure that your environmental conditions are relatively constant.

	<ems:properties>

		<ems:property>Environment</ems:property>

		<ems:value>4</ems:value>

	</ems:properties>

5. CombinedAntenna - This property indicates that all the antennas marked with `included' are grouped. That means a host has only to address the antenna with the smallest index to get reads from all combined antennas (antenna 1, 3 and 4 are combined - host executes `Read Full' ONLY for antenna 1 to get reads from antenna 1, 3 and 4).

This parameter only works for antenna one. The reader tends to produce antenna faults whenever a value other than antenna 1 is chosen.

Because we generally want to distinguish between antennas, we discourage the usage of this parameter and have not connected it for now. It has been kept in case those interested in using it wish to make modifications in the future.

	<ems:properties>

		<ems:property>CombinedAntenna</ems:property>

		<ems:value>1</ems:value>

	</ems:properties>

6. Wait - Reader Wait Time is used by the underlying adapter framework to pause between read cycles. The normal operation of the reader is to issue a read command (since autoread is simulated, one read command is required for each read cycle). The reader returns all tags read during this time, after which, the adapter framework waits for the 'wait time' specified.

	<ems:properties>

		<ems:property>Wait</ems:property>

		<ems:value>80</ems:value>

	</ems:properties>

PrintronixAdapter

The PrintronixAdapter is used to communicate with the Printronix SL5000e Printer. The attributes are shown in TABLE A-8.

TABLE A-8 PrintronixAdapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	Sample name = PrintronixPrinter
classname	java classname	com.sun.autoid.adapter.printronix.PrintronixAdapter
Common Properties	See TABLE 2-4 for general description and values
`LogLevel` `hostname` port readerepc autoread communicationTimeout scanDuration	not used by this device
Additional Properties	.
`template`	Used to specify the location of the default print template.	/tmp/templatefile.txt
template.variable	Template idenfitied by word `variable`. There can be zero or more occurences of this property, each with a unique substitution for variable.	The value can be either URL or local file. For example, if sample name =`template.case`, then sample value = `/tmp/templatecase.txt`

SAMSysAdapter

The SAMSys adapter is used to communicate with the SAMSys MP9320 EPC V2.7 Reader. The attributes are shown in TABLE A-9.

TABLE A-9 SAMSysAdapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	Sample value = `SAMSysReader`
classname	java classname	`com.sun.autoid.adapter.SAMSys.SAMsysAdapter`
Common Properties	See TABLE 2-4 for general description and values
`LogLevel`
`hostname`	IP address or hostname of the Reader where the SAMSys Reader is executing	must be configured with a static IP address, or to boot from DHCP and obtain the IP address specified in this property.
`port`		default is port 2001
`readerepc` autoread
scanDuration	See Additional Properties Information for SAMSysAdapter
communicationTimeout	See Additional Properties Information for SAMSysAdapter
Additional Properties
enableCommandResponseCRC	Command Response Cyclic Redundancy Check (CRC). See also Additional Properties Information for SAMSysAdapter	true = perform check false = omit check
enableTagReadResponseCRC	Response Cyclic Redundancy Check (CRC). See also Additional Properties Information for SAMSysAdapter	true = perform check false = omit check
protocols	Specifies the type of RF protocol to be scanned for by the reader. When no `protocols` property is defined, the settings on the reader are used without modification. The reader can scan for multiple types simultaneously	Multiple `protocols` can be specified by using a comma-separated list such as, [IS186B,EPC1] Tested values are IS186B and EPC1. See also Additional Properties Information for SAMSysAdapter
`readerepcANT`n	EPC value associated with the ANT1, ANT2, ANT3, and ANT4 antennae of the reader, where the variable n equals the number of the antenna.	Example of usage: property name=r`eaderepcANT1` and value=urn:epc:tag:gid-96:1.2.11
`antennaSequence`	Specifies the specific antenna(s) from which to read. The order of the antennas listed in the property is significant.	Default is `ANT1`. To activate a sequence of ANT1 then ANT3 then ANT2, use the following value for `antennaSequence` - `ANT1,ANT3,ANT4`
cycles	Antenna Inventory Round Operations - defines the number of inventory operations performed on each antenna before hopping to the next antenna in the antenna sequence. See also Additional Properties Information for SAMSysAdapter	Default value = 1
antennanPower	Specify the desired power level, where the variable n designates the antenna number.	Values can be entered as hexadecimal or decimal digits. Hexadecimal values must be prefixed with the characters `0x`. The following example sets the same power levels for both antenna 1 and antenna 2: property name =`antenna1Power` with value = `0x60` and property name = `antenna2Power` with value = `96`
buzzerMode	The SAMSys reader produces an audible beep when tags are observed in its field of view. The 'buzzer' is enabled or disabled with this property.	values can be ON or OFF
regulatoryParty	Sets the Transmit Power Configuration (TPC) register within the SAMSys reader. See also Additional Properties Information for SAMSysAdapter	values are ETSI and FCC
observationSetTimeout	Sets the timeout threshhold used to detect the end of a reported tag observation set. This is separate and disctinct from the `communicationTimeout`, which is used for all other communication timeouts except the detection of the end of an observation set.	default 100 msec

Additional Properties Information for SAMSysAdapter

1. communicationTimeout - This property is used exclusively for all commands and responses on the device, except tag read commands and the respective responses. The property defines the inactivity threshold for reader responses. Performance can be highly dependent on this property, therefore we recommend reducing it from the default value of 10000ms. (10 seconds) You can start with a value of 1500ms, and make further reductions after observing deployment-specific performance. Observe the read performance with log levels set to FINEST. For more information , refer to the common properties section.

Both communicationTimeout and observationSetTimeout properties are used for detecting responses to the read command. The communicationTimeout property is used for the initial response, while observationSetTimeout is used for all subsequent observation responses. communicationTimeout behaves as described above for all other commands.

The property observationSetTimeout sets the inactivity threshold for signalling that an observation set has completed. Default is 100 msec. This value can be reduced after observing deployment-specific performance as described above.

2. enableCommandResponseCRC - Command Response Cyclic Redundancy Check (CRC). Each command response received from the reader is provided with a CRC checksum. The SAMSysAdapter enables you to verify that the command response arrived without any transmission error. Alternatively, this check can be omitted. The enableCommandResponseCRC property is used to establish whether these checks are performed - valid values are true and false.

3. enableTagReadResponseCRC - Response Cyclic Redundancy Check (CRC). Each reported tag observation sent from the reader is provided with a CRC checksum. The SAMSysAdapter enables you to verify that the transmitted tag data arrived without any transmission error. Alternatively, this check can be omitted to achieve greater system throughput. The enableTagReadResponseCRC property is used to establish whether these checks are performed, valid values are true and false.

4. scanDuration - The SAMys reader does not offer the ability to poll for a specified duration as some other reader devices do. The SAMSysAdapter emulates this capability. The adapter waits for the end of transmission from the reader (which could exceed the specified value) and dwells for the remaining time if the elapsed time is less than the value specified in the scanDuration property.

5. protocol - The SAMSys reader supports reading a number of different RFID tags. The value of this property specifies the types being used during data capture. The default is ALL. Multiple property definitions can be combined by using a comma-separated list.The following protocols have been tested with this release:

For ISO 18000-6A, the value is IS186A

For ISO 18000-6B, Intermec Intellitag, Philips I-CODE HSL, the value is IS186B

For Alien EPC, the value is EPC1

For EM 4022, EM4222 the value is STG

For EPC0, the value is EPC0

6. readerepcANTn - This is the EPC value associated with the ANT1, ANT2, ANT3, and ANT4 antennae of the reader, where the variable n equals the number of the antenna. This property overrides the value specified by readerepc for this particular antenna. The property readerepc applies to the entire system as long as an EPC has not been specified for a particular antenna. The property readerepcANTn is useful for specifying that the events from two or more antennae from a single reader be handled by two or more separate processing chains. See also readerepc.

Note - It is not necessary to set the antenna property to enable the use of the various antennae. Setting the EPC Identifier for the antenna tells the RFID Event Manager to discriminate between the antennae if they are enabled. Enabling a specific antenna is done through the use of the antennaSequence property.

7. cycles - Antenna Inventory Round Operations. The SAMSys reader enables the Multiplexer Configuration Word (MCW) register to be set to specify the number of inventory operations per round. This property defines the number of inventory operations performed on each antenna before hopping to the next antenna in the antenna sequence. See the SAMSys Comprehensive Heuristic Unified Messaging Protocol for more detailed information.

8. antennanPower - Specifies the desired power level. The SAMSys reader has 48 power settings settings. The lowest setting is 60 translating to 12 dBm and 16 mW. 02 corresponds to 34.7 dBm 2.95 W.

60, 5e, 5c, 5a, 58, 56, 54, 52, 50,

4e, 4c, 4a, 48, 46, 44, 42, 40,

4e, 4c, 4a, 48, 46, 44, 42, 40,

3e, 3c, 3a, 38, 36, 34, 32, 30,

2e, 2c, 2a, 28, 26, 24, 22, 20,

1e, 1c, 1a, 18, 16, 14, 12, 10,

0e, 0c, oa, 08, 06, 04, 02

9. regulatoryParty - Sets the Transmit Power Configuration (TPC) register within the SAMSys reader. Setting the value of this property to FCC sets the reader for FCC operation. Setting the value to ETSI sets the reader to ETSI operation with frequency hopping. Leaving the property unset leaves the reader register unchanged. SAMSys recommends changing this parameter only at the direction of SAMSys personnel. See the SAMSys Comprehensive Heuristic Unified Messaging Protocol for more detailed information.

ZebraAdapter

The ZebraAdapter is used to communicate with the Zebra Technologies R110XiIIIPlus Printer. The attributes are shown in TABLE A-10.

TABLE A-10 ZebraAdapter Attributes
Name	Description	Values
Name	Unique name identifying this adapter	sample name = ZebraPrinter
classname	java classname	com.sun.autoid.adapter.zebra.ZebraAdapter
Common Properties	See TABLE 2-4 for general description and values
`LogLevel` `hostname` `port` `readerepc` `autoread` `communicationTimeout`
`scanDuration`	not used by this device
Additional Properties	.
`template`	Used to specify the location of the default print template.	/tmp/templatefile.txt
template.variable	Template idenfitied by word `variable`. There can be zero or more occurences of this property, each with a unique substitution for variable.	The value can be either URL or local file. For example, if sample name =`template.case`, then sample value = `/tmp/templatecase.txt`
`description`	Specifies a description to be printed on the lable	value = label description text