Hi,
I updated my Classic 200, about end Nov, to 2079. I was happy with the existing FW, but due to the old MyMidnite being shutdown in Feb, thought I should do it. I don't use MM much, just when we're away from our house for more than a week or so.
A few days after the update I had no LA data.
Since the update I've a total of 3 disconnects, LA & MM get nothing.
The last 2 have happened after 10 days each time.
I have to reboot the Classic to get network connection.
I haven't any problem with other LAN devices, so must be the 200. Plus, it was rock solid prior to the update.
The Classic otherwise is running fine.
Any ideas?
Thanks,
dRdoS7
Since I did that update I have had to restart my Classic a couple times too . And like you mentioned - the previous firmware never did that.
The Local Status app also seems to be a bit fussier about making the connection too.
Larry
Hi,
Quote from: ClassicCrazy on January 09, 2016, 07:47:47 PM
Since I did that update I have had to restart my Classic a couple times too . And like you mentioned - the previous firmware never did that.
The Local Status app also seems to be a bit fussier about making the connection too.
Larry
Guess we need your brother Half to pop by!
dRdoS7
Ryan calls the shots AFAIK....More like you need Andrew, he built the data base and keeps it going, just that he is in Europe... so a 8 hr +- delay...
Because of the winter I haven't updated to this latest firmware. But it sounds like some of the existing network connections problem persist with this new version that was suppose to resolve the the network disconnects. If that is the case it is disappointing that this bug has existed for so long.
Hopefully others will weigh in with their results good or bad with regards to this issue both with the LA and MM.
What I am hearing is that evidently when the Local App stops talking with 2079 that there is another piece of
software that will continue to work and talk with the Classic instead of the LA. I think that there is a version
of that software (Karl's) on this site but don't know where right at the moment. This is PC software and not
code for Android or iPhone. Can't remember the name right off but uses modbus over TCP/IP.
Happy new year ! But not as happy as it would be if this problem didn't' still exist.
boB
Andrew is tracking this down, What it seems like is that My MidNite is sending back a corrupt packet and that kills the network stack in the Classic. I can confirm this IS related to My Midnite and those not using My Midnite seem to be reporting 2079 as perfectly stable on the TCP/IP connection
Quote from: Halfcrazy on January 10, 2016, 08:58:16 AM
Andrew is tracking this down, What it seems like is that My MidNite is sending back a corrupt packet and that kills the network stack in the Classic. I can confirm this IS related to My Midnite and those not using My Midnite seem to be reporting 2079 as perfectly stable on the TCP/IP connection
Ryan, both ClassicCrazy and dRdoS7 have reported connections problem with the Local App above. Hopefully those that don't have problems as well as those that do will report their results here on both the LA and MM. Some folks just don't really use the LA. So it would be nice to know what they use and don't use. A more scientific survey on whether the Ethernet connection problems have been resolved for both the Local App and MyMidnite would be great.
Once El Nino fills up our lakes I'll be able to update to the latest firmware and report my own results.
Hi,
It looks as though it was 3 times it reset with 10 day intervals, I hadn't scrolled back far enough in MM. The new MM is "slightly" different to the MM I'm used to.
Next "event" is due about 20th Jan.
dRdoS7
I dont use MM, and only occasionally use the LA (configuration), but the blackbox runs on a very similar basis to the LA (persistant / blocking modbus over ethernet connection) and at a more aggressive timing rate, (1s instead of 2s). Since 2074/2079, the connection has given zero issues either disconnects, or resets. Thus im confident that the core stack is now fixed. However what the LA and MM contribute to all this i couldnt say.
Zb,
I would have to agree with that. Upfirmwared a C150 to 2709 a few weeks ago using W10 (that was an 'interesting' exercise) and using a DUE to extract limited registers every <1s over tcp AND it has run very problem free.
Judging by how quickly the gauges refresh I'd say every half second register readings.
No delays, hiccups, hangups, weird things etc.
I do not open/close the connection, it just stays open, 26 days and counting... Don't use MyMN or LA.
dgd
Quote from: dgd on January 11, 2016, 03:20:28 PM
Zb,
I would have to agree with that. Upfirmwared a C150 to 2709 a few weeks ago using W10 (that was an 'interesting' exercise) and using a DUE to extract limited registers every <1s over tcp AND it has run very problem free.
Judging by how quickly the gauges refresh I'd say every half second register readings.
No delays, hiccups, hangups, weird things etc.
I do not open/close the connection, it just stays open, 26 days and counting... Don't use MyMN or LA.
dgd
What SWare you using dgd ? Is web access enabled or off ?
My $$ is on the latest Black Box variant (ie. 'DUE')
FW 2079 : I rarely log into MM. Often I check into the LA a few times a day to get a reading and then leave it in the background on my macbook air. Other times I use the third-party Android app, which works quite well. I haven't noticed any issues with 2079. The only downside (to myself) is that you are only able to have one connection at a time. Either the LA on one computer but not multiples or the android app.
Is it possible to eventually have multiple connections?
Mymidnite quit reporting my system yesterday at about 11:15 am central time - in an auto equalize cycle. I won't be able to get out and check if it is also locked up for Local Status app connections or if it is an internet problem on my end until the weekend.
I also reported it on the mymidnite contact form in case it was something that needs to be looked at on Midnite end .
Larry
Hi,
Quote from: ClassicCrazy on January 13, 2016, 11:01:32 AM
Mymidnite quit reporting my system yesterday at about 11:15 am central time - in an auto equalize cycle. I won't be able to get out and check if it is also locked up for Local Status app connections or if it is an internet problem on my end until the weekend.
I also reported it on the mymidnite contact form in case it was something that needs to be looked at on Midnite end .
Larry
Think that it is MM, according to this:
Quote from: Halfcrazy on January 10, 2016, 08:58:16 AM
Andrew is tracking this down, What it seems like is that My MidNite is sending back a corrupt packet and that kills the network stack in the Classic. I can confirm this IS related to My Midnite and those not using My Midnite seem to be reporting 2079 as perfectly stable on the TCP/IP connection
Only 6 days 'til the next one!
If/when it happens again, I'll remove mine from MM.
dRdoS7
boB,
I'm using Arduino DUE with code compiled on Arduino IDE1.6.6 C++ compiler with ethernet modbus library MgsModbus-v0.1.1 working as Modbus master.
27 Days tcp connection to Classic #6191, FW 2079, no problems so far. :)
On W10 laptop also just testing HTML5 code for gauge display with jquery-1.4.2.min.js-tk-modbus to connect to Classic for 1 second limited-register-set readings.
Uptime 3 days, Classic #1779, FW 2079
I dont think I changed the test Classics setup to enable web access, I though that only applied when MyMN is being used.
dgd
I have three classic 150 that I upgraded to 2079. Two are set to auto reset at night and one that is used for wind mode isn't. I had no problems using the local app before upgrading. since the upgrade the one that doesn't reset at night keeps losing communication and I have to reset it before it will communicate again.
Hi,
Quote from: dmclain on January 14, 2016, 11:41:48 AM
I have three classic 150 that I upgraded to 2079. Two are set to auto reset at night and one that is used for wind mode isn't. I had no problems using the local app before upgrading. since the upgrade the one that doesn't reset at night keeps losing communication and I have to reset it before it will communicate again.
How often?
Are you using MM?
dRdoS7
Are most forum users utilizing the auto reset on midnight function in the Classic? Especially those that have remote setups where they are not around for extended periods?
Cloud
I think I had the auto reset on mine - but I will have to check it next time I get out there .
Auto reset , off grid - YES, YES...
Quote from: Cniemand on January 14, 2016, 11:54:49 PM
Are most forum users utilizing the auto reset on midnight function in the Classic? Especially those that have remote setups where they are not around for extended periods?
Cloud
I have Auto Reset ON with my system as it is unattended except for a few hour visit once ever 7 weeks from Nov-March. I download the daily logs to check HI Battery readings and Float time to make sure thinks are working well. Check the S/G and battery water.
Quote from: dgd on January 13, 2016, 06:58:04 PM
boB,
I'm using Arduino DUE with code compiled on Arduino IDE1.6.6 C++ compiler with ethernet modbus library MgsModbus-v0.1.1 working as Modbus master.
27 Days tcp connection to Classic #6191, FW 2079, no problems so far. :)
On W10 laptop also just testing HTML5 code for gauge display with jquery-1.4.2.min.js-tk-modbus to connect to Classic for 1 second limited-register-set readings.
Uptime 3 days, Classic #1779, FW 2079
I dont think I changed the test Classics setup to enable web access, I though that only applied when MyMN is being used.
dgd
Thanks DGD. So your own software. Good to know.
Keeping web access OFF should help I think. Maybe later you can turn it ON and see if you experience disconnects.
Or not.
boB
John, do you come across issues with lack of regular cycling? Sulphation. more EQ needed?
Cloud
Quote from: Cniemand on January 16, 2016, 03:26:30 PM
John, do you come across issues with lack of regular cycling? Sulphation. more EQ needed?
Cloud
Haven't notices any and they are now in their 6 year of operation. I got 15 years out of the last set and they were way undercharged because of my old set up. That got revamped in 2010. I do have the Classic in skip mode skipping 4 days. That has worked out last year because we had little rain and little clouds. A little different this year with the storms coming in every few days. They get a good loading in the spring, summer, fall (March-1st of Nov) running a 1/3HP DC swamp cooler about 12 hrs a day along with all the other gadgets.
Quote from: dRdoS7 on January 14, 2016, 05:13:29 PM
Hi,
Quote from: dmclain on January 14, 2016, 11:41:48 AM
I have three classic 150 that I upgraded to 2079. Two are set to auto reset at night and one that is used for wind mode isn't. I had no problems using the local app before upgrading. since the upgrade the one that doesn't reset at night keeps losing communication and I have to reset it before it will communicate again.
How often?
Are you using MM?
dRdoS7
I am using MM2 and I have to reset the one classic about once a week.
Quote from: ClassicCrazy on January 13, 2016, 11:01:32 AM
Mymidnite quit reporting my system yesterday at about 11:15 am central time - in an auto equalize cycle. I won't be able to get out and check if it is also locked up for Local Status app connections or if it is an internet problem on my end until the weekend.
I also reported it on the mymidnite contact form in case it was something that needs to be looked at on Midnite end .
Larry
Just got back to check on remote site connections - internet is fine , can't connect with Local Status App with computer either . The MNGP is fully functional . Checked and Auto Reset was off - I just set it to on and will wait to see if the reset at midnight tonight will get network working again without me having to reset the power to the Classic.
Larry
QuoteJust got back to check on remote site connections - internet is fine , can't connect with Local Status App with computer either . The MNGP is fully functional . Checked and Auto Reset was off - I just set it to on and will wait to see if the reset at midnight tonight will get network working again without me having to reset the power to the Classic.
The Auto Reset last night fixed the network issue and mymidnite v2 is reporting again. I thought I had that enabled already but must have gotten turned off somewhere along the way.
Larry
Quote from: ClassicCrazy on January 17, 2016, 12:04:12 PM
QuoteJust got back to check on remote site connections - internet is fine , can't connect with Local Status App with computer either . The MNGP is fully functional . Checked and Auto Reset was off - I just set it to on and will wait to see if the reset at midnight tonight will get network working again without me having to reset the power to the Classic.
The Auto Reset last night fixed the network issue and mymidnite v2 is reporting again. I thought I had that enabled already but must have gotten turned off somewhere along the way.
Larry
AhA ! I guess there IS some good in forgetting some things.
boB
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
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.
Quote from: phxmark on January 19, 2016, 11:46:33 PM
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
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.
Hi,
Quote from: dRdoS7 on January 19, 2016, 09:59:30 PMI'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
Hi,
Quote from: dRdoS7 on February 11, 2016, 06:31:45 PM
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. :D
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
Quote from: dRdoS7 on February 28, 2016, 05:16:03 PM
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 :o
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
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
Quote from: dRdoS7 on March 09, 2016, 06:46:05 AM
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
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.
Hi,
Quote from: ClassicCrazy on March 09, 2016, 09:00:36 AM
Quote from: dRdoS7 on March 09, 2016, 06:46:05 AM
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
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
Quote from: australsolarier on March 10, 2016, 06:28:08 PM
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
Quote from: australsolarier on March 10, 2016, 06:28:08 PM
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
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...????
Quote from: Westbranch on March 11, 2016, 11:54:41 AM
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.
thanks John, I'll dig into that tonight when I get out there... like on the 'X files' the truth is out there.... somewhere.
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
Hi,
Quote from: dRdoS7 on March 11, 2016, 05:10:04 PMAs 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
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.
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.
Quote from: australsolarier on March 23, 2016, 09:33:44 PM
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
Hi,
Quote from: boB on March 24, 2016, 03:43:54 AMYes, 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
Whoo-oooo. That is awesome news boB.
FWIW i get the same!
[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 ;)
Quote from: australsolarier on March 23, 2016, 09:33:44 PM
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.
Quote from: dRdoS7 on March 24, 2016, 05:43:16 PM
Hi,
Quote from: boB on March 24, 2016, 03:43:54 AMYes, 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. :o
dRdoS7
Are you saying theres a beta out?
Yes but it is VERY beta.
http://bob.midniteftp.com/MidNiteSolarUpdate_2096_3-27-2016_v5.02.exe (http://bob.midniteftp.com/MidNiteSolarUpdate_2096_3-27-2016_v5.02.exe)
Quote from: Halfcrazy on March 31, 2016, 06:58:53 PM
Yes but it is VERY beta.
http://bob.midniteftp.com/MidNiteSolarUpdate_2096_3-27-2016_v5.02.exe (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.
Quote from: Halfcrazy on March 31, 2016, 06:58:53 PM
Yes but it is VERY beta.
http://bob.midniteftp.com/MidNiteSolarUpdate_2096_3-27-2016_v5.02.exe (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
Quote from: ClassicCrazy on April 01, 2016, 12:10:09 AM
Quote from: Halfcrazy on March 31, 2016, 06:58:53 PM
Yes but it is VERY beta.
http://bob.midniteftp.com/MidNiteSolarUpdate_2096_3-27-2016_v5.02.exe (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.
That is correct this is a Classic only update after 2079 but as with 2079 you MUST do a VMM
Quote from: Resthome on April 01, 2016, 01:28:43 AM
Quote from: ClassicCrazy on April 01, 2016, 12:10:09 AM
Quote from: Halfcrazy on March 31, 2016, 06:58:53 PM
Yes but it is VERY beta.
http://bob.midniteftp.com/MidNiteSolarUpdate_2096_3-27-2016_v5.02.exe (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
Larry..
Glad to see it work Larry. Now wait for 10 days and see if you get any disconnects. :D
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
Hi,
Quote from: Resthome on April 01, 2016, 01:02:28 PM
Larry..
Glad to see it work Larry. Now wait for 10 days and see if you get any disconnects. :D
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
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
Quote from: ClassicCrazy on April 21, 2016, 10:38:28 PM
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
(//)
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.
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...
Quote from: ClassicCrazy on April 29, 2016, 11:02:07 AM
Quote from: ClassicCrazy on April 21, 2016, 10:38:28 PM
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.
Quote from: Westbranch on May 11, 2016, 03:07:38 PM
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.
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.
Quote from: Resthome on May 11, 2016, 02:08:25 PM
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
Quote from: zoneblue on May 12, 2016, 05:20:57 AM
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.
Quote from: Resthome on May 11, 2016, 02:08:25 PM
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.
Quote from: Resthome on May 11, 2016, 11:02:16 PM
Quote from: ClassicCrazy on April 29, 2016, 11:02:07 AM
Quote from: ClassicCrazy on April 21, 2016, 10:38:28 PM
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
The ten day issue was in the classic firmware, and was fixed to my satisfaction in 2096. However if we are to define "my satisfaction", it is this:
- maintaining a permanently open single modbus RTU connection
- on a local area network.
AFAIK the local app works in the same manner as BB, ie as above. I have not tested 'open, read, close' in a long time. I suppose i should for the sake of science.