Please, read it up to end!
The CARBUS analyzer and your interface don’t require activation!
- Install drivers
- Download CARBUS analyzer archive, unpack it
- Run CarBUSAnalyzer.exe
You have to install a virtual COM port driver by ST-Microelectronics before working.
After installing the driver and connecting the interface to the computer, a device “STM Virtual Com Port” should appear in the Ports section. The port will be assigned a number, for example COM3, as in the screenshot below. The port number will need to be entered in the CARBUS Analyzer program when connecting to the interface, so remember this number.
Possible problems in installing the driver and how to solve them
Problems with driver installation can occur on older versions of Windows XP and Windows 7. The interface is defined in the manager as a virtual COM port, but when you try to connect to it, the software hangs on or fails. In this case, please note that there are two drivers available for download on our site, and try to install a different driver version from the one that was installed first. This usually helps to solve the problem.
The second problem may be the low speed of the interface. In this case, the received packets are displayed with a clear delay. This may be due to the fact that the USB controller is obsolete on the computer. The solution is to use an external USB hub (Splitter) that agrees the size of the interface packets and the USB controller of the motherboard.
To work with the CAN-Hacker 3.2 interface as the CAN and LIN tire analyzer it is necessary to download the CARBUS Analyzer software on the DOWNLOAD page.
Then unpack the downloaded archive.
The archive contains both the CARBUS Analyzer program itself and the UBT firmware files (UBT folder) upgrade utility from the current firmware files (UBT Firmware files) folder
Configure CARBUS Analyzer and CAN bus interface
The CAN-Hacker 3.2 interface works with two firmware types:
CH32_20200307_CANLIN_GW_CR.bin– firmware for working with CAN or LIN buses
Supports: two CAN channels or one LIN channel (requires activation), CAN Gateway mode,
Bandwidth: 4000 frames per second. It is Optimal for the CAN Bomber mode
Default – CH32_xxxxxxxx_CANLIN_CR.bin – firmware for working with CAN or LIN buses
Supports: two CAN channels or one LIN channel (requires activation)
Bandwidth: 8000 frames per second.
Both firmwares allow working with both CAN and LIN buses. To work with the Can_hacker 3.2 interface in CARBUS Analyzer, the Settings menu must select the type of the connected interface in the Device Type drop down list.
Select – CAN-Hacker v3.x
В выпадающем списке Device mode необходимо выбрать режим работы интерфейса. Доступные режимы:
- CAN High speed Dual channel mode – working with CH32_xxxxxxxx_CANLIN_CR.bin firmware. RX: 8000 frames per second
- LIN mode – LIN bus analyzer. It requires Activation.
- CAN Low speed Gateway mode – working with CH32_xxxxxxxx_CANLIN_GW_CR.bin. RX: 4000 frames per second. CAN Gateway mode is supported
In the Source drop down list, you must select the port on which the system interface is defined .
Configure CAN channels
CAN channels are configured on the Channel 1: CAN and Channel 2: CAN tabs. These tabs become visible after you select the interface mode to work with the CAN bus.
Channel baudrate – sets the CAN bus speed.
Listen only mode – Converts the interface to Listen only mode, which loses the ability to send frames, but when receiving frames across the bus, the interface does not flag the acknowledgement of ACK reception on the bus, making the interface invisible to other devices on the bus.
Invalid Device type message will appear if the interface type is not correctly defined or if it is loaded with an obsolete firmware
CAN bus connection
The CAN bus is connected with the interface cable
Yellow\black– CAN-Low channel 1
Yellow\white– CAN-High channel 1
Orange\black – CAN-Low channel 2
Orange\white – CAN-High channel 2
DIP switch on the device board serves to connect terminator resistors of 120 ohm between CAN-High and CAN-Low lines. In the ON position, the resistors are connected.
When connecting to a single-wire bus CAN (SWCAN – Single Wire CAN, GMLAN), it is necessary to connect the CAN-Low wire to the mass (GND) of the examined car or control unit, and the CAN-High wire to the SWCAN GMLAN line.
If the CAN settings are done correctly, the physical connection to the bus is correct and the bus is exchanged, then the CAN bus data will be displayed in the receiving window after pressing the Connect button.
A detailed description of the work with CARBUS Analyzer as CAN bus analyzer is available on a separate page – link.
LIN bus analyzing
(LIN bus adapter must be installed and activated)
- Click Settings
- Device type -> CAN-Hacker v3.x
- Device mode -> LIN mode
- Source -> COM port of the interface
After interface configuration:
- Setings -> Channel 1: LIN.
- Channel baudrate -> LIN bus baudrate
- Detection time – > a minimal pause between LIN frames. 2ms – default
The LIN CRC Type parameter defines the type of checksum method used when working with a LIN bus. This option does not affect the ability of the interface to accept frames. If the checksum type is not correctly defined, then the receiving party will ignore the frameswhen passing through the interface.
The LIN bus is connected by the LIN analyzer cable supplied with the option.
Red – +12 V
Black – GND
Blue – LIN
Important! The connection to the LIN bus of the tested device or car requires a mandatory GND connection and a power supply of +12 V.
If the connection and settings are done correctly and the LIN bus under study is active, i.e. data is exchanged between the Master and Slave nodes or queries are received from the Master node, then the LIN bus data is displayed in the reception window.
A detailed description of the work with CARBUS Analyzer as a LIN bus analyzer can be found on a separate page – link.