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.

Bytes 0–3<br />

Bytes 4–7<br />

Bytes 8–11<br />

The Write Quadlet Request for point 0 would look like this:<br />

CHAPTER 4: USING THE IEEE 1394-BASED PROTOCOL<br />

Write Quadlet Request for point 1 (hex): 000004000000FFFFF0C0004400000180<br />

Write Quadlet Request for point 2 (hex): 000004000000FFFFF0C0008400000180<br />

Write Quadlet Request for point 3 (hex): 000004000000FFFFF0C000C400000180<br />

As you can see, the only difference in these packets is the memory map address for the point.<br />

For more information on module types <strong>and</strong> setting point types, see “Configuring I/O Points,<br />

Event/Reactions, <strong>and</strong> Security” on page 92.<br />

Configuring I/O Point Types—Write Response Packet (Brain➞PC)<br />

The response from the brain is a simple acknowledgment, as you saw before, with the ACK or<br />

NAK appearing in the rcode parameter:<br />

destination_ID tl rt tcode pri<br />

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0<br />

source_ID rcode reserved<br />

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0<br />

reserved<br />

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0<br />

Reading <strong>and</strong> Writing<br />

Memory map address for point 0’s point type<br />

Point type designation for digital output<br />

Now that the PC has successfully connected to the brain, sent a Powerup Clear, <strong>and</strong> configured<br />

I/O points as necessary, you can read <strong>and</strong> write to the points.<br />

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

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

Saved successfully!

Ooh no, something went wrong!