for the last 2 weeks the lite seems to be having issues connecting to the local app and mymidnite . the only way i can get it back "on line" is to "cold boot" it ( remove the array and the battery).. then it reconnects and then i have to reset all the config parameters date time voltage limits and the web settings ( yes i remember to save after ea setting) . i then have to use the bully menu to reboot it again so that the web connection( mymidnite) will work.. this works ok for a day or two. then i am back to the same not connect retrying issue for both the local app and mymidnite. . there have been no changes to the router or network.. seems this happens every 6 months or so ..
very frustrating time consuming and a pain in the butt to have to go thru every other day
if i leave the local app running 24/7 it seems to be ok??
suggestions ?
Hi,
Is the Lite in "Custom" Mode? If not then any configuration you do with the Local App will be lost after a reboot.
not in custom mode (i need a set /known ip)... if i do a cold boot ( no battery/no solar) YES all settings are lost .. which is why i do a BULLY menu reboo(t after setting the settings). that keeps the settings so mymidnite works
firmware rev 1549
network 1547
It does sound to me like your MNDP is not set to custom. You MUST set it to custom in order to be able to use the local app to configure the lites. Otherwise evertime you reboot it the MNDP will reprogram the classic to the dip switch defaults, and youll lose local app settings.
This is something that isnt totally clear from the instructions, but the reality is that MNDP custom is the only useful dipswitch setting. Youd only not use it if the classic was truly alone in the world, with no access to any other means of configuring it, and you didnt mind the inability to fine tune the settings.
Also you "Should" be able to connect to it with the Local App and set a Static IP as well. So if you set the dip switches and get it running like you have. Log on to it with the Local app and verify everything. Then unplug the MNLP and set it to Custom and Plug it back in.
Now it will be a Static IP forever unless you change it with the Local App.
Also the new code Andrew released helps a lot with the Ethernet glitches so that may be worth a try as well
Ryan
RYAN
did as suggested all settings set via app then removed and unpluged MNLP. set s1 switches s1-s7 to custom (except no 8 eq still in man)
then repluged and replaced MNLP . we shall see what happens in the rest of the week
new day same problem local app will not connect to controller.. CRAP!
Not sure if the lites have the same firmware generation as the non-lite classic. I have a non-lite myself
But for me the 1500 firmwares always had lots of connection problems. I gave up on the local app last year. Only when I upgraded to 1700's last winter (needed by WBjr SOC) did the connection from local app became mostly stable. It still looses connection every few weeks, but not often. Mind you, I do not have the last 17xx on there. Once SOC became stable, I am not so much bothered anymore, maybe the very last is even better on the connection.
GohstNH
Try rebooting the Classic without setting the dip switches and see if it comes back. i think it may be time to update the firmware to try and avoid these drop outs
Ryan
cold booted it and it did come back all local app setting came back correct except the date.. no switchers were changed
ryan has worked fine for 6+ months with no changes with in my network.. now i believe in the last 6months there has been some adobe air updates which have been installed
Yeah I would try new firmware and see if that helps?
ok so 3 hr later i have the firmware 1849 and network 1839 installed ( midnite sure needs to update it online firmware update instruction) a NEWBIE would never get it to work ..
did the factory reboot (j1 j4)
local app connected all setting changed to previous setting with except to the new local app menu items (i.e temp window battery status meter) bully menu reboot
no s1 switch were changed (still in custom mode )
under info i notice a db1-db5 with what appeasr to be hex values after them not sure what that means ???
so we shall see what happens in the a.m.
What would be helpful is to know where my instructions are so far out of line? I would love to make them step by step and thought I had?
Ryan
Ryan,
FWIW, I used the latest production firmware updates with the Win7 instructions this weekend. I am a complete NEWB and it worked perfectly. There was absolutely no confusion for me.
Good to here Rybren, as I said my goal is not to make it hard I want it to be as clear and easy to follow as possible. Anyone who thinks there is an opportunity to make it better I am all ears and will make the necessary changes
connected this A.M. we shall see how the rest of the week goes
I Used windows xp install directions..
Quote from: GHOSTNH on August 06, 2014, 07:15:39 AM
connected this A.M. we shall see how the rest of the week goes
I Used windows xp install directions..
Can you tell me what steps where wrong and what was wrong with them so i can fix it?
Nah man, those firmware install instructions are pretty darn clear IMO.
ryan
i will review the steps again and give you feed back . i got lost trying to follow the steps with installing the usb driver cuz i could not find the MIDNITE FOLDER. in doing so installed something else on comm 8 so had a conflict "in use" that would not let the midnite usb driver use the comm 8 port
Ghost..,
Almost all of us here have been newbes at updating FW on Classics and KIDs. So welcome aboard.
Have not used a computer with XP as the updater.
But, have used a Windoze 7 Laptop. I had a bit of trouble at first ... because I was NOT following, exactly, the clear directions from MidNite.
Once I did follow the directions, to a tee, things went quite smoothly, even for me -- not a computer jock.
Believe that many issues revolve around the very difficult nature of Windoze, AND Microsoft.
Glad that you got your Classic updated. Subsequent updates should be much easier. Some CCs cannot be updated in the field -- they require a return to the manufacturer, or, perhaps doing a field board swap, with one that has updated firmware. I like MidNite's approach.
Just opinions. Vic
"Following, EXACTLY''.
Exactly, I concur with Vic 101% ;D
Had the Windoze blues for a month, my discovery was WAIT for the small CPU in the Classic to finish what ever step it is doing and not to expect a 'typical' CPU reaction time... wait, it will happen.