SAMSys Readers

1
SAMSys Readers

• Multi Protocol
• Multi Frequency

2
System Architecture

• Concentrators
• Serial line interface
• Ethernet interface
• TCP/IP stack
• TFTP transfer support
• XML and SOAP
• HTML web page interface
• Operator Interface
• Forth interpreter
• Auto configuration
• Plug and Play support.

• Servers
• SAMSys provides utilities and samples only
• Suggested operation XML / SOAP
• Apache or MS SOAP servers
• .NET or JAVA applications
• Standard Browsers
• Readers
• CHUMP protocol, standard commands
• Xrefernce of tag commands and data structures
• serial line, single or networked
• RS-232 or RS-485
• Human readable
• FORTH interpreter

3
Reader Interface
Serial Interface with RS-485 network support

• Multi-Protocol Support
• Configure first through variable that can be
  short duration or can be held in flash. The read
  commands are then standard regardless of
  protocol.
• Protocol Select Word
• Specific Protocol Configure words, ie bit/byte
  swap, auto resets, time slots, data size

4
Concentrator Interface
Serial and Ethernet network support

• System Support
• Support for networked readers on RS-485 and
  conversion from CHUMP protocol to network
  standards XML and SOAP.
• HTML web page interface allowing applications and
  support functions such as diagnostics and
  upgrades through standard browsers
• Operator Interface and local application function
  support through the Forth interpreter.
• Support for auto configuration of new readers or
  replacement readers on the CHUMP network.
• Plug and Play support to server.
• Server support CHUMP, FTP/XML, HTML web page, XML
  and SOAP.

5
Protocol Challenges

• Non-byte wide fields, ie. 5-bits do we left or
  right justify.
• Bit swaps and byte swaps.
• Data sizes
• CRC standardization
• ID separate or data field?
• Data Format Fields
• Application Format Fields
• Standardization of Cross Reference of Tag
  Commands and Data Structures

6
T6 API Implementation

• Supported 1999 to 2000
• Implemented
• Open
• Identify
• Read Write
• Other functions, mainly debug logging, stubs
  were in place so as not to fault on the call but
  there was no substance behind the call simply
  default replies.
• Required dll support on the server to implement
  these calls, allowed for direct reader and
  concentrator connections.
• Support software also in place in the
  concentrator.
• Support dropped because of complexity of data
  structures, insufficient interest from our
  customers and dll / operating system support
  required.