Got it to update finally - but for some reason this update did not want to go - when I powered on the Classic I heard the port 8 acknowledged on my laptop and could see it on Device manager but no transfer would happen. I tried everything uninstall and reinstall the update software, restart the computer, tried it numerous times shutting off the update and Classic and then finally for some reason it took and transferred and all went well. The MNGP transferred okay after that as well.
So just posting this in case anyone else has problem - keep trying . I have never had this not start transfering as soon as I turned the Classic back on with the update window on and have done lots of updates. Using Windows 7 .
I did the VMM reset and really like now being able to upload all the parameters back in using the Local Status app instead of going through each one again.
Happy to now say I am at
Firmware:
- Classic Rev: 2056
- Network Rev: 2045
Larry
I wonder if my Antivirus software was messing with this update. I just got an update from my Symantic antivirus that said it had been deleted and called it an Infostealer virus. Is there something different in this update from all the others ?
Never had any problems with it being blocked or deleted in the past .
Larry
I just re-installed W7 on another machine.. 186 updates included.... during several program installs I ended up with similar blockages. spoke to my techie friend and he told me to disable for a short time and when the program is running and the AV balks tell it to accept, etc.... the issue appears to be any program that attempts to make a change to some specific portion of memory seems to be 'caught' by the AV... W7 has turned into normal MS bloatware... :o :'(
Yeah - could have been something to do with the new Windows updates .
I thought I had given some kind of exception to the Midnite updater when I installed it but it may have been just to get to the site from Firefox. Must be hard for a software provider like Midnite to keep up with all the registrations or whatever they are called to make their software look legit to browsers and antivirus .
All is well that ends well though - got the Classic updated !
I had Notron Security Suite delete a copy of the 2050 update i had on my Win 7 desktop. That's new as i never had an issue with Midnite and Norton before. I restored it and excluded it and haven't had a problem since.
Yikes just had this pop up trying to download 2056. Think i will wait until Ryan makes an appearance on this.
What up with one firmware update after another in the last few day? What ever happen to beta testing these before putting them into production?
yeah that is like one I saw too - I downloaded it anyway !
Reported Unwanted Software Page!
This web page at fusion.midnitesolar.com has been reported to contain unwanted software and has been blocked based on your security preferences.
Unwanted software pages try to install software that can be deceptive and affect your system in unexpected ways.
What up with one firmware update after another in the last few day?
I seem to remember boB saying in another thread, that 2050?( I think), had some issues and there were several other later versions that would be released as soon as they tested out, sounds like there were several coders at work to me...
Quote from: Westbranch on August 21, 2015, 08:56:35 PM
What up with one firmware update after another in the last few day?
I seem to remember boB saying in another thread, that 2050?( I think), had some issues and there were several other later versions that would be released as soon as they tested out, sounds like there were several coders at work to me...
Yeah, 2050 showed up in production after months of no updates, no announcement. Then it had problems with installs with XP which boB fixed and they put 2054 out now we have 2056. That's okay but what happened to beta testing before going into production. I think most of these came about because of install problems vs changes to the actual firmware.
I'm still waiting for them to bless a Win10 install since MS is pushing this pretty hard and you almost have to stop the MS Windows update service to keep from getting it push to you machine. If you just try to delay it the delay is only for 3 days.
My Midnite is not working for me now- it must have reported right after I did the update because it shows 2056 firmware revision on the device page.
The only thing I did was reload my parameters using Local Status App - which has always been reporting to the /50.57.186.168 mymidnite beta or alpha page or whatever it is. But now there is nothing.
Guess I will report it on the Mymidnite section.
Just had a thought - maybe I need to reload that alpa network update again ?
Larry
from the Readme on firmware revisions
SVN Rev 2042. Networking Rev. 2024 (unchanged networking from 5-15-2015)
Fixed Reason For Resting #2 issue at higher powers.
This version is good for My Midnite 2 (MM2) with networking fixes
8-3-2015
Classic Rev. 2046 Networking Rev. 2045
This version is good for My Midnite 1 (MM1) which is the present web service
MNGP... No changes
Hmm - I wonder if that means I do have to reload the alpha networking - they seemed to have gone back and forth on that one !
I reloaded the network Beta again and am back on the MyMidnite alpha site -
The local status app now says I have
- Classic Rev: 1923
- Network Rev: 1824
Guess I will leave it here since I like the MyMidnite alpha page to know what is going on my system when I can't be at Local Status App.
I didn't think that the newest update would kick me off that - it has been a long time now since I got on it and probably that long since I last did a firmware update. Hard to keep up with it all sometimes !
Larry
Quote from: Resthome on August 21, 2015, 09:51:11 PM
Yeah, 2050 showed up in production after months of no updates, no announcement. Then it had problems with installs with XP which boB fixed and they put 2054 out now we have 2056. That's okay but what happened to beta testing before going into production. I think most of these came about because of install problems vs changes to the actual firmware.
My guess is that 2050 was driven by the new classic SL. (SL is the classic that completely solves all ethernet issues... permanently ;).
BTW, 2050 still watchdog resets (with heavy ethernet use) at the same interval as the 1900 series.
Quote from: zoneblue on August 23, 2015, 07:27:44 PM
Quote from: Resthome on August 21, 2015, 09:51:11 PM
Yeah, 2050 showed up in production after months of no updates, no announcement. Then it had problems with installs with XP which boB fixed and they put 2054 out now we have 2056. That's okay but what happened to beta testing before going into production. I think most of these came about because of install problems vs changes to the actual firmware.
My guess is that 2050 was driven by the new classic SL. (SL is the classic that completely solves all ethernet issues... permanently ;).
BTW, 2050 still watchdog resets (with heavy ethernet use) at the same interval as the 1900 series.
I'm sure the 2050 was about the SL. But then came 2054 to fix the install issue and then 2056 to fix another issue.
I'm not sure we will ever eliminate all the network and connection issues they have been going on too long. Maybe the next Classic hardware version.
Quote from: Resthome on August 23, 2015, 08:37:57 PM
Quote from: zoneblue on August 23, 2015, 07:27:44 PM
My guess is that 2050 was driven by the new classic SL. (SL is the classic that completely solves all ethernet issues... permanently ;).
BTW, 2050 still watchdog resets (with heavy ethernet use) at the same interval as the 1900 series.
I'm not sure we will ever eliminate all the network and connection issues they have been going on too long. Maybe the next Classic hardware version.
The ethernet issues would be unlikely to have anything to do with hardware.
But you are, sadly, completely correct that the network and connection issues will probably never be resolved.
This has been the one outstanding negative feature of the Classic and since its been known about now for years I would be surprised if it has not had a major impact on potential sales.
When I recently attended a solar energy seminar in Oz where a consultant who appeared to know what he was talking about, was pushing Outback and Morningstar controllers, was asked about the superior features of the Midnite Classic (not by me)
he said they were excellent but were never debugged properly as they suffered random resets and the network features were broken. His advice was if you need internet connectivity then the MSmppt60 was the way to go.
The Classic owner who asked the question replied 'but they are working on fixing it'
I could never fully understand why MN did not just get an experienced network programmer and do the job properly using an easily available ethernet stack for embedded processors.
Pity MN would not open source the Classic code (2 years ago when asked) as I suspect the user community would have debugged and probably redesigned the
ethernet areas of the firmware or maybe the complete firmware.
As ZB noted the solution is the SL :P
dgd
So 2050 was to remove menus for the Classic Lite, Sadly boB compiled in Debug mode so it showed it was missing a .dll file
So 2054 was sent out to fix that but was compiled in 64 bit
So 2056 was rolled out.
The issue here is all 3 of these have the OLD Ethernet code so any fixes Andrew had are not in here because sadly we are behind on the New My MidNite server
I was hoping we would have had My Midnite 2 done and wrapped up by now.
Sorry for all the delays and rapid fire updates. If I had a regular Classic I would not bother to update to these new code revisions as they are simply for the SL
Quote from: Halfcrazy on August 24, 2015, 05:22:43 AM
So 2050 was to remove menus for the Classic Lite, Sadly boB compiled in Debug mode so it showed it was missing a .dll file
So 2054 was sent out to fix that but was compiled in 64 bit
So 2056 was rolled out.
The issue here is all 3 of these have the OLD Ethernet code so any fixes Andrew had are not in here because sadly we are behind on the New My MidNite server
I was hoping we would have had My Midnite 2 done and wrapped up by now.
Sorry for all the delays and rapid fire updates. If I had a regular Classic I would not bother to update to these new code revisions as they are simply for the SL
Ryan,
Thanks for the update. It would be helpful if you or someone from Midnite would post the particulars about an update before/as they are being posted to the software tab on the web page as current production firmware. I know you have to get updates out fast when it includes functionality for new models, but a little communication would be a big help since we have been waiting a fairly long time for what we hear are fixes/improvement to the network discnnects.
Well the network code is likely still going to be a while. It is rolled into the new My Midnite server and Andrew is being pulled a few directions so I suspect progress on My MidNite 2 is going to slow down. Actually the behind the scenes is Andrew is actually working on the 3rd server for My Midnite and it is a much more robust scale-able solution.
Thanks for the update Ryan. Is this a network fix only for MyMidnite or will it help/fix the LA disconnects also?
Ryan, in that case could midnite seperate the core network stack fixes and just do a release for that seperate from the mymidnite stuff.
Unfortunately the fixes that you guys want (as far as I can tell) are in the my midnite 2 code and
cannot be folded into the MM1 code.
Dam.
boB
MM is part of the core network program and unfortunately cannot be easily separated. I had my Microsoft hat on while building the update and screwed up. I also assumed that I'd have MM2 up and running by now but the SL units popped up and I have a lot of production support to handle at the moment.
We should have 2 versions of 2056 soon. One for MM1 and one for MM2. Again I apologize for the delay on MM2
Quote from: Halfcrazy on August 31, 2015, 05:34:37 AM
We should have 2 versions of 2056 soon. One for MM1 and one for MM2. Again I apologize for the delay on MM2
So if we are not a user of the either of the MyMidnite web pages new (beta) or the current one do I understand correctly that we could use the MN2 firmware with the LA or do we have to stay with MN1? And will the Network version number be different or some way we can identify which firmware is loaded.
Just trying to get an understanding as we are leaving for the lake for two weeks and this will probably be the last long trip to observe the Classic in action this year. So if MN2 can be used with the LA and has the network fixes I would love to have a chance to take it with me when we leave so I can try it out.
With all this talk of Firmware updates and network stuff...will my two Classics be able to talk with my Outback Power inverter/Mate 3 (Optics RE)? It would be excellent to have data from the Classics (solar power watts for example) to be seen on the Optics RE screen. Or is this too much to ask?
Ditto. Id settle for a beta with MM2 code.
Quote from: Jacotenente on August 31, 2015, 04:26:56 PM
With all this talk of Firmware updates and network stuff...will my two Classics be able to talk with my Outback Power inverter/Mate 3 (Optics RE)? It would be excellent to have data from the Classics (solar power watts for example) to be seen on the Optics RE screen. Or is this too much to ask?
Thats never been on the cards as far as im aware. There are just so many permutations of different manufacturer gear (usually with proprietary protocols), and when these sorts of things come together its when some specific joint venture /cooperation emerges, usually driven by a particular project or large customer.
How is Optics RE working out for you anyway. How long have you been using it, and how stable do you find it?
On the other hand some of us are working on blackbox type projects to get mate3/axs to talk to midnite centric monitoring systems. Ultimately we are all hanging out for the midnite inverters!
Quote from: Halfcrazy on August 31, 2015, 05:34:37 AM
We should have 2 versions of 2056 soon. One for MM1 and one for MM2. Again I apologize for the delay on MM2
Thats going to be interesting. Hopefully not another level of obfuscation that ends up creating busy signal phone support at MN.
Since you are going that path what about an Occam's razored version that just removes all reference to MyMidnite from the ethernet code?
dgd
Quote from: zoneblue on August 31, 2015, 04:44:33 PM
Ultimately we are all hanging out for the midnite inverters!
Hmmm, not heard anything yet about the MN inverters, have you?
Powerjack boards arrived today so not too long now for a 6Kw 48V 230Vac 50Hz inverter.
A fast tracked inverter from MN who make the monster toroid transformer, make the container, use chinese PJ power electronics, interface an MNGP to it for stats reporting, setup etc. Now that would be a winner 8) but maybe more chance of a porcine squadron overflying my PV array ::)
dgd