On top, a wide range of device drivers and a C-Toolkit, free of charge, are available. 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. The 'device class' (e.g. CIFX) and the 'hardware options' defining available hardware connections and to download a firmware and a configuration later on. Have a look into the 'netX DPM Interface Manual' Rev.12 Page about standard card information located in the 'System Information Block'. If the device-specific driver is distributed through Windows Update, you can manually update the driver by using Device Manager. For more information about how to do this, see update drivers in Windows 10. If the device is not yet connected, first install the device-specific driver, such as by using the appropriate installer. However, there are many peoples said they can’t find ports in Device Manager and they desperately need a solution to it. COM Ports Not Showing in Device Manager: Ture Cases. One: Com Port is Missing / Ports Option Not Available In Device Manager. My com port is missing. And the ports option is not available in Device Manager. In addition, Hilscher also offers a free of charge cifX Toolkit (C-source code based) which allows to write own drivers based on the Hilscher netX DPM definitions including the CIFX API functions (the toolkit is described in a separate cifX/netX Toolkit manual, see NXDRV-TKIT).
Contact us
Customer Center (Delivery dates/Price information)
Individual consultation
A complete List of our contact data is available here.CIF Device Driver | DRV | Hilscher.com
Most operating systems require a device driver to integrate hardware components. Hilscher CIFX/COMX components require such device drivers as well. Hilscher offers a series of device drivers for a wide variety of operating systems. All Hilscher drivers have a standard user interface (CIFX-API) and are based on a C toolkit also usable for independent device driver development. The drivers are fully responsible for managing the communication components, including loading firmware and configuration files. The user interface contains all of the functions needed to initialize, parametrize, exchange I/0 data and acquire status information. Depending on the operating system, the user interface is contained in a DLL or library. As far as possible, the drivers support existing bus connections such as ISA, PCI, PCIe and dual-port memory connections. The C toolkit, and therefore the basis of the driver code, is designed in such a way that an unlimited number of communication components can be used simultaneously. However, the specific characteristics of each operating system must be taken into account.