Download Package Communication Solutions - 2024-06-1
Note:
Before getting started, please make sure that your system fulfills the system requirements listed in the user manual for your product and note the errata CIFX M22XX90XX and CIFX HPCIE90 Errata ERR 03 EN.pdf. The product documentation can be found on the download section at the end of this page.
If you feel unsure about any point, please get in touch with Hilscher's support team.
First Steps
- Install the software components mentioned below.
- Mount the Hilscher product into the system.
- Download a firmware into the Hilscher product via Device Explorer.
- Set up a network configuration with I/O data via Communication Studio.
- Download the configuration into the product and start the communication.
- Optional: Check data exchange with “cifXTest” utility, which is installed in the Windows Control Panel with the cifX Device Driver (NXDRV-WIN).
- Connect the application.
Software Installation
cifX Device Driver
Install the cifX Device Driver on your host system to gain access to the cifX card via PCI Express.
→ ...\Driver_&_Toolkit\Device Driver (NXDRV-WIN)\Installation\cifX Device Driver Setup.exe
Device Explorer
Install the Device Explorer to load a communication firmware into the cifX card.
→ …\Software_&_Tools\Configuration_Software\Device_Explorer…
Device Library
Install the Device Library which provides a collection of device and communication DTMs for the Configuration Software Communication Studio.
→ …\Software_&_Tools\Configuration_Software\Device_Library…
Communication Studio
Install the Communication Studio to set up a network configuration.
→ …\Software_&_Tools\Configuration_Software\CommunicationStudio…
Firmware
For full support with the Hilscher tool chain, the minimum firmware version listed on this Product Download Package has to be used. If a later version of a firmware is used from Hilscher Knowledge Base, the firmware type "Use Case C" has to be chosen in the download folder.
Documentation
Documentation for all hard- and software components included in this Product Download Package is available on the path: …\Documentation\...
The Documentation Library on the Hilscher Knowledgebase includes further documents: https://hilscher.atlassian.net/wiki/display/DL/Documentation+Library+Home
Application Notes
Application Notes, e.g. commissioning examples, are available in the Global Support Space: https://hilscher.atlassian.net/wiki/x/ue9RBw
Device Driver Windows (NXDRV-WIN)
Operating System | Windows XP | Windows Vista | Windows 7 (KB3033929) | Windows 8/8.1 | Windows 10 (Desktop / Secure Boot) | Windows 10 (Server) | Windows 11 | |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Driver Version | V1.0.0.0 | V1.0.0.0 | V1.0.0.0 | V1.2.3.0 | ≥ V1.3.0.0 (2018-03-1) | - / - | ≥ V2.8.0.0 | |||||
Architecture | x86 | x64 | x86 | x64 | x86 | x64 | x86 | x64 | x86 | x64 | x64 | x64 |
Status |
A one-off verification with a specific driver version was done. More information can be found under: FAQ: Does the driver run on Windows Server?
For other operting systems follow the link.
Device Explorer - Tool to load a communication firmware to a hardware target.
Operating System | Windows 7 | Windows 8 | Windows 8.1 | Windows 10 |
---|---|---|---|---|
Status |
Communication Studio - Tool to create a network configuration and to download to the device.
Operating System | Windows 8 | Windows 8.1 | Windows 10 |
---|---|---|---|
Status |
Device Library - Library with all Hilscher devices for the Communication Studio.
Operating System | Windows 8 | Windows 8.1 | Windows 10 |
---|---|---|---|
Status |
The documentation can be downloaded on the download section.
CC-Link | CANopen | DeviceNet | PROFIBUS-DP | CC-Link IE Field | CC-Link IE Field Basic | EtherCAT | EtherNet/IP | Modbus/TCP | POWERLINK | PROFINET IO | Sercos | VARAN | OPC UA Server * | MQTT* | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Slave | Slave | Master | Slave | Master | Slave | Master | Slave | Slave | Slave | Master | Adapter | Scanner | Client/Server | Controlled Node | Device | Controller | Slave | Master | Client | Server | Publisher/Subscriber | |
CIFX 50 | ||||||||||||||||||||||
CIFX 50E | ||||||||||||||||||||||
CIFX 70E | ||||||||||||||||||||||
CIFX 80 | ||||||||||||||||||||||
CIFX 90\F | ||||||||||||||||||||||
CIFX 90E\F | ||||||||||||||||||||||
CIFX 104 | ||||||||||||||||||||||
CIFX 104\F | ||||||||||||||||||||||
CIFX 104C | ||||||||||||||||||||||
CIFX 104C\F | ||||||||||||||||||||||
CIFX M3042100BM\F | ||||||||||||||||||||||
CIFX M223090AE | ||||||||||||||||||||||
CIFX M224290BM | ||||||||||||||||||||||
CIFX HPCIE90 |
*Available in combination with an Industrial Ethernet protocol. For more information see IoT Solution LFW - Hilscher Confluence (atlassian.net)
Systembus | Format | Communication Controller | USB Diagnostic | SYNC0/1 | Slave Adress Switch | 2-channel | Integrated NVRAM | Detached network interface | Extended Temperature Range | |
---|---|---|---|---|---|---|---|---|---|---|
CIFX 50 | PCI | - - - | netX 100 | 1) | 3) | |||||
CIFX 50E | PCI Express | - - - | netX 100 | 1) | 3) | |||||
CIFX 70 | Low Profile PCI Express | MD1 | netX 100 | 1) | ||||||
CIFX 80 | Compact PCI | 3U | netX 100 | 1) | ||||||
CIFX 90\F | Mini PCI | - - - | netX 100 | 1) | 4) | |||||
CIFX 90E\F | Mini PCI Express | - - - | netX 100 | 2) | 3) | 4) | ||||
CIFX 104 | PC/104 | - - - | netX 100 | 1) | ||||||
CIFX 104\F | PC/104 | - - - | netX 100 | 1) | 4) | |||||
CIFX 104C | PCI-104 | - - - | netX 100 | 1) | ||||||
CIFX 104C\F | PCI-104 | - - - | netX 100 | 1) | 4) | |||||
CIFX M3042100BM\F | M.2 PCI Express | M.2 3042 Key B+M | netX 100 | 2) | 4) | |||||
CIFX M223090AE | M.2 PCI Express | M.2 2230 Key A + E | netX 90 | 2) | 4) | |||||
CIFX M224290BM | M.2 PCI Express | M.2 2242 Key B + M | netX 90 | 2) | 4) | |||||
CIFX HPCIE90 | PCI Express halfsize | - - - | netX 90 | 2) | 4) |
Legend
1) SYNC0/1 via 3-pin connector
2) SYNC0/1 via system bus
3) For DP, CO and DN only
4) Using a Assembly Interface (AIFX) with a cable
CIFX netX100 support | CIFX netX90 support | Further Information can be found at ... | Note | |
---|---|---|---|---|
C-Toolkit | ||||
Windows | Device Driver Windows (NXDRV-WIN) | |||
Windows CE | Device Driver Windows CE (NXDRV-CE) | |||
Linux | ||||
INtime | Device Driver INtime (NXDRV-INtime) | |||
IntervalZero RTX® | Device Driver RTX (NXDRV-RTX) | |||
QNX | Device Driver QNX (NXDRV-QNX) | |||
WinAC | Device Driver WinAC (NXDRV-WinAC) | |||
InCoSol OPC DA Server | Third party OPC DA Server provided by InCoSol GmbH | |||
CODESYS | https://www.codesys.com/products/codesys-fieldbus/industrial-ethernet/profinet.html | Third party device driver and configuator provided by the CODESYS Group |
CC-Link | CANopen | DeviceNET | PROFIBUS-DP | CC-Link IE Field | CC-Link IE Field Basic | EtherCAT | EtherNet/IP | Modbus/TCP | POWERLINK | PROFINET IO | Sercos | VARAN | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Master | Slave | Master | Slave | Master | Slave | Master | Slave | Master | Slave | Master | Slave | Master | Slave | Scanner | Adapter | Client/Server | Managing Node | Controlled Node | Controller | Device | Master | Slave | Manager | Client | |
COMX 52CA 1) | |||||||||||||||||||||||||
COMX 52CN 2) | |||||||||||||||||||||||||
COMX 51CA 1) & 4) | |||||||||||||||||||||||||
COMX 51CN 2) | |||||||||||||||||||||||||
COMX 100CA 1) | |||||||||||||||||||||||||
COMX 100CN 2) |
Legend
1) With protocol-specific fieldbus connector on board.
2) Fieldbus interface via pin strip to the base board. Fieldbus connector needs to be implemented on the base board.
3) comX 52 is a compatilble drop-in replacement of comX 10 for fieldbus slave only
4) Special EtherCAT Slave with Rotary Switches acc. to ETG.5003-1
Host interface | Diagnostic interface | SYNC0/1 | Slave | Integrated 1) Webserver (servX) | Raw Ethernet (NDIS)6) | TCP socket interface 6) | ||||
---|---|---|---|---|---|---|---|---|---|---|
SPM | DPM | USB | UART | |||||||
CC-Link Slave | COMX 52Cx-CCS | |||||||||
CANopen Slave | COMX 52Cx-COS | |||||||||
DeviceNET Slave | COMX 52Cx-DNS | |||||||||
PROFIBUS-DP Slave | COMX 52Cx-DPS | |||||||||
EtherCAT Slave | COMX 51Cx-RE | 2) | ||||||||
EtherNet/IP Adapter | COMX 51Cx-RE | 3) | 5) | |||||||
Modbus/TCP Client/Server | COMX 51Cx-RE | |||||||||
POWERLINK Controlled Node | COMX 51Cx-RE | |||||||||
PROFINET IO Device | COMX 51Cx-RE | 3) | 5) | |||||||
Sercos Slave | COMX 51Cx-RE | |||||||||
EtherCAT Master | COMX 100Cx-RE | |||||||||
EtherCAT Slave | COMX 100Cx-RE | |||||||||
EtherNet/IP Scanner | COMX 100Cx-RE | |||||||||
EtherNet/IP Adapter | COMX 100Cx-RE | |||||||||
Modbus/TCP Client/Server | COMX 100Cx-RE | |||||||||
POWERLINK Controlled Node | COMX 100Cx-RE | |||||||||
PROFINET IO Controller | COMX 100Cx-RE | |||||||||
PROFINET IO Device | COMX 100Cx-RE | |||||||||
Sercos Master | COMX 100Cx-RE | |||||||||
Sercos Slave | COMX 100Cx-RE | |||||||||
VARAN Client | COMX 100Cx-RE |
Legend
1) If supported, the integrated WebServer is activated as default. Can be deactivated via Firmware TAG-List.
2) Instead of NDIS EtherCAT supports EoE
3) The NDIS functionality is deactivated as default, but can be activated via Firmware TAG-List.
Real-Time Ethernet will be offered to the host in Channel 0, NDIS and TCP socket in channel 1 and in IoT communication in channel 2.
Channel 1 (NDIS and TCP socket interface) and Channel 2 (IOT communication) can only be accessed in SPM host interface mode. In DPM host interface mode only Channel 0 (RTE) can physically be adressed
4) LWIP TCP stack is used, which has a different API (socket API) than the Hilscher TCP stack.
5) Hilscher TCP stack is used, which has a different API (HIL TCP API) than LWIP TCP stack.
6) NDIS and TCP socket interface can only be accessed in SPM host interface mode, because only Channel 0 can be physically adressed in DPM mode.
Host interface | CANopen | DeviceNet | PROFIBUS-DP | EtherCAT | EtherNet/IP | Modbus/TCP | POWERLINK | PROFINET IO | Sercos | VARAN | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SPM | DPM | PCIe | Master | Slave | Master | Slave | Master | Slave | Master | Slave | Scanner | Adapter | Client/Server | Managing Node | Controlled Node | Controller | Device | Master | Slave | Manager | Client | |
NJ 52D 1) | ||||||||||||||||||||||
NJ 51D 1) | ||||||||||||||||||||||
NJ 100DN 1) | ||||||||||||||||||||||
NJ 100EN 2) |
Legend
1) Host interface: Dual-port memory
2) Host Interface: PCI Express
Diagnostic interface | SYNC0/1 | Slave | Integrated 1) Webserver (servX) | Raw Ethernet (NDIS)6) | TCP socket interface 6) | |||
---|---|---|---|---|---|---|---|---|
USB | UART | |||||||
CANopen Slave | NJ 52x-COS | |||||||
DeviceNET Slave | NJ 52x-DNS | |||||||
PROFIBUS-DP Slave | NJ 52x-DPS | |||||||
EtherCAT Slave | NJ 51x-RE | |||||||
EtherNet/IP Adapter | NJ 51x-RE | 3) | 5) | |||||
Modbus/TCP Client/Server | NJ 51x-RE | |||||||
POWERLINK Controlled Node | NJ 51x-RE | |||||||
PROFINET IO Device | NJ 51x-RE | 3) | 5) | |||||
Sercos Slave | NJ 51x-RE | |||||||
EtherCAT Master | NJ 100x-RE | |||||||
EtherCAT Slave | NJ 100x-RE | |||||||
EtherNet/IP Scanner | NJ 100x-RE | |||||||
EtherNet/IP Adapter | NJ 100x-RE | |||||||
Modbus/TCP Client/Server | NJ 100x-RE | |||||||
POWERLINK Controlled Node | NJ 100x-RE | |||||||
PROFINET IO Controller | NJ 100x-RE | |||||||
PROFINET IO Device | NJ 100x-RE | |||||||
Sercos Master | NJ 100x-RE | |||||||
Sercos Slave | NJ 100x-RE | |||||||
VARAN Client | NJ 100x-RE |
Legend
1) If supported, the integrated WebServer is activated by default and can be deactivated via firmware TAG list.
2) Instead of NDIS EtherCAT supports EoE
3) The NDIS functionality is deactivated as default, but can be activated via Firmware TAG-List.
Real-Time Ethernet will be offered to the host in Channel 0, NDIS and TCP socket in channel 1 and in IoT communication in channel 2.
Channel 1 (NDIS and TCP socket interface) and Channel 2 (IOT communication) can only be accessed in SPM host interface mode. In DPM host interface mode only Channel 0 (RTE) can physically be adressed
4) LWIP TCP stack is used, which has a different API (socket API) than the Hilscher TCP stack.
5) Hilscher TCP stack is used, which has a different API (HIL TCP API) than LWIP TCP stack.
6) NDIS and TCP socket interface can only be accessed in SPM host interface mode, because only Channel 0 can be physically adressed in DPM mode.
If you have problems unzipping the files, please use a tool like 7-ZIP.
Return to overview page ...