-
Notifications
You must be signed in to change notification settings - Fork 502
Hardware support
If you get the message "Driver selection failed" in the BUSMASTER Trace Window, you might not have the correct drivers installed. This page provides information on the supported hardware and driver download information:
- 8 devices (no support planned yet)
- ASAM HiL API (no support planned yet, see https://github.com/rbei-etas/busmaster/issues/103)
- dSpace (no support planned yet, see https://github.com/rbei-etas/busmaster/issues/119)
- Eberspächer (no support planned yet)
- Elektrobit (no support planned yet, see https://github.com/rbei-etas/busmaster/issues/98)
- esd (no support planned yet)
- ETAS (supported in v1.0.0+)
- I+ME ACTIA (no support planned yet)
- Intrepid Control Systems (supported in v1.1.0+)
- IXXAT (supported in v1.6.5+)
- Kvaser (supported in v1.3.0+)
- MHS-Elektronik (supported in v1.6.0+)
- National Instruments (no support planned yet, see https://github.com/rbei-etas/busmaster/issues/97)
- PEAK-Systems (supported in v1.0.0+)
- Softing (no support planned yet, see https://github.com/rbei-etas/busmaster/issues/73)
- sontheim (no support planned yet)
- VCI API (no support planned yet, see https://github.com/rbei-etas/busmaster/issues/35)
- Vector Informatik (supported in v1.2.0+)
- VisionSystems (no support planned yet)
- USB2CAN: not supported yet
The USB2CAN driver is available at http://www.8devices.com/product/2/usb2can/downloads.
The CANAL API description is available at http://www.8devices.com/product/2/usb2can/downloads.
ASAM HiL API currently defines the standard interface regarding CAN use cases for Hardware-in-the-Loop testing.
t.b.d.
t.b.d.
t.b.d.
t.b.d.
t.b.d.
t.b.d.
t.b.d.
t.b.d.
t.b.d.
Not supported yet. See https://github.com/rbei-etas/busmaster/issues/98
- http://www.eb-tresos-blog.com/autosar-4-0/solutions/tresos/eb-2100/
- http://www.eb-tresos-blog.com/autosar-4-0/solutions/tresos/eb-5100/
- http://www.eb-tresos-blog.com/autosar-4-0/solutions/tresos/eb-61x0/
t.b.d.
t.b.d.
The support should cover at least the following interfaces:
The drivers are available as part of the CAN SDK.
The CAN SDK is available at http://www.esd.eu/esd2004/german/products/Software/can_sdk_summary_e.htm
The support is available in version 1.0.0+. Please select "ETAS BOA" respective "ETAS ES581" as hardware interface.
These devices work:
These devices do not work:
- ES590/ES591/ES690
- ES6515, ES6516 and ETAS ES6520. See below for VCI devices.
These devices are not tested yet:
If your ETAS interface is connected via Ethernet and it is not found in the BUSMASTER Hardware Selection, try the following:
- Network protection (e.g. firewall) should be down or configured to allow communication from/to the device.
- Use a static IP address in the device's subnet.
- Make sure the Windows 7 Network Discovery does not change the configuration!
- Don't run the Hardware Service Pack before running BUSMASTER as it could change the device's IP address.
ETAS devices are supported using the ETAS Hardware Service Pack. It contains the hardware abstraction layer "ETAS BOA Runtime Framework" and the drivers "ETAS Drivers - ECU and Bus Interfaces" (ED-EBI). It also contains the IP-Manager component which is necessary to automatically configure the Ethernet-connected interfaces, e.g. ES59x.
BUSMASTER in all versions up to v1.6 supports BOA v1.4.
For ES581 devices there is a direct driver available if you select "ETAS ES581" in the "Hardware Interface" menu. This entry first tries to load ETASneo40.dll and then icsneo40.dll as fall back. BUSMASTER comes with both libraries installed in the application folder. If you experience problems with the distributed drivers try to delete one or the other library. In this case the global installed libraries are used instead.
As BUSMASTER does not install anything global, e.g. in Windows System32, there should be no influence on other applications on the system. However there is one exception. The LoadLibrary of Windows is clever in the way that it detects when an equally-named library is already loaded, even if it's used by another application. So if you start BUSMASTER first, the same library is used for other applications, e.g. INCA, as well and vice-versa.
There is an SDK available to implement new hardware underneath the BOA framework called "ETAS BOA Framework Development Add-on", and an SDK to build applications based on BOA called "ETAS ECU and Bus Interfaces Integration Package" (EBI-IP).
Both SDKs are available upon request. The necessary header files of the ETAS BOA Framework Development Add-on are part of the BUSMASTER source codes.
Currently there is only a feature request in issue #364.
- XS LITE
t.b.d.
t.b.d.
The support is available in version 1.1.0+. Please select "IntrepidCS neoVI" as hardware interface.
Intrepid devices are supported using the neoVI library (icsneo40.dll). At least version 3.5.1 is required.
There are two installers from Intrepid that install the icsneo40.dll in the Windows %system32% folder:
- Vehicle Spy Trial installs Version 3.5.1.67 or higher and device firmware version 0.71 or higher. This installation is recommended.
- RP1210/J2534 API Installer installs Version 3.5.1.61 or higher and device firmware version 0.69 or higher.
Intrepid provides an API documentation that contains links to download the driver.
The support is available in version 1.6.5+. Please select "IXXAT VCI" as hardware interface.
The support is available in version 1.3.0+. Please select "Kvaser CAN" as hardware interface.
- Leaf
- Memorator
- other devices should work
The Kvaser library is installed by the BUSMASTER installer. In addition you need the "Kvaser Drivers for Windows 2000/XP/Vista/Windows 7". The download is available at http://www.kvaser.com/downloads.html. Select "Driver" as "Download Type". The current version of the drivers is 4.6 (date 2011-11-29).
The Kvaser CANlib SDK provides an Application Programming Interface for interfacing to all Kvaser hardware platforms. The download is available at http://www.kvaser.com/downloads.html. Select "Development Kits and Tools" as "Download Type". The current version of the SDK is 4.6 (date 2011-11-29).
The support is available in version 1.6.0+. Please select "MHS Tiny-CAN" as hardware interface.
All bus interfaces listed at http://www.mhs-elektronik.de/cgi-bin/mhs.pl?id1=2&id2=0:
- Tiny-CAN I
- Tiny-CAN II-XL
- Tiny-CAN IV-XL
- Tiny-CAN M1
- Tiny-CAN M232
Tiny-CAN devices are supported using the Tiny-CAN API.
t.b.d.
Not supported yet. See https://github.com/rbei-etas/busmaster/issues/97
- All bus interfaces listed at http://www.ni.com/comm/ and http://www.ni.com/can/.
t.b.d.
t.b.d.
The support is available in version 1.0.0+. Please select "PEAK USB" as hardware interface.
PEAK devices are supported using the PCAN API and the Peak OEM drivers.
The PCAN API was obtained by RBEI and is delivered by BUSMASTER. It is installed as canapi2.dll in the BUSMASTER installation folder.
The Peak OEM drivers are part of the following download: http://www.peak-system.com/fileadmin/media/files/usb.zip. Execute the contained PeakOemDrv.exe to install the drivers. The default location is C:\Program Files\PCAN\Drivers.
The Development Kit was obtained by RBEI and is not available for free download.
Not supported yet. See https://github.com/rbei-etas/busmaster/issues/73
- All bus interfaces listed at http://www.softing.com/home/en/automotive-electronics/products/hardware/bus-interfaces/index.php?navanchor=3010007.
The driver is available on their download page.
Softing devices can be used with their CAN-API or as VCIs (see below).
Not supported yet.
An overview of CAN interfaces is available at: http://www.sontheim-industrie-elektronik.de/en/products/interfaces.html
t.b.d.
t.b.d.
Not supported yet. See https://github.com/rbei-etas/busmaster/issues/35
- ETAS ES6515
- ETAS ES6516
- ETAS ES6520
t.b.d.
t.b.d.
The support is available in version 1.2.0+. Please select "Vector XL" as hardware interface.
- CANcardXL
- CANcaseXL
- other devices should work
Vector devices will be supported using the Vector XL Driver Library. The current version is 7.5. It gets installed at "C:\XL Driver Library".
In addition the Vector Driver Setup should be run. The current version for Windows XP/Vista/7, 32 bit is 7.7.52. Others versions are available in the Vector Download-Center. The drivers get installed at "C:\Windows\System32\drivers".
The Vector XL Driver Library includes the API. The current version is 7.5. It gets installed at "C:\XL Driver Library".
Not supported yet.
All devices on http://visionsystems.de/1_1_5.html should be supported:
A driver download is available on the download page at http://visionsystems.de/downloadcenter.php
The VSCAN API is available on the download page at http://visionsystems.de/downloadcenter.php