Strange reset during the day

[boB]

I reset both Classics a few minutes ago and on 200BA94A the hex flags changed from
10043280   to
100432C0   then
10043200
so it seems only a power off/on reset will clear the ..80 flag.  I though this was supposed to clear every day 11:59pm? The MyMN shows it as an Internal reset and really needs to be auto reset at least daily.
the modbus registers are:
04340       0x0012
04341       0xe380
04342       0xf000
04343       0xe121
so these are just the normal power on values. 

I have definitely noticed that since changing to 1401 firmware these random resets are much less frequent

dgd

Those registers  434x  content are default and what come up normally.
No, it does not clear.  You CAN clear it by just resetting that register bit 0x80 though.

Check the registers  434x  when the flags equal   10043280   (or at least the 0x80 bit) and then those
registers should show something different.  When you say change to 1401 firmware, is that BACK TO
1401 from the newer firmware ?   The trick is to catch the numbers after an  10043280  flat setting
so we can see what is going on.

(I can't remember off the top of my head if 1401 is new or old)  (too lazy and going to sleep now)

boB

[dgd]

Firmware 1401 is latest AFAIK.  I will await another random reset then see whats in those 43xx registers

dgd

[RossW]

Firmware 1401 is latest AFAIK.  I will await another random reset then see whats in those 43xx registers

Really really crap day today. Getting around 100W from my 3.6KW arrays... but had a reset.

24/Jun/2013 12:55:01
4131=0x3200  <-- watchdog flag not set.
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121


24/Jun/2013 13:00:02
4131=0x3280   <-- watchdog flag set.
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121


24/Jun/2013 13:05:00
4131=0x3200  <-- watchdog flag reset after earlier condition.
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121


(Basically, I check every 5 mins. If the WD flag is set, I send an SMS alert message to myself, clear the flag, and keep logging.)

[TomW]

Ross;

Good info! I just grepped my rather short 3 days of logs and see no instance of the reset. I was logging to the SD card on the Pi so was clearing them regularly to keep the space free.

With your recent update (.17) I shifted logging to the 32 gig USB stick so should be able to log every couple minutes for a long time without concern for filling the space.

You are not using the Local App are you? I got convinced that it was the Local App causing resets here but it was not exactly a detailed troubleshooting result just an "educated guess".

Tom

[boB]

Firmware 1401 is latest AFAIK.  I will await another random reset then see whats in those 43xx registers

Really really crap day today. Getting around 100W from my 3.6KW arrays... but had a reset.

24/Jun/2013 12:55:01
4131=0x3200  <-- watchdog flag not set.
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121


24/Jun/2013 13:00:02
4131=0x3280   <-- watchdog flag set.
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121


24/Jun/2013 13:05:00
4131=0x3200  <-- watchdog flag reset after earlier condition.
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121


(Basically, I check every 5 mins. If the WD flag is set, I send an SMS alert message to myself, clear the flag, and keep logging.)

Those registers ~SHOULD~ be giving different values, ~IF~ the Classic reset due to a Data Abort like
my unit did.

So, there are two other ways this could happen...

One requires the Auto-Restart be enabled, which should trigger at 23:59  (Midnight)
I think that we already went over this one and your A-RST was NOT enabled and
also your clock is correct.

The other way this could happen is if the Classic got stuck in a ~normal~ loop
for 5.0 seconds or more...   (I try not to do moderately long loops but sometimes ya gotta)

I will look into the "other" way now.  The timing profiles I have done, which are very
accurate, have never been anywhere near 5 seconds long so I must look harder now !

Maybe your EEprom is hanging up or something ?  I'll start there.

I'm still in Germany so will start looking in a couple of days.

Thanks for the info !  This is exactly the type of thing I needed to know !

boB

[dgd]

just started MyMinite and it shows internal reset on my Classic 250,  9CF96252, fw 1401,  modbus registers same as before:

04340       0x0012
04341       0xe380
04342       0xf000
04343       0xe121

so it would seem whatever is causing this reset in not being detected by the watchdog monitoring that reports info to these registers.

dgd

[RossW]

Thanks for the info !  This is exactly the type of thing I needed to know !

Just happened again - I wish I had some time to stop and look, but its not going to happen in the next week or so!

25/Jun/2013 10:30:00
4131=0x3200
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121

25/Jun/2013 10:35:02
4131=0x3280
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121

[boB]

Thanks for the info !  This is exactly the type of thing I needed to know !

Just happened again - I wish I had some time to stop and look, but its not going to happen in the next week or so!

25/Jun/2013 10:30:00
4131=0x3200
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121

25/Jun/2013 10:35:02
4131=0x3280
4341=0x0012
4342=0xe380
4343=0xf000
4344=0xe121

Yeah, unless I'm missing something, it's stuck in a loop and timing out the WDT.
I'll get it now.   The hardest part is duplicating YOUR problem !

I may be making some special software to try, Ross.  Others may also need to try it.

I may also add to that special software, a WDT enable/disable bit just for you to
try out.  I don't want that to be a permanent option though because if it really does
crash, you want the Classic to reset gracefully.

Ross, did you ever try your Classic for a couple of days without the Ethernet connected to
see if it still resets ?   Anybody else try that ?    DGD ?

DGD..... " shows internal reset on my Classic 250,  9CF96252, fw 1401,"

Is  "9CF96252"  your ID or the flags register on My Midnite ?  If flags, it is not
showing a WDT reset.

ONE more thing...  Has anybody noticed if the Classic ever resets while is is "Resting"
Is it ALWAYS running and charging when you notice it ?  I don't suppose people are going
to stare at a Classic while is is Resting, but they might notice that the kW-Hours went to
zero before 23:59  and after the sun went down.

boB

[dgd]

I may also add to that special software, a WDT enable/disable bit just for you to
try out.  I don't want that to be a permanent option though because if it really does
crash, you want the Classic to reset gracefully.

Ross, did you ever try your Classic for a couple of days without the Ethernet connected to
see if it still resets ?   Anybody else try that ?    DGD ?

I have a Classic 150 at an isolated location and its not ethernet connected. No random reset, ever.  There is a new broadband link being installed there next week and then the Classic will be network connected and fwupdated to latest. It will be interesting to see if it starts getting these random resets.

DGD..... " shows internal reset on my Classic 250,  9CF96252, fw 1401,"

Is  "9CF96252"  your ID or the flags register on My Midnite ?  If flags, it is not
showing a WDT reset.

Sorry thats just the Classic ID.

ONE more thing...  Has anybody noticed if the Classic ever resets while is is "Resting"
Is it ALWAYS running and charging when you notice it ?  I don't suppose people are going
to stare at a Classic while is is Resting, but they might notice that the kW-Hours went to
zero before 23:59  and after the sun went down.

Yes, this has happened, reset after dark while resting,  sets KW/hr to zero and then at 11:59 logs show energy for day was zero.

dgd

[RossW]

I'll get it now.   The hardest part is duplicating YOUR problem !

Yeah, I get special problems

I may also add to that special software, a WDT enable/disable bit just for you to
try out.  I don't want that to be a permanent option though because if it really does
crash, you want the Classic to reset gracefully.

Agreed.

Ross, did you ever try your Classic for a couple of days without the Ethernet connected to
see if it still resets ?

I'm still trying to get to it. Been stupid busy and not likely to be any less so for at least another 10 days.

ONE more thing...  Has anybody noticed if the Classic ever resets while is is "Resting"
Is it ALWAYS running and charging when you notice it ?  I don't suppose people are going
to stare at a Classic while is is Resting

I don't have to. I've got a script monitoring it all the time, collecting and logging data.
And examining the WD-RESET bit. If that bit is set, it sends me an email, and a text message immediately.
It then resets the WD-RESET bit and resumes monitoring. I've never had one when there hasn't been at least some sun.
Doesn't mean it can't happen, but I've not witnessed one. (out of about 30 resets, 100% have been during "charging" time)

[boB]

DGD said...    "I have a Classic 150 at an isolated location and its not ethernet connected. No random reset, ever.  There is a new broadband link being installed there next week and then the Classic will be network connected and fwupdated to latest. It will be interesting to see if it starts getting these random resets."

I need a bit more information.  Has "THAT" particular unit reset when it was plugged into Ethernet ??

To troubleshoot this, I need a Classic that is resetting when plugged into Ethernet/Internet to be
unplugged from Ethernet/Internet to see if it is the Ethernet or something else.

I think that only TomW has actually done this.

RossW, your connection that monitors all the time and emails you "IS" connected so that
does not count as being disconnected I don't think.  You would have to watch it just
once in a while to see if it resets or not when disconnected.  If you let it sit for a day
unconnected and then either look at it to see that it did not reset its kW-Hours
and THEN BRIEFLY connect to it to read the 4131 register to see if it did a WDT reset,
that is what we need to see I think.

boB  (boarding the plane now in Munich)

[dogfox]

Just wanted to report in..

Since I DISabled 'web access', I have not had a reset that I could detect.  My arduino logger has not picked up any turbine voltage spikes that would illustrate a reset (because
I am currently running my dump load off of aux2 and aux2 would not work if the classic was resetting-allowing a spike).

I initially thot that current surges were playing a part but we have had numerous wind events where gusts would produce current surges of up to 600w and no probs.

Thanks again for looking into this.



 

[justmeleep]

ONE more thing...  Has anybody noticed if the Classic ever resets while is is "Resting"
Is it ALWAYS running and charging when you notice it ?  I don't suppose people are going
to stare at a Classic while is is Resting, but they might notice that the kW-Hours went to
zero before 23:59  and after the sun went down.

boB

Yes!  I was out fiddling around in the garage (where the Classic is) late one evening and noticed that it had suddenly reset the kwh back to zero, and I'd noticed that it had a kwh hour value (total) for the day just before that.

Keeping with the theme here, I have not, however, noticed a reset unless the classic is on-line/connected (ethernet cabled).  It does seem to be remarkably random.  I've seen it do it two or three times in a single day, and I've had it go a week or two without doing it...

Lee.

[boB]

ONE more thing...  Has anybody noticed if the Classic ever resets while is is "Resting"
Is it ALWAYS running and charging when you notice it ?  I don't suppose people are going
to stare at a Classic while is is Resting, but they might notice that the kW-Hours went to
zero before 23:59  and after the sun went down.

boB

Yes!  I was out fiddling around in the garage (where the Classic is) late one evening and noticed that it had suddenly reset the kwh back to zero, and I'd noticed that it had a kwh hour value (total) for the day just before that.

Keeping with the theme here, I have not, however, noticed a reset unless the classic is on-line/connected (ethernet cabled).  It does seem to be remarkably random.  I've seen it do it two or three times in a single day, and I've had it go a week or two without doing it...

Lee.

Lee, this is good information.
I wonder though if you haven't seen it reset while the Ethernet was unplugged because the Ethernet is
normally plugged in and it hasn't had a chance to reset ?

Another question...   What do you remember about the battery voltage and loads on the battery when
it was resetting during the day ?  Do you have any other charging sources going into that battery bank ?

boB

[justmeleep]

Lee, this is good information.
I wonder though if you haven't seen it reset while the Ethernet was unplugged because the Ethernet is
normally plugged in and it hasn't had a chance to reset ?

Another question...   What do you remember about the battery voltage and loads on the battery when
it was resetting during the day ?  Do you have any other charging sources going into that battery bank ?

boB

It is possible that I haven't seen it because the ethernet is normally connected.  I have seldom disconnected it, since I first got it to work.  I do have the classic reset itself every night, and occasionally will lose connectivity for a day, or whatever, but other than that, it's almost always connected.  I've just lived with the re-sets.  Lately, mymidnite has said it's undergoing "maintenance" so  I've wondered if I should just unplug it, at least when I'm not home and not accessing it that way either (like is the case right now - my house (and charge controller) is in one state, and I'm in another).  I really like the information I get on mymidnite, when I get it, which is why I've lived with it.  On the other hand, I haven't seen a random reset at all, in weeks (knocking loudly on wood ).

I do not have any other charging sources going into my classic, other than the solar panels on my roof (currently a supposed 2k worth - 8 250watt panels - 4 more are on order).  I do have a load on the battery bank - like my fridge, freezer, all of my computers, and I have it set to where if the battery voltage is high enough it also turns on a (portable) air conditioner, with the "excess power").  So, my load varies, but it always available - I try not to let potential solar power go to waste.  This does cause the battery voltage to vary, both with the load, and of course with sun conditions.  And, it does seem like I've seen more resets when that is exactly what is happening, than when the sun is constant, and the load is as constant as it gets.

I hope this is useful/helpful information to know,

Lee.