Getting Started - Commissioning NetX Adapters

If you want to use a NetX adapter with a CODESYS runtime system, then you must install the following drivers:

• For CODESYS Control Win V3: Driver SysDrv3s.sys

• For CODESYS Control RTE V3: Driver RTIOwdmGenericc.sys or SysDrv3s.sys

  Note: The installed driver must be passive. When using CODESYS Control RTE V3, it is also possible to install no specific driver at all.

The NetX firmware and the NetX boot loader are located in the HilscherCIFX folder for both runtime systems.

The NetX Second Stage Boot Loader and the NetX firmware are reloaded to the NetX chip each time the runtime system is started.

1. Open the file CODESYSControl.cfg of the respective runtime system directory in a text editor.

2. Remove the semicolon in the section [ComponentManager] at the beginning of the entry CmpHilscherCIFX so that the entry is no longer commented out.

3. In the area [CmpHilscherCIFX], follow the steps below to edit the entries for the NetX adapter and the NetX configuration.

   The following entries must exist for the firmware and boot loader:

   DynamicFirmware=1

   BootloaderFile=./HilscherCIFX/Firmware/NETX100-BSL.bin

   FirmwareFilePath=./HilscherCIFX/Firmware

4. If the entry DMAMode=1 is commented out, then remove the semicolon (;) at the beginning of the line.

5. Remove the semicolon in front of the following entries:

   Device.0.BootloaderFilePath=.\\HilscherCIFX\\Firmware\\NETX100-BSL.bin

   Device.0.Channel.0.FirmwareFile=.\\.\\HilscherCIFX\\Firmware\\cifxcom.nxf

   Description:

   • Device.X.BootloaderFilePath: Specifies the file path and the file name of the NetX boot loader for each NetX chip. (The relative path starts in the installation folder. Absolute paths are also possible.) If multiple NetX chips are used, the multiple files paths must also be specified:

     Device.0.BootloaderFilePath=.\\HilscherCIFX\\Firmware\\NETX100-BSL.bin

     Device.1.BootloaderFilePath=.\\HilscherCIFX\\Firmware\\NETX100-BSL.bin

   • Device.X.Channel.X.FirmwareFile: Specifies the file path and the file name of the NetX firmware for each NetX chip and each channel. (The relative path starts in the installation folder. Absolute paths are also possible.) In most cases, only channel 0 is used. If multiple NetX chips are used, the multiple files paths must also be specified:

     Device.0.Channel.0.FirmwareFile=.\\HilscherCIFX\\Firmware\\cifxcom.nxf

     Device.1.Channel.0.FirmwareFile=.\\HilscherCIFX\\Firmware\\cifxcom.nxf

6. If you want to receive more comprehensive logger messages from your controller (device editor of the controller, Log tab), then remove the semicolon (;) at the following locations: in the area [CmpHilscherCIFX] before the entry TraceLevel=0xffffffff, and in the area [CmpLog] before the entries:

   Logger.0.Name=PlcLog

   Logger.0.Filter=0xFFFFFFFF

7. Save the file CODESYSControl.cfg.

1. Create a new standard project in CODESYS by clicking File ‣ New Project . In the New Project dialog, select the Standard project template.

2. In Standard Dialog, select the controller (example: CODESYS Control Win V3) and click OK.

   ⇒ The new standard project is displayed in the device tree.

3. Click Add Device in the context menu of the controller.

4. In the Add Device dialog of Profibus ‣ DP Master , select a NetX fieldbus master (example: CIFX-PB) and click Add Device.

5. Double-click the NetX fieldbus master in the device tree (example: CIFX-PB) and select the NetX Configuration tab in the editor.

6. Select Slot 0 from the Slot drop-down list and NetXComChannel0 from NetX com channel .

   Caution: The number of the selected slot (example: Slot 0) must correspond to the number of the device in the file CODESYSControl.cfg (example: Device.0). Likewise, the number of the selected NetX com channel (example: NetX com channel 0) must correspond to the entries in the file CODESYSControl.cfg (example: Channel.0).

7. Build the project, log into the controller, and start the application by clicking Debug ‣ Start .

   ⇒

   

   If there are no error messages, then the NetX adapter has been configured correctly and you can now continue developing the project.

See also

• Profibus DP Master - 'NetX Configuration'

• PROFIBUS DP Slave Device - 'NetX Configuration'