USB, Ethernet and PCIe host interfaces with single- or dual-channel classical CAN and CAN FD used for robot commissioning, control and diagnostics.
Comparison 06 · Audit sample
Robot host-to-CAN interface evidence table
Host-to-CAN adapters compared at the protocol, timestamp, isolation, environmental and driver layers.
CAN, CAN FD, CANopen and device-specific application protocols are different layers. A USB adapter does not make host timing deterministic.
| Field | Kvaser USBcan Pro 2xHS v2 | HMS Networks / Ixxat Ixxat USB-to-CAN V2 professional | Kvaser U100P | HMS Networks / Ixxat Ixxat USB-to-CAN FD compact | Kvaser Kvaser Leaf v3 | Kvaser Kvaser Ethercan HS | Kvaser Kvaser PCIEcan HS | HMS Networks / Ixxat Ixxat USB-to-CAN V2 compact |
|---|---|---|---|---|---|---|---|---|
| CAN channelsChannel count does not establish isolation or synchronized timing. | 2MTwo galvanically isolated channels.Source ↗ | 2MTwo RJ45 interfaces with supplied D-Sub 9 adapter cables.Source ↗ | 1MNo extra condition in selected source.Source ↗ | 1MD-Sub 9 CAN/CAN FD interface.Source ↗ | 1MSingle-channel interface.Source ↗ | 1MSingle high-speed CAN channel.Source ↗ | 1MSingle high-speed CAN channel.Source ↗ | 1MSingle high-speed CAN channel.Source ↗ |
| Classical CAN bitrateOfficial-document conflicts remain visible. | 20–1000 (product page) / 50–1000 (user guide) kbit/sCTwo official current-facing documents publish different minimum bitrates.Source ↗ | 10–1000 kbit/sMCAN high-speed ISO 11898-2:2016.Source ↗ | 10–1000 kbit/sMNo extra condition in selected source.Source ↗ | 10–1000 kbit/sMHigh-speed CAN ISO 11898-2:2016.Source ↗ | 20–1000 kbit/sMManufacturer product specification.Source ↗ | 40–1000 kbit/sMManufacturer product specification.Source ↗ | 20–1000 kbit/sMManufacturer product specification.Source ↗ | 10–1000 kbit/sMHigh-speed CAN according to ISO 11898-2.Source ↗ |
| CAN FD supportUnknown means the selected record does not support a positive claim. | Up to 8 Mbit/sMRequires a correct physical-layer implementation.Source ↗ | UnknownNo adequate published value in the selected source set. | Up to 8 Mbit/sMRequires correct physical-layer implementation.Source ↗ | Up to 8 Mbit/sMISO and non-ISO CAN FD; verified-by-testing statement.Source ↗ | Up to 8 Mbit/sMCAN FD mode.Source ↗ | NoMSelected Ethercan HS record is classical CAN.Source ↗ | NoMSelected PCIEcan HS record is classical CAN.Source ↗ | NoMSelected V2 compact record is classical CAN.Source ↗ |
| Host interfaceUSB, Ethernet and PCIe create different scheduling, security and driver boundaries. | USB Hi-SpeedMUSB bus powered.Source ↗ | USB 2.0 Hi-Speed, 480 Mbit/sMCompatible with USB 1.1 and USB 3.x according to family documentation.Source ↗ | USB 2.0MUSB bus powered.Source ↗ | USB Type-AM5 V USB powered.Source ↗ | USB 2.0MHost scheduling and driver behavior still apply.Source ↗ | 100BASE-TX EthernetMNetwork transport rather than USB.Source ↗ | PCI ExpressMInternal expansion-card interface.Source ↗ | USB 2.0 Hi-Speed, 480 Mbit/sMHost scheduling and driver behavior still apply.Source ↗ |
| Timestamp capabilityNumeric resolution and qualitative claims are not equivalent. | 1 µsMDevice technical data.Source ↗ | High-precision on-board timestampingMNo numeric resolution is published in the selected product specification.Source ↗ | 1 µsMPrecision U100P variant.Source ↗ | Not published in cited specificationURCI checked the cited official specification on the verification date.Source ↗ | 50 µsMOnboard timestamp specification.Source ↗ | 25 µsMOnboard timestamp specification.Source ↗ | Not published in cited specificationURCI checked the cited official specification on the verification date.Source ↗ | Not published in cited specificationURCI checked the cited official specification on the verification date.Source ↗ |
| Galvanic isolationPresence and withstand rating are distinct facts. | Yes, both channelsMIsolation present; voltage withstand is not stated in the selected product table.Source ↗ | 1 kV DC for 1 s / 500 V AC for 1 minMManufacturer product specification.Source ↗ | 5000 VAC rms for 60 sMDesign/test statement in current documentation.Source ↗ | 800 V DC / 500 V AC for 1 minMDatasheet general specification.Source ↗ | YesMCAN bus side.Source ↗ | YesMCAN bus side.Source ↗ | YesMCAN bus side.Source ↗ | 1 kV DC for 1 s / 500 V AC for 1 minMManufacturer datasheet value.Source ↗ |
| Driver / API baselineCurrent OS and driver releases require continuing verification. | UnknownNo adequate published value in the selected source set. | Windows VCI; Linux ECI / SocketCAN family supportMExact platform support must be checked against the current driver release.Source ↗ | UnknownNo adequate published value in the selected source set. | UnknownNo adequate published value in the selected source set. | Windows and LinuxMExact kernel, distribution and driver release require current verification.Source ↗ | REST API and t programsMFeature support; application design determines latency and recovery.Source ↗ | Windows and LinuxMExact current driver compatibility requires verification.Source ↗ | Windows VCI; Linux ECI / SocketCANMExact current distribution and kernel support must be checked.Source ↗ |
Values are transcribed from the linked sources and were checked on the date shown by each record. V = independently verified; M = manufacturer claimed; D = RCI derived; C = conflicting; U = unknown.
Interpretation rule
The condition belongs to the number.
RCI does not compute winners from this audit sample. The table’s purpose is to show what can be compared now, what requires a shared test, and which public fields are still missing.
Read the full method →