14.08.2013 Views

snap ethernet-based i/o units protocols and programming guide

snap ethernet-based i/o units protocols and programming guide

snap ethernet-based i/o units protocols and programming guide

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 4: USING THE IEEE 1394-BASED PROTOCOL<br />

Response packet or a Write Response packet. The structure <strong>and</strong> parameters of the request <strong>and</strong><br />

response packets are shown beginning on page 93.<br />

Writing Data<br />

To change the configuration or status of an I/O point, to enable a counter, or to write other data,<br />

the host sends a Write Request packet containing the destination address <strong>and</strong> the new data to<br />

be written. The SNAP Ethernet-<strong>based</strong> brain responds by returning a Write Response packet<br />

indicating success or failure.<br />

Reading Data<br />

The host can also access the status of I/O modules, counter values, <strong>and</strong> other data by reading<br />

the appropriate memory locations from the SNAP Ethernet-<strong>based</strong> brain memory map. The host<br />

computer simply sends a Read Request packet asking for data from those memory locations, <strong>and</strong><br />

the brain returns the data in a Read Response packet.<br />

The following diagram shows a specific example of a host computer reading data from a SNAP<br />

Ethernet-<strong>based</strong> brain:<br />

Streaming Data<br />

Most communication involves the two-step process of request <strong>and</strong> response. But the SNAP<br />

Ethernet-<strong>based</strong> brain can also stream data, as explained on page 35. Streaming uses UDP <strong>and</strong><br />

does not require a response.<br />

For more information on using streaming, see page 88.<br />

SNAP Ethernet-Based I/O Units Protocols <strong>and</strong> Programming Guide 81

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

Saved successfully!

Ooh no, something went wrong!