-
• #2
Many thanks Gordon.
-
• #3
Did anyone else have troubles with updating to 1v62? It failed quite badly in my case http://forum.espruino.com/conversations/1250/#comment19230
-
• #4
Worked as expected with WebIDE
Sacha
-
• #6
I've installed 1v63 from latest commit. Wiznet now works better, although I still got the following once:
INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI RX INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI RX INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI RX INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI RX INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI TX INTERNAL ERROR: Timeout on SPI RX at line 29 col 13 req.end(body); ^ in function "sendGrove" called from line 1 col 11 =undefined =undefined ERROR: Socket error -7 while sending Callback ->{"message":"exception.LabradorException: Feed PUT call limit has been exceeded for address 77.100.6.154. One cal ->l every 10 seconds is allowed. ","errCode":"RATE_LIMIT_EXCEEDED","success":false}
I'm pleased to say that even after this, further GETs worked.
I can't quite give it a complete 100% bill of health, but it feels a lot better
Martin
-
• #7
Update - it's better, but still a bit patchy. I'm still getting the socket -7 error. I also still get "no free sockets" but I was doing HTTP requests more quickly than every minute. The Internal SPI error I still see, but generally only get when sending a new program to the device after a socket error - in this case, it just loops showing this error
-
• #8
You can find tow different Sharp Memory LCD breakout boards on tindie.
-
• #9
@mgg1010 the timeout errors occur because the Web IDE is trying to get in contact with the board. If it can't get a response within a short time period, it sends
Ctrl + C
which breaks out of whatever Espruino was doing - in this case sending SPI data to the WIZnet chip - and hence the errors.It shouldn't cause a problem - but the Web IDE should probably be a bit more patient before it sends the Ctrl-C :)
-
• #10
Perhaps we could have a parameter in Web IDE configuration to turn this off or change the delay?
(See my separate post on similar error messages in I2C)
-
• #11
Well, I just made an issue for it: https://github.com/espruino/EspruinoWebIDE/issues/89
It should wait longer - thinking about it, it may just send Ctrl-C regardless which would obviously be a mistake.
-
• #12
Thanks.
Now out! A bunch of new features and fixes:
Also updated the website with a bunch of contributions I've had over the last week, including @mgg1010's Date/Clock module, a MPL115A2 module, a Midi module, and a Sharp Memory LCD module.