Hi Basil, My apology for the slow response ... I've been on vacation. I have attached the Intermec extensions XML definition and XSD files. Can you see a mistake that is causing Custom extensions to be handled incorrectly? Thank you,
Rob Buck This message is intended only for the named recipient. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of this information is strictly prohibited.
<?xml version="1.0" encoding="UTF-8"?> <!-- Copyright 2009, Intermec Technologies Corp. --> <llrpdef xmlns="http://www.llrp.org/ltk/schema/core/encoding/binary/1.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:h="http://www.w3.org/1999/xhtml"; xsi:schemaLocation="http://www.llrp.org/ltk/schema/core/encoding/binary/1.0/llrpdef.xsd";> <vendorDefinition name="Intermec" vendorID="1963" /> <namespaceDefinition prefix="Intermec" URI="http://www.intermec.com/rfid/llrp"; schemaLocation="llrp-Intermec-schema.xsd" /> <!-- --> <customEnumerationDefinition name="IntermecEngineCodeEnumeration" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright=""> <h:p></h:p> </description> </annotation> <entry value="0" name="Success"/> <entry value="1" name="Insufficient_Tag_Power"/> <entry value="3" name="NAK"/> <entry value="4" name="Read_Error"/> <entry value="5" name="Write_Error"/> <entry value="7" name="Lock_Error"/> <entry value="9" name="Unlock_Error"/> <entry value="10" name="Query_Lock_Error"/> <entry value="12" name="Kill_Error"/> <entry value="14" name="Illegal_Command"/> <entry value="15" name="Address_Range_Check_Error"/> <entry value="16" name="Nonspecific_Error"/> <entry value="17" name="Privilege_Error"/> <entry value="18" name="Memory_Lock_Error"/> <entry value="19" name="Blocked"/> <entry value="20" name="Duty_Cycle"/> <entry value="22" name="No_Response"/> <entry value="23" name="CRC_Error"/> <entry value="24" name="Collision"/> <entry value="25" name="Memory_Overrun_Error"/> <entry value="26" name="Erase_Error"/> </customEnumerationDefinition> <!-- **************************************************************************** --> <!-- Events --> <customParameterDefinition name="IntermecResetStartEvent" vendor="Intermec" subtype="16" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright="Copyright 2009, Intermec Technologies Corporation"> <h:p>Event generated when the internal RFID hardware undergoes a reset. For example, when a bluetooth radio module is disconnected/reconnected.</h:p> </description> </annotation> <allowedIn repeat="0-1" type="ReaderEventNotificationData"/> </customParameterDefinition> <customParameterDefinition name="IntermecResetCompleteEvent" vendor="Intermec" subtype="19" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright="Copyright 2009, Intermec Technologies Corporation"> <h:p>Event generated when the internal RFID hardware completes recovery from a reset event.</h:p> </description> </annotation> <allowedIn repeat="0-1" type="ReaderEventNotificationData"/> </customParameterDefinition> <customParameterDefinition name="IntermecROSpecLoopEvent" vendor="Intermec" subtype="21" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright="Copyright 2009, Intermec Technologies Corporation"> <h:p>Event generated when an ROSpec with looping enabled (see IntermecEnableROSpecLoop parameter) restarts execution of its SpecParameter list.</h:p> </description> </annotation> <allowedIn repeat="0-1" type="ReaderEventNotificationData"/> </customParameterDefinition> <!-- **************************************************************************** --> <!-- ROSpec Options --> <customParameterDefinition name="IntermecEnableROSpecLoop" vendor="Intermec" subtype="5" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright="Copyright 2009, Intermec Technologies Corporation"> <h:p>Enable/disable looping of all specs (e.g. AISpec and RFSurveySpecs) within an ROSpec. When enabled, the ROSpec will not stop when the list of specs has completed execution; it will restart execution of all specs in the list.</h:p> </description> </annotation> <field type="u1" name="EnableSpecLooping" /> <reserved bitCount="7"/> <allowedIn repeat="0-1" type="SpecParameter"/> </customParameterDefinition> <!-- **************************************************************************** --> <!-- AISpec Options --> <customParameterDefinition name="IntermecAISpecStopTrigger" vendor="Intermec" subtype="28" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright="Copyright 2009, Intermec Technologies Corporation"> <h:p>Intermec-specific AISpec stop trigger. This trigger can be used in conjunction with the standard AISpecStop trigger. If this IntermecAISpecStopTrigger is specified, and the standard AISpecStopTrigger is type Null, only the IntermecAISpecStopTrigger will be used. If the IntermecAISpecStopTrigger is specified and the standard AISpecStopTrigger type is not Null, both triggers will be used, and the first trigger condition to be met will stop the AISpec.</h:p> </description> </annotation> <parameter repeat="1" type="Custom"/> <allowedIn repeat="0-1" type="AISpec"/> </customParameterDefinition> <customParameterDefinition name="IntermecAISpecStopTriggerMinimumTries" vendor="Intermec" subtype="31" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright="Copyright 2009, Intermec Technologies Corporation"> <h:p>Intermec-specific AISpecStopTrigger used to specifiy the minimum number of inventory rounds per AISpec execution.</h:p> </description> </annotation> <field type="u16" name="MinimumTries"/> <parameter repeat="0-N" type="Custom"/> <allowedIn repeat="0-1" type="IntermecAISpecStopTrigger"/> </customParameterDefinition> <customParameterDefinition name="IntermecAISpecStopTriggerMinimumTimeout" vendor="Intermec" subtype="32" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright="Copyright 2009, Intermec Technologies Corporation"> <h:p>Intermec-specific AISpecStopTrigger used to specifiy the minimum duration (in milliseconds) for AISpec execution.</h:p> </description> </annotation> <field type="u32" name="MinimumTimeout"/> <parameter repeat="0-N" type="Custom"/> <allowedIn repeat="0-1" type="IntermecAISpecStopTrigger"/> </customParameterDefinition> <customParameterDefinition name="IntermecAccessResult" vendor="Intermec" subtype="0" namespace="Intermec"> <annotation> <documentation></documentation> <description copyright="Copyright 2009, Intermec Technologies Corporation"> <h:p></h:p> </description> </annotation> <field type="u16" name="Result" enumeration="IntermecEngineCodeEnumeration"/> <allowedIn repeat="0-1" type="TagReportData"/> </customParameterDefinition> </llrpdef>
llrp-Intermec-schema.xsd
Description: llrp-Intermec-schema.xsd
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
