I reworked the communications link last night. Removed the timer approach and went to the approach that the client sends a character, the server replies with the JSON string, on receipt by the client, but before the JSON parse, the client sends another character, then does the JSON parse within a try/catch framework. The results run much faster and much longer without errors
The port used in the browser is 8000 not 8080. (you can edit it if you like). So the IP address line of the browser reads:
http//192.168.1.6:8000
The latest are attached.
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.
I reworked the communications link last night. Removed the timer approach and went to the approach that the client sends a character, the server replies with the JSON string, on receipt by the client, but before the JSON parse, the client sends another character, then does the JSON parse within a try/catch framework. The results run much faster and much longer without errors
The port used in the browser is 8000 not 8080. (you can edit it if you like). So the IP address line of the browser reads:
http//192.168.1.6:8000
The latest are attached.
2 Attachments