Create a new Project

• Open Hilscher Sycon.net

Add Devices

• On the right side of the netDevice Window, the device catalogue can be accessed.

Add Profinet IO Controller

• select "PROFINET IO → Master → CIFX RE/PNM V3" (if there is an older Firmwareversion in use, use CIFX RE/PNM) and drag and drop it to the grey Bus-line.
  

Add netField Device

Import netFIELD Device Description File

• Import the GSDML, provided for the netField devices by selecting Options → "Network → Import Device Description"

• select the correct protocol and open the GSDML File

• The Device catalog will now be reloaded. After that, the device is available as Profinet IO "Slave" in the Device catalog.

Insert netFIELD Device

• select "PROFINET IO → Slave → netFIELD", in the device catalog and drag and drop it to the Green PROFINET line.

• If the device is not shown in the device catalogue, select "Network → Device Catalog..." and click "Reload Catalog" or completely restart Sycon.net.

PROFINET IO Device Settings

Add Modules to netFIELD Device

• Double-click the netFIELD Device in the netDevice window to open Configuration window.
  In the Navigation Area, select "Modules".
  
  
• Add one module and and select "8-Bit IO Link Master", to the Device Module List (Slot 1).

• Replace Submodule 2 with "IOL-Display IFM E30391".

• The Submodule Details, show the I/O data provided by the IO Link Dveice IFM E30391.
  It is always displayed from the perspective of the IO Controller, which means that the shown OUTPUT data, are INPUT data in the perspective of the IO Device.
  
  
• save your settings with "Apply" and close the window with "OK".
  

PROFINET IO Controller settings

• Double-click to the CIFX PROFINET IO Controller, to open the CIFX PNM Configuration.

Device Assignment

• open "Driver" in the Navigation Area and select "CIFX Device Driver".
  
  

• now open the Device assignment, and scan for devices.
  Select the CIFX Device, to be configured.

• Save your selection with "Apply".

Licensening

• When using the CIFX Card as an PROFINET IO Controller, a Master license is needed.
  In the Navigation Area, open "Licensing", to check is a Master license is available on the CIFX Card.

Set IO Controller IP-Adress

• In the Navigation Area "Confiruation → Controller Network Settings", the IP Adress for the IO Controller can be set.
  All Slaves need to be set to the same Subnet.

Define netFIELD IO Device Name of Station (Devicename)

• Open in the Navigation Area "Configuration → Device Table.
  The Device table shows all Slaves, added to the Profinet line.
  
  
• In the Device table the name of Station for each device can be changed. Make sure, it is the same assigned to the Device.
  The default Name of Station for netFIELD Device is always "netfield" but can be changed using a DCP Tool (for example the Ethernet Device Configuration Tool).
  The name defined in the IO Controller Settings, always need to fit the Devices configuration.

Define netFIELD IP-Address

• Since in PROFINET the IP-Addess of all slaves are defined at communication startup by the IO Controller, the IP-Address of the IO Device need to be configured in the IP Address Table of the IO Controller.
  
  
• Therefore open in the Navigation Area "Configuration → IP Address Table" and set the IP Address, which should be assigned to teh netFIELD IO Device.

Address Table

• The Adress table shows on which Address on the Process image of the CIFX Card, which part of the configured IO Data can be found.
  Therefore it is needed to indicate where to write through the netFIELD Device to the IO Link Device (IFM Display).
  
  
• The Table shows, that the Input Process data of the IFM Display, will be available at Offset 8 (perspective of IO Controller)
  It also shows, that the Output Process data for the IO Link IFM Display, start at Offset 8.

• Provider and Consumer Status, indicates the IOCS/IOPS which need to be handled.
  Please find a more detailed Application Note, concerning the Status Byte handlung, here:
  Profinet-V3 - IOCS / IOPS [EN]

Download configuration to CIFX IO Controller

• After the configuration has been finished, it only needs to be downloaded to the CIFX Card.
  Therefore select the right-click to the CIFX IO Controller in the "netDevice" view and select "Download".

• Accept the upcoming window:

• 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.

• In this state, only the diagnosis can be accessed.
  To change the configuration, it needs to be disconnected again:

Diagnosis

• Right-click to the CIFX Card and select "Diagnosis".

• The Diagnosis shows geneal informations about the current communication.
  
  
• In case of a running communication, the CIFX Status LEDs show the following:

SYS

SF

BF

• This is how the diagnosis should look like, in case of a working communication to netFIELD Device:

• The Station Diagnosis shows the following:

• 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

Testcase: IO Link IFM Module removed

• In case the IO Link Module has been removed from the netFIELD Device, the CIFX Status LEDs now show the following:

SYS

 SF

BF

• This status means the following:

• The Station Diagnosis also indicates an upcoming diagnosis from the netFIELD Device:

The Communication State, indicates a configuration mismatch:

Diagnostic Tools

Packet Monitor

The Packet Monitor is used to send and receive acyclic datapackets.

IO Monitor

The IO Monitor is used to send and receive IO Data, to check the current communication.

It does only work, if a communication is already successfully established.

To send data to the IO IO Device, enter the output data to be sent into the "Output Data" area and click "Update".

At the opposite device, the corresponding data is being received now.

The Field "Output data", shows the data sent by the IO Device to the IO Controller.