Possible issue with R103

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Possible issue with R103

#1 Post by dduley » 24 Apr 2016, 00:15

I had 10 esp modules all running happily on R101. Uptimes were in the thousands of minutes. When R103 popped up i upgraded all 10 units via OTA update. All went fine but then i noticed 2 of the modules started resetting themselves every few minutes. One i connected via USB and re burned it. it still had issues. When it resets it says manual reboot. I wound up issuing a Reset command to wipe out all of the preset tasks. That seemed to work. On the second unit the Reset trick did not work. I started messing around with the logging levels. I set serial to zero and web to four. Then it started to work fine.
Has anyone else seen any flakey behavior with R103?

JR01
Normal user
Posts: 260
Joined: 14 Feb 2016, 21:04
Location: South Africa

Re: Possible issue with R103

#2 Post by JR01 » 24 Apr 2016, 01:06

dduley wrote:Has anyone else seen any flakey behavior with R103?
Yes, struggling with it now. Serial interface works, web not. Every now and then the web interface will load, but very slow.
-----------
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.

JR01
Normal user
Posts: 260
Joined: 14 Feb 2016, 21:04
Location: South Africa

Re: Possible issue with R103

#3 Post by JR01 » 24 Apr 2016, 01:09

dduley wrote:I had 10 esp modules all running happily on R101.
Bit of a newbie on the Arduino compile, I use ESPEasy_Master - which is R103, if you say R101 is working, where do I find that code to compile?
-----------
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.

JR01
Normal user
Posts: 260
Joined: 14 Feb 2016, 21:04
Location: South Africa

Re: Possible issue with R103

#4 Post by JR01 » 24 Apr 2016, 01:11

I have 2 x R78's, and one R103 on ESP12F, and although this one is unresponsive on web interface, it seams they are happily talking to one another on UDP. Strange.... the 1st two are the R78's, the last one is the version R103. See below.
QUESTION: Does anybody know what the "Age" column is for? why would the R103 have an age of 8?
Screen Shot 2016-04-24 at 1.12.52 AM.png
Screen Shot 2016-04-24 at 1.12.52 AM.png (21.35 KiB) Viewed 15227 times
-----------
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.

dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Re: Possible issue with R103

#5 Post by dduley » 24 Apr 2016, 20:23

JR01 wrote:
dduley wrote:I had 10 esp modules all running happily on R101.
Bit of a newbie on the Arduino compile, I use ESPEasy_Master - which is R103, if you say R101 is working, where do I find that code to compile?
Hi JR01,

It was on Github a few days ago but now R101 has been replaced by R103.
I didn't see any archives that would contain older versions

dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Re: Possible issue with R103

#6 Post by dduley » 24 Apr 2016, 20:29

JR01 wrote:I have 2 x R78's, and one R103 on ESP12F, and although this one is unresponsive on web interface, it seams they are happily talking to one another on UDP. Strange.... the 1st two are the R78's, the last one is the version R103. See below.
QUESTION: Does anybody know what the "Age" column is for? why would the R103 have an age of 8?
Screen Shot 2016-04-24 at 1.12.52 AM.png
I think the Age value is how long ago that node sent out a UDP message. So your R103 that is acting slow appears to be acting slow for the UDP as well. What value do you have set for the Message Delay under Tools/Advanced?

Ever since I set my Serial logging to 0 my troubled R103 unit has been working fine. It shows 1200 minutes of uptime where before It would only live 4 minutes max. It may be coincidental but whatever I did something started working.

Try issuing a RESET command under Tools/command. This will wipe all Access Point settings and any tasks that you may have configured. I have noticed that sometimes this is required to get things working properly again.

Regards

Dave

JR01
Normal user
Posts: 260
Joined: 14 Feb 2016, 21:04
Location: South Africa

Re: Possible issue with R103

#7 Post by JR01 » 25 Apr 2016, 22:43

Thank you Dave and others, yes, debug - 0 Serial ; debug - 4 Web works, but the web interface stands still longish periods, but it works, busy with more tests.
-----------
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.

stefbo
Normal user
Posts: 19
Joined: 24 Apr 2016, 15:35
Location: Germany

Re: Possible issue with R103

#8 Post by stefbo » 25 Apr 2016, 23:45

Hi
updated to 104 and still the resets occur. I have set debug - 0 Serial ; debug -2 Web. Sometimes the node works for hours, but the it starts resetting again. Sometime it helps to switch it off completely...
No clue what causes this.
The errors occur on esp8266-201's and on a esp8206-01
Any help welcome
Stefan

dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Re: Possible issue with R103

#9 Post by dduley » 26 Apr 2016, 00:42

stefbo wrote:Hi
updated to 104 and still the resets occur. I have set debug - 0 Serial ; debug -2 Web. Sometimes the node works for hours, but the it starts resetting again. Sometime it helps to switch it off completely...
No clue what causes this.
The errors occur on esp8266-201's and on a esp8206-01
Any help welcome
Stefan
Hi Stefan,
My experience is limited to the ESP8266-12E and the ESP8266-07 modules. If you are using a -01 module, are you compiling the code for the correct memory size? Check your setting under the Tools menu in the Arduino IDE.

Dave

stefbo
Normal user
Posts: 19
Joined: 24 Apr 2016, 15:35
Location: Germany

Re: Possible issue with R103

#10 Post by stefbo » 26 Apr 2016, 21:09

Hi Dave,
I use the 512k (64 k SPIFF), which should be appropriate for -01 and -201 modules.Any other ideas?

Stefan

tozett
Normal user
Posts: 734
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Possible issue with R103

#11 Post by tozett » 26 Apr 2016, 22:22

there had been here in the forum a discussion about capacitors on certain esp modules,
to get more stability. this had led to this wiki-entry:

http://www.esp8266.nu/index.php/Power

may you want to have a look ...

dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Re: Possible issue with R103

#12 Post by dduley » 01 May 2016, 19:33

JR01 wrote:Thank you Dave and others, yes, debug - 0 Serial ; debug - 4 Web works, but the web interface stands still longish periods, but it works, busy with more tests.
Hi JR01,

Did you ever resolve your slow web interface? Are you, by chance, trying to connect more than one DS18B20 at a time? I just tried that and when I went to set up the 2nd temperature sensor the ESP module became extremely slow in responding to the web interface.

Dave

dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Re: Possible issue with R103

#13 Post by dduley » 01 May 2016, 20:47

stefbo wrote:Hi Dave,
I use the 512k (64 k SPIFF), which should be appropriate for -01 and -201 modules.Any other ideas?

Stefan
Hi Stefan,

I have had many problems with resetting. The code as it stands right now isn't very stable. I think there are issues with task storage memory or something like that. I have set up a unit and it will work fine for days or weeks. Then I go to add another task and everything falls apart. I will delete the task and it goes away but the task name remains but it isn't the task name of the task I just deleted!I think these things will all get sorted out eventually.
Another issue is the quality of the hardware. I have bought 30 or 40 of these things from various places and there is a big difference in the quality of the parts. I have had some units work right out of the package and others I have had to re-flash and on a few I even had to perform surgery to replace the flash chip on the ESP module. I am getting to be an expert on de-bricking ESP modules. I have one unit that is in a Junction box outside controlling my pool. If the internal temperature of the Jbox get above 105 degrees F then it resets. I shaded the Jbox and it works fine unless we have a hot day. A friend of mine has the exact same setup I do for his pool and his Junction box is in direct sunlight for most of the morning. His Jbox temp has gotten as high as 130 degrees F and his ESP board just chugs along fine.

You might try issuing a RESET command from the tools menu in the Command box. This will clear everything out. You will have to re-setup your module but it may make it more stable. Sometimes Even RESET doesn't do it though.

Good Luck

Dave

stefbo
Normal user
Posts: 19
Joined: 24 Apr 2016, 15:35
Location: Germany

Re: Possible issue with R103

#14 Post by stefbo » 02 May 2016, 00:13

Dear Dave, dear tozett,
thanks for your valuable help. I added an additional 100n capacitor between VCC and GND and a 15n capacitor between RST and GND. This seemed to make it a little bit better, but I still got the resets.
I also read about the ERASE command which also did not make it much better. The longest period I observed are about 200 min.
I will now try the RESET...
One strange thing is that usually the first period (after power up) is longest, then afterwards the reset occurs more and more frequently. Dave, maybe this confirms your assumption with the task storage.
Soon I will try our esp-12's maybe they are more stable than my -201 an -01

Stefan

tozett
Normal user
Posts: 734
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Possible issue with R103

#15 Post by tozett » 02 May 2016, 08:16

i had reboots with my esp12 modules
(the ones shown here with my breadboard setting),
http://www.esp8266.nu/index.php/Breadboards

recently switched over for testing to wemos mini d1 modules,
wich are very more stable...

User avatar
costo
Normal user
Posts: 500
Joined: 21 Nov 2015, 15:03
Location: NL, zw-NB

Re: Possible issue with R103

#16 Post by costo » 02 May 2016, 14:26

stefbo wrote: I added an additional 100n capacitor between VCC and GND and a 15n capacitor between RST and GND. This seemed to make it a little bit better, but I still got the resets.
100nF extra capacitance over the Vcc does not help very much. You need to add a good capacitor of about 10 uF, with low self inductance. So a tantalium capacitor is a good fit for that. (2u2, 4u7, 10uF or 22uF all will do well)
If you use a breadboard then it is advisable to solder that capacitor directly on the ESP module between Vcc and Gnd. If you have a permanent setup than locate this capacitor very close to the ESP module.

JR01
Normal user
Posts: 260
Joined: 14 Feb 2016, 21:04
Location: South Africa

Re: Possible issue with R103

#17 Post by JR01 » 02 May 2016, 21:29

dduley wrote:Hi JR01, Did you ever resolve your slow web interface? Are you, by chance, trying to connect more than one DS18B20 at a time? I just tried that and when I went to set up the 2nd temperature sensor the ESP module became extremely slow in responding to the web interface. Dave
Hi Dave, I added the tantalum as suggested by previous contributors here, and this http://www.esp8266.nu/index.php/Power, I went up to R105, and I did this with an ESP12E and an ESP12F. The 12F has the "stuttering http" interface, where as !@E with R105 does not have.... I only tried one 12F, will see if I get same with another 12F.
-----------
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.

stefbo
Normal user
Posts: 19
Joined: 24 Apr 2016, 15:35
Location: Germany

Re: Possible issue with R103

#18 Post by stefbo » 04 May 2016, 00:04

I made another observation: I let my devices run overnight and obviously they rebooted several times. In the morning the load was on 100% even if uptime was only 1 minute. The normal load is about 5% after power up. After a few reboots I also observed loads around 25% with the tendency to increase after each reboot.
Anybody any idea what causes this load?
I can somehow live with rebooting, but if it reboots it should reboot completely :D ...
Stefan

dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Re: Possible issue with R103

#19 Post by dduley » 04 May 2016, 00:44

stefbo wrote:I made another observation: I let my devices run overnight and obviously they rebooted several times. In the morning the load was on 100% even if uptime was only 1 minute. The normal load is about 5% after power up. After a few reboots I also observed loads around 25% with the tendency to increase after each reboot.
Anybody any idea what causes this load?
I can somehow live with rebooting, but if it reboots it should reboot completely :D ...
Stefan
Hi Stefan,

I have had similar issues. This ISN"T the ol' blame it on too few capacitors thing. This is firmware and I am sure it will be fixed eventually. I have one unit that has three DS18B20 temperature sensors connected. It will run for weeks with a singe task looking at just one of the sensors. If I add another task for the second sensor it will run fine just after a reboot but will get progressively slower and slower to respond. After a few hours it acts completely unresponsive and resets itself every 1 or 2 minutes. If I hit the reset button it plays nice again for awhile. Heaven help me if I add a third task for the last temperature sensor. It becomes very slow right away. Reset doesn't help at all. It takes 1 to 2 minutes for any of the web pages to load. When I finally am able to go to the Devices menu and delete a task the task doesn't completely go away. Everything goes except for the task name which will now contain the name of another task. Something is not indexed correctly.

Anxiously awaiting R106!! :D

Dave

JR01
Normal user
Posts: 260
Joined: 14 Feb 2016, 21:04
Location: South Africa

R105 on ESP12E / ESP01 - very stable...

#20 Post by JR01 » 10 May 2016, 20:40

Hi, just wanted to say, R105 is very stable, still running it on bread board, no issues with speed of that interface. I think the trick was debug 0 on serial. Still have not tested another ESP12F to see if also getting stuttering http interface. Thank you to Dev's! (looking forward to R106)
-----------
IOTPLAY. Tinkerer, my projects are @ http://GitHub.com/IoTPlay, and blog https://iotplay.org. Using RPi, Node-Red, ESP8266 to prove Industry 4.0 concepts.

dduley
Normal user
Posts: 93
Joined: 06 Feb 2016, 17:56

Re: Possible issue with R103

#21 Post by dduley » 10 May 2016, 22:19

stefbo wrote:Hi Dave,
I use the 512k (64 k SPIFF), which should be appropriate for -01 and -201 modules.Any other ideas?

Stefan
Hi Stephan,

I started to have similar issues to what you are seeing with one of my modules after I did an OTA upgrade to R105. I added a 2nd and third DS18B20 temperature sensor. It got slower and slower with the addition of each sensor. I finally had to reduce it back to a single sensor to get any response at all. I then started watching the Log. I noticed a relatively large amount of connection failures. It would get slower and slower as time went on and then it would reset on its own and then be fine for a short while. The unit finally became completely unresponsive. It started missing timing events and my pool pump did not turn on for 4 straight days. Last night I opened the j-box and connected my laptop using the USB port on the NODEMCU module. When I pressed reset I got the usual boot message at 78400 baud but then it seems to grid to a screeching halt. I tried typing a few serial commands such as "Settings". I was distracted for 20 minutes or so and when I came back I was surprised to see it had responded! I re-flashed with R105 using the Arduino IDE and the USB cable. It flashed OK but it was still unresponsive. I then gave it the "RESET" command via the serial port. I waited 15 minutes and it finally responded and cleared the module. I re-setup the module from scratch and it has been fine ever since. It has bee up now for over 500 minutes so far without a hiccup.
I do believe that there are some memory initialization issues. I have noticed weirdness after OTA upgrades from time to time. Perhaps there is a difference between a wired flash and the OTA upload in terms of what gets cleared out. I see as of today R106 is out. I am anxious to play with it and see if anything has changed. The changelog on github only speaks of a couple of minute changes.

Regards

Dave

stefbo
Normal user
Posts: 19
Joined: 24 Apr 2016, 15:35
Location: Germany

Re: Possible issue with R103

#22 Post by stefbo » 11 May 2016, 01:07

Hi Dave,
probably it is due to the larger memeory of the 12E modules, that you observed this behaviour later than me. In the meantime I made two modifications:
In the WebServer.ino file are in three locations calls to malloc: char *TempString = (char*)malloc(80); But the TempString is never used. I commented these lines out and it still compiles.
I also changed the power supply (I use a 18650 LiPo with charging module always connected to power supply and a LF33CV linear voltage regulator) which made everything more stable. One -01 module without any sensors connected is now online for ~24h: new record!!! A 201 with 2 DS1820's , a BMP085 and an OLED display is on for 260min without reboot (also quite good). It seems the load is slowly increasing, but I am not fully sure as I do not see a way to monitor it continuosly.
My impression is that the latter improved my situation more than the first...
I also observed the same behaviour than you: I had a module which was completely unresponsive. Even after a power down and reset by connecting RX andTX it continuously rebooted (~every 5 sec). Now after 2 days rest it worked again without problems. Strange....
Stefan

azure
New user
Posts: 2
Joined: 28 May 2016, 07:33
Location: Tamilnadu, India
Contact:

Re: Possible issue with R103

#23 Post by azure » 28 May 2016, 08:03

I think issues are not with firmware, its because of flash tool.
while flashing we have to erase the total memory including user data in esp before downloading latest firmware.
but, none of the flash tools are doing this.
P.Kannan
Whatsapp: +91-9488557777
HAM CallSign: KD0NER
Echolink: KD0NER

User avatar
beic
Normal user
Posts: 142
Joined: 18 Aug 2016, 18:19

Re: Possible issue with R103

#24 Post by beic » 18 Aug 2016, 18:40

So, is that issue fixed?

tozett
Normal user
Posts: 734
Joined: 22 Dec 2015, 15:46
Location: Germany

Re: Possible issue with R103

#25 Post by tozett » 19 Aug 2016, 09:42

erase flash succesfully reported in this forum from other users:
here ->
http://www.esp8266.nu/forum/viewtopic.p ... 1732#p8014
and
http://www.esp8266.nu/forum/viewtopic.p ... lash#p8055

Post Reply

Who is online

Users browsing this forum: Semrush [Bot] and 40 guests