11.01.2014 Views

DeviceNet Master Protocol API

DeviceNet Master Protocol API

DeviceNet Master Protocol API

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>DeviceNet</strong>-<strong>Master</strong> Fundamentals • 17<br />

2 Fundamentals<br />

2.1 General Access Mechanisms on netX Systems<br />

This chapter explains the possible ways to access a <strong>Protocol</strong> Stack running on a netX system :<br />

1. By accessing the Dual Port Memory Interface directly or via a driver.<br />

2. By accessing the Dual Port Memory Interface via a shared memory.<br />

3. By interfacing with the Stack Task of the <strong>Protocol</strong> Stack.<br />

The picture below visualizes these three ways:<br />

1<br />

2<br />

(Extended) Status Block Send Mailbox Reveive Mailbox Output Data Image Input Data Image<br />

AP Task<br />

3<br />

Fieldbus Task(s)<br />

Network Abstraction Layer<br />

Network<br />

Figure 1 - The three different Ways to access a <strong>Protocol</strong> Stack running on a netX System<br />

This chapter explains how to program the stack (alternative 3) correctly while the next chapter<br />

describes accessing the protocol stack via the dual-port memory interface according to alternative 1<br />

(and 2, if the user application is executed on the netX chip in the context of the rcX operating system<br />

and uses the shared DPM). Finally, chapter 5 titled “The <strong>DeviceNet</strong> Application Interface” describes<br />

the entire interface to the protocol stack in detail.<br />

Depending on whether you choose the stack-oriented approach or the Dual Port Memory-based<br />

approach, you will need either the information given in this chapter or those of the next chapter to be<br />

able to work with the set of functions described in chapter 5. All of those functions use the four<br />

parameters ulDest, ulSrc, ulDestId and ulSrcId. This chapter and the next one inform<br />

about how to work with these important parameters.<br />

Hilscher Gesellschaft für Systemautomation mbH – Rheinstr. 15 – D-65795 Hattersheim<br />

Edition 3 – <strong>API</strong>:<strong>DeviceNet</strong>-<strong>Master</strong>#EN– 2009/01

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

Saved successfully!

Ooh no, something went wrong!