Ok it has come to my attention that a couple people may be having issues keeping the Local App connected to the Classic. What I have done is installed the App on my Echolink PC and left it going with 4 Classics for close to 2 months with no issues (Since I upgraded Classic code). So what I need is for those people that are having issues to jump in here and give me as much info on there setup as possible.
IE: How the Classic is wired to the network and how the PC is hooked to that same network. Brand and model numbers of devices will be helpful. Also Classic and MNGP firmware dates as well as Local App version.
I found older Classic code had a slight bug 2 of my 6 Classics would stop talking to the Network and would need a reboot. Also I think Andrew has made some tweaks in the App software to help as well. I would ask anyone having issues to make sure they have the latest Classic/MNGP code and the newest Local App.
Classic/MNGP Code will be on our website today or Monday so might as well wait for that it actually fixes a slight bug in logging as well as other stuff.
In the Local App there is a Radio Button labeled Click on the Config Tab and Click Update now.
Please give me as much detail as possible and I will make every attempt to recreate the issues.
Ryan
Hi Ryan
I had the issue pop up the last couple weeks on my system as well. I think it was after the auto-update for the software, current version software is 0.1.4 and all three Classics have the November 09 update.
System has been working fine since the last Classic update and no issues until just recent. Classics will come up in the software with a disconnect notice " Device Not Available" and when you restart the program the Classics can not be found.
If you reboot the Classics then the software auto finds the Classics and the displays come back on line for about 5 to 6 hr then become disconnected again.
I have all classics plugged into an 8 port Links hub and this hub is connected to my main Cisco wireless/4port hub.
If you need any more info please let me know
Cheers
Danny
Hi Ryan
I did forget that I did have a similar issue with the previous Classic update prior to Nov 09 version where the software local app would not find the Classics the next day or about 10 to 12 hr after starting the software program, and you would have to reboot the Classics to get them back on line but once I loaded the Nov 09 update the problem went away until the last couple weeks.
I have not made any changes to the way my system is connected for the last 6 months to the hubs.
Cheers
Danny
Half,
I have the same exact problem. It was working like a champ until recently.
Cheers...
Damani
Damani
Yours is also the Classic not the App correct?
Ok just talked to Andrew and he feels these Classic issues over the last few days are related to a software upgrade he did to My MidNite. Even though you are not accessing My MidNite your Classic is if it is connected to the net. He has disabled this code but if problems persist you should go into the Net Menu and set Web Access to Disabled.
Keep me posted
Ryan
Half,
I have three classic hooked up to a local network through a port. As far as I am aware they are not connected to the net, but I mabye wrong. I will disable the net on the classic anyway as see how that goes. I to have upgraded all of my classics(200 and 2 150's) with the Nov 9 firmware. It was working like a champ even when the computer went to sleep it would awake and still be connected. I have my app to auto update. I think that was what Danny was refering to.
Cheers...
Damani
Yeah, try it again guys and let us know if it's better now.
Thanks,
boB
I reset my Classics when I got home after work and if they have kicked out in the morning I will set the Classics to disable the web access.
I will post in the morning to let you know if Andrews code change stopped it or if it has to be stopped at the Classic.
Cheers
Danny
MN,
I disabled the net function on the classics and restarted them and the connection on the app has been stable since then. I will let you guys know it acts up again but so far so good.
Cheers...
Damani
Ryan
I checked this morning and the local app software is still running after running all night.
I only rebooted the software and the Classics last night when I got home from work and did not disable the web access on the Classics.
I would guess that whatever Andrew changed on the MyMidnite site worked.
I will leave my setup the same and let you know if I have any problems in the next while
Cheers
Danny
This is good news ! Thanks guys !
boB
I have downloaded the latest Local App software and hopefully someone can help with all the issues:
1) Constantly disconnects, I have gone overnight without it disconnecting but usually it's between a couple of minutes to a couple of hours then I have to reboot the Edimax Wireless Range Extender/Access Point where the Classic 150 is connected. The Classic just seems to quit sending a signal to it. It doesn't seem to matter whether I have Web Access enabled or disabled. Sometimes I even have to remove the IP settings on the configuration screen of the Local App and re-type them in to get it to work.
2) I get this error message every time I start the Local App software "[ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Error #3001" errorID=3001]" I click OK and the program works fine until I click on the "config" tab, then I get the error message again. I click OK and the program works fine.
3) Is there anyway to save the changes permanently when I click "config" then "classic" and change the "Power Meter Scale"? It always reverts back to the original settings if I close the program and reopen it.
4) Is there anyway to get all the data out of the Classic and on to my computer? Not just the data while the Local App is running, but all the data stored in the Classic?
Any help would be appreciated. :)
Hi, Drew,
First off, I'm sorry that you're having so much trouble with the Classic and Local App. I've been trying to make this as robust as possible so let's see if we can get to the heart of the matter.
As far as your 3001 Error and setting "stickiness": The 3001 error is permissions-related, that is a "File or Directory Access denied". Which can mean that the settings directory doesn't exist or that there is a permissions problem. The latter is highly dependent on your Operating System. The configuration (and log) data is stored in the following places:
Windows XP:
c:\Documents and Settings\<username>\Application Data\com.midnitesolar.LocalStatusPanel\
Windows 7:
C:\Users\<username>\AppData\Roaming\com.midnitesolar.LocalStatusPanel\Local Store
MAC OSX:
/<username>/Library/Preferences/com.midnitesolar.LocalStatusPanel/
Linux (depends on distribution):
/Users/<username>/.appdata/com.midnitesolar.LocalStatusPanel/
or
/home/<username>/.appdata/com.midnitesolar.LocalStatusPanel/
So for that particular problem it may have something to do with the directory. Try navigating to that directory to see if it exists. Windows 7, Linux, and OSX may potentially have permissions issues, particularly Windows 7 which in my opinion is a steaming pile of half-cooked...but I digress.
As for #4: I am working on grabbing the log data from the Classic and adding that to the Local App, but I haven't had a chance to finish it yet. Once that is in place, you will be able to download it and export to a csv file for use in your favorite spreadsheet program. I recommend Libre Office.
Hope this helps someone. I'll be working on the other issues offline. Thanks for your patience.
-A
Hi all, new to Classic...
I have this problem with the Classic Lite connecting and disconecting to the App. I have my lock code typed correctly but still I cannot find where to disable the Web Access. I've gone through all the config tabs and can't find it. Please tell me where can I disable. Thnaks.
Quote from: jabal on October 21, 2012, 04:21:48 AM
Hi all, new to Classic...
I have this problem with the Classic Lite connecting and disconecting to the App. I have my lock code typed correctly but still I cannot find where to disable the Web Access. I've gone through all the config tabs and can't find it. Please tell me where can I disable. Thnaks.
I don't think you can disable that from the Local App.
Hopefully we can change that !
There's a few other things it could have as well.
Getting closer on your disconnect issue I believe.
boB
It's in the classis mngp under net, next, advanced menu
I`ve got no MNGP I have a classic lite thus the only way I have to communicate is either through USB or Local App. The local app still conects and disconnects every 20 seconds or so, everytime with a new different IP adress.
Help is appreciated. Thanks
Ok finally what I did is to connect my Classic Lite to an old 3Com router I have. This way from my mac I can either connect via WIFI to the router that provides internet access or to the router which is connected to the Classic. This way the local app works fine...
I finally joined today so I could ask if the Classic communication issue via ethernet has been fixed? I cannot find the answer searching and reading through the forum. Of course that does not mean it is not posted here just that I am too dense to find or recognize it! I have a Classic 150.
It seems I can connect once a day for a few minutes with the local app, ping it, etc. but eventually it just goes dead on the ethernet port. No ping reply and the Local App says "Busy"?
I hope to be able to gather the data from the Classic to process offline.
I use Ubuntu 11.10 so updating the firmware requires me to take it to a friends who uses Winders.
I updated to the current firmware 3 weeks ago but not sure which version it was or how to tell from the panel on the Classic 150? 6-29-2012 V2.69 comes to mind?
Anyway, wondering if this issue has been resolved?
Once that is resolved I will be asking about using modpol on Linux.
Thanks for any information.
TomW
Tom
Andrew and boB are locked in the room until they get this resolved. Andrew thinks he has it and we will be testing this theory out. Also on the firmware Andy has a working Linux installer I am told. Robin is going to go to engineering and see if he thinks he can use it.
Ryan
Quote from: Halfcrazy on October 30, 2012, 03:52:16 PM
Andrew and boB are locked in the room until they get this resolved.
Andy has a working Linux installer I am told. Robin is going to go to engineering and see if he thinks he can use it.
Ryan
Ryan;
I am willing to play guinea pig on the Linux installer. If I can't break it, nobody can! :o
I think those guys should get bathroom and pizza breaks. Provided they stay in the building, of course! ;D
Sure like this Classic 150. Running it on my 520 watts of Kyoceras while I wait for the fresh install of 1500 watts of Samsung 250 watt units. Luckily this communication issue does not affect the MPPT section near as I can tell. Really looking forward to getting it reliably communicating. Ain't software glitches fun.
Thanks for the response.
Tom
Tom, welcome to our little forum !
Even when the Classic ethernet locks up, one can usually still ping it.
Not sure why you can't ?? Are you trying to ping it on your local network ?
Check to make sure the IP address didn't get changed via DHCP. I notice at
home that sometimes my router want to keep giving it new IP addresses.
I usually set it for DHCP, let it get an IP address, and then set it for
static mode and press ENTER to lock in that IP address.
Of course, you may already be doing that ?
boB
Hi All,
After some months away, here are my two cents :
After upgrades of Classic firmware, MNGP, and AIR Software upgrade, i encountered the lock of the Local App, during the day with the Classic saying BUSY.
After rebooting it in the night, it comes the next day.
Now, it has gone, since in the configuration menu of the Local App, I added the IP address of my Classic, which disappeared after an update.
Yann
PS : Is the Local App Version 2.4 the latest ??
Quote from: boB on October 30, 2012, 05:07:50 PM
Tom, welcome to our little forum !
Even when the Classic ethernet locks up, one can usually still ping it.
Not sure why you can't ?? Are you trying to ping it on your local network ?
Check to make sure the IP address didn't get changed via DHCP. I notice at
home that sometimes my router want to keep giving it new IP addresses.
I usually set it for DHCP, let it get an IP address, and then set it for
static mode and press ENTER to lock in that IP address.
Of course, you may already be doing that ?
boB
boB;
Thanks for the warm welcome!
I gave it a static IP (192.168.2.225) on my LAN. I just checked it all on the panel and it shows that as the IP. I cannot ping it as is now. Changing it to DHCP now to see if that makes a difference. No joy. It picked up 192.168.2.104 from the DHCP server and i cannot ping it or connect the local app to it. Status Panel says "device not available" even with the automatically detect-Classics is checked and the IP was added. The IP in the network tab still shows the .225 I gave it for static. Should that show the IP provided by the router or the one I entered?
Sorry but I am confused which is not unusual. I think I will try a quick start see if I can start from scratch on the network config. No joy there, either, Still holding that 192.168.2.225 address even after the quick start and set for DHCP and the router says it has 192.168.2.104 as an IP. No ping on either IP and the Status Panel says "Device Not Available".
If it matters my Status Panel says it is Application Version 0.3.3, Open Flash Charts Version 2 Kvasir (midnite remix) running on Ubuntu 11.10
Awaiting your (gentle) cluehammer blow. ;D
Thanks.
Tom
Quote from: Halfcrazy on October 30, 2012, 03:52:16 PM
Andrew and boB are locked in the room until they get this resolved.
Andy has a working Linux installer I am told. Robin is going to go to engineering and see if he thinks he can use it.
Ryan
I run ubuntu off my netbook, and it's my OS of choice. Willing to play guinea pig ... as long as I won't screw the machine up too badly ...
Quote from: TomW on October 30, 2012, 06:16:27 PM
I gave it a static IP (192.168.2.225) on my LAN. I just checked it all on the panel and it shows that as the IP. I cannot ping it as is now. Changing it to DHCP now to see if that makes a difference. No joy. It picked up 192.168.2.104 from the DHCP server and i cannot ping it or connect the local app to it. Status Panel says "device not available" even with the automatically detect-Classics is checked and the IP was added. The IP in the network tab still shows the .225 I gave it for static. Should that show the IP provided by the router or the one I entered?
Sorry but I am confused which is not unusual. I think I will try a quick start see if I can start from scratch on the network config. No joy there, either, Still holding that 192.168.2.225 address even after the quick start and set for DHCP and the router says it has 192.168.2.104 as an IP. No ping on either IP and the Status Panel says "Device Not Available".
Can I make a suggestion or two? Make the 192.168.2.104 address static with mask 255.255.255.0 on you classic. Remove any other secondary ip addresses it has.
If you have an Ethernet cable longer then 2 metres between the classic and router then use a shorter cable and connect it to a powered Ethernet hub then connect hub to longer cable to your router.
I used a cat5 cable into the classic but replaced this with a shielded cat6 cat7 cable. I also had the lock tab broke off so that I could remove the cable from the classic's socket but this allowed the cable to creep out. It didn't come right out but enough to make for an unreliable connection. Bring the cable out of the classic keeping it away from the power cables.
Set the local app to discover classics, don't specify a static IP address.
None of these may make and difference to your network problem but its something to try while awaiting a solution from MN...
Dgd