In the end, I don't see the value in trying to view the entire buffer in one shot, at the end, when the buffer count already tells me I have 18k instead of 24k bytes of data received. In fact, that proves that dumping each buffer to the console as I receive it not causing any problems. If it were, I would have accumulated more data by not printing the data vs. printing the data. However, I get the same amount of data in either scenario.
I've stripped the code down to its bare minimum (where 'bare minimum' is defined as the code required to do a wifi/tcp connection and nothing else). No difference.
It's possible/likely that I need to set/change some configuration field that I'm unaware of, but other than that, I no longer think the problem is with my code. So unless there's a miracle, I'll have to think of something else with which to use these cool devices.
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.
In the end, I don't see the value in trying to view the entire buffer in one shot, at the end, when the buffer count already tells me I have 18k instead of 24k bytes of data received. In fact, that proves that dumping each buffer to the console as I receive it not causing any problems. If it were, I would have accumulated more data by not printing the data vs. printing the data. However, I get the same amount of data in either scenario.
I've stripped the code down to its bare minimum (where 'bare minimum' is defined as the code required to do a wifi/tcp connection and nothing else). No difference.
It's possible/likely that I need to set/change some configuration field that I'm unaware of, but other than that, I no longer think the problem is with my code. So unless there's a miracle, I'll have to think of something else with which to use these cool devices.