| Table of Contents |
|---|
...
select the PROFIBUS Slave from the list of Stand-Alone-Slaves.
When Configuring a CIFX M223090AE Device, please select "CIFX DP/DPS V2.10".
the device will now be added to the network in the Solution Explorer. Several configuration options are now available:
Device Assignment
...
Scan for devices and select the Device to be configured.
PROFIBUS Settings
Station Address
Open the PROFINET Settings → Network, to define the Station Address, which is needed for the Master to establish a communication.
The Station Address has to be equal to the one defined in the Master Configuration.
Module Configuration
Open the Module configuration and add the needed Modules with a doubleclick on them or using the "Insert" or "Append" buttons.
...
After the configuration is finished, Download the configuration by selecting the Device in the Solution Explorer and clicking "Download" or right-click to the device and select "Download".
After the Download is finished, the Device will now automatically "Connect", which is indicated by a green background. This means, the Diagnosis is now available.
Diagnosis
Mark the current Device and click "Diagnostic", or right-click to the device and select "Diagnostic" to open the diagnosis.
The Diagnosis shows geneal informations about the current communication.
This is how the diagnosis should look like, in case of a working communication to a PROFIBUS Master:
The field "Communication error", gives information about the current communication state.
All Error Codes can be found in the following document: https://kb.hilscher.com/display/DL/Hilscher+status+and+error+codes
Establish communication
At startup the PROFIBUS-DP Slave will not start the cyclic data exchange with the PROFIBUS-DP Master until the first Input data are updated from the application to the stack.
As long the first update of the Input data is not done by the application the stack will generate a so called static diagnostic to the master.
This will be shown in the General Diagnosis as follows:
As soon the first Input data are written the normal data exchange will start.
This is for safety reason to make sure that the very first Input data transferred from the slave to the master are valid data from the application.
To simulate the first Input data update from the application to the stack, the IO Monitor in Communication Studio can be used.
Therefore open the IO Monitor in the Diagnosis and click "update":
In the General Diagnosis, the Communication will now be started:
Diagnostic Tools
Packet Monitor
...