DeviceNet Master Protocol API
DeviceNet Master Protocol API
DeviceNet Master Protocol API
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 • 25<br />
2.4 Client/Server Mechanism<br />
2.4.1 Application as Client<br />
The host application may send request packets to the netX firmware at any time (transition 1 2).<br />
Depending on the protocol stack running on the netX, parallel packets are not permitted (see protocol<br />
specific manual for details). The netX firmware sends a confirmation packet in return, signaling<br />
success or failure (transition 3 4) while processing the request.<br />
The host application has to register with the netX firmware in order to receive indication packets<br />
(transition 5 6). Depending on the protocol stack, this is done either implicit (if application opens a<br />
TCP/UDP socket) or explicit (if application wants to receive unsolicited DPV1 packets). Details on<br />
when and how to register for certain events is described in the protocol specific manual. Depending on<br />
the command code of the indication packet, a response packet to the netX firmware may or may not<br />
be required (transition 7 8).<br />
Application<br />
<br />
netX<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Figure 4: Transition Chart Application as Client<br />
The host application sends request packets to the netX firmware.<br />
The netX firmware sends a confirmation packet in return.<br />
The host application receives indication packets from the netX firmware.<br />
The host application sends response packet to the netX firmware (may not be required).<br />
Request<br />
Indication<br />
Confirmation<br />
Response<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
Change language