http://www.midnitesolar.com/firmwareReport.php?firmware_ID=17&firmwareProduct_ID=1&act=edit
So this code does 3 things above and beyond production code 2056:
1- Better network code (Much More stable)
2- Supports MMv3
3- Fixes a bug in Auto EQ (1 of 3)
To use MM v3:
address for MM ver 3 is https://159.203.65.201 (https://159.203.65.201)
you need to put JUST the IP 159.203.65.201 in the dns over ride on the classic, Save it and reboot it.
Please report ANY classic oddities to me, And also please poke around MM v3 and report any errors to me either here on this thread or by email
Thank you
Ryan
Will give it a try soon as I can even though my Symantec antivirus didn't like that I just downloaded it ! Guess they don't understand solar.
Quote from: ClassicCrazy on November 03, 2015, 11:26:31 AM
Will give it a try soon as I can even though my Symantec antivirus didn't like that I just downloaded it ! Guess they don't understand solar.
Was it the .exe file you downloaded that it didn't like ?
BTW, I ran that file through https://www.virustotal.com/
which tries pretty much all of the anti-virus softwares you would want and only
3 of them came up with something... Not Norton or Symantec though so not
sure what's up with that. These are false positives of course, like build 2055 or 2054
showed up as. Pretty darn strange if you ask me.
boB
PS, I understand that sometimes AV software just makes things hard for you to install but I am not
sure why they should do that if they don't think that file contains a virus ?
This is what it said Bob.
(//)
I'll lay my money on: since it is NEW and want to MAKE CHANGES to you hard drive and there is NO HISTORY on it to speak of , the default path is ''it must be a virus''... hyper caution
I got a quick-to-defeat message, from AVG that V. 2054 was suspicious... just accepted install and off it went...
Weird that your Symantec checks different than the one in Virustotal ?
Either way, it's a false alarm.
Quote from: boB on November 03, 2015, 04:14:12 PM
Weird that your Symantec checks different than the one in Virustotal ?
Either way, it's a false alarm.
It's also unsigned so Norton does not like that. It is being trapped by the extensions Norton adds to the Browsers so IE quarantines it. Chrome allows you to recover and keep it anyway.
Any other way to do a VMM reset other than with the holding buttons and repowering ? Thing is I have my MNGP remoted and only way I can do it is to take the cover off the classic and plug it back in long enough to VMM it. No one ever seems to be around when I want to do this and my arms aren't 50 feet long !
I know there is the jumper pull but that is about same effort as putting the display back on .
Anyway off to see how my Windows 10 does with the firmware update.
Larry
you've got the 2 methods at your 'fingertips', pardon the play on words..... ;)
what about those 2 fangs from that snake? ::)
I agree both are a pain, and don't forget about how you throw the CB's with the free arm that has to go around your neck to reach the cb's... :o :o >:( all ata the same time, keeping the 2 buttons depressed all the way...
Firmware:
- Classic Rev: 2074
- Network Rev: 2073
But I gotta say - that was a pain in the @^# ! My Windows 10 just wouldn't do the update and I spent way too long trying everything reinstalling update software, uninstalling and reinstalling drivers, restarting computer , etc.
The thing is that with terminal program it would get data from Classic just fine. But the firmware update would not start. There was one point in the process of doing drivers it said something didn't install right do I want to do something and I said no because I could see port 8 just fine in device manager and it said Midnite driver . Maybe I should have done whatever but I couldn't ever get that message to repeat even when I uninstalled and reinstalled drivers again.
So I finally got another laptop that I have with windows 7 and installed update and got the driver installed and everything worked just fine. Only thing I noticed was I know we are supposed to wait for all black windows to close but the first part of the update the window would not close so I closed it well after it said update completed. For the MNGP part of the update the windows closed like they normally do.
Anyway so far so good - I will see how mymidnite v3 looks in the morning .
Larry
Yes there is a hardware VMM:
The way to do the hardware version of the factory restore (VMM)is as follows. There are 4 sets of jumpers directly above the blue terminal block. For the purpose of this we will call the left most jumper JP1 and the right most JP4 (actually labeled "Boot")
Step 1- Turn the PV and Battery power off to the Classic and remove the front cover
Step 2- Locate the 2 jumpers JP1 and BOOT (JP4). Take the actual jumpers and keep them in your hand
Step 3- Turn the Battery power on to the classic
Step 4- within 1 minute place jumper JP4 on its two pins and then place jumper JP1 on its two pins. at this point the 3 leds on the top of the circuit board should flash back and forth for about 60 seconds.
Step 5- After the flashing stops power down the classic and remove JP1 and JP4 and stow them back on a single pin like they where.
Step 6- Put the front cover on and power up the Classic Lite. If you have the MNLP set to Custom you will need to go to the local app and reset the battery voltage and setpoints etc.
Quote from: Halfcrazy on November 03, 2015, 05:36:26 AM
http://www.midnitesolar.com/firmwareReport.php?firmware_ID=17&firmwareProduct_ID=1&act=edit
So this code does 3 things above and beyond production code 2056:
1- Better network code (Much More stable)
2- Supports MMv3
3- Fixes a bug in Auto EQ (1 of 3)
To use MM v3:
address for MM ver 3 is https://159.203.65.201 (https://159.203.65.201)
you need to put JUST the IP 159.203.65.201 in the dns over ride on the classic, Save it and reboot it.
Please report ANY classic oddities to me, And also please poke around MM v3 and report any errors to me either here on this thread or by email
Thank you
Ryan
Yesterday update to FW2074 and VMM, auto EQ was set to 3 days interval with a 2 days setup but today classic counter in view is stuck to 23 days interval and 3 days setup...
Erik
Quote from: ClassicCrazy on November 04, 2015, 01:51:45 AM
Firmware:
- Classic Rev: 2074
- Network Rev: 2073
But I gotta say - that was a pain in the @^# ! My Windows 10 just wouldn't do the update and I spent way too long trying everything reinstalling update software, uninstalling and reinstalling drivers, restarting computer , etc.
The thing is that with terminal program it would get data from Classic just fine. But the firmware update would not start. There was one point in the process of doing drivers it said something didn't install right do I want to do something and I said no because I could see port 8 just fine in device manager and it said Midnite driver . Maybe I should have done whatever but I couldn't ever get that message to repeat even when I uninstalled and reinstalled drivers again.
So I finally got another laptop that I have with windows 7 and installed update and got the driver installed and everything worked just fine. Only thing I noticed was I know we are supposed to wait for all black windows to close but the first part of the update the window would not close so I closed it well after it said update completed. For the MNGP part of the update the windows closed like they normally do.
Anyway so far so good - I will see how mymidnite v3 looks in the morning .
Larry
Larry, Thanks for verifying that there is a problem doing firmware updates with Win10. I had the same issue and I have not seen a solution from Midnite. Hopefully they will come up with a solution.
Yes I know about the hardware VMM but might as well just use the MNGP if I take the cover off (plug it in with small jumper) Maybe I will see if there is a way to put a double jack in there and leave the small cable sticking out with the longer cord left plugged in . It would just save having to take the cover off . Yeah not too big a deal but would make it easier.
I used Local Status app to restore all the setpoints.
Anyway the update seems to be working fine now and is reporting into mymidnite v3.
Just as a follow up to last night problems with Windows 10 - is this the correct driver for Windows 10 ?
(//)
Larry
Quote from: SolarMusher on November 04, 2015, 10:25:35 AM
Yesterday update to FW2074 and VMM, auto EQ was set to 3 days interval with a 2 days setup but today classic counter in view is stuck to 23 days interval and 3 days setup...
Erik
Erik, it may take the Classic to wake up before it takes on the new day interval and retry values.
You can update it to the new values right now by going to TWEAKS and I think the second menu.
A-EQ-RST I think it is. Highlight that item and press the UP button.
Then check the Auto EQ VIEW to check that the values changed.
boB
Salut boB,
Auto Eq interval change was made the day before and the Classic was awake this morning when I checked the counter.
Did EQ-RST and it updates the counter to the right values, great.
Was this EQ-RST there in tweaks before or is it new? I never paid attention to it.
Erik
Quote from: SolarMusher on November 04, 2015, 02:43:49 PM
Salut boB,
Auto Eq interval change was made the day before and the Classic was awake this morning when I checked the counter.
Did EQ-RST and it updates the counter to the right values, great.
Was this EQ-RST there in tweaks before or is it new? I never paid attention to it.
Erik
Yes, that EQ-RST was always there. I think the counter will set itself first thing the next day but it was
easier to do this when it was first designed but still needed a way to quickly test the counter so it was
left there just in case.
boB
boB, did Ryan talk to you about ebay here in canada?
I would be curious to know what you're thinking about it.
I didn't have any feebacks from Robin.
Erik
Erik
boB doesnt do anything on the sales/money side of things. That will be all Robin. I will nudge him again
I know that Ryan but was just curious to have an external point of view.
Anyway that's not the place to talk about that.
Erik