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
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 />
IEEE 1394 node appears logically as a 48-bit address space. To communicate with a device, you<br />
read from <strong>and</strong> write to specific memory addresses in that space.<br />
The SNAP Ethernet-<strong>based</strong> brain’s memory map is similar to a grid of mailboxes, with each<br />
mailbox having its own memory address. (See Appendix A for the detailed memory map of the<br />
brain.) Every I/O module appears in two ways in this memory map:<br />
1. As bank data for block reads <strong>and</strong> writes (for example, all counters in one bank)<br />
2. As individual point data for reads <strong>and</strong> writes of individual points.<br />
Communication Packets<br />
Communication using the Opto 22 IEEE 1394-<strong>based</strong> protocol basically involves an IEEE 1394<br />
packet placed inside a TCP/IP or UDP/IP packet. These nested packets look like this TCP example:<br />
The SNAP Ethernet-<strong>based</strong> brain uses the following types of request packets specified by the IEEE<br />
1394 st<strong>and</strong>ard:<br />
Read Quadlet: reads four bytes starting at an address<br />
Read Block: reads N bytes starting at an address<br />
Write Quadlet: writes four bytes starting at an address<br />
Write Block: writes N bytes starting at an address.<br />
To start communication with the SNAP Ethernet-<strong>based</strong> brain, the host computer sends one of<br />
these four packets via TCP/IP or UDP/IP. To complete each transaction, the brain returns a Read<br />
80 SNAP Ethernet-Based I/O Units Protocols <strong>and</strong> Programming Guide