I anticipate that the VESC protocol will be poorly suited for things like the science system, so I added a JsonDriver.
Json embedded devices must read the 7 bytes of VESC ReqSubscription message, and reply with {"name":"MyName"} (replacing "MyName" with whatever you want to identify the device as.
USBManager then figures out if it speaks JSON or VESC and creates the appropriate driver for it.
Edit: Json devices also must precede all messages they send with the number of bytes in that message.
I anticipate that the VESC protocol will be poorly suited for things like the science system, so I added a JsonDriver.
{"name":"MyName"}(replacing "MyName" with whatever you want to identify the device as.Edit: Json devices also must precede all messages they send with the number of bytes in that message.