A Forum run by Enthusiasts of MidNite Solar

MidNite Solar Monitoring software and hardware => Local App software => Topic started by: mahendra on June 12, 2013, 05:57:49 PM

Title: new classic lite not connectting to local app
Post by: mahendra on June 12, 2013, 05:57:49 PM
i just got a new classic lite 200 to add to my existing classic 150,but it rarely connects to the local app and whenever it does it does not stay on for long and keeps disconnecting.please advise.thank you.i even updated it to the latest firm ware but that didn't help either.
Title: Re: new classic lite not connectting to local app
Post by: atop8918 on June 12, 2013, 06:27:49 PM
I would suggest trying to set the IP address to static using the DIP switches. If there available addresses are not compatible with your network then you can use the local app on the rare moments it connects to assign a static IP address. Make sure t set the DIP switches to "custom mode" for the settings to stick. Be advised that in static mode you must use the Local App to change all other settings.
Title: Re: new classic lite not connectting to local app
Post by: mahendra on June 12, 2013, 06:56:59 PM
did that already still didnt work
Title: Re: new classic lite not connectting to local app
Post by: zoneblue on July 17, 2013, 01:37:59 AM
Do you have the latest local app and latest firmware. I found esp the former helped my timeouts. I use a static address to a router running dhcp and just use the address range outside the dhcp. Works.

Title: Re: new classic lite not connectting to local app
Post by: atop8918 on July 17, 2013, 03:16:12 AM
Yes, those symptoms (connecting and quickly disconnecting) are indicative of a possible address conflict. Have you tried removing the original Classic from the network to see if the Lite then connects reliably? If that is the case then it is possible that the addresses are conflicting.
Title: Re: new classic lite not connectting to local app
Post by: RossW on July 17, 2013, 05:04:36 AM
Quote from: atop8918 on July 17, 2013, 03:16:12 AM
Yes, those symptoms (connecting and quickly disconnecting) are indicative of a possible address conflict.

Any device SHOULD do an ARP WHOHAS (IP address) *BEFORE* it binds to the address itself, and certainly way before anything could connect to it.