new classic lite not connectting to local app

Started by mahendra, June 12, 2013, 05:57:49 PM

Previous topic - Next topic

mahendra

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.
1.5kw on Midnite classic 150(whizbang jr.) networked 0.660kw on classic lite 200 wbjr ,180ah CALB Lifepo4 48v battery bank,jkbms 150amps bms(top balanced) Outback vfx3648.
Soon to be added Sol Ark 8k with 5Dyness Bx51000 ,7.8kw pv

atop8918

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.

mahendra

1.5kw on Midnite classic 150(whizbang jr.) networked 0.660kw on classic lite 200 wbjr ,180ah CALB Lifepo4 48v battery bank,jkbms 150amps bms(top balanced) Outback vfx3648.
Soon to be added Sol Ark 8k with 5Dyness Bx51000 ,7.8kw pv

zoneblue

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.

6x300W CSUN, ground mount, CL150Lite, 2V/400AhToyo AGM,  Outback VFX3024E, Steca Solarix PL1100
http://www.zoneblue.org/cms/page.php?view=off-grid-solar

atop8918

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.

RossW

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.
3600W on 6 tracking arrays.
7200W on 2 fixed array.
Midnite Classic 150
Outback Flexmax FM80
16 x LiFePO4 600AH cells
16 x LiFePO4 300AH cells
Selectronics SP-PRO 481 5kW inverter
Fronius 6kW AC coupled inverter
Home-brew 4-cyl propane powered 14kVa genset
2kW wind turbine