11.01.2014 Views

PROFIBUS DP-Master

PROFIBUS DP-Master

PROFIBUS DP-Master

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The Application Interface 295/315<br />

6.4 The APM-Task<br />

The APM-Task only offers packets regarding redundandancy function. Nevertheless you should be<br />

aware of its existence as it is very important for performing internal processes. These concern for<br />

instance such important things as:<br />

• Diagnosis<br />

• Routing of packets<br />

• Database operations<br />

• Data Exchange with Dual Port Memory.<br />

• Error processing<br />

To get the handle of the process queue of the APM -Task the Macro TLR_QUE_IDENTIFY() has to<br />

be used in conjunction with the following ASCII-queue name<br />

ASCII queue name<br />

Description<br />

" APM_QUE” Name of the APM-Task process queue<br />

Table 181: FSPMM-Task process queue<br />

The diagnostic and error messages which can be issued by the APM-Task are described in section<br />

7.4 of this document.<br />

In detail, the following functionality is provided by the APM -Task:<br />

Overview over Packets of the APM-Task<br />

No. of<br />

section<br />

Packet<br />

Command<br />

code<br />

(REQ/CNF<br />

or<br />

IND/RES)<br />

Page<br />

6.4.1 <strong>PROFIBUS</strong>_APM_CMD_REDUNDANT_MODE_REQ/CNF – Set <strong>Master</strong> to<br />

active/passive<br />

0x3000/<br />

0x3001<br />

296<br />

6.4.2 <strong>PROFIBUS</strong>_APM_CMD_REDUNDANT_MODE_IND – Indicate Status<br />

changed of active <strong>Master</strong><br />

Table 182: Overview over the Packets of the APM-Task of the <strong>PROFIBUS</strong> <strong>DP</strong> Protocol Stack<br />

0x3002 299<br />

<strong>PROFIBUS</strong> <strong>DP</strong>-<strong>Master</strong> |<br />

DOC061001API12EN | Revision 12 | English | 2010-12 | Released | Public © Hilscher, 2006-2010

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

Saved successfully!

Ooh no, something went wrong!