CAN-Interfaces: USBtin and USBtingo
| USBtin EB | USBtingo EB |
Photo | | |
CAN | CAN 2.0 | CAN 2.0, CAN-FD |
USB | Full speed (FS) 12 Mbit/s | High speed (HS) 480 Mbit/s |
Protocol | Simple serial protocol (USB CDC) | Throughput optimized USB protocol |
RX buffer | 0.25 kByte 16 messages | 32 kByte 2048 messages (dlc=0) 409 messages (dlc=64) |
RX throughput (depends on host performance) | 100% load on 250 kBaud | 100% load on 8 MBaud |
Logic analyzer (CAN-RX sampling) | - | up to 40 Msps |
Hardware timestamping | - | RX and TX Resolution: 10 µs |
Hardware filter | 2+4 | 32+32 |
Controller | Microchip 8 bit PIC 48 MHz | NXP 32 bit ARM 120 MHz |
Dimension | 57x25 mm² | 36x18 mm² |
Connector | Mini-USB | Micro-USB |
Power | USB powered No galvanic isolation | USB powered No galvanic isolation |
Frequently asked questions
Which of the two interfaces should I use?
For new projects, take a closer look at
USBtingo. CAN-FD and the logic analyzer function are significant enhancements. Due to the integration into python-can many platforms and connected projects (e.g. cantools, canopen) are available.
USBtin has been available for a long time, proven in many projects and is supported by a large number of tools and projects. If neither CAN-FD, the logic recording function nor higher throughput is required, USBtin is suitable.
Are both interfaces compatible, can I use tools like USBtinViewer with USBtingo?
No, the protocol is different. USBtin uses a simple serial protocol, the communication of USBtingo is optimized for performance (short latency and high throughput).