Ok, I've just updated the code so new firmwares will hopefully automatically call close - let me know if that works ok for you.
I also added some extra debugging when sending data. The splitting of data is expected - it's just to do with the buffer sizes Espruino uses internally. What's not expected is if it doesn't immediately send the second packet. I think the send function is waiting for SEND OK but it's possible it doesn't get it because it receives the > first - hopefully seeing the debug text from the new build will show that's what's happening - in which case it's an easy fix.
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.
Ok, I've just updated the code so new firmwares will hopefully automatically call close - let me know if that works ok for you.
I also added some extra debugging when sending data. The splitting of data is expected - it's just to do with the buffer sizes Espruino uses internally. What's not expected is if it doesn't immediately send the second packet. I think the send function is waiting for
SEND OK
but it's possible it doesn't get it because it receives the>
first - hopefully seeing the debug text from the new build will show that's what's happening - in which case it's an easy fix.Thanks for your help with this!