Cheap WiFi modules

[richard]

things improve if :-
1. I serve up the webpage in one continuous string
2. I control when the rxbuffer actually accumulates data (it auto triggers on a \r ( 0x10) ) , still needs a 350 byte buffer or 500 bytes for some browsers

the cache toggle signal in this example toggles when a rxbyte is cached and the reply signal when the rxbuff is emptied and parsed for data.

multiple connections still elude me , I find the behaviour of some browsers is quite baffling ,and they lock up the module upon connection .
hitting the refresh button while the current page is still coming causes the esp module to reset and start talking at a different baud rate , I can find no cure for this other than a hardware or a power on reset.

[richard]

I think I have a workable multi connection model worked out . it doesn't like a few browsers esp some Linux/android ones at this stage its been done in C
if anyone is interested PM me and you can get the ip address and have a go (its probably prudent not make it public) and you're welcome to the code too.
after playing with these things for days I think a multi connection version for pbp is not worth the effort and not necessary for me anyway . I really just want to monitor remote things and maybe tweak a few of their settings on the fly . one connection is amply for most if not all my requirements ,and it will be great just being able to set the time on the solar tracker for daylight savings time changes without having to get on the roof and plug the laptop into the tracker

[richard]

a header like this

HTTP/1.1 200 OK\r\nContent-Type: text/html\r\nConnection: close\r\nRefresh: yyy\r\nContent-Length: xxx\r\n\r\n

where yyy = refresh rate in seconds and xxx is the number of bytes in your page (the header not included) is a good thing

The AT+CIPCLOSE,NN is no required when you do this , although multiconnections are even more problematic a single user connection is more robust

ps this is a header not a <heading>

[richard]

Had a go at the cloud update ,it failed miserably and therefore i had to reflash device using the gpio0.low method and their flash tool.
I tried this version from their update site link 'ESP8266_AT_V00180902_04 (0018000902-AI03)_unconfirm version.bin '
it still reports its version as 0018000902-AI03 but the android devices can now connect without locking the esp8266 up and the stability of the unit is much improved things are looking up