Network disconnects since updating to 2079 FW

[Resthome]

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...?

WB

Seems what needs to be looked at is what it is using for login credentials. I'm pretty sure that the information/data between the Classic and MyMidnite is encrypted as I believe that has been mentioned in the forums. I would have to guess it has to be the Device ID and/or the MAC address that has to match your MyMidnite account information. But that's only a wild guess since that what the MyMidnite accounts are set up with. Have you double checked those entries? What Browser are you using?

Looks like it knows about Serial number also and I don't remember entering that it might have be read from the Classic at one time.

Another tidbit since I believe you are on Satellite. •Slow networks. The Classic does not require a high-bandwidth network connection; however, it does require a fairly low-latency one. By doing a speed test, you should be able to check the ping speed. If this is much greater than 100ms or so then you might have trouble accessing MyMidNite.

Some more information from MyMidnite FAQ for what it is worth.

What is the Device ID anyways?

The device ID is a username, of sorts, to let it be identified by the MyMidNite server. This number is a random value assigned to each classic separately from the Serial Number. The two are separate to make it more difficult for a malicious third party to "guess" a username.

I'm concerned about my privacy and the privacy of my data.

You should be, especially in light of recent events. MyMidNite uses an encrypted channel to authenticate devices and transmit data. The communications channel is secured with a one-time-key which means that the encryption key changes everytime the webserver and device communicate. This makes it very difficult to decrypt communications packets.


I'm currently seeing a message about unable to contact server.

[Westbranch]

thanks John, I'll dig into that tonight when I get out there... like on the 'X files' the truth is out there.... somewhere.

[dRdoS7]

Hi,

As a last resort, before downgrading the FW, I've blocked incoming packets to the Classic in my router. It's logged so I'll see any comms., in theory. See how that goes, find out on the 19th.

dRdoS7

[dRdoS7]

Hi,

As a last resort, before downgrading the FW, I've blocked incoming packets to the Classic in my router. It's logged so I'll see any comms., in theory. See how that goes, find out on the 19th.

dRdoS7

Bugger! Missed the last vital step of blocking on the router, and that was to put it at the TOP of the list, before "Allow All".

Fixed that on the 23rd.

So, got a disconnect on the 22nd, slightly later than scheduled, but that was probably due to losing comms on the 12th, which I thought was the Classic, but in the end needed a router reset.

dRdoS7

[australsolarier]

hello all, just to be pedantic, i timed the actual disconnect time:
(to the status panel via lan)

it is 9 days 22 hours and 46 minutes
give a couple of - or + minutes.

this is with two midnite classics.

for the midnite blokes that are familiar with binary numbers, it possibly might help find out where that timer is situated. yes, the midnite classic has the potential for unlimited possibilities.

[Westbranch]

HI John, as I posted in the other thread, I have replaced my Classic with CL 29032 and got the same result, no comms with the MM2 site, and now waiting for Andrew to let me know what the database host has said as there is a ticket in on my issue.... I did have a few hiccups getting it setup the way I wanted but got those sorted...

You said Another tidbit since I believe you are on Satellite. •Slow networks. The Classic does not require a high-bandwidth network connection; however, it does require a fairly low-latency one. By doing a speed test, you should be able to check the ping speed. If this is much greater than 100ms or so then you might have trouble accessing MyMidNite.


There was a note posted by a new member on Hughes equipment...  I am on Xplornet and they use a Hughes modem...  Darrin mentioned the latency issue so I will see if I can get that info this weekend.

[boB]

hello all, just to be pedantic, i timed the actual disconnect time:
(to the status panel via lan)

it is 9 days 22 hours and 46 minutes
give a couple of - or + minutes.

this is with two midnite classics.

for the midnite blokes that are familiar with binary numbers, it possibly might help find out where that timer is situated. yes, the midnite classic has the potential for unlimited possibilities.

Yes, this observation coincides precisely with what Andrew found to be wrong...  A 64 bit timer that was inadvertently extern'd as a 32 bit timer which counts about 10 days.  New firmware is being tested now that also includes global WB Jr. current limiting.

boB

[dRdoS7]

Hi,

Yes, this observation coincides precisely with what Andrew found to be wrong...  A 64 bit timer that was inadvertently extern'd as a 32 bit timer which counts about 10 days.  New firmware is being tested now that also includes global WB Jr. current limiting.

boB

Excellent, can't wait (but I will).

dRdoS7

[zoneblue]

Whoo-oooo. That is awesome news boB.

[zoneblue]

FWIW i get the same!

Code Select Expand


[2016-01-19 15:13:04] - Socket successful
[2016-01-19 15:13:05] - Modbus read error
[2016-01-19 15:13:06] - Creating socket...
[2016-01-19 15:13:23] - Socket successful //<-----
[2016-01-29 13:57:49] - Modbus read error
[2016-01-29 13:57:50] - Creating socket...
[2016-01-29 13:57:50] - Socket successful
[2016-01-29 13:57:51] - Modbus read error
[2016-01-29 13:57:52] - Creating socket...
[2016-01-29 13:57:52] - Socket successful


19/01/2016 15:13 less  29/01/2016 13:57   
Is  9.94752315    days
Or 9 days 22 hours 44 minutes and 26 seconds... exactly.

Sure, in reconnects, but doesnt hold that connect for more than a second each time. My connect log is now 11086895 lines long, yeah thanks Andrew lets be fixing that

hello all, just to be pedantic, i timed the actual disconnect time:
(to the status panel via lan)

it is 9 days 22 hours and 46 minutes
give a couple of - or + minutes.

this is with two midnite classics.

for the midnite blokes that are familiar with binary numbers, it possibly might help find out where that timer is situated. yes, the midnite classic has the potential for unlimited possibilities.

[dRdoS7]

Hi,

Yes, this observation coincides precisely with what Andrew found to be wrong...  A 64 bit timer that was inadvertently extern'd as a 32 bit timer which counts about 10 days.  New firmware is being tested now that also includes global WB Jr. current limiting.

boB

Excellent, can't wait (but I will).

dRdoS7

Apparently I couldn't after all, so I updated.

dRdoS7

[zoneblue]

Are you saying theres a beta out?

[Halfcrazy]

Yes but it is VERY beta.

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

[ClassicCrazy]

Yes but it is VERY beta.

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

In case anyone is wondering what's new in it
2-15-2016      Version 2096

         Added Register 4406, ADDRESS 4405 that allows  global battery
         current limit via Whizbang Junior.  WbJrGlobalLimitIRef
         Set WbJrGlobalLimitIRef to MAXIMUM wanted battery charge
         current (times 10 because this number includes 10ths of an amp)
         For example, 123.4 amps would be 1234.  Default is 3000 amps         

3-27-2016      Main app version 2096 (no change)
         Networking code version 2097 fixes a 10 day Ethernet disconnect issue
         No MNGP changes yet.

[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