These are chat archives for esp8266/Arduino

19th
May 2015
Michael Miller
@Makuna
May 19 2015 00:14
Are there any checks for creating too large/much data in .irom.text section?
Michael Miller
@Makuna
May 19 2015 02:28
I can get the compiler/tools into a bad state with too many strings. See the bottom of esp8266/Arduino#222
meronz
@meronz
May 19 2015 06:39
@igrr downloaded the Arduino 1.6.4, installed the Esp support and works like a charm... A big thanks to everyone!
Ivan Grokhotkov
@igrr
May 19 2015 06:40
cool!
meronz
@meronz
May 19 2015 06:45
And works even if i use beginPacket() instead of beginPacketMulticast() ;)
Now i should work to the rest of the implementation, reading the answers! :D
Michael Miller
@Makuna
May 19 2015 06:51
Win8.1x64, works great so far!
meronz
@meronz
May 19 2015 07:24
(i was using Ubuntu x86_64)
meronz
@meronz
May 19 2015 07:49
are there any documents explaining wdt reset causes?
Ivan Grokhotkov
@igrr
May 19 2015 07:50
WDT reset causes? There's only one — WDT was not kicked for about a second or so
meronz
@meronz
May 19 2015 07:56
So there is something looping somewhere
ficeto
@ficeto
May 19 2015 12:54
Screen Shot 2015-05-19 at 15.52.46.png
ficeto
@ficeto
May 19 2015 14:04
uint16_t getTermistor(uint16_t value) {
  double temp;
  temp = log(((10230000 / value) - 10000));
  temp = 1 / (0.001129148 + (0.000234125 * temp) + (0.0000000876741 * temp * temp * temp));
  temp = temp - 273.15;
  return (temp > 120) ? 0 : (uint16_t)(temp * 10);
}
equals wdt reset
Markus
@Links2004
May 19 2015 14:43
the log function has a problem?
ficeto
@ficeto
May 19 2015 14:44
yes
Markus
@Links2004
May 19 2015 14:45
ok this is bad, its shut be in the libm. i wish we can use a real debugger.
Markus
@Links2004
May 19 2015 14:57
@ficeto looked at you screenshot nice feature :)
i plan to add support for websockets to the sever and may on top of it for socked.io (0.9) protocol
ficeto
@ficeto
May 19 2015 14:58
WebSockets issomething i've wanted for a while
never got down to write it
read a few implementations
we have base64encode/decode so no reason not to do it
a TCP stack rework is needed though
working right now on the JS lib for graphing data from the ESP
Markus
@Links2004
May 19 2015 15:01
as long you not do binary on WebSockets you not need base64.
then the whole implementation is phasing text between 0x00 {payload} 0xFF and some http header stuff :)
ficeto
@ficeto
May 19 2015 15:02
there was some base64 for the handshake though
Markus
@Links2004
May 19 2015 15:05

socked.io (0.9) protocol as client i have already running on the ESP8266 but never need base64 for that.
need to take look to the specs. but my header looks like that:

GET /socket.io/1/websocket/[SOME_ID_HERE] HTTP/1.1\r\n
Host: 127.0.0.1\r\n
Origin: Arduino-MS-SocketIOClient\r\n
Upgrade: WebSocket\r\n
Connection: Upgrade\r\n\r\n

after that you have an websocket to the server
then the data is encoded
0x00 [PAYLOAD_HERE] 0xFF

ficeto
@ficeto
May 19 2015 15:06
well.. let's not get limited to some particular impementation
should conform with the standart in order to make it work with any client
Markus
@Links2004
May 19 2015 15:07
yes when i do it then i do a full implementation ;)
Markus
@Links2004
May 19 2015 15:14
a base64 + sha1 is needed for a more security http://stackoverflow.com/questions/18265128/what-does-sec-websocket-key-for/18268003#18268003 but at the moment i dont see where the more security comes from.
have we sha1 support somewhere?
Markus
@Links2004
May 19 2015 15:32
wow in the latest RFCs WebSockets got more complex then I imagine. Last time i check the protocol out it was really easy.
ok this where 5 years a go :)
Michael Miller
@Makuna
May 19 2015 17:28
@igrr Is it ok if I add a link in the readme that points to my NeoPixelBus github code?
Ivan Grokhotkov
@igrr
May 19 2015 19:35
@Makuna sure, there's a Libraries section there I think
@Links2004 we have sha in ROM
need to expose it though
Markus
@Links2004
May 19 2015 19:37
nice will take a look end of the week.
Ivan Grokhotkov
@igrr
May 19 2015 19:38
I'll send you a link to the source of those particular functions a bit later
so you don't have to guess function signatures from linker script :)