Network disconnects since updating to 2079 FW

[Resthome]

Yes but it is VERY beta.

http://bob.midniteftp.com/MidNiteSolarUpdate_2096_3-27-2016_v5.02.exe

Must not be the Windows 10 version since Classic didn't seem to recognize it - although I didn't mess around making sure the port was still set up okay.
Larry

The actual CTL files would have to be put in the Firmware folder of the Win10 Classic Programmer for this to work with the existing Win 10 loader. Sure wish what ever new loader Midnite is working on for Win10 would be made available sooner that later. Since there appears to be an issue with MNGP updates.

Since this update doesn't have any changes for the MNGP it appears you would have to modify the registers to have the limits work as the default appears to be set at a max value. Seems this might be a work in progress, except for the 10 day network reset.

[Halfcrazy]

That is correct this is a Classic only update after 2079 but as with 2079 you MUST do a VMM

[ClassicCrazy]

Yes but it is VERY beta.

http://bob.midniteftp.com/MidNiteSolarUpdate_2096_3-27-2016_v5.02.exe

Must not be the Windows 10 version since Classic didn't seem to recognize it - although I didn't mess around making sure the port was still set up okay.
Larry

The actual CTL files would have to be put in the Firmware folder of the Win10 Classic Programmer for this to work with the existing Win 10 loader. Sure wish what ever new loader Midnite is working on for Win10 would be made available sooner that later. Since there appears to be an issue with MNGP updates.

Since this update doesn't have any changes for the MNGP it appears you would have to modify the registers to have the limits work as the default appears to be set at a max value. Seems this might be a work in progress, except for the 10 day network reset.

Thanks for the info - I put the ctl files into windows 10 uploader and it all went okay.
I am guessing that the uploader will always select the newest files , even if others are there ? I had deleted the old ones just to make sure though .
Also updated the MNGP even though it was the same file . Then did VMM and restored my setpoints with Local Status App - all good so far.
Firmware:     
- Classic Rev: 2096
- Network Rev: 2097

Larry

[Resthome]

Larry..

Glad to see it work Larry. Now wait for 10 days and see if you get any disconnects. 

[ClassicCrazy]

I hadn't noticed the disconnect problem on Mymidnite  since I had turned on auto reset at midnight . I suppose I could turn that off again to test it out.

Larry

[dRdoS7]

Hi,

Larry..

Glad to see it work Larry. Now wait for 10 days and see if you get any disconnects. 

I don't know about Larry, but I've not had the "10 Day" disconnect. It's been > 11 days since my last confession, sorry, update to 2096.

Hooray!!!

Many thanks to the tireless worker/s who fixed this.

dRdoS7

[ClassicCrazy]

I have been having dropouts on MyMidnite since I updated to 2096  - I just posted in MyMidnite  section about it .
http://kb1uas.com/mnsforum/index.php?topic=3178.new#new

Larry

[ClassicCrazy]

I have been having dropouts on MyMidnite since I updated to 2096  - I just posted in MyMidnite  section about it .
http://kb1uas.com/mnsforum/index.php?topic=3178.new#new

Larry

I just went back to 2079. I noticed on 2096 version that ending amps didn't seem to be working - the other day it never shut off until the Absorb timer timed it out . I had that set for 7 hours and you can see from the graph that system amps had leveled out long before that and had also reached 100% SOC long before that . I had ending amps set for 2.2 amps and there was minimal load on the system at the time.
It went into absorb about 8:15 and into absorb about 15:12 according to MyMidnite plot below
Larry

[Resthome]

Well no change in the Local App disconnects with Network 2097 firmware as I had suspected since I had tried this when it was Alpha that Andrew had posted. So since Zoneblue has said that it has resolved his network issues what can it be? It sure isn’t my network as I have eliminated that by making a direct Ethernet connection to the Classic from my laptop. Since the laptop has no other Ethernet disconnect issues my money is now leaning toward the way the Local App handles the connection. So the network fix is not fixed for  the Local App with Network 2097 firmware seems to love to disconnect trying to export Offline data.

Are we ever going to see a fix for these Local App disconnects? I don't have internet connections on the boat netwok the only think on that network is the Classic and my laptop. So a fix for MyMidnite doesn't do me any good.

[Westbranch]

RH, I have only downloaded data a few times, and I remember once that it crashed while trying to 'get' at/to the data before it could be downloaded,  using a W7 machine over LAN at the cabin. 

My theory?  The problem is in the LApp code...

I have been using Grahams Android LApp app, works like a charm, just does not have the graphing of multiple units,  A and V to battery is my usual combo to watch for entering Absorb and Float...

[Resthome]

I have been having dropouts on MyMidnite since I updated to 2096  - I just posted in MyMidnite  section about it .
http://kb1uas.com/mnsforum/index.php?topic=3178.new#new

Larry

I just went back to 2079. I noticed on 2096 version that ending amps didn't seem to be working - the other day it never shut off until the Absorb timer timed it out . I had that set for 7 hours and you can see from the graph that system amps had leveled out long before that and had also reached 100% SOC long before that . I had ending amps set for 2.2 amps and there was minimal load on the system at the time.
It went into absorb about 8:15 and into absorb about 15:12 according to MyMidnite plot below
Larry

Larry, just tried 2096 and WBjr end amps is working for me. I had to check the check box in the LA to use end amps with WBjr after the VMM. It was unchecked aced the VMM.

[Resthome]

RH, I have only downloaded data a few times, and I remember once that it crashed while trying to 'get' at/to the data before it could be downloaded,  using a W7 machine over LAN at the cabin. 

My theory?  The problem is in the LApp code...

I have been using Grahams Android LApp app, works like a charm, just does not have the graphing of multiple units,  A and V to battery is my usual combo to watch for entering Absorb and Float...

Yeah I use Graham's app also but I like the LA data because it is at 2 sec resolution so you can spot unusual behavior.  But yeah I am suspecting the LA on the data export that uses mod us FTP to dump the data although today I was seeing disconnects just sitting in the status window of the LA it always reconnects and never have to reboot the Classic but you have to click OK to acknowledge the disconnect and then view and you go back to the status window rather than where you where.

[zoneblue]

RH,

The BB connection log confirms the connection has remained up since april 18. So the classic is just fine.

A clue might be how 2079 behaved in blackbox v local app.  2079 with its ten day bug, reportedly disconnected from the local app on the ten day mark and didnt reconnect by itself. Where as on blackbox, while the connection did close it was able to create a new one and keep going. So, yeah local app id say is the issue there.

So since Zoneblue has said that it has resolved his network issues what can it be? It sure isn’t my network as I have eliminated that by making a direct Ethernet connection to the Classic from my laptop. Since the laptop has no other Ethernet disconnect issues my money is now leaning toward the way the Local App

[Resthome]

RH,

The BB connection log confirms the connection has remained up since april 18. So the classic is just fine.

A clue might be how 2079 behaved in blackbox v local app.  2079 with its ten day bug, reportedly disconnected from the local app on the ten day mark and didnt reconnect by itself. Where as on blackbox, while the connection did close it was able to create a new one and keep going. So, yeah local app id say is the issue there.

So since Zoneblue has said that it has resolved his network issues what can it be? It sure isn’t my network as I have eliminated that by making a direct Ethernet connection to the Classic from my laptop. Since the laptop has no other Ethernet disconnect issues my money is now leaning toward the way the Local App

I believe the 10 day disconnect was associated with My Midnight. I never had the Local App stay connected for any where near 10 days let along a day. But the symptoms seem to be the same as with the BB closing and then recreating a new connection. Wonder why it got fixed for he BB with 2096 and not for the Local App? Don't think any work is being don on the LA at this time and AIR updates do not seem to correct it.

[ClassicCrazy]

I have been having dropouts on MyMidnite since I updated to 2096  - I just posted in MyMidnite  section about it .
http://kb1uas.com/mnsforum/index.php?topic=3178.new#new

Larry

I just went back to 2079. I noticed on 2096 version that ending amps didn't seem to be working - the other day it never shut off until the Absorb timer timed it out . I had that set for 7 hours and you can see from the graph that system amps had leveled out long before that and had also reached 100% SOC long before that . I had ending amps set for 2.2 amps and there was minimal load on the system at the time.
It went into absorb about 8:15 and into absorb about 15:12 according to MyMidnite plot below
Larry

Larry, just tried 2096 and WBjr end amps is working for me. I had to check the check box in the LA to use end amps with WBjr after the VMM. It was unchecked aced the VMM.

I went back to the 2079 firmware and auto reset at midnight . Since then I haven't had any more the the random dropouts on MyMidnite .  I did change my ending amps setting also- maybe due to seasonal or battery age I noticed that it was charging too long after the amps leveled off ( and long after SOC went 100%) . Now everything is working fine . I will wait until 2096 or whatever has the newest features added on MNGP before I upgrade firmware again.
Larry