Cifx Device Driver
Dorthea Seate
i have installed a mPCI Card from Hilscher in to a SBC. As written in the documentation the 3S driver has to be installed but in the directory $\GatewayPLC\Driver\x64 the driver is not existing. Only in the Directory $\GatewayPLC\Driver is the SysDrv3S.sys Driver available. When i try to install the driver, i get a message "the Install class is not present or is invalid".
I am having this issue as well with my Hilscher-cifX PCI device. I am trying to install the SysDrv3S driver onto it using the method described above. Device Manager -> cifX Communication Interface -> Update Driver -> ... Have disk... and I get the "The Install class is not supported or Invalid" message.
Hello, does someone have an update of this Issue ? I have the same problem. I use Codesys RTE V3.5.11.40 and want to install the Codesys Driver of the CIFX50E-DP under: C:\Program Files\CODESYS\CODESYS Control RTE3\SysDrv3S\SysDrv3S.inf, but become the same message "The Install class is not supported or Invalid". Did someone solve this issue ?
Time ago I did this with Codesys RTE V3.5.18.0 and had not problem.
I got it !!! Thanks the advice of a Codesys colleague. We have to install the old driver from RTE 3.5 SP17 and then the new one.
So...I downgraded my Codesys Control RTE from V3.5.18.40 to RTE 3.5 SP17. So I took the Codesys RTE V3.5.17.30 (unpacked) from the website: -control-rte-sl-bundle.html. For this I uninstalled before the whole Codesys V3.5.18.40 from control panel->programs->programs and features. I also uninstalled the driver and software of Hilscher (Sycon.net, Hilscher Driver), but before uninstalling the Hilscher Software, I put the Hilscher licence on the CIFX50E-DP card with the Sycon.net tool, in order that the CIFX50E-DP works as a Profibus Master. But this is specific for my project.
So...after installing Codessys RTE V3.5.17.30, I installed the old driver from : C:\Program Files\CODESYS\CODESYS Control RTE3\SysDrv3S\SysDrv3S.inf (right click -> install). Then I opened the device manager and had to install also the driver in the device manager (Device Manager -> cifX Communication Interface -> Update Driver).
Then I unistalled codesys RTE V3.5.17.30 (from Control panel) and installed the last version Codesys RTE V3.5.18.40. Then I installed the new driver from C:\Program Files\CODESYS\CODESYS Control RTE3\SysDrv3S\SysDrv3S.inf and also in the device manager. It works !!
To work with a Hilscher device make sure that you have the recommended driver installed, newest SYCON.net, and firmware prepared. Profinet requirements are written down in Hilscher_Channel_Open_Profinet documentation.
The easiest way to install firmware to the cifX Driver is using the cifX Driver Setup software - the Windows Search in the start menu should find this tool, otherwise it is located in C:\Program Files\ cifX Device Driver directory. In the cifX Driver Setup Utility select the channel you want to configure (usually channel 0 - CH#0) and remove preexisting firmware by clicking "Clear". To add a new firmware file click "Add", navigate to the downloaded profinet slave firmware and click "Open". Finally, click "Apply" - the button should turn disabled.
Channel configuration files are generated in SYCON.net software. Firstly, pick a proper slave device using a PCI card, here we use the Profinet Stand-Alone Slave, and drag it to the gray bus on the "Network View".
To open card configuration, double click on its icon and select the "Configuration/Modules" category in the Navigation Area on the left side of the dialog. In the main window you can add individual modules. Remember that in Profinet, Slot configuration must match the configuration from your master device, otherwise the connection will not work. For boolean indicators we recommend "1 Byte Output" or "1 Byte Input".
You can see the final address table (addresses on the Hilscher device where input or output data will be available) in the "Configuration/Address table" category. If you plan to use IORead and IOWrite filters, for example Hilscher_Channel_IORead_SInt8, note the addresses. You can switch the display mode to decimal, as Aurora Vision Studio accepts decimal addressing, not hexadecimal. Aurora Vision Studio implementation of Profinet checks whether the address and data size match. In the sample configuration below, writing a byte to address 0x002 would not work, because that module address starts at 0x001 and spans 2 bytes. Moreover, Aurora Vision Studio prohibits writing with a SlotWrite filter to input areas, and reading with a SlotRead filter from output areas. Click "OK" when you have finished the proper configuration.
The final step is to generate configuration files for Aurora Vision Studio. You can to this by right clicking on the device icon, then navigating to "Additional Functions->Export->DBM/nxd...", entering your configuration name and clicking "Save". You can now close SYCON.net for this example, remember to save your project before, so that it is easier to add new slots.
At the beginning of every program where you want to use filters intended for communication over a Hilscher card you need to add Hilscher_Channel_Open_Profinet filter. The configuration files generated in the previous step are now required in inConfig (xxx.nxd) and inNwid (xxx_nwid.nxd) properties of that filter. These files are used when there is no connection between a card and a Profinet master. In that case Aurora Vision Studio updates the card configuration and starts the communication. For IO, we recommend SlotRead and SlotWrite filters, as they are more convenient. For example, the Hilscher_Channel_SlotWrite_SInt8 filter writes 8 bytes of signed data to the selected slot. Slot numbers match those in the "Configuration/Modules" category of card configuration in SYCON.net program.
The protocol stack is executed autonomously on the PC card and process data exchange with the host is done via Dual-Port-Memory or DMA (Direct Memory Access). Thanks to the common Hilscher Platform Strategy all PC cards use the same driver and tools - independent of protocol and card format. Thanks to the netX technology there is exactly one hardware needed for the realization of all Real-Time Ethernet protocols. A change of the communication protocol is done by just loading a different firmware.
The PC based automation is evolving and the Hilscher cifX PC card family keeps the pace. With continuous expansion for new standards, protocols and formats, as M.2, mini PCIe halfsize or CC-Link IE Field, customers are always prepared for new market demands.
I agree Our site saves small pieces of text information (cookies) on your device in order to deliver better content and for statistical purposes. You can disable the usage of cookies by changing the settings of your browser. By browsing our website without changing the browser settings you grant us permission to store that information on your device.
When you operate the Hilscher card with the CODESYS Control RTE V3 runtime system, then you must not use the supplied Hilscher driver for the network adapter. If you use CODESYS Control RTE V3 with NetX, then you need to install SysDrv3s.sys (SysDrv3S subdirectory) which is supplied with the RTE installation package.
BootloaderFilePath: File path and file names of the NetX boot loader for each NetX controller. A relative path starts in the installation directory. An absolute path can also be used. If you are using more than one NetX controller, then you need to specify more than one file path.
Device.X.Channel.X.FirmwareFile: File path and file names of the NetX firmware for each adapter and each channel. A relative path starts in the installation directory. An absolute path can also be used. Only "Channel 0" is used most of all. If you are using more than one NetX chip, then you need to specify more than one file path.
As soon as the runtime system is running, entries for CmpHilscherCIFX appear in the runtime system logger. You see the entries in the Log dialog of the device editor in CODESYS, as well as in the LogPLCxx.csv file in the CODESYS Control RTE V3 directory.
Open the configuration dialog for the fieldbus master by double-clicking the entry in the device tree. Switch to the NetX Configuration tab. Set the values of Slot and NetX com channel so that they are identical to the device numbers in the configuration file CODESYSControl.cfg. Compare the values with the logger entries of the runtime system.
Open the configuration editor of the PLC (the Communication Settings are also found in this editor), switch to the Log tab, and click the green arrow. CODESYS loads and displays all logger entries from the PLC. Then you can search for errors and exceptions.
If unresolved references are present in the application, then the runtime system component is not loaded or an incorrect version is loaded. Check the CODESYS logger. The CmpHilscherCIFX component has to have been loaded.
This means that the runtime does not find the NetX adapter or chip. Check that the adapter is inserted correctly and the corresponding driver is installed. For more information, see above: Installing the Windows driver.
The CODESYS Group is the manufacturer of CODESYS, the leading hardware-independent IEC 61131-3 automation software for developing and engineering controller applications.
CODESYS is a registered trademark.
The 30 x 22mm card enables IPCs, HMIs, and robotics systems to support Real-Time Ethernet and Fieldbus networks. The product includes all necessary hardware and software components, including protocol stacks, device drivers and network connectors, says Hilscher.
The cifX M.2 is equipped with the same dual Cortex-M4 based netX 90 multiprotocol communication chip found on other Hilscher cifX cards (PDF), which are available in mini-PCIe, PCIe, PCI, cPCI, and PC/104 form factors. It also supports the same protocols and application interfaces.
The cifX M.2 cards are available in five preconfigured models for EtherCAT-Slave (EtherCAT-Secondary), EtherNet, PROFINET, PROFIBUS, and Open ModBus/TCP. Each is available with an external card that includes dual Real-Time Ethernet ports.