ⓘ DRV256 is a USB CDC virtual COM port device. No baud rate setting is needed ??the transport is USB virtual serial, so the host baud rate is a placeholder only (any value works in practice).
1. USB CDC Bridge Behavior ??Host baud setting is a placeholder; transport is USB virtual serial.
Packet Path: Host virtual COM port -> USB CDC device -> board bridge -> all four servo ports in parallel.
Servo-originated packets from individual downstream devices are merged by the board and sent back upstream through the same USB CDC channel.
The bridge does not reinterpret servo packets. For standard servos it forwards the original serial frame as-is. For ESC targets it converts the command intent to the protocol selected by the ESC protocol register (`0x83`).
All servos connected to a single DRV256 must be set to the same baud rate on the servo-side serial bus. DRV256 automatically detects the connected servos' baud rate ??no manual baud rate configuration is required on the board. Only these servo-side baud rates are supported: 115200, 1 Mbps, 2 Mbps.
In addition to USB CDC, DRV256 exposes UART, RS485, and CAN as alternate host interfaces (see Interface, Page 1). Whichever interface is used, the data sent and received is identical to what is sent and received when the USB CDC virtual COM port is open ??only the physical transport differs.
The serial packet format forwarded by DRV256 follows the same protocol used by the servos themselves.
See
Actuator Serial Interface.
drv256_dashboard.html is a self-contained, zero-install browser application (Web Serial API) for DRV256 development and testing. No driver installation is needed on any OS, and host baud-rate setting is irrelevant ??the transport is USB virtual serial.
After connecting, add one or more motor IDs (0??54) to track: the dashboard automatically treats IDs 251??54 as ESC targets and all other IDs as standard servos, reading back each tracked motor's Position, Velocity, Current, Torque, Voltage, and Temperature as live line-graph subplots. A built-in
packet builder lets you pick a command (READ / WRITE / ADD / COMMIT / ABORT and their
*_WITH_ACK variants), target ID list, and register address/value, and assembles the resulting frame in a raw hex editor with byte-by-byte syntax highlighting, live validation, CRC auto-fix, and one-click send ??plus a System/RX log of all traffic.
See
DRV256 Dashboard.
2. ID And Model Number Allocation
| Device Class |
Model Number |
ID Range |
Description |
| Standard servo * | Product-specific | 0-250 | Available range when the USB Servo Driver reserves the upper IDs for ESC outputs. |
| ESC channel 1 | 0xFF | 251 | Mapped to ESC output 1 |
| ESC channel 2 | 0xFF | 252 | Mapped to ESC output 2 |
| ESC channel 3 | 0xFF | 253 | Mapped to ESC output 3 |
| ESC channel 4 | 0xFF | 254 | Mapped to ESC output 4 |
* Using DRV256 reduces ACT48's usable ID range to 0-250.