Well, I believe you can write to a characteristic and use try...catch to see if you get an error, but there's no TX_COMPLETE event.
I'd say for maximum speed, use the UART interface as that does handle those events correctly. Even so I've actually had to reduce the amount of transmits that can be done on each connection interval as it's not reliable on some platforms.
There's nothing proprietary about the UART (far from it, it's a spec that Nordic themselves defined) so nothing stops you implementing it on a non-Espruino device later.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Well, I believe you can write to a characteristic and use
try...catch
to see if you get an error, but there's no TX_COMPLETE event.I'd say for maximum speed, use the UART interface as that does handle those events correctly. Even so I've actually had to reduce the amount of transmits that can be done on each connection interval as it's not reliable on some platforms.
There's nothing proprietary about the UART (far from it, it's a spec that Nordic themselves defined) so nothing stops you implementing it on a non-Espruino device later.