My Status panel stopped working..KaPutt. I ditched the IP address and renewed it,among other things and I'm getting a ERROR #2002 when i try to logon. it attempts to logon "CONNECTING" then says "DEVICE NOT AVAILABLE".
Where do I start??
Quote from: plongson on December 13, 2012, 04:45:54 PM
My Status panel stopped working..KaPutt. I ditched the IP address and renewed it,among other things and I'm getting a ERROR #2002 when i try to logon. it attempts to logon "CONNECTING" then says "DEVICE NOT AVAILABLE".
Where do I start??
Did you reset the Classic ? What is the software rev in the Classic ?
Is this the Ethernet/internet drop off problem we used to see ??
boB
Hey boB
No, didn't reset the Classic. I'm 200 miles away right now and it went from working this morning to nada.
Software is 10?? the one just before this last update today.
I'm not there to check the internet connection so I can't validate that one way or the other.
Just wondered if the #2002 error meant anything?
Sucks getting use to monitoring the status and then it goes away...LOL
Any help you have is always greatly appreciated...
Paul
For what its worth. It sure sounds like the ole ethernet communication error. Never saw that # error myself though.
Another thought. When you say "I ditched the IP address and renewed it,..." if you changed the Classics' local IP address and use port forwarding on your router it will not get to the Classic from outside to the new IP address on the local network.
Just saying..
Tom
No, didn't change anything on the Classic I'm far and away from there tonight. What I did was remove and re install the Local Status app and the address under "config".
All it does is..."connecting" then immediately after..."device not available".
When I get back what do you think? Power off the Classic and reboot? Networking is really not my forte.
I have so many other thing going right now, this is really down the list, like they say, but I sure would like to get ti working again!
Quote from: plongson on December 13, 2012, 08:15:26 PM
Hey boB
Just wondered if the #2002 error meant anything?
Paul
At least the #2002 error is not a biggie. Wouldn't worry about that one at all.
It is some kind of Adobe AIR error (AIRerr ?) that comes up some times and
is very difficult to debug as it appears to be buried deep within Adobes' code
somewhere. I have never seen it to meany anything more important than
maybe restarting the local app and usually comes up when assigning
a new IP address or installing a new local app software version I think.
It's the other errors that are more important at this time.
Thank you for the information. I don't suppose you have
the auto-restart enabled in that Classic ??
boB
Wow, Auto-restart...I didn't even know that was an option. How do you get to it and I sure will activate it. What do you think? Is that something that should be enabled? I like the sounds of it.
Quote from: plongson on December 13, 2012, 10:17:56 PM
Wow, Auto-restart...I didn't even know that was an option. How do you get to it and I sure will activate it. What do you think? Is that something that should be enabled? I like the sounds of it.
Auto Restart is in the TWEAKS menus... It is labelled A-RST. Next time you are at the Classic just turn it to ON and
press ENTER to make sure the Classic remembers that is is supposed to be ON when it does restart/reset.
This tweak makes the Classic reset every night at midnight just after it saves the daily logging numbers and
changes back to BULK etc.
This is not quite as good as just insuring the Ethernet won't crash at all, but if the Classic is inaccessible,
it's probably the next best thing to it especially if it is 200 miles away.
boB
Thanks boB. I will make that change! Dang, there are so many facets to the Classic it's amazing. I learn something at every turn...
Paul
Hey boB,
I got a chance this last week to make the changes you recommended to the Classic setup (reboot every night) and while I was home for that few days, the remote status app worked great. I was also RIGHT THERE and it was not running off the DYNdns internet connection, but was running through the router wireless.
Now this week, I'm gone again and go to bring up the remote app and...nothing again. It said the same thing "connecting" "Device not available"...so I'm thinking it's got to be the DYN connection...THEN, out of the blue, yesterday, I click on it and out of the blue IT WORKS! And it works all day with no problems.
Then this morning, guess what... :-\ "device not available". I've played around with the DYN server setup and it seems to be working.
Any ideas on what to check when I get back again on the classic, router, etc. to get things up again?
It's so damn funny that one day it will work and then be down the next...???
I hate to be PITA but I'm not sure where to look now.
Paul
Hello Paul
I have a similar issue but it happens from here at the house.
I have 2 Classics and have them hooked to my router with a switch in the battery room. Anyway, I hooked them up came in the house and both showed up and all was well for 6 or 8 hrs then one gave the "device not available" business. It does that for a while and then shows up for a while with no apparent pattern or reason.
The weird thing is now a few week out it is either getting happier or I just don't look as often. It is always the same one that says unavailable and it's on the solar array the one on the turbine is more fun to watch and I can get battery info without the hike out there so it's not a big deal for me. I know this probably doesn't help you but I thought the similar intermittent nature interesting.
Wade
Thanks Wade, It seems we have similar problems going here. It might seem it's not the DYNdns. Mine is still down this morning and hasn't been up since Christmas day.
Thanks for the info...
When I had the #2002 error, I had the local app watching from another computer and it went away when I closed the local app on the 2nd computer.
Just FYI
Tom
I am told the Error #2002 is a bogus Adobe Air thing. Andrew says it has nothing to do with Working or Not Working. We have found that the Port number can cause all sorts of oddness on the stability of the Classic. We have found the Port if not 502 should be way higher say 1300 or higher.
Ryan
Thanks guys, that's a good place to start. First chance I get I will bump up that port number. I sure would like to get it going again, you become dependent on that remote app after a while.
More questions...I sure wish I knew more about networking...but,
When I click on the local app and it says "connecting" then I get "Device not available" doesn't that seem to indicate the local app has been hit with a request to open the Classic?
I've been reading about ports and port forwarding and some ISP block common ports (anything below 1024 or something like that) Could my ISP for my ranch be blocking the request from the Local APP not allowing the app to open?? Or when I get the "Device not Available" does it seem like it is a "Classic not wanting to answer the command" sort'a issue??
I'm not there again for a while to change port protocol and it's really on my mind...
Thanks...Maybe i should take a networking class at the community college...LOL
I have been troubled on and off with the "Device not available" issue. I'm using a DNS service due to my ISP assign a dynamic IP address. I'm forwarding port 502 through my router. On a hole It works most of the time but.....
I do now and then get "Device not available" usually I just ignoring it and come back in 5 min and try again and it would connect and be fine. When why and how this happens is a little erratic so I haven't been able to sort out why it happens.
My thinking is if it worked once don't change anything as it should work again ???
That said this morning I have the "Device not available" showing. All I did to make it happen was unplug my router so I could tidy up the cables then plug it in again the same as it was before.Now i cant connect to the classic I just get the same "Device not available" . :( I have tried several times over the last few hrs and nothing works.
I hate intermittent problems as its hard to know why its happening.
QuoteNow this week, I'm gone again and go to bring up the remote app and...nothing again. It said the same thing "connecting" "Device not available"...so I'm thinking it's got to be the DYN connection...THEN, out of the blue, yesterday, I click on it and out of the blue IT WORKS! And it works all day with no problems.
I get the same issue as above but again I try not to change settings as it usually starts to work again on its own. Some times after trying most of the day it can get frustrating. Its usually then when I give up and then by chance its starts to work.
kurt
Thanks Kurt
My son will be at the ranch this weekend and I'm going to have him reboot the router and we can give that a try... let's hope.
Quote from: plongson on December 27, 2012, 08:26:45 PM
More questions...I sure wish I knew more about networking...but,
Yes, me too ! Just when I'm feeling pretty knowledgeable about networking, even internal workings,
something new comes along and I feel so dumb.
I guess that's why the network gurus (if you can find them) make the big bucks !
boB
Well, my son is at the ranch and he reset the modem and the router, went from STATIC to DCHP and back, even disabled WEB ACCESS...testing with me on the phone between every step and no luck. The Remote Status panel will not connect from this end. I still am using port 502 cause that is a bit more than I want to ask him to do right now.
Everything still ended up with "DEVICE NOT AVAILABLE" ...
At this point, the remote just doesn't work...
Have you tried having him reset the Classic? I can send you the URL to one of my classics to try to make sure you are seeing the outside world? Let me know via PM and I can do that
Ryan
Thanks Ryan, we'll do that next (reset). I'll send yor a PM right now.
He reset the classic and...NFG...It is set to reset every-night in the TWEEKS though anyway. Did you get the PM?
Just checking but you did set up the port forwarding in the router correct? It will be interesting to see if you can see my Classic.
Ryan
WTF?? Device unavailable accessing yours...
Well I am not sure what to say? If you send me the credentials for yours via PM I will see if I can see it from here? I have seen cases where public internet locals block certain ports and can cause issues like this.
Ryan
I think I just tried yours and it tried but failed. Is someone looking at it at home? The Classic supports only 1 connection at a time.
Ryan
Nope, no one is on and the status panel is off.
What is really nuts is I cannot access YOUR Classic from MY MSSP... It's like my installation of MSSP is FUBAR. I have already deleted and re installed the app, even downloaded it again and reloaded it to no avail...
Not being able to access yours pretty much proves it isn't a port 502 issue on my end... I would think. :-\
By the way Ryan, I really appreciate you taking the time to work on this problem with me.
Paul
Ryan, the MSSP hooked up to your classic this morning, so I guess the app is OK. Still no connectivity to my Classic. Just an update.
If you were to pick a new port to forward to what would you suggest?
My guess is it is not the port as 502 should be flawless. You mentioned you played with Static and DHCP on the classic? Did you go into the actual router and change the ip address for the classic for the port forwarding? I know I did that one trip I had forgot to make sure the IP address in port forwarding matched the Classic. I can still not see yours so my guess is it is a port forwarding issue in the router if a power cycle of the classic did not make it work for a little while.
What do you have for a router at home?
Ryan
Ryan, I haven't been into the router (at the classic site) since initial setup and all was well on both ends. When I made that comment about static/DHCP, no numbers were changed, just switching between STATIC/DHCP in the classic and testing the response at each change.
As far as the router at the Classic location, again nothing has changed because I cannot access but it was communicating. Yesterday, the CAT-5 was plugged and replugged on the router end but not on the classic end, I didn't want my son in there, I'll try that next weekend.
The router on this end (non classic end) is a Cisco/Linksys. What are you thinking here? Maybe this end is blocking the 502? Crap, I dunno at this point.
What happened to Midnite supporting a web-based monitoring site? Is that still in the works? I paying $20 a year to DYNDNS for that service, I gladly pay that to Midnite just to not have these headaches.
Magnum has a web setup for their stuff, but it's $$$$$
Na it is definitely either on the classic end or DynDNS. Can someone on site go to www.whatismyip.com and tell us what the public ip address is at this time. We can then try that in the app instead of the dyndns account name. This will tell us witch one it is?
Ryan
We're dead now because my son just left the ranch and no one is at the house until probably Friday.
So what are you saying...If I get that location IP address at that moment, I can put that address into the Classic (and the router?), and we should see the Classic?
No put that address into the app. Basically this will replace DynDNS and tell you which one of the 2 are this issue.
Ryan
Well, until next weekend, I'll give this one a rest... LOL
Thanks, Ryan
I am having some trouble setting up a Classic here at the house on this old Westell DSL modem that used to work
for port forwarding but doesn't seem to now...
I can ping it from the outside but can't see the classic. Maybe it's because it is set up as PPP and not router ?
There is not manual for it so it is hard to tell how to exactly use it although I have gotten it to work before.
boB
Quote from: offgridQLD on December 27, 2012, 09:06:48 PM
That said this morning I have the "Device not available" showing. All I did to make it happen was unplug my router so I could tidy up the cables then plug it in again the same as it was before.Now i cant connect to the classic I just get the same "Device not available" . :( I have tried several times over the last few hrs and nothing works.
I hate intermittent problems as its hard to know why its happening.
Strange behaviour indeed.
I can think of two possible issues worth investigating
1. IP numbers, when you repowered the router it rediscovers what devices are on your local network and where necessary uses dhcp to allocate IP numbers from its ip number pool to devices not already with an ip number. These devices can include laptops,desktops,tv,DVD player,iPads,cellphones,iPods,etc.. And of course Classics.
If one of these is given the IP number you are trying to use on the Classic then it's a problem, the local app can find the ip number you have specified in the local app setup BUT the device responding in not a Classic, hence the device not available message from the local app.
Possible solution is to set the Classic to an IP number well outside the dhcp pool (which often starts at 100 and can be up to 150). So try selecting a number below this. Eg 70. So classic is at 192.168.1.70 mask 255.255.255.0 -assuming your LAN is using the 192.168.1.0 class C network.
2. The Ethernet cable from Classic to router may not be providing the cleanest signal or my be at borderline signal levels. After a while (seconds to days) the router or Classic may after multiple retries manage to communicate but in meantime the local app can't find the Classic hence device not available message.
Possible solutions: replace Ethernet cable, use different port on the router's Ethernet hub, use shorter Ethernet cable and if there is still a problem then use a real short Ethernet cable from the Classic to a small powered Ethernet hub situated near the Classic and run the longer Ethernet cable from another port in the hub to you router. This appears to clean up and strengthen the Ethernet signalling.
Hope this helps
Dgd
Quote from: Halfcrazy on December 27, 2012, 12:28:36 PM
I am told the Error #2002 is a bogus Adobe Air thing. Andrew says it has nothing to do with Working or Not Working.
Ok I'm biased here but it's such a pity to have the local app locked into this adobe crap. When air was dropped from Linux it removed any desire I had to support them. They even force you to take the air crap when you d/l any of their other products (you can't opt out )
It sort of brings into question if the fancy car-dash graphics of the local app are worth having if the price is to allow another software corporate to lock you into their products. That's the real reason they dumped Linux support, they can't so easily lock a Linux machine into their products.
Since all the Classic data is easily available via modbus then a nice open source C++ based local app using the modbus lib and one of the freely available graphics libs is IMHO the way to go..
Ok, rant over, back to the single malt.... :P
Happy new software bug free, Ethernet working perfectly and lots free KWhrs new year
Dgd
Quoteback to the single malt....
I'm a Kentucky Straight Bourbon Whiskey man myself, and depending on the outcome of my labors on the Classic this weekend, I'll have an excuse to toast success or sorrow. LOL
I believe there is some ongoing work being done to free us from the AIR environment.
(HTML 5 maybe ? )
We looked at a LOT of different multi-platform environments and Adobe AIR was the best
and offered the most possibilities.
Java and everything else are not very good turns out. They lack a lot of network and programming
niceities. Did you know that Java does not even have signed arithmetic ? Or maybe it was
unsigned arithmetic ? One of them anyway.
boB
Quote from: dgd on January 02, 2013, 03:04:07 PM
Ok I'm biased here but it's such a pity to have the local app locked into this adobe crap. When air was dropped from Linux it removed any desire I had to support them. They even force you to take the air crap when you d/l any of their other products (you can't opt out )
It sort of brings into question if the fancy car-dash graphics of the local app are worth having if the price is to allow another software corporate to lock you into their products. That's the real reason they dumped Linux support, they can't so easily lock a Linux machine into their products.
Since all the Classic data is easily available via modbus then a nice open source C++ based local app using the modbus lib and one of the freely available graphics libs is IMHO the way to go..
Ok, rant over, back to the single malt.... :P
Happy new software bug free, Ethernet working perfectly and lots free KWhrs new year
Dgd
Dgd;
Exactly my thoughts. I am very unhappy when I have to use proprietary software. More so when it means I have to use other proprietary software (spelled M$) to use that proprietary software.
I also understand the need to support the broad swath of users.
I cannot see it being that hard to code up a similar app without the Adobe crap?
Tons of graphic apps / libraries for open source systems.
Maybe an SDK for the Classic App bits would stimulate some folks to code up some superior apps without the BS of proprietary hoops to get things working.
BTW, my Local App (Ubuntu) has started to bail out again after several weeks of running fine. With everything buried in locked software it is very hard to sort out "why".
/end rant.
Anyway, we are likely on the same page here.
Tom
Quote from: plongson on January 02, 2013, 04:36:53 PM
Quoteback to the single malt....
I'm a Kentucky Straight Bourbon Whiskey man myself, and depending on the outcome of my labors on the Classic this weekend, I'll have an excuse to toast success or sorrow. LOL
you need an excuse? :o I gave those up years ago since I discovered a little amber nectar lubricates groking software gremlins. I wonder how much easier it would be to configure and network a Classic if the instruction manual started with..
1. Pour out a double single malt Scotch Whisky (or equivalent substitute (not that there really is such a thing! ::) ))
2. Add a tad of cold water
3. Imbibe and enjoy the warmth
4 Repeat steps 1 to 3 if not warm enough
5. Proceed to install Classic.. etc..
BTW, Paul, I hope your weekend sojourn finds and squishes that network gremlin
dgd
HaHa...! An excuse? Nah, been enjoying this juice far too long for that...LOL
I'm not to the point yet where all I have is Ketchup and hot sauce in the 'frig but we did take a vacation and tour the distilleries of Kentucky.
Damn, did this get off topic or what?
Quote from: dgd on January 02, 2013, 05:50:25 PM
I wonder how much easier it would be to configure and network a Classic if the instruction manual started with..
1. Pour out a double single malt Scotch Whisky (or equivalent substitute (not that there really is such a thing! ::) ))
2. Add a tad of cold water
3. Imbibe and enjoy the warmth
4 Repeat steps 1 to 3 if not warm enough
5. Proceed to install Classic.. etc..
dgd
dgd;
If they did that in "official" documentations their lawyers would have a stroke.
Just sayin...
Not a drinking man anymore but never got the taste for Scotch, preferred Jack Daniels or some of the liquid corn my uncles distilled in the barn basement. It was good for degreaseing parts, too.
Tom
Quote from: TomW on January 02, 2013, 05:29:39 PM
Maybe an SDK for the Classic App bits would stimulate some folks to code up sonme superior apps without the BS of proprietary hoops to get things working.
Tom
yes, that would be a move in the right direction. When we (eventually) see some user developed monitoring/reporting software then these will add to the Midnite experience, hopefully stimulating interest (and sales).
Much like an online store would do (sorry couldn't resist this poke ;D )
dgd
Quote from: dgd on January 02, 2013, 05:50:25 PM
Quote from: plongson on January 02, 2013, 04:36:53 PM
Quoteback to the single malt....
1. Pour out a double single malt Scotch Whisky
2. Add a tad of cold water
dgd
Awhk eye Laddie, #3 is an abomination to a RRRRReeeeel Scot, men have been hung for less!
The ohnly waaater that shuuudd be in the tot is ICE!
back to topic...
Quote from: boB on December 30, 2012, 06:55:51 PM
I am having some trouble setting up a Classic here at the house on this old Westell DSL modem that used to work
for port forwarding but doesn't seem to now...
I can ping it from the outside but can't see the classic. Maybe it's because it is set up as PPP and not router ?
There is not manual for it so it is hard to tell how to exactly use it although I have gotten it to work before.
boB
ISPs use encapsulated PPP (eg PPP over atm - PPPoA) on DSL links as a transport layer for IP traffic hence providing internet services over broadband DSL. So the PPP setting is good.
If the DSL modem/router has done port forwarding before then its probably a case of RTM to get it working again. Google for the manual or if the ISP supplied the modem call their tech support ;D
dgd
Quote from: dgd on January 03, 2013, 01:47:05 AM
Quote from: boB on December 30, 2012, 06:55:51 PM
I am having some trouble setting up a Classic here at the house on this old Westell DSL modem that used to work
for port forwarding but doesn't seem to now...
I can ping it from the outside but can't see the classic. Maybe it's because it is set up as PPP and not router ?
There is not manual for it so it is hard to tell how to exactly use it although I have gotten it to work before.
boB
ISPs use encapsulated PPP (eg PPP over atm - PPPoA) on DSL links as a transport layer for IP traffic hence providing internet services over broadband DSL. So the PPP setting is good.
If the DSL modem/router has done port forwarding before then its probably a case of RTM to get it working again. Google for the manual or if the ISP supplied the modem call their tech support ;D
dgd
Thanks dgd ! I did finally get it to work and port forward just fine.
It had been quite a while using that Westell modem but I played and figured it out again.
I don't remember it being ppp or pppoe a few years ago and so I thought it had changed some how.
boB
Here is the update on "Device not Available".
I got back to the ranch last night and hit this project first thing this morning. I borrowed a laptop with a Verzion 3-G stick so I could test locally. I checked my local router settings and it had the correct hostname, port 502 and the Classic IP was 192.168.11.30 just as I left it.
I go check the Classic and it is 192.168.11.29. I made the appropriate settings in the router and viola, the MSSP jumps to life...no mystery there, although I am very happy.
But what the heck happened?? First off, this place is WAY off grid and no one is messing with it. We can rule that out up front. The App worked great for weeks then went down for two weeks only to come up on Christmas Day then was down until I made the correction.
Does the Classic have a built in default IP that it could fall back on? I just matched the router to the Classic just in case.
SO...THANKS for all the help and advise. For now it is working and I REALLY hope it stays connected.
Bottom line, the IP's did not match. Now I just need to find out how/why it happened.
Paul
plongson;
Now that is curious.
Mine has run a few weeks or so and never saw it change IP address once I set it to static.
Maybe you have mischievous packrats or a poltergeist?
Maybe it (or the router) rebooted and got a fresh IP from the router?
I have seen that happen to other devices. Have an IP then reboot and gets a different IP because the DHCP server thinks the original lease was still valid / in use??
Good luck with it.
Tom
Hey Tom, the Classic is on static and I assure you I believe in both packrats AND poltergeist! LOL
I've been in troubleshooting maintenance all my life, both mechanical and electrical and I've found it it can go wrong it WILL go wrong. Sometimes there is just no logical explanation for "events" other than HooDoo or VooDoo.
Actually the fix was easy, I'm no network guy, but I'm learning. Just hope the gremlins go elsewhere to play for a while.
Paul
So the classic was in static and it changed addresses?
Okay so what what is the software revision?
The classic should not be changing IP addresses if it's static.
boB
The Classic was/is in STATIC and here is the other dope...
Classic 250V (rev 4)
MAC: 06:1F:D0:00:04:22
Device ID: 929F 73E3
IP: 192.168.11.29:502
Firmware:
- Classic Rev: 1181
- Network Rev: 1122
Dunno'...
Quote from: plongson on January 05, 2013, 03:00:24 PM
The Classic was/is in STATIC and here is the other dope...
Classic 250V (rev 4)
MAC: 06:1F:D0:00:04:22
Device ID: 929F 73E3
IP: 192.168.11.29:502
Firmware:
- Classic Rev: 1181
- Network Rev: 1122
Dunno'...
Its all working now :) theres that excuse you needed. ;)
When I install new networks with 'odd' devices on it I often write the ip address on a sticky label and attach on side just in case the IP fairy makes a surprise visit and numbers get adjusted.. although DHCP is a well beaten scapegoat :o
dgd
Quote from: plongson on January 05, 2013, 03:00:24 PM
The Classic was/is in STATIC and here is the other dope...
Classic 250V (rev 4)
MAC: 06:1F:D0:00:04:22
Device ID: 929F 73E3
IP: 192.168.11.29:502
Firmware:
- Classic Rev: 1181
- Network Rev: 1122
Dunno'...
Just for grins, try setting the classics static IP address outside of the routers DHCP allocation Space if it happens to be inside of it now
boB, I'll see what I can do but what is an example of the number range?
We already got a start on celebrating the success...LOL It's too damn cold to do much else...
(http://i1199.photobucket.com/albums/aa471/plongson/Odds%20and%20Ends/Whiskey_zpsac943a80.jpg)
Quote from: boB on January 05, 2013, 06:53:21 PM
Just for grins, try setting the classics static IP address outside of the routers DHCP allocation Space if it happens to be inside of it now
boB;
Just FYI, I have had mine set for static with an IP within my DHCP range with no issues (so far). I am comfortable with networking and related geeky stuff so figured I could sort out any IP issues if they arose.
My DD-WRT router seems to sense when an IP is in use and not pass it out.
My Classic info:
Classic 150V (rev 4)
MAC: 06:1F:D0:00:08:8F
Device ID: 4445 531A
IP: 192.168.2.129:502
Firmware:
- Classic Rev: 1181
- Network Rev: 1122
My DHCP range is from .100 to .150 and I have something like 15 devices on the LAN and most get DHCP setup info.
Just FYI
Tom
Paul, has your IP address changed since .29. ??
Try this, turn off the classic and the router and turn them both back on again and see if the IP address days put. In fact, try that a couple of times.
boB
Quote from: TomW on January 05, 2013, 08:23:05 PM
Just FYI, I have had mine set for static with an IP within my DHCP range with no issues (so far). I am comfortable with networking and related geeky stuff so figured I could sort out any IP issues if they arose.
My DD-WRT router seems to sense when an IP is in use and not pass it out.
My DHCP range is from .100 to .150 and I have something like 15 devices on the LAN and most get DHCP setup info.
Just FYI
BTW FYI AFAIK Cisco WRT54G DHCP groks C150
ie DHCP works fine with Classic
HNY
dgd
Well, here we go again.
As soon as I got back in town I tried running the app. Guess what, "Device Not AVAILABLE". GRRRRR!
I tested it on two laptops before I left, one connected to the local network and he other connected to the 3g stick. I swapped back and forth etc and all was fine.
Here, I used this local laptop AND tested the same laptop/3g stick that worked just a few hours before and it too says "Device Not AVAILABLE"...WTF is going on? I sure wish I had someone there who could check and make changes while I'm here...
If that IP has changed again i'm really stumped.
Oh well, I'll just keep plugging along.
Paul
plongson;
Have you broken a mirror or had a black cat cross your path lately? Maybe walked under a ladder?
Too bad you can only be in one place at a time. It makes sorting it out kind of tough.
I can't offer anything but sympathy. That is darned weird.
Personally, I would set up a Linux laptop on site and forward another port to it so you could log in to it and see what is happening on the local network. Maybe even export the desktop to a remote computer to run the app on the local network? Beyond that, without someone on site to check things, I have no idea how to help sort out what is going on.
Good luck with it.
Tom
Maybe if set up a LOGMEON type of thing and left the laptop running I could be in both places. I still wouldn't know if the Classic had a new IP though.
Quote from: plongson on January 07, 2013, 10:42:10 AM
I still wouldn't know it the Classic had had a new IP though.
plongson;
Well, if you can get on the local network you can ping the classic IP and see if it is live. If you can get a browser to look at active clients page of the router it shows what is on the network with what address. Every network device has a unique "MAC address" the router shows that info for active clients so you can be sure the Classic has the right IP if the address is active. At least mine does.
My Classic is named C150-1 as this copy / paste shows from my router:
Name IP Address MAC Address Active Connections
pi2 192.168.2.125 B8:27:EB:96:E9:22 0
C150-1 192.168.2.129 06:1F:D0:00:08:8F 2
There is the possibility the ISP is blocking certain protocols or ports but then it seems you would not have gotten it to work by going out then back in when you were there.
May need one of the big brains to help sort this one out, I am just shooting at shadows. ;D
Tom
Quote from: plongson on January 07, 2013, 10:25:14 AM
Well, here we go again.
As soon as I got back in town I tried running the app. Guess what, "Device Not AVAILABLE". GRRRRR!
I tested it on two laptops before I left, one connected to the local network and he other connected to the 3g stick. I swapped back and forth etc and all was fine.
Here, I used this local laptop AND tested the same laptop/3g stick that worked just a few hours before and it too says "Device Not AVAILABLE"...WTF is going on? I sure wish I had someone there who could check and make changes while I'm here...
If that IP has changed again i'm really stumped.
Oh well, I'll just keep plugging along.
Paul
Cripes! you really need tha bottle now. Ideas..
It would be interesting to hear from the local app developer what the exact meaning of "Device not available" is.
Is it:
No response from IP number, or
No device (Classic) for the IP number the local app is looking at, or
The local app has found the required device (ie Classic) but that the Classic is not responding as it should.
I suspect it covers all cases
Which makes me think your local app where you are, now may not even be seeing the network where the Classic is connected.
So at the town location what is the local network number on the router? ie class C network, is it also 192.168.11.0 with router at .1 ?
What IP number have you told the local app to find the remote Classic at?
dgd
Paul,
just some more suggestions..
So at the remote locatiion all was good? you used laptop with 3G stick that went via one ISP and connected back to your local network (and Classic) via another ISP.
Unless the Classic has a bug that changes its IP number all should be stable at remote end. ;D
It may be worth contacting the help desk of the ISP (town end) and asking if they have active port filtering that could be excluding port 502 (Modbus Protocol). You will probably get a geek who cannot provide an answer so email may be the way. Depending on their security policy you may need to request a port be made available and they may decide the port number.
dgd
The router is 192.168.11.1 and the classic is 192.168.11.29 The router port forward is setup CLASSIC, 192.168.11.29 and port 502
I access the Classic remotely via DYNDNS at barkingdoglodge.dyndns-server.com with the app set and configured there, port 502
If there was an issue with the local ISP blocking 502, the 3g stick shouldn't work would it??
I just contacted the local ISP there and they do not block 502, only IRC and some mail sets. Does this make sense?
I'll bet that frigg'n IP # flipped again...
Quote from: plongson on January 07, 2013, 03:31:48 PM
The router is 192.168.11.1 and the classic is 192.168.11.29 The router port forward is setup CLASSIC, 192.168.11.29 and port 502
I access the Classic remotely via DYNDNS at barkingdoglodge.dyndns-server.com with the app set and configured there, port 502
If there was an issue with the local ISP blocking 502, the 3g stick shouldn't work would it??
I just contacted the local ISP there and they do not block 502, only IRC and some mail sets. Does this make sense?
I'll bet that frigg'n IP # flipped again...
OK, you're positive that the Classic is set to static and you viewed that on the MNGP NET menu ?
We've never seen it go off of STATIC before is why I have to ask. I have seen it change to
one less IP address when in DHCP of course.
I think you did things right but I have to ask. If you have set up remote administration of your
router, you could see if it was on another IP address and if it was, you could change it to
whatever it went to. I would tend to assume that if it did change IP addresses again, it
would go down to .28 but changing IP addresses in static mode is unheard of as yet.
To my knowledge, you would be the first one. Still, asking the net guru what he thinks.
Haven't heard back an opinion yet.
boB
OK, you're positive that the Classic is set to static and you viewed that on the MNGP NET menu? Absolutely, next time I'll take a picture to prove I'm not crazy...LOL
The router isn't set on remote, I wish it was and I wish I knew how to do it.
There might be a chance I'll be back up there one day this week for some business and if so, you can bet I'll be on this one like a chicken on a June bug. I'll get my wife to man a computer here and I'll be there...Probably Wednesday though.
Quote from: TomW on January 07, 2013, 12:18:06 PM
Quote from: plongson on January 07, 2013, 10:42:10 AM
I still wouldn't know it the Classic had had a new IP though.
plongson;
Well, if you can get on the local network you can ping the classic IP and see if it is live. If you can get a browser to look at active clients page of the router it shows what is on the network with what address. Every network device has a unique "MAC address" the router shows that info for active clients so you can be sure the Classic has the right IP if the address is active.
Tom
Or if you get plongson's live IP number for his router then you could tracert -p502 and see what replies after his router 8)
dgd
Paul & dgd, would this be a good use for a PVN, private virtual network,installation?
or is there something better now, used it 8 - 10 years ago for remote access to another cpu...
Quote from: plongson on January 07, 2013, 03:31:48 PM
The router is 192.168.11.1 and the classic is 192.168.11.29 The router port forward is setup CLASSIC, 192.168.11.29 and port 502
I access the Classic remotely via DYNDNS at barkingdoglodge.dyndns-server.com with the app set and configured there, port 502
If there was an issue with the local ISP blocking 502, the 3g stick shouldn't work would it??
I just contacted the local ISP there and they do not block 502, only IRC and some mail sets. Does this make sense?
I'll bet that frigg'n IP # flipped again...
Paul,
Have you brought the laptop with 3G stick with you?
Does it still connect to the Classic when running local app?
If not can the laptop ping the router where the Classic is located?, you will need to ping the 'live IP number as allocated by the ISP
dgd
dgd,
I'm pushing my business up there a day early because the weather is suppose to get $hitty. I'll have a chance this morning to mess with it for an hour or so (once I get there) before I head out for the meeting.
I'll take the LT with the 3g stick and the other LT is onsite. In a nutshell, how do I ping the router from the 3g LT? I was also going to have my wife run the app from this LT taken to her work this morning.
I'm becoming obsessed with finding out WTF is going on wit this thing..LOL
THANKS!!!! for the help!
Paul
Paul;
From inside the Local Network this link will tell you what the routers IP is on the side to the world:
http://www.whatismyip.com/ (http://www.whatismyip.com/)
It might help see if the dyndns or whatever is working right?
Tom
Well, I'm here and made a quick test before I head out for the meeting and the LT with the 3g stick connected to the Classic here.
The IP's did not change and both the router and the Classic had the same .29 number. I used "WhatsmyIP" and got 208.66.36.38 for the LT on the local router. I put that number into the 3g LT Google Chrome Browser and it came up "Oops Google could not connect"
I'm pretty much lost here, what should I try next. I also allowed anonymous ping requests with no joy.
I'll be back in an hour or so and mess with it some more.
Paul
Quote from: Westbranch on January 08, 2013, 12:17:54 AM
Paul & dgd, would this be a good use for a PVN, private virtual network,installation?
or is there something better now, used it 8 - 10 years ago for remote access to another cpu...
I think you mean VPN. That might work - it would require a local computer connected to the router that the classic is connected too. However a VPN in that situation might be overkill since security (the main advantage of a VPN) is likely not an issue (is your classic data Top Secret!). A simpler solution with a local computer left connected is to use one of the many free VNC applications (UltraVNC or TightVNC for Windows or Chicken of the VNC for MacOS are good choices).
This is what I do: I have a small, low power HP netbook ($150 from ebay) that is left connected to the router in my utility room that my classic is wired to. It is running UltraVNC server and allows me to connect to it and view/control the Local Ap from the local network and from any remote internet connected computer, smart phone or tablet. I also run a weather station app and Wattplot on the local computer so I have lots of data and control even when I'm away. I even use the webcam if I want to "look" at my power panel.
Paul, I realize you're trying to diagnose why direct connection to the classic remotely is not working - how frustrating! But the above would be one solution for remote monitoring if you can't figure it out. Good luck.
Paul;
I am not getting a response from that IP you posted.
traceroute gets to cc-cmts.awinetworks.net and then just spins til it times out.
This may not be an issue you can fix. Looks like a routing issue with awinetworks.net from here
I think its time to contact them to see whats going on?
Tom
Quote from: TomW on January 08, 2013, 01:46:25 PM
Paul;
I am not getting a response from that IP you posted.
traceroute gets to cc-cmts.awinetworks.net and then just spins til it times out.
This may not be an issue you can fix. Looks like a routing issue with awinetworks.net from here
I think its time to contact them to see whats going on?
Tom
Paul,
As Tom says that IP number does not seem to be visible on the internet. This really needs to be sorted, contact your ISP.
dgd
Well, check this out. I called my wife 200 miles away and talked her through loading the local app on her office PC. Hostname port 502 etc...and the local app comes up with the status panel. I get her to log off, and it comes up on the 3g stick LT sitting here, Log off the 3g stick and it comes up on the local router sitting here. The biggie is getting it on her office PC.
So all indications are it is working but I have no idea why it does and does not...
I'm still fooling with this for a bit more, anything else to check???
I disabled the firewall on my router here and traceroute went through.
Quote from: mtdoc on January 08, 2013, 01:44:57 PM
Quote from: Westbranch on January 08, 2013, 12:17:54 AM
Paul & dgd, would this be a good use for a PVN, private virtual network,installation?
or is there something better now, used it 8 - 10 years ago for remote access to another cpu...
This is what I do: I have a small, low power HP netbook ($150 from ebay) that is left connected to the router in my utility room that my classic is wired to. It is running UltraVNC server and allows me to connect to it and view/control the Local Ap from the local network and from any remote internet connected computer, smart phone or tablet. I also run a weather station app and Wattplot on the local computer so I have lots of data and control even when I'm away. I even use the webcam if I want to "look" at my power panel.
Yes that is the way to go, a Raspberry Pi fits into that scenario perfectly. Love the idea of a web cam looking at the Classics MNGP.
Next logical step would be one of those low cost robot arms to press the Classic's rubber buttons :P
dgd
Quote from: plongson on January 08, 2013, 02:40:30 PM
So all indications are it is working but I have no idea why it does and does not...
Excellent, I often find that when a wife gets involved the gremlins take flight. :)
Firewalls ::) there to protect your network, even from you. >:(
Quote from: plongson on January 08, 2013, 02:44:08 PM
I disabled the firewall on my router here and traceroute went through.
BRAVO, and a simple , yet very vexing, solution to boot
Quote from: Westbranch on January 08, 2013, 05:50:07 PM
Quote from: plongson on January 08, 2013, 02:44:08 PM
I disabled the firewall on my router here and traceroute went through.
BRAVO, and a simple , yet very vexing, solution to boot
Well that wasn't the solution to the problem, it was just to get traceroute through.
I don't know what the solution was or at this point if the status panel will even continue to run. I didn't do anything up there. All I did was check the IP on the Classic and router, setup my wife to log on remotely over the phone. My end worked, her end worked and I called every so often on the way back to be sure the "Device was Available".
I got here and MSSP came up and I could see my Classic. I haven't a clue why because nothing is different or changed. I'm not gonna @&%@ though...IT"S WORKING FOR NOW!!!
I want to give a BIG THANK YOU to everyone that helped and contributed to my problem. You are a great bunch!! Hopefully I can return the favor sometime.
In the mean time have a couple of virtual shots of that fine Kentucky Bourbon Whiskey pictured earlier in the post...LOL
Paul
(http://i1199.photobucket.com/albums/aa471/plongson/Odds%20and%20Ends/MSSP_zps0a708d58.png)
(http://i1199.photobucket.com/albums/aa471/plongson/Odds%20and%20Ends/rsz_img_0424_zps259ef206.jpg)
Excellent !!
I would really like to know what the deal is though...
SO, the Local App started working withOUT anyone having to go and touch the Classic or your router
at the lodge ???
Go drink your whiskey !
boB
boB, the only "touching" was to check the Classic IP and back out, then check for a connection on the 3g stick LT (which failed the first attempt but was successful when I re-tried the App a second time), then checked the IP on the router (which was also correct). It worked on the office PC in Las Vegas and works right now here at the PC it has not worked for probably 4 weeks.
Dunno, beats the hell out of me. We have a GREAT bunch of very helpful experts here though. I'm very impressed...
Well, you guessed it...get up this morning and check the MSSP and "Device not Available". Something happens overnight that won't allow communication and when it's done, it's done.
I'm done too, I hate defeat but this got me. I'll have to live without this one. :'(
Boy it sure sounds like an issue with the ISP and something stopping that port come back to you? I have never seen intermittent issues like this be the Classic. I am flat lost on this one as well. We could try swapping the Classic if anyone thinks that may be the issue?
Ryan
DGD , yes I did mean VPN, must have dyslectic fingers as well as a dyslectic mind...
Paul, it sounds like you should get a VPN program running, what it does is let you 'run' your home computer from a LT that is elsewhere, ie when you are traveling. Just have to leave the 'slave' running. so you do not have the ? >:( >:(?? as to why you can not connect remotely. that way you can call up the CC250 and if no connection, just look at the CC 'through' the base cpu. you can remotely do anything remotely as long as the base cpu is on line.
I may end up doing that. I just got off the phone with the local ISP and they checked things on their end (very helpful) and all looked good. They said to eliminate the DNS and log in directly without going through a third party and see if that helps. That was also recommended by Ryan, probably the next step but not for about 10 days now...
Quote from: Westbranch on January 09, 2013, 12:09:13 PM
DGD , yes I did mean VPN, must have dyslectic fingers as well as a dyslectic mind...
I think you meant that for mtdoc...
Quote
Paul, it sounds like you should get a VPN program running, what it does is let you 'run' you home computer from a LT that is elsewhere, ie when you are traveling. Just have to leave the 'slave' running. so you do not have the ? >:( >:(?? as to why you can not connect remotely. that way you can call up the CC150(?) and if no connection, just look at the CC 'through' the base cpu. you can remotely do anything remotely as long s the be cpu is on line.
This is an excellent idea and using an el-cheapo low power laptop is the way to go for the 'base' cpu.. and of course its good for monitoring more than one Classic plus other devices such as webcams etc..
dgd
found this one on Tucows, seems to be freeware...http://www.tucows.com/preview/1475767/Free-VPN
Quote from: dgd on January 09, 2013, 02:55:49 PM
This is an excellent idea and using an el-cheapo low power laptop is the way to go for the 'base' cpu.. and of course its good for monitoring more than one Classic plus other devices such as webcams etc..
dgd
Yeah, Here's a screenshot I took from my work computer of the VNC connection view of the HP netbook that monitors my system. (yeah - great production here in the PNW on a rainy January day :() With a free VNC server app on the local computer (UltraVNC in this case)- I can open up that computers desktop from a web browser using the VNC viewer at http://danielwebb.us/software/vnc/vncviewer.html. I can control that computer with the VNC, expand the local app, change settings, etc. Wattplot will even let me make some changes remotely on my Outback inverter- (turn off AC input, trigger Aux, etc).
OK, I'm not leaving this alone...am I?
When I get the "Device not Available" message I also get "UNKNOWN" above the username. Does this mean anything to you? (boB, Ryan, anyone)
Would this appear it's stopping at the DNS, router or Classic? I just on a fishing expedition until I get back.
I'm gonna eliminate the DNS in the next attempt and go straight from here to there and see what happens.
(http://i1199.photobucket.com/albums/aa471/plongson/Odds%20and%20Ends/MSSPscreenshot_zpsad85bc56.png)
mtdoc, right VNC....that was the program I used.
I remembered that it was developed by a research lab called .. ???.. at a Uni...???
Thanks to Wiki-p-d-a, VNC was created at the Cambridge, UK Olivetti & Oracle Research Lab .
Now called RealVNC http://www.realvnc.com/
Great utility for this and still free, though has retail versions with more features.
Lots of good free VNC utilities. I use UltraVNC and TIghtVNC on Windows and Chicken of the VNC for Mac.
A Real VNC Java applet is used on that website I pointed to - handy for looking at your system behind a firewalled system like here in my office. 8)
Quote from: plongson on January 09, 2013, 05:46:42 PM
When I get the "Device not Available" message I also get "UNKNOWN" above the username. Does this mean anything to you? (boB, Ryan, anyone)
Where it says UNKNOWN is where the Classic's name is shown when it connects. The line below is usually the ip number or the DNS server as shown here.
Quote
Would this appear it's stopping at the DNS, router or Classic? I just on a fishing expedition until I get back.
I'm gonna eliminate the DNS in the next attempt and go straight from here to there and see what happens.
Since the "Device not available" is a generic message from the local app then it's not possible to infer any more detail about the exact cause of the error.
Dgd
Well guys, this a milestone. I figured out why the MSSP wouldn't connect and it wasn't the Classic or the router. The reason was mentioned by several of you through this entire thread, but it really never sunk in. Anyway, it's running.
My ISP changed the IP address on me. It's obviously a dynamic service and the timing couldn't be better (worse?) as to change on the frigg'n day after I got it to run at the ranch. MURPHY's Law... It makes me crazy!
I called the ISP and had them ping my account, got the dang CURRENT IP, dumped it into the hostname on DYNDNS, hit the MSSP app and what should appear to my wondering eyes?...the status panel.
I'll bet you guys hate working with Rookies...LOL
Paul
Most routers have a place in them to set up notification for dyndns. This allows the router to notify DynDNS that there has been an IP address change.
Ryan
Dyndns has an updater too. Ya think that will work? I guess we'll see, I loaded it and set it up to monitor that IP.