06.01.2015 Views

INfinity 510 Protocol Reference Guide - Sirit

INfinity 510 Protocol Reference Guide - Sirit

INfinity 510 Protocol Reference Guide - Sirit

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 1 - Introduction<br />

Machine Interface<br />

Command/Response and Event Channels<br />

The machine interface is a direct connection to the reader’s<br />

command/response and event channels. The command/response channel<br />

is a bidirectional interface and connects across port 50007. Commands<br />

and the corresponding responses are sent across this channel. The event<br />

channel is unidirectional and connects across port 50008. The event<br />

channel reports asynchronous events such as errors, tag arrivals, and<br />

digital output triggers.<br />

A sample of software code required to open a communication session with<br />

a reader is provided in the Establishing a Machine Interface section in<br />

Chapter 2.<br />

Interface <strong>Protocol</strong><br />

The <strong>INfinity</strong> <strong>510</strong> reader’s native protocol is ASCII text based and is used to<br />

communicate over the Command/Response and Event Channels.<br />

Every command is sent to the reader over port 50007 and should end with<br />

\r\n. The corresponding reader response will end with \r\n\r\n. An<br />

example of a command and response is shown in the following:<br />

fcc\r\n\r\n<br />

Events are returned from reader over port 50008. Every event is completed<br />

with \r\n\r\n. An example event is shown in the following:<br />

event.tag.report tag_id=0xAABBCCDDEEFFGG\r\n\r\n<br />

<strong>INfinity</strong> <strong>510</strong> <strong>Protocol</strong> <strong>Reference</strong> <strong>Guide</strong> 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!