Datasheet

Fig Export the configuration
This will create a configuration file, in some cases two files, that should be copied to the process
station.
cifX driver configuration
The Linux cifX driver should be installed on the process station. Follow the instructions to build
and load the driver.
A directory tree for the driver configuration should be created under opt/cifx.
On /opt/cifx the bootloader, eg NETX100-BSL.bin, should be placed. Under /opt/cifx/deviceconfig
one directory for each card is created, with the serial number as directory name, and under this a
directory with the device number and serial number, eg /opt/cifx/deviceconfig/1250100/22219. On
this directory a file, device.conf is created. This should contain an alias, that is the identification of
the card in the Proivew configuration. The alias has to correspond to the Alias attribute in the
Hilscher_cifX_Master object.
An example of device.conf:
alias=PROFINET
irq=yes
This directory also contains a sub directory, channel0, where the firmware for the board is placed,
together with the configuration files generated from SYCON.net. In the example below
cifXpnm.nxf is the firmware for the Profinet controller, and config.nxd and nwid.nxd exported from
the SYCON.net configuration
> ls /opt/cifx/deviceconfig/1250100/22219/channel0
cifXpnm.nxf
config.nxd
nwid.nxd
Proview configuration
The Proview I/O configuration uses the Hilscher_cifX_Master, Hilscher_cifX_Device and
Hilscher_cifX_Module objects, which represents the agent, rack and card levels.
Place a Hilscher_cifX_Master object in the node hierarchy under the $Node object. Set the Alias
attribute to the same alias as in the device.conf file for the board in the driver configuration. Set also
the correct Process and ThreadObject.
Below the master object, a Hilscher_cifX_Device object is created for each device/slave on the bus,
and below this, a Hilscher_cifX_Module object for each module on the device/slave. The input and
output areas for the modules are configured with channel objects. Create the correct type of input
and output channels, and set representation to match the structure of the areas. Read more about this
in Specify the data area in the Profibus section above.
The data areas are read from, and written to, a double ported memory on the cifX board. It is
important that the slave and module order, as well as the channel specification, matches the
SYCON.net configuration, so that the areas for each module can be read and written on the correct
offset in the double ported memory. The offset and size for each device and module are calculated
at runtime, and stored in the device and module objects. These offsets and sizes can be compared
with the SYCON configuration.