...
All Hilscher netX based devices processing a Hilscher standard firmware, performing in the same way.
The DPM Layout
The DPM structure is a representation of the hardware functions and places the functions and corresponding information into separate, independent, areas.
...
Source Files: Comming with the driver
cifXUser.h
cifXErrors.h
...
Development Environment
The following picture gives an overview of the possible development environments and the migration to embedded systems.
This should help to choose a programming level fit best to the application needs.
Additional Resources
...
The CIFX API is the general application programming interface (API) which offers all necessary function to handle a netX device.
The API offers general handling functions and functions corresponding to the DPM components described above.
Example API functions:
Asynchronous Services (Packets) | |
|---|---|
API Function | Description |
xChannelGetMBXState | Retrieve the channels mailbox state |
xChannelGetPacket | Read a packet from the channel receive mailbox |
xChannelPutPacket | Send a packet via the channel send mailbox |
........... | |
Cyclic Data Services (I/O's) | |
|---|---|
| API Function | Description |
xChannelIORead | Instructs the device to place the latest data into the DPM input data area and passes them to the user |
xChannelIOWrite | Copies the data to the DPM send data area and waits for the firmware to retrieve them |
.......... | |
The complete API is described can be found in the "cifX API PR xx EN.pdf" manual.
...
Protocol API manuals can be found on the "Communication Solution DVD" in the .\Documentation\Programming Manuals\ directory and
the manual file names are containing the protocol stack name, e.g. "PROFIBUS Master Protocol API....pdf"
Development Environment
The following picture gives an overview of the possible development environments and the migration to embedded systems.
This should help to choose a programming level fit best to the application needs.