What is the difference between netHOST and CIFX [EN]

The Hilscher netHOST Device is used to replace a CIFX Card, which requires a PCI or PCIE Slot.

It ts therefore ideal for the implementaton in networks or laptops.

A netHOST FB is a full-featured and autonomously operating Fieldbus master allowing industrial PCs and other embedded systems the control of Fieldbus networks over an ordinary LAN connection.

A simple TCP/IP based transport protocol transfers the services between the controlling unit and the device.

For device integration a DLL for Windows and a ‚C‘ source code for embedded solutions is provided.

In both cases the call interface (API) is identical to Hilschers PC cards. This makes a netHOST a „remotely controllable PC card for field installations“.

Nevertheless, there are some differences betweeen netHOST and CIFX Cards, that have to be considered.

Main differences

Different conditions that an Ethernet connection brings with it compared to the PCI interface should be considered. For example longer response times and missing real-time properties.

The behavior with regard to transmission and response times is not as reproducible as via the PCI bus. The cycle time of the application can also be subject to major fluctuations.

There should be no difference on the fieldbus side.

Migration of an CIFX Application to netHOST

a few adjustments need be de done to migrate a CIFX application to netHOST:

1. Rename the netXTransport.dll to CifX32DLL.dll and replace the old CifX32DLL.dll with it.

Please find more informations about the netXTransport.dll here: https://kb.hilscher.com/display/CIFXDRV/netX+Diagnostic+and+Remote+Access

2. Add the PlugIn directory of the netX driver into your application folder. There are all the needed connectors for USB and TCP connection.

The folder can be located in the netHOST DVD: "...\netHOST Solutions\Setups & Drivers\netHOST Test"

The newest DVD is available here: https://www.hilscher.com/de/support/downloads/

3. The name of the netHOST is different in you application.

Instead of "cifx0" it is now "TCP0_cifx0" The name has to be changed in every function that needs it, f.e. "xChannelOpen()"

4. Only when using a fieldbus protocol instead of a realtime ethernet protocol, the Channelnumber needs to be changed from Ch0 to Ch1.

5. Initialise the driver and configure the connectors. (netX Diagnostic and Remote Access - Host Device PR 03 EN.pdf)

6. The application has to be newly compiled