PROFIBUS DP Slave (Protocol API, netX)

Getting started/Configuration 38/228
Bit 6: Auto configuration (WRMSTRT_FLG_AUTOCONFIG):
Flag that indicates if set to TLR_TRUE(1) that the slave stack requests the host application for
check configuration and user parameter data. If set to TLR_FALSE(0), the stack handles
configuration and parameter data.
Bit 7: Address change not allowed (WRMSTRT_FLG_NO_ADDR_CHANGE):
Flag that indicates if set to TLR_TRUE(1) that the slave stack does not support the “Set Slave
Address” command. If set to TLR_FALSE(0), changing the bus address via the master is activated
and the slave stack does support the “Set Slave Address” command
4.3.1 Behavior when receiving a Set Configuration / Warmstart
Command
The following rules apply for the behavior of the PROFIBUS-DP Slave protocol stack when
receiving a set configuration command:
• The configuration packets name is PROFIBUS_APS_SET_CONFIGURATION_PRM_REQ
for the request and PROFIBUS_APS_SET_CONFIGURATION_PRM_CNF for the
confirmation.
• The configuration data are checked for consistency and integrity.
• In case of failure all data are rejected.
• In case of success the configuration parameters are stored internally (within the RAM).
• The parameterized data will be activated only after a channel init has been performed.
• No automatic registration of the application at the stack happens.
• The confirmation packet PROFIBUS_APS_SET_CONFIGURATION_PRM_CNF only
transfers simple status information, but does not repeat the whole parameter set.
For all former versions up to firmware version V2.0.12.1, only the warmstart command (the
predecessor of the set configuration command) was present showing up the following deviations
from the behavior described above:
3. For the first time the stack receives a warmstart/set configuration packet the stack will start
up automatically.
4. On every further received warmstart/set configuration packet the stack waits for a channelinit
to be performed until reconfiguration takes place.
5. Registration of the application at the protocol stack is also done automatically.
4.4 Process Data (Input and Output)
The input and output data area is divided into the following sections:
• Input and Output Data for PROFIBUS DP Slave
I/O Offset Area Length (Byte) Type
0x1000 Output block 244 Read/Write
0x2680 Input block 244 Read
Table 34: Input and Output Data for Remote Device Station with One Occupied Stations, Single Setting
For more information about the configuration of inputs and outputs refer to section Configuration of
Inputs and Outputs on page 55.
PROFIBUS-DP Slave | Protocol API
DOC050401API12EN | Revision 12 | English | 2012-01 | Released | Public © Hilscher, 2005-2012