[adriaanvdc]

Hi Ray,

I’ve upgraded to 2.1.2 and for the last 3 days were able to login successfully without any restarts. Unfortunately with all the rain we had over the last two weeks non of the programs have run.

I’ll provide more feedback once the programs start running again.

Regards,

Adriaan

[adriaanvdc]

Hi Samer/Ray

Thank you Samer.

I’ve order an Atmega1284, and will program that, and see if its more stable. I’ll provide feedback once this is done.

Regards,
Adriaan

[adriaanvdc]

Hi Ray,

I’ve changed the names for all the programs to short names, but +- 18 hours later and the controller is unresponsive (Chrome say waiting for 10.0.0.25…) again. The http://10.0.0.25/jp?pw=opendoor response is now:

{"nprogs":3,"nboards":1,"mnp":14,"mnst":4,"pnsize":12,"pd":[[67,127,0,[360,660,900,-1],[900,0,0,0,0,0,0,0],"GrassTd"],[67,127,0,[380,680,920,-1],[0,900,0,0,0,0,0,0],"GrassBd"],[3,85,0,[400,0,0,0],[0,0,2700,0,0,0,0,0],"TreesDd"]]}

I generally reset the controller before  I go to bed +- 10:00pm and if I check the controller the next morning again +- 07:30am, then it’s unresponsive on the http://10.0.0.25/jp?pw=opendoor command. The other commands does work however….

Could this be a memory issue? Would loading a older firmware help you debug the issue further?

Regards,
Adriaan

[adriaanvdc]

Hi Ray/Samer,

Were you able to determine why this is happening ? Is there any other debug information I can provide that might help with resolving this issue?

Regards,
Adriaan

[adriaanvdc]

Hi Samer,

Thank you for the help!

The output for http://10.0.0.25/jp?pw=opendoor is:
{"nprogs":3,"nboards":1,"mnp":14,"mnst":4,"pnsize":12,"pd":[[67,127,0,[360,660,900,-1],[900,0,0,0,0,0,0,0],"Grass Top"],[67,127,0,[380,680,920,-1],[0,900,0,0,0,0,0,0],"Grass Bottom"],[3,85,0,[400,0,0,0],[0,0,2700,0,0,0,0,0],"Trees Back"]]}
Let me know if you need anything else?

Regards,
Adriaan

[adriaanvdc]

Hi Samer,

I did the JSON tests, and the results are:

1. http://10.0.0.25/jn?pw=opendoor
Response: {“snames”:[“Back-Grass Top”,”Back-Grass Bot”,”Back-Trees”,”S04″,”S05″,”S06″,”S07″,”S08″],”masop”:[255],”ignore_rain”:[0],”act_relay”:[0],”stn_dis”:[248],”maxlen”:16}

2. http://10.0.0.25/jo?pw=opendoor
Response:{“fwv”:210,”tz”:56,”ntp”:1,”dhcp”:1,”ip1″:10,”ip2″:0,”ip3″:0,”ip4″:25,”gw1″:10,”gw2″:0,”gw3″:0,”gw4″:1,”hp0″:80,”hp1″:0,”ar”:1,”ext”:0,”seq”:1,”sdt”:0,”mas”:0,”mton”:0,”mtof”:0,”urs”:1,”rso”:0,”wl”:21,”den”:1,”ipas”:0,”devid”:0,”con”:110,”lit”:100,”dim”:5,”rlp”:0,”uwt”:1,”ntp1″:204,”ntp2″:9,”ntp3″:54,”ntp4″:119,”reset”:0,”dexp”:0,”mexp”:5}

3. http://10.0.0.25/js?pw=opendoor
Response: {“sn”:[0,0,0,0,0,0,0,0],”nstations”:8}

4. http://10.0.0.25/jc?pw=opendoor
Response:{“devt”:1416071394,”nbrd”:1,”en”:1,”rd”:1,”rs”:1,”rdst”:1416096593,”loc”:”pws:IGAUTENG145″,”wtkey”:”*REMOVED*”,”sunrise”:310,”sunset”:1113,”sbits”:[0,0],”ps”:[[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0,0],[0,0]],”lrun”:[1,2,819,1416033220]} – I did change the wtkey.

5. http://10.0.0.25/jp?pw=opendoor
Response: The response took very long and then times out. It does not display anything.

I’ve also checked the console, and no error is displayed in the console.

Whats the way forward?

Regards,
Adriaan

[adriaanvdc]

Hi Ray/Samer,

This is still happening, and appears to be a UI issue, as I’m able to access the system successfully via the API. Can you please let me know what I can do to try and debug the issue?

I’m currently remote rebooting the system before using the UI, but I can’t keep on doing that just so that I can access the UI. I really need this resolved.

Regards,
Adriaan

[Author]

Posts