Firmware 2079

[lox]

Windows 10 is close. I am testing a beta version now, it does not have error detection so if it fails it doesn't tell you but it is rock solid. I will release it here tomorrow as beta and the next rev will have error detection. I can say it is MUCH MUCH MUCH easier to use, no com ports, no drivers just plug it in and click update (well ok there are 5 steps in the instructions )

Ryan

Any Idea when we can get our hands on this for Windows 10 users everywhere, i'm dying to update my classic

Gerry

+1

[ClassicCrazy]

Okay - midnite update to 2079 done at midnight !
We will see how it goes.

Larry

[mattpenn]

First time poster, several month lurker! I've been running a Classic 150 with older MyMidnite 1 compatible firmware, no problems on an off grid PV system. Excited about the expanded logging (including WizBangJr Amps to/from the Batteries) and with the older MyMidnite shutting down next year I figured it was time to update.

I updated my firmware via my Mac, and I'll tell you how I did it!:

I've got a copy of VMWARE which is a cross platform Virtual Machine host. For me it allows my Mac to run virtualized copies of Windows, including pass through USB support.

You can get free time limited virtual copies of most versions of Windows from Microsoft to run for up to 90 days at https://dev.windows.com/en-us/microsoft-edge/tools/vms/mac/ and drop them into your Virtual Machine software ready to go.

I loaded up windows 7, downloaded the latest firmware, and unplugged the ethernet from my classic. I've heard it's helped some people with their firmware updates go more successfully. Followed the update instructions, updated my classic, and then the MNGP and everything went off flawlessly! Now I just need to wait for some sun tomorrow so I can see some data points on the new My Midnite site!

I noticed my older logging data didn't transfer over to the new MyMidnite site, is that intentional?

[Westbranch]

IIRC, Andrew migrated the MM1 data to the beta form of MM2, but maybe he didn't do it for the final release version.. 

I'm waiting for a new board for my CL 150 to arrive, but so far the post office has sent in the opposite direction from me, to SanFran... I'm in Canada...

[Resthome]

I'm waiting for a new board for my CL 150 to arrive, but so far the post office has sent in the opposite direction from me, to SanFran... I'm in Canada...

Wrong time of year for shipping. It will eventually get there.

[Westbranch]

You are right John... add a weekend in too... never mind that old guy in a red suit 
I am waiting for them to pull a FedEx and ship it through the Twin Cities or ? where ever their main distribution depot is.. .  and sometimes we thing the gov makes strange decisions 

We are now getting some wet/snowy weather and I hope I can do the change over before getting snowed out... or in...

[atop8918]

I'm sorry but the older mm1 data won't be available on MM2. You can download it on the original site though if you want. I do apologize for this, but the datasets were too hard to merge in the timeframe!

[Halfcrazy]

So I have a beta updater here for windows 10. Good news is it works super easy and has worked on at least 10 pcs, Bad news is it failed on one pc but that pc had a driver issue.

Anyone that wants to take a stab at it I can send it out. Keep in mind it could fail as it is beta and if it does you will have an erased classic. I would of course work with you on getting it replaced if you do not have access to a windows 7 machine. So for now I would prefer to keep this in the states to expedite shipping if we need to.

If you want to try email me for the file and directions. (it is like 4 steps to the directions)

ryan@midnitesolar.com

[ClassicCrazy]

I have been on Firmware 2079 for a week or two now and all has been fine.
But this morning I logged on with Grahams Android app and it loaded up at first - but then I shut the inverter off just to see how much current it takes to run it - and then then when I turned it back on the Android App would load up and then go back to sync and load up - it kept going back and forth loading data and then going back to nothing again. I tried resetting the router to make sure no issue there. The Local status app would not connect either.

So I restarted the Classic and the Grahams Android app works again normally . But now the Local Status app won't connect ( and yes I shut off the Android App first )  I suppose I should restart my laptop to rule out any issues there.

I looked at the history of Mymidnite and see it lost it's sync about 11:45 pm and didn't come back on until I restarted the Classic this morning.  Pehaps these are all related ?

I just looked at the router info ( using DDWRT flashed in Linksys 54g ) and in the LAN info the Classic is showing up on it's static address . It wasn't at first but I switched the plug to a different port on the back and it showed up. Before that the Local Status App actually connected - but after I shut it off and reloaded it back to the TRYING to connect screen.

So weird that Grahams Android App connects every time , but the Local Status App won't - and I tried Auto Detect and the Static connection  settings on that. After I send this off I will restart my laptop and see if that straightens it all out.

( restart did not solve Local Status App connecting via laptop )

Larry

[Resthome]

Larry, just for grins try turning the Android device all the way off, just to be sure it isn't holding a connection to the Classic and then try the LA again.

[ClassicCrazy]

Larry, just for grins try turning the Android device all the way off, just to be sure it isn't holding a connection to the Classic and then try the LA again.

Nope - that didn't do it - shut off Android and Local Status App still won't connect.
I guess I could go reset the Classic again .

Larry

[ClassicCrazy]

Earlier as an experiment I had the Android App connected and showing data , then uplugged the Classic cat5  from the router , and the Android App lost it's data - but filled in again when I plugged the the Classic back in to router. 

[Resthome]

Larry,

That's not saying much for the new firmware with the new network code. I ran the Alpha code of this and still had network disconnects. So I was hopping some of this would get resolved with 2079.  It could be that these network issues are really a LA issue.

I have to wait until the spring to update to 2079 as I'm only there for a few hours every 6 or 7 weeks until springtime and I need something stable until I can check it out for a few days.

I've run Graham's app under BlueStacks on a Windows machine and BlueStacks will sometimes keep the network connection to the Classic even after closing the app and will not allow the LA to connect until I end task the BlueStacks process that are still running. So it was just a though on my part about turning the Android device off to seek if that would allow the LA to connect. OH Well!

[ClassicCrazy]

Larry,

That's not saying much for the new firmware with the new network code. I ran the Alpha code of this and still had network disconnects. So I was hopping some of this would get resolved with 2079.  It could be that these network issues are really a LA issue.

I have to wait until the spring to update to 2079 as I'm only there for a few hours every 6 or 7 weeks until springtime and I need something stable until I can check it out for a few days.

I've run Graham's app under BlueStacks on a Windows machine and BlueStacks will sometimes keep the network connection to the Classic even after closing the app and will not allow the LA to connect until I end task the BlueStacks process that are still running. So it was just a though on my part about turning the Android device off to seek if that would allow the LA to connect. OH Well!

Okay here is what works - don't know why
If I start out fresh with Android off - connect up with computer local status app ( wired connnection to router ) connects fine.
Shut off Local Status app - then connect up with Android App - connects fine.
Shut off Android App - then Local Status App won't connect . Shutting off the Android didn't seem to help - but then I noticed that when I started the Android back up the Local Status app would connect again.
I then tried same thing again but I shut off Android wifi and then the Local Status App would connect .
So must be some weird local router/ wifi issues.
Never had that happen before but I haven't been using the Android App for awhile.
Larry

[Resthome]

Larry,

That's not saying much for the new firmware with the new network code. I ran the Alpha code of this and still had network disconnects. So I was hopping some of this would get resolved with 2079.  It could be that these network issues are really a LA issue.

I have to wait until the spring to update to 2079 as I'm only there for a few hours every 6 or 7 weeks until springtime and I need something stable until I can check it out for a few days.

I've run Graham's app under BlueStacks on a Windows machine and BlueStacks will sometimes keep the network connection to the Classic even after closing the app and will not allow the LA to connect until I end task the BlueStacks process that are still running. So it was just a though on my part about turning the Android device off to seek if that would allow the LA to connect. OH Well!

Okay here is what works - don't know why
If I start out fresh with Android off - connect up with computer local status app ( wired connnection to router ) connects fine.
Shut off Local Status app - then connect up with Android App - connects fine.
Shut off Android App - then Local Status App won't connect . Shutting off the Android didn't seem to help - but then I noticed that when I started the Android back up the Local Status app would connect again.
I then tried same thing again but I shut off Android wifi and then the Local Status App would connect .
So must be some weird local router/ wifi issues.
Never had that happen before but I haven't been using the Android App for awhile.
Larry

Humm...  Well I guess restarting the Android back up would probably reset everything including the network WiFi on the Android. So it sounds like it is similar to what I see when running Graham's app with BlueStacks and something appears to hold that last connection to the Classic open where the LA then will not connect because of the one connection limit of the Classic. I just always figured it was the BllueStack emulator.