-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Description
correct me if I am wrong but some VESCs have 2 uart ports, the second usually being connected to some onboard bluetooth and called the "permanent UART" in vesc tool. However lispBM scripts do not have any way to read/write raw data from that, only through the vesc comm protocol send-data and event-data-rx/recv-data. I want to use both for 2 different peripherals, so right now I use a vesc express for more uart ports, but actually is there anything preventing the second uart port being exposed to lispBM?
Also relatedly I notice that reading raw data from uart (uart-read-bytes) is unbuffered and bytes are just dropped if there is no uart-read-* taking place, so it is very easy to miss bytes if the lisp script cannot keep up and restart the reading fast enough. Am I interpreting the behaviour correctly and is it intended?