Interfaces
Software Support
IXXAT supports its CAN interfaces with a wide variety of powerful software packages. In addition to the standard CAN driver software, these also include development, analysis and configuration tools, as well as program libraries for higher layer protocols.CAN drivers for Windows
The delivery specification of every IXXAT CAN board includes the universal driver "Virtual CAN Interface" (VCI) for Windows 2000/XP/Vista/Windows7. This powerful driver package supports all CAN boards, regardless of their PC interface, with a uniform programming interface (API). This means that applications based on VCI-API can be used with all IXXAT CAN boards without modifying the application program.
The VCI CAN driver also contains a simple CAN bus monitor which enables transmission and reception of CAN objects in a CAN system.
As is typical with Windows, the IXXAT CAN boards are installed conveniently and safely via the Windows device manager.
Linux, INtime and RTX
For the Linux, INtime and RTX operating systems IXXAT provides the ECI driver. The ECI driver currently supports the active IXXAT interfaces. The passive interfaces will still be supported by the BCI driver for Linux.
LabView and LabWindows
For the standard visualization interfaces LabView and LabWindows, IXXAT provides free, fully functional integration examples based on the VCI CAN driver. Here, all important functions for transmitting and receiving CAN messages are fully supported. The IXXAT CAN interface boards can be operated directly under LabView and LabWindows with minimal adaptation work. If required, the integration examples can be quickly adapted to specific customer requirements.
CANopen and SAE J1939
The CANopen Master API enables PC access to CANopen systems via the active CAN interfaces from IXXAT. Based on this software package, powerful Windows based control, test and service programs can be developed quickly and easily. For the realization of complex CANopen PC-based control solutions IXXAT offers in addition to the CANopen Master API also the CANopen Manager API.
The SAE J1939 API for Windows is based on the IXXAT J1939 protocol software and is used to create PC-based SAE J1939 service and test applications.
| CAN Interfaces |
 |
 |
 |
 |
 |
 |
 |
 |
 |
| Passive CAN Interfaces | |||||||||
| PC-I 04/PCI | X | X (BCI(3)) |
- |
- | - | X | X | X | X |
| CAN-IB100/PCIe | X | X (ECI) | - |
- | X |
X |
- |
- |
- |
| CAN-IB120/PCIe Mini | X | X (ECI) | - |
- | X |
X |
- |
- |
- |
| PC-I 04/104 | X | X (BCI(3)) | - |
- | - | - | X | X | - |
| Aktive CAN Interfaces | |||||||||
| iPC-I 320/PCI II | X | X (ECI) |
X |
X | X | X | X | X | X |
| iPC-I 320/104 | X | X (BCI(3)) |
- | - | X | - | X | X | - |
| iPC-I XC16/PCI | X | X (ECI) | X | X | X | X | X | X | X |
| iPC-I XC16/PCIe | X | X (BCI(3)) | - | - | X | X | X | X | X |
| iPC-I XC16/PMC | X | X (ECI) | X | X | X | X | X | X | - |
| CAN-IB200/PCIe | X | X (ECI) |
- |
- |
- |
X |
- |
- |
- |
| iPC-I 165 | X | X (BCI(3)) |
- | - |
- | - | X | X | X |
| CAN@net II | X | X(1) | - | - |
X | X | X | X | - |
| Mobile CAN Interfaces | |||||||||
| tinCAN 161 | X | - | - | - |
X | X | X | X | X |
| USB-to-CAN II | X | X (ECI) | - | - |
X | X | X | X | X |
| USB-to-CAN compact | X | X (ECI) | - | - |
X | X | X | X | X |
| CANblue II |
X | X(2) | - | - |
- | X |
- | - | - |
1.) The Linux connection is made with the Generic version of the product by a TCP/IP socket interface, which provides all necessary CAN functions.
2.) The connection is made by the Generic version of the product using Bluetooth SPP communication, which has to be supported by the operating system. The serial ASCII protocol provides all necessary CAN functions.
3.) The BCI is not be developed further. New and future products will be supported by the ECI.