You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
The figure provides an overview and shows the system layers and the accompanying documentation.
Please select the type of application that you want to create. Then select the type of driver that you want to use.
Application
Application to access the cyclic I/O data (Basic)
The application programm needs access to the cyclic I/O data. Configure the device using a configuration software e.g. SYCON.net.
| The cifX API is the interface used by the application program. The manual contains a target and fieldbus independent programming interface to netX-based hardware running a standard Hilscher fieldbus protocol or firmware. | |
Application to set parameter, access the cyclic I/O data and reading status information (Advanced)
The application programm needs access to the cyclic I/O data and to status information of the device or network.
| The cifX API is the interface used by the application program. The manual contains a target and fieldbus independent programming interface to netX-based hardware running a standard Hilscher fieldbus protocol or firmware. | |
| The dual-port memory interface manual describes the structure, definitions and functions of the dual-port memory. | |
| If you are using a master device then configure the device using a configuration software e.g. SYCON.net. The Protocol API manual describes the fieldbus-specific programming interface. There are several manuals, one for each protocol. | |
If you are using a slave device then you can configure the device from you application program. The Protocol API manual describes the fieldbus-specific programming interface. There are several manuals, one for each protocol. | |
Application to use the full functionality (Expert)
The application programm needs access to the cyclic I/O data and to status information of the device or network. Additionally, the application programm wants to use e.g. acyclic services, wants to do object handling or wants to configure the master device.
| The cifX API is the interface used by the application program. The manual contains a target and fieldbus independent programming interface to netX-based hardware running a standard Hilscher fieldbus protocol or firmware. | |
| The dual-port memory interface manual describes the structure, definitions and functions of the dual-port memory. | |
If you are using a master device then configure the device using a configuration software e.g. SYCON.net or configure the master device by your application program. The Protocol API manual describes the fieldbus-specific programming interface. There are several manuals, one for each protocol. | |
| If you are using a slave device then you can configure the device from you application program. The Protocol API manual describes the fieldbus-specific programming interface. There are several manuals, one for each protocol. | |
Driver
Driver for standard operating system
You are using a one of the following operating systems:
Windows | |
Linux | |
QNX | |
VxWorks | |
Windows CE | |
Third party driver
If you are using INtime or RTX:
Own driver development based on toolkit
You are using an approriate operating system or you want to access to the serial dual-port memory. Then you can use our driver toolkit for this purpose.
The cifX/netX Toolkit provides C-source and header files allowing abstract access to the dualport memory (DPM) defined by Hilscher for cifX and comX devices and netX-based components. | |
| The cifX API is the interface used by the application program. The manual contains a target and fieldbus independent programming interface to netX-based hardware running a standard Hilscher fieldbus protocol or firmware. | |