new to the forum ..about a week ago I registered for my midnite . windows 7 allowed me to see the add controller to start data collection with no data ( was told to upgrade to 1401) windowxp just show a black blank page with view and edit ..
today I upgraded to 1401 and I still get the same results web enable is turned on xp still show just the black blank page with edit and view and no controller windows 7 show the controller but no data so what am I doing wrong??
have you loaded the latest version of Adobe AIR?
Hi, GhostNH,
When you say WinXP, which browser are you using? Is it Internet Explorer? Can you check which version it is? Should be under Help->About. I think you might have trouble with MyMidNite for versions of Internet Explorer under version 9. I will have to put a warning on the page about this.
As for the data feed, are you able to access the Classic on your local network using the Local Application? Are you running behind a firewall?
Is the Classic running in DHCP mode or Static? In either case you may want to check the settings for D1 and D2 under the NET menu. If you are having trouble with your Classic accessing MyMidNite you may have to manually setup your DNS address by setting the network to STATIC and then using the DNS entry from your PC. This can be found under Control Panel->Network (and sharing center for 7)-<your primary network adapter here)->Right click + Status ->Details.
Thanks!
-Andrew
Actually it looks like it works ok back to Internet Explorer version 8 which was what I was designing for. Version 7 or less won't render correctly due to incompatible libraries. You may have to upgrade your Windows XP version of Internet Exploder or use the latest FireFox or Chrome, or Opera for that matter!
Thanks,
-Andrew
win7 is ie10 win xp is ie 8
local app works using in house network
app work over internet as well
static ip
classic lite ( no control panel)
Huh, my version of exploder seems to render correctly, mind you this is on Win 7 so maybe there is something weird going on with XP.
What are your Static Settings for the Classic? Are D1 and D2 set to the correct DNS values? Is the GW set correctly to your Internet router address?
Thanks,
-A
ip is set to 192.168.1.223 port 502
dns 1 is 75.75.75.75 dns 2 is set to 75.75.75.0.0 ( tried twice to reset it to the router dns of 75.75.75.76.76) keeps reseting
do not know what you mean by GW
error I made dns 2 75.75.0.0 tried to reset to 75.75.76.76 twice it just went back to .0.0 gw is set to 192.168.1.1
Aha. I think the problem might be that you need to set the MNLP to "custom" mode in this case. There seems to be a problem where the DNS gets clobbered when in Static IP mode. Try setting the MNLP to "custom" mode, reset the unit and then reconfigure the Network settings using the Application. This bug seems to affect some Lite Units.
ok set to dhcp mode router picked 192.168.1.21 as ip port 502 reset unit can not change ip dns subnet or gw in app networksettings
Do the DNS and gateway address look correct now? You may end up having to remove the MNLP entirely and just use the Local App to configure the unit.
gw is what it was set to before going to dhcp ( 192.168.1.1) dns 1 is the same 75.75.75.75 dns 2 is the same 75.75.0.0. again this is a lite it has no panel (mnlp)
Hi, GhostNH,
Sorry, I'm using the catalog names, then MNLP is the Lite's display where the MNGP is the Graphics display.
Have you reset the Classic since changing the DHCP option? You might want to try that to see if it resolves correctly.
One other thing to try is to open a console window on Windows:
on XP:
Start->Run->cmd.exe
on win7:
Start->Search programs and files->cmd.exe
Then type:
nslookup mymidnite.com
You should see something like:
Server: UnKnown
Address: 75.75.75.75
Non-authoritative answer:
Name: mymidnite.com
Address: 98.129.247.45
If not then there may be something amiss with some network settings. In most cases the Classic dials in fine right out of the box although on some networks it seems it gets wacked out.
Sorry for the troubles!
-A
Quote from: atop8918 on August 10, 2013, 08:56:08 AM
In most cases the Classic dials in fine right out of the box although on some networks it seems it gets wacked out.
Sorry for the troubles!
-A
Andrew;
Did you guys ever figure out if specific routers / switches were causing troubles?
I tried a couple different routers but it "seemed" it was fixed by one of your updates?
Tom
here is what I get
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\hp>nslookup mymidnite.com
Server: cdns01.comcast.net
Address: 75.75.75.75
Non-authoritative answer:
Name: mymidnite.com
Address: 98.129.247.45
C:\Users\hp>
Hi Tom!
Ryan might be better able to answer that question. I think we have a shortlist of routers somewhere that have been problematic.
The Classic is supposed to act like a browser and just accesses the Internet on port 80 like a browser so it should just work. It seems not to though! Most of my testing seemed to work in-house with most of the routers we tested. We tested mostly cheap routers though because of our budget! I know that boB had some DNS issues with his ISP-issued cable modem, while the same one in the office worked fine. The wonderful world of networking!!!
WELL STILL DOES NOT WORK !!!!!!
I REMOVED THE CONTROLLER FROM THE MY MIDNITE ACCOUNT AND NOW IT WILL NOT LET ME REENTER THE MAC OR DEVICE ID !! WHAT A CRAPPY SOFTWARE SYSTEM... I PURCHASED THIS ITEM BECAUSE IT WAS IP ADDRESSABLE AND WEB VIEWABLE .. BUT SEEMS THAT ALL THE HYPE ABOUT THESE FEATURES ARE USELESS AND THIS IS ONLY A FEW MONTHS OLD AND ALREADY HAD TO UPDATE FIRMWARE JUST TO SUPOSEDLY GET IT TO WORK WITH MY MIDNITE.. I WOULD NOT AT THIS TIME RECOMMEND THIS PRODUCT TO ANY SOLAR INSTALLER OR SYSTEM IT HAS WAY TO MANY PROLEMS NOT ONLY WITH MY MIDNITE BUT ALSO WITH THE APP THAT DOES NOT EVEIN WORK ON ANDRIOD..
GhostNH
Sorry you are so unhappy with your Classic. You really cant remove the main controller from My MidNite as that is what gave you access to the account. As far as it working on My MidNite I have browsed this thread quickly and I see no one has asked. Have you checked and saved "Web Access" in the Local App?
As far as the controller being old and out of date, REV 1401 was not a bug fix it was a firmware package that was released simultaneously with the actual release of My MidNite.
I am sure Andrew and I can help get My MidNite going. Please let me know if you checked and saved Web Access on the Local App.
Ryan
Quote from: Halfcrazy on August 10, 2013, 08:45:34 PM
Please let me know if you checked and saved Web Access on the Local App.
Ryan
Ryan;
I went back and looked closer.
In the first post he said Web Access is enabled.
Usually these things turn out to be simple things. Sorting out "what" is the fun part.
Sorry to see you having trouble, GHOST. Mymidnite was just beta testing stage a short while ago and like most new software compatibility issues do crop up. Give them a chance to sort it out and I am pretty sure they will get your system working as advertised.
I do all my monitoring locally mostly because I have horribly unreliable internet so I pull data from the Classic and process it locally. Even if the software is not behaving properly on logging / monitoring you can be assured the controller still does its job properly.
Tom
I know the frustration ! Just tonight at my dad's, (he's 92) I plugged my windows 7 laptop into his
Ethernet cable and my computer could not make a connection. Windows is supposed to be easy too
but no go.
Remember just 30 years ago we didn't have anything like this and didn't have any of these troubles
we have today with these very complicated high technology toys ! Life was so simple and
processors were real slow (~ 4 MHz) and memory was small (~64 K).
This stuff is NOT easy to design and is sometimes not easy to get to work with every single
one of the multitude of different pieces of equipment out there that are supposedly built
to some "standard" specifications.
I'm surprised that it ever works ! You can't expect to win them all and will sometimes
run across a combination of equipment that does not play well together.
BTW, my Westell DSL modem/router is the one here at home that crashes (or at least used
to crash) my Classic.
boB
I've checked the logs and it does look like the device is dialing in correctly, however it is not able to authenticate. This was the behavior I was seeing prior to the 1401 firmware update. It is possible that your particular network is not playing nicely with the authentication procedure.
GHOSTNH, can you give me the model of router you are using to connect to the Internet? We might have to get one in-house to see if we can solve the problem. If it is a popular router then we might save a lot of folks some headaches.
Ryan is correct, in order to make an account on the system you need a valid device ID and MAC combination. You can't re-register for the same device. I am happy to clear the account for you if you like. Or you can delete the account using the controls under the Edit tab.
web access was enable and has continued that way
router is a Linksys wrt54gl FIRMWARE 4.30.14 BUILD 5 OCT 6 2009
my midnite showed and un assigned controller this am ( thanks for the reset Andrew) I assigned the controller and still get the msg "this controller has been unable to connect to server for 2 weeks "
BTW every time I try to log in to my midnite 1 st attempt say " you are not authorized to access this page" 2nd attempt get me in >>
BTW the app display show 50.x volts when actual volts measured at the controller battery terminal is on 49.x battery current seems right ..
like I said earlier I purchased this system for the ip addressable and viewing over the net although it does work in house and the app works via the net not every where I travel will have the app or allow me to put it on their system.. plus if I forgot to close the app and am out somewhere I can not use the app over the network... would be nice if the app worked on android and allowed multiple connects... problem solved .. I can not speak to the my midnite site because so far I can not see now it works .
also would be nice if once data logging is enable that continues weither or not the app is running
and as already mentioned the c/f translation because I monitor the fet /battery/ pcb temp of the unit which is located remotely.. that help to decide if I need to turn on fans etc
GoshtNH
From what I can see the Classic is not sending packets for one reason or another. Can you go to the Config tab of the local app and then the Tech tab and grab a screen shot of the IP settings? In case you where not familiar with Print Screen, you can open and have showing on the computer screen anything you want to get a snap shot of. Click Print Screen. Now open Paint and click Paste and the images will show there.
I have attached a sample from my office. I suspect it is a DNS issue but need a little bit of info. I do apologize if this info has been asked for before. What do you have for internet service (IE Cable modem, DSL etc and is it a single Ethernet jack out and no wireless or is it a router as well? Also can you tell me the IP address of the Linksys?
Ryan
Also have you powered down the physical Classic completely waited 1 minute and powered it back on? I find with any networking device after a flurry of changes a Power cycle helps.
Ryan
ryan
after loading the 1401 firmware I did power down and wait ( count to 10) then powered back up
after making change per Andrew I again powered down waited ( count to 10) and then powered back up
cable modem ( Comcast isp) then Linksys wrt54gl router see above post for firmware revision then port of router go to computers classic lite all hardwired only wire less is android and printer.
which ip do you want the router ( 192.168.1.1) the Comcast gateway ip,, the ip assigned by Comcast to my mac ????
screen shot attached
I am assuming the cable modem is just that a modem? Basically it has a coaxial input and an Ethernet output? I am slightly confused as you mention the Comcast passing out IP addresses and in theory the Linksys should be doing that? I am wondering if it is doing something for the DNS. For instance on my system I have the following:
Cable modem
Linksys router set to 192.168.1.1 and it gets its DNS from the cable modem
Netgear Router 3 miles away set to 192.168.2.1 and its DNS is set to 192.168.1.1 and its gateway is set to 192.168.1.1
The devices IE Classics are then set to 192.168.2.xxx and there gateway is set to 192.168.2.1 and there DNS is set to 192.168.2.1
So basically I am wondering if the Classic should try to point its gateway and DNS to the Linksys instead? I may say try it for the afternoon and see if not Andrew will be able to help us tomorrow.
Ryan
I'm actually seeing GHOSTNH's packets at the server. The problem is not a DNS issue, unfortunately. There seems to be something else going on. The setup is identical to what I had at home which had no problem authenticating. I am seeing his Classic call into the server and try to authenticate, then it all goes wrong. This is the same behavior we were seeing with the pre-1401 firmware. Looks like the bug is still a bug. I will have to get to the bottom of this quickly since undoubtedly GHOSTNH is not the only customer with this issue.
Again, I apologize, GHOSTNH for the problems. Most users just plug in and go, unfortunately something about your network is making the Classic unhappy. I will give this full attention.
Remember that Tom W had a Linksys wrt54gl router that caused him troubles until he replaced
it with something else ?
This problem sounds like it might be something different now though.
boB
1 issue solved the battery offset in the app was set to 1 so the meter display 1 volt higher then actual battery volts .. wish they were all this easy
Andrew, Ryan where are we on the issues of my data collection and my midnite?
Hi, GHOSTNH,
Sorry for the delay. We will have a release in the next couple of days which incorporates a possible fix for the issue. Ryan will post the update under the firmware section of the Classic Charge Controller thread as usual. If this latest does not solve the issue, then I will continue to work on trying to resolve the problem.
Again, sorry for the troubles.
Andrew/ryan updated firmware tonight I see no change on mymidnite account
Ok I think I know what it is now. There seems to be an issue with some ISP's DNS lookup.
Try this on the PC on the same LAN:
Click the start icon and in the Run window type CMD.
When the CMD program shows click it to open it.
Now in the black window type this, nslookup www.mymidnite.com and post back the results.
Now in the same window type this, nslookup mymidnite.com and post back the results.
My theory is the second one will gather the right IP address for My Midnite.
Ryan
I use 8.8.8.8 as a nameserver (Google's Public DNS) and it is both faster and more reliable than my "ISP" nameserver.
It returns both addresses as same IP here. (98.129.247.45)
Just a thought.
Tom
Yeah we are finding some oddities. Time Warner returns www.mymidnite.com correct but hoses it without the www. We found a few out of the country today that are the other way around www hoses it. Andrew will get a fresh start in the AM and we will come up with a plan.
Coincidentally apparently 8.8.8.8 or 8.8.4.4 do not work in some other countries according to Andrew.
Ryan
Quote from: Halfcrazy on August 20, 2013, 08:41:32 PM
Yeah we are finding some oddities.
Speaking of "oddities"...
You have no reverse (PTR) record for 98.129.247.45.
Sure, it kinda works without it, but it's NOT RIGHT.
midnite.com has at times returned a plethora of A records likely to cause some problems...
Yup that's the magic of "cloud" hosting. Billions of interlocking parts working perfectly in harmony, until they don't, then its a 50,000,000 piece jigsaw puzzle where all the pieces are the same shade of puke-green...
The lack of reverse entry is disturbing though. Maybe we'll have to switch name provider to get this sorted out properly. In the meantime I'll try to work on a band-aid for the shorter term.
Quote from: atop8918 on August 21, 2013, 03:09:42 AM
The lack of reverse entry is disturbing though. Maybe we'll have to switch name provider to get this sorted out properly.
Your DNS provider cannot control the PTR records unless it's their address space (or its yours and you delegate the IN-ADDR.ARPA to them - but if you have it, you're unlikely to be using someone else to do your DNS!)
the results
C:\Users\hp>Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\hp>nslookup www.mymidnite.com
Server: cdns01.comcast.net
Address: 75.75.75.75
Non-authoritative answer:
Name: www.mymidnite.com
Address: 98.129.247.45
C:\Users\hp>nslookup mymidnite.com
Server: cdns01.comcast.net
Address: 75.75.75.75
Non-authoritative answer:
Name: mymidnite.com
Address: 98.129.247.45
C:\Users\hp>
Ok should have some beta classic software soon that allows you to point the Classic directly to the servers IP address. Lets see if this helps.
Ryan
Alright...I found another issue on the server -- several actually.
GHOSTNH, your data should now be coming through the pipe, I apologize for the delay. I finally found that one obscure little script was changing some users' Classic credentials which effectively does not let them log in. I've fixed the error and the script and hopefully repaired all the damage. That's what backups and backups of backups are good for.
We will also have another beta release for users who are experiencing the DNS issue where the mini Classic DNS engine is not getting the expected format of A records from some brands of routers and servers. This version will allow you to override the DNS algorithm and point directly at the server.
;D :D :D :D :D :D :D :D :D ANDREW ..We have a connection and data stream Thanks!!!! I was about to ask for a refund /return of the unit cus of the issue configuring and data logging particularly via web based..now I have to try mymidnite on the android and see if it works cuz I hate luging a laptop around in my travels .. looks like I only have two days of data I guess the older data is lost forever??
agin thanks to you ryan and tom for the inputs
Hi, GhostNH,
I tested the site out on a few Android phones -- it should work fine though you won't be able to use the managment tab yet. iOS you're on your own.
Yes the older data is lost forever. We only store 2 weeks' worth of high-resolution data and then daily totals after that. There is an export facility you can use to backup the data for your own use. We will provide an email service to automate this in the future.
I use it all the time on my Samsung Galaxy S3 it works very well.
Ryan
up until 9/9 my midnite was working perfectly I had to shut down the array/ controller to clean up some wiring issues . when I did I changed from dhcp to static ip and put the covers back on . This is because I keep having to reboot cable modem and router which I then have to find the new ip of the classic lite and reconfigure the router and the local app. So for the last few days my midnite has not functioned ..I did update the app to lastest rev the lite firmware is still 1549 web is enabled . I have tried the dns2 setting of 98.129.247.45 mentioned in this and other threads to point directly to the server my static ip is 198.162.1.223:502 and the gateway is 198.162.1.1.. ryan andy tom etc what am I doing wrong this time??
Quote from: GHOSTNH on September 12, 2013, 04:19:38 PM
my static ip is 198.162.1.223:502 and the gateway is 198.162.1.1..
Can you triple-check that?
192.162.x.x isn't RFC1918 address space, I suspect you've mis-keyed and wanted 192.168.1.whatever
Quote from: GHOSTNH on September 12, 2013, 04:19:38 PM
my static ip is 198.162.1.223:502 and the gateway is 198.162.1.1.. ryan andy tom etc what am I doing wrong this time??
That "static ip is 198.162.1.223:502" doesn't seem right?
Especially the :502 part. That designates a port to access the Classic at IP198.162.1.223.
I don't do windows so not sure if its a typo or something?
Tom
yup tom w and ross w I did mistype it is set to 192.168.1.1 gateway and 192.168.1.223 ip and port 502
If you change the DNS2/DNS override value then you have to reboot the classic for it to "take".
I did power it down an wait 10 and repower but the dns2 filed changed back to 0.0.1.1 I then changed it to 98.129.247.45 and yes I did remember to "enter" the new value
Hmm, if the DNS2 value is getting reset to 0.0.1.1 on reboot it will never work.
Sorry if you've already been over this but is the MNLP set to "custom"? If so and the DNS2 is still getting over-written then you may just have to unplug the MNLP.
I would suggest the following:
1- Unplug the MNLP,
2- Use the Local App to set DNS 2/override to 98.129.247.45
3- Hit Enter as you suggested.
4- Reboot the Classic.
At this point double check the DNS2 address using the local app. If it is still set to 98.129.247.45 then you should be good to go. If you want to use the MNLP just for the lights, then you can set the dip switches to "custom" and then plug it back in.
You may have to keep an eye on it if it reboots though.
GhostNH
If you are using the latest Local App 0.3.29 (I hope you are as the one before that would read values wrong on occasion) correct? If so there are to places to set the port number and I found you have to set the Modbus port to actually change it. Although that should have no bearing on My Midnite.
Ryan
andrew/ryan using the latest app (0.3.29) as stated in the post...
also stated was I took the unit off dhcp /custom and went to static because of constant reboot of the cable modem and router and then have to reconfigure the app and the router with the new dhcp ip
if I unplug the mnlp then I will be in custom mode (dhcp) and be back to what im trying to avoid
grrr
The way that the mnlp dip switches work is that on boot the mnlp sends the dip switch settings to the controller. After that their setting is immaterial. So in order to set up a lite, what i do is use the dip switches to set the static ip, boot, then set the static ip in local app. Then turn off the lite, change the dip switch to custom, then restart it, at which point it will keep in the previous local app settings.
The other way would be to set custom to begin with. Find out which ip the lite gets, go in to local app, then change to static. MNLP stays in custom.
Hi GHOSTNH,
Zone Blue is absolutely correct:
the Classic remembers what it was set to last time. If you unplug the MNLP and reboot the Classic it will be exactly what it was before. In fact you don't even need an MNLP / MNGP if you configure with the local application. "Custom mode on the MNLP just tells it to stop telling the Classic what to do. So if you set the Classic to STATIC and give it an address with the local app, then it will boot up that way without the MNLP or the MNGP. In fact, the MNLP might be the problem in your particular situation.
OK just powered down unit removed cover removed cable ..Repowered up app shows all setting remained the same as when the unit was powered down static ip web enabled and the dns override show the ip of the my midnite server .. lets see if I get data streams now umm do I have a bad front panel??
Worthy to note that I have to log in twice to my midnite to see panel ...first attempt says I am not authorized. I did not log in incorrectly.. happens ever time
late in the day here but it does appear that some data is streaming to my midnite . so perhaps I do have a bad panel .. now how do I get that replaced or checked etc ?? perhaps the bad panel is the source of most of my problems with this unit for the last 45 days...
Quote from: GHOSTNH on September 16, 2013, 04:33:23 PM
Worthy to note that I have to log in twice to my midnite to see panel ...first attempt says I am not authorized. I did not log in incorrectly.. happens ever time
This issue is do to the fact the first attempt is bookmarked as http:// and it is a secure connection. https:// so the thing to do is to bookmark the second link.
Ryan
Quote from: GHOSTNH on September 16, 2013, 04:52:02 PM
late in the day here but it does appear that some data is streaming to my midnite . so perhaps I do have a bad panel .. now how do I get that replaced or checked etc ?? perhaps the bad panel is the source of most of my problems with this unit for the last 45 days...
Send me an Email ryan@midnitesolar.com with your shipping info
I did not bookmark the site
just entered mymidnite.com
I do understand tho and will bookmark the site for https:
perhaps in future this to shall be fixed
The problem is that the site is not properly redirecting to https: on the login screen.
If you login to http://www.mymidnite.com you will be asked to do it again.
The answer is to login to:
https://www.mymidnite.com
notice the httpS vs http
We are working on solving this problem but so far the solutions have caused more issues (anyone remember the "too many redirects" error?) Drupal is a very powerful CMS and makes some very complex things very easy to do, unfortunately it also makes some really simple things REALLY difficult to do as well...
got the new mnlp today installed it .. I had to reset the gateway ip and enable web seems to be working . I get live data to mymidnite and im in static ip mode with the front panel plugged in .. so it appear the panel I had was D.O. A. when I got the unit .. perhaps it is the cause of most of my issues with the unit from day 1
Thanks Ryan and the rest of the mymidnite crew :)
DO I need an RMA number to return the defective panel?
Na just trash that unit.
Ryan