Adapters, operating systems and drives that CAN Servo Tool works with.
can0, can1… for example candleLight (gs_usb) devices and Kvaser USB through the kernel driver.Details and setup: Supported adapters.
Any CANopen® device described by an EDS file: the object dictionary, SDO, PDO, NMT and the frame log work with it. The drive screens work with servo drives that implement the CiA 402 device profile.
We will list drive models here once they have been tested on a bench. Using a drive or an adapter that is not listed? Tell us about it.
Anything else? Write to us.
PEAK PCAN-USB and compatible PEAK USB adapters: on Windows through PEAK's PCAN-Basic driver or WinUSB, on Linux through the kernel SocketCAN driver, on macOS through the app's own driver with libusb.
GCAN USBCAN-I/II on Windows, Linux and macOS through the app's own driver; GCAN software is not needed. On Windows it works through GCAN's driver if that is installed, or through WinUSB. Linux needs a udev rule (see Supported adapters). macOS needs libusb.
Any SocketCAN interface on Linux: adapters with a Linux kernel SocketCAN driver, for example PEAK, candleLight (gs_usb) devices such as CANable with candleLight firmware, and Kvaser USB through the kernel driver.
slcan (Lawicel) serial adapters, for example CANable with slcan firmware, USBtin and other Lawicel-compatible adapters, on Windows, macOS and Linux.
USB-CAN Analyzer (Waveshare USB-CAN-A and compatible adapters based on the CH340 USB-serial chip) on Windows (the CH340 driver is needed), macOS and Linux.
EBYTE ECAN-U01 and ECAN-U01S on Windows, macOS and Linux. Both CAN ports appear in the Interface list, and one of them can be open at a time. No vendor driver is needed: it is a standard USB serial device.
The built-in emulator needs no adapter at all.
Yes. Connected adapters appear in the Interface list by name, and you do not choose a driver. Serial ports that are not CAN adapters are not listed.
Yes, two. It does not report bus errors (bus-off, error passive), so the app cannot show them. It also sends remote (RTR) frames with DLC 0, so a node that strictly requires DLC 1 in a node guarding request will not answer through it.
It has no listen-only mode. It does not report bus errors such as bus-off or error passive; the app only shows when a frame was not acknowledged by any node. Only one of its two CAN ports can be used at a time.
Kvaser USB adapters work on Linux through the kernel SocketCAN driver. The native Kvaser CANlib driver on Windows and IXXAT VCI are planned, and we are waiting for hardware to test them.
Yes for GCAN USBCAN-I and USBCAN-II (USB ID 0C66:000C), both CAN ports, through the app's own driver. The eRob USB CAN Debugger is built on that GCAN hardware: if Windows Device Manager or lsusb shows USB ID 0C66:000C, it works the same way.
Yes. The built-in emulator of a CANopen node and a CiA 402 drive lets you try the tool without hardware. The app still needs a license, and the free one is enough.
The standard set of CiA 301: from 10 kbit/s up to 1 Mbit/s.
Windows and Linux. macOS also works.
Yes. Pick the one you need in the Interface list on the Connection screen. The software node feature and the master share one adapter.