Network disconnects since updating to 2079 FW

[dRdoS7]

Hi,

10 day disconnect happened on schedule.

I'll set it to do a Auto Reset from now on. There was a reason I didn't previously, but I can't remember why. I guess I'll find out soon enough!

dRdoS7

[phxmark]

My Classic has just started the network disconnects. It was working since the upgrade but just started doing this. Funny thing, I can ping it the whole time.

Another thing I noticed, it acts like something is resetting as the time/date is at default and the KWH display is zeroed out when I can connect back to it.

It goes down for about 2 minutes and only stays up about 1 minute.

[boB]

My Classic has just started the network disconnects. It was working since the upgrade but just started doing this. Funny thing, I can ping it the whole time.

Another thing I noticed, it acts like something is resetting as the time/date is at default and the KWH display is zeroed out when I can connect back to it.

It goes down for about 2 minutes and only stays up about 1 minute.

Is "Web Access"  turned ON or OFF (enabled/disabled)  I hear that it may be more stable if WA is off

[phxmark]

Another thing I noticed, it acts like something is resetting as the time/date is at default and the KWH display is zeroed out when I can connect back to it.

It goes down for about 2 minutes and only stays up about 1 minute.
[/quote]

Is "Web Access"  turned ON or OFF (enabled/disabled)  I hear that it may be more stable if WA is off
[/quote]

I actually did a hardware reset to defaults (jumpers) on the unit this morning and reset all the parameters. Seems to be much better now. I did do a VMM (left-right-power on) after the firmware update but this morning I thought just for sheets and grins I will do a full hardware reset. Will see how long it lasts now. WA is on.

[dRdoS7]

Hi,

I'll set it to do a Auto Reset from now on. There was a reason I didn't previously, but I can't remember why. I guess I'll find out soon enough!

I found out why very soon: I use Aux1 on "Diversion", when bat > 54 turn off AC, when bat < 49 turn on AC.

So, the Reset turns Aux1 off before it's necessary, ie. AC On, and it won't go back to bat, even if it's > 49.

I have a relay (NC), on a timer, that interrupts the Aux1 signal to the AC relay (NC) once per day. This is so the inverter won't automatically S/D after the max set time (1440 mins) on bat. I have this for when we aren't home, and could be running off bat for several days.

So, the question is: will the fix be soon, or should I remove my Classic from MM? I'm not pushing, I can live without MM, I use it only rarely and while we're away from home, but it's easier than logging in with TeamViewer to my 24/7 PC server running LA & Inverter SW.

I've already turned "Auto Reset" to Off, and may just remove from MM until the problem is fixed.

Thanks,

dRdoS7

[dRdoS7]

Hi,

I've already turned "Auto Reset" to Off, and may just remove from MM until the problem is fixed.

An quick update:

Removed Classic from MM.

I've had (about - forgot to start a log) 1, or 2 disconnects since removing from MM.

I started a log too.

So, now I've turned off "Web Access", see if that prevents the network failure.

I didn't turn WA off earlier because I thought (wrongly!) that would stop LA getting data.

dRdoS7

[dgd]

I've had (about - forgot to start a log) 1, or 2 disconnects since removing from MM.

So, now I've turned off "Web Access", see if that prevents the network failure.

I didn't turn WA off earlier because I thought (wrongly!) that would stop LA getting data.

I have had FW2079 on two Classics since just after it was released and although I have used the LA a couple of times for fairly quick setup of the AUX controls I do not leave it connected.
Even so, one Classic kept its ethernet working for 34 days until I disconnected it, there was a repeating one second grab of 40 modbus registers for a web page gauge display.
Every day just after midnight the Cubie autoreset its comms, closing and reopening the connection and reloading from SD card. Web Access not enabled, don't use My MM 
It sure appeared to me that the ethernet was stable even though I closely observed what happened (nothing) on 10 days since startup intervals as ZB indicated his link was dropping after exactly 10 days uptime.

So has anyone else tried using any other ethernet utility to connect to the Classic and NOT use the LA?
Does the Android App also see network dropouts?
Has the LA been ruled out as a cause for these dropouts?

dgd

[dRdoS7]

Hi,

Well 10 days, and it's lost network again.

I'm going back to the 1609 FW. I'll have to check, but I think that was the last one I had installed.

dRdoS7

[ClassicCrazy]

Hi,

Well 10 days, and it's lost network again.

I'm going back to the 1609 FW. I'll have to check, but I think that was the last one I had installed.

dRdoS7

Did it do this despite the Auto Reset being turned on ? I haven't had any more lockups on MyMidnite since I turned that on.

Larry

[zoneblue]

Just to clarify, my 2079 classic has now been up 52 days, with 24/7 1s calls, with no reboots of any kind, and no auto reset enabled. What does occur on around the 10th day is that the continuously held modbus RTU connection fails, and the cubie simply closes it and reopens a new connection. That connection then lasts exactly one second, and the process of close and reopen occurs each second. Filling my connect log up right quick.

So while for all practical purposes while it appears to be stable, theres still something that is not quite right. However i much prefer this firmware by a long shot, as it cures the wdt reboots.

[dRdoS7]

Hi,

Hi,

Well 10 days, and it's lost network again.

I'm going back to the 1609 FW. I'll have to check, but I think that was the last one I had installed.

dRdoS7

Did it do this despite the Auto Reset being turned on ? I haven't had any more lockups on MyMidnite since I turned that on.

Larry

I turned AR off (see reason a few posts back - Feb 11th).

The previous FW I had loaded was (mostly) stable. I could leave for months, and monitor it while away either with MM, or LA, via Teamviewer. I'll only be able use LA now, and I'll have a month to make sure it actually is all again OK before we leave.

dRdoS7

[australsolarier]

i can confirm that 10 day disconnect. only rebooting the midnite reables lan connection to the status panel. there is definitively a timer in there that does something after 10 days. it has done it repeatedly on 2 midnites. i wrote down the exact times of the reboots.
very interesting feature in the midnite classic

[dRdoS7]

i can confirm that 10 day disconnect. only rebooting the midnite reables lan connection to the status panel. there is definitively a timer in there that does something after 10 days. it has done it repeatedly on 2 midnites. i wrote down the exact times of the reboots.
very interesting feature in the midnite classic

Very interesting (and unwanted) feature.

Hopefully soon to be removed. Because apart from that, it's fine.

dRdoS7

[TomW]

i can confirm that 10 day disconnect. only rebooting the midnite reables lan connection to the status panel. there is definitively a timer in there that does something after 10 days. it has done it repeatedly on 2 midnites. i wrote down the exact times of the reboots.
very interesting feature in the midnite classic

I have to wonder what else is common in this network system besides The Classic(s)? Routers, hubs / switches, etc may be a problem, too.

I have not upgraded my Classics for a long while as the system is 150 miles north of me and is basically offline with dead batteries as we are trying to sell that place.

At one point long ago I had one ethernet switch that appeared to be at least part of the problem. It was a cheap Wally World (spelled Walmart) Chinese switch.

Just from here.

Tom

[Westbranch]

Tom, I am starting to think it is mainly something in the Classic(s) at leas for me.... as soon as I changed to 2079, we are talking minutes here,  I have not been able to connect, no other changes, I replaced one of the boards and I have even put in a brand new Cl (an new RMA unit) and still no go.... Andrew is trying to get to the bottom of this...  I get a 401 Unauthorized return message..  so the only other part I can not control is the sat internet system, and it worked at the start...?