| Table of Contents |
|---|
...
Please follow the installation instructions in our "Getting Started"-Application Note, if you have not done yet:
https://kbhilscher.hilscheratlassian.comnet/wiki/pages/viewpage.action?pageId=121244280=122810308
This Commissioning Guide is also available on Youtube:
| Widget Connector | ||
|---|---|---|
|
Firmware Download
Since the CIFX M223090AE can be used for several communication protocols, a fitting Firmware for PROFIBUS Slave needs to be downloaded first.
...
fitting firmware can be found either on the ComSol_90_4x00 DVD or on our Knowledge Base:
https://kbhilscher.hilscheratlassian.comnet/wiki/display/HILKB/Technologies
After adding the Firmware, it can now be selected in the "Firmware" Area.
Please select the device and the firmware you want to download. In this example, please choose the Firmware "PROFIBUS Slave":
...
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:
...
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.
...
The field "Communication error", gives information about the current communication state.
All Error Codes can be found in the following document: https://kbhilscher.hilscheratlassian.comnet/wiki/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
...