Page 1 of 2

Portal DDNS

Posted: Sun May 05, 2013 6:11 pm
by coolbird
HI

I keep updating the portal address from the ip to the DDNS (tested and working) but it keeps reverting back to the ip! :oops:

Re: Portal DDNS

Posted: Sun May 05, 2013 6:15 pm
by rimai
The ip address should be your public ip address, isn't it?
The portal updates the address by itself everytime the controller pings the server. Kind of a DDNS service :)
So, when your isp changes your ip, the next time the controller pings the server, it will send along the updated ip address and the portal will save that ip automatically.

Re: Portal DDNS

Posted: Sun May 05, 2013 6:22 pm
by coolbird
I think I know what the problem is, I need to enter the DDNS address in the wifi adapter itself.

Will try again in the morning.

Portal DDNS

Posted: Sun May 05, 2013 7:17 pm
by lnevo
Dont bother. The portal will change it. You only need dyndns for iphone/android apps

Re: Portal DDNS

Posted: Sun May 05, 2013 7:46 pm
by coolbird
But I am getting
Unreachable Address in the portal yet it is getting the readings off the RA, I can contact the wifi inside the network and external (throught the DDNS) but there is no remote control.

Portal says "Only available with valid wifi address. To add or update your wifi address, please click on the update link, next to Reef Angel logo above the dashboard. Please make sure you have setup your router with DDNS properly and that you can connect to your Reef Angel Controller remotely." which I presume to mean I am to enter my DDNS address!!

Android is getting a, "Error 23: XMLSAX Parser" error

Thanks for any help

Re: Portal DDNS

Posted: Sun May 05, 2013 7:47 pm
by rimai
Yeah, I need to update that message.
It was created when we didn't have this ip auto update feature.
What you need to do is setup port forwarding on your router.

Re: Portal DDNS

Posted: Mon May 06, 2013 2:20 am
by coolbird
Need some help with this one, I am still getting unavailable address in the portal, yet the portal is getting data from the RA.
I have checked port 2000 and that is open.
DDNS is setup and working (I can run the basic web server at http://xxxxxxxxxx:2000/wifi

when click on my address (either the IP or the DDNS address) on the RA banner in the portal I recieve:

HTTP/1.1 200 OK
Server: ReefAngel
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Connection: close
Content-Type: text/html
Content-Length: 41

<h1>Reef Angel Controller Web Server</h1>

Any help would be gratefully received.

Thanks

Re: Portal DDNS

Posted: Mon May 06, 2013 7:57 am
by rimai
http://www.yougetsignal.com/tools/open-ports/
Are you using this to test your port 2000?

Re: Portal DDNS

Posted: Mon May 06, 2013 8:32 am
by coolbird
rimai wrote:http://www.yougetsignal.com/tools/open-ports/
Are you using this to test your port 2000?
Hi Roberto

Yep, I have checked both the ip address and the DDNS address both show port as open! :(

Re: Portal DDNS

Posted: Mon May 06, 2013 8:41 am
by rimai
Can you access your controller using web browser?
http://ipaddress:2000

Re: Portal DDNS

Posted: Mon May 06, 2013 9:34 am
by coolbird
rimai wrote:Can you access your controller using web browser?
http://ipaddress:2000
Yep I can get it locally with http://ip addess:2000/wifi and externally throught the external web address showing in the portal and the DDNS address.

Confusing

Dave

Re: Portal DDNS

Posted: Mon May 06, 2013 11:38 am
by rimai
I got the same results.
Are you behind a proxy of some sort?

Re: Portal DDNS

Posted: Mon May 06, 2013 11:42 am
by coolbird
rimai wrote:I got the same results.
Are you behind a proxy of some sort?
Hi

Clever question but no,,,no proxy, strange isnt it!!

Regards
Dave

Re: Portal DDNS

Posted: Mon May 06, 2013 11:49 am
by rimai
Yeah... Server is responding:
System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine
on this line:
HttpWebResponse response = (HttpWebResponse)request.GetResponse();
When it tries to connect to your controller, but any attempt I try with browser yields in successful connections.
I did try to trace route, but keep getting timeouts. I'm not sure if this would affect anything or not... :(

Code: Select all

Tracing route to cpc18-stkp8-2-0-cust121.10-2.cable.virginmedia.com [86.4.11.122
]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  69.198.171.165
  2     4 ms     4 ms     4 ms  172.28.141.148
  3   213 ms   200 ms   188 ms  192.168.67.94
  4   284 ms   386 ms   368 ms  207.239.114.153
  5     *      182 ms   167 ms  vb1500.rar3.sanjose-ca.us.xo.net [216.156.0.137]
  6   201 ms   225 ms   214 ms  207.88.14.226.ptr.us.xo.net [207.88.14.226]
  7   252 ms   260 ms   293 ms  te4-2-10g.ar2.sjc2.gblx.net [64.208.110.113]
  8   396 ms   220 ms   200 ms  ae9-40g.scr4.snv2.gblx.net [67.17.72.13]
  9   339 ms   332 ms   357 ms  xe7-0-0-10g.scr4.lon3.gblx.net [67.16.164.13]
 10   367 ms   398 ms   491 ms  lag2.ar9.lon3.gblx.net [67.17.106.149]
 11   417 ms   432 ms   470 ms  virgin.lag4.ar9.lon3.gblx.net [64.214.128.38]
 12   414 ms   327 ms   315 ms  bagu-core-2b-ae0-0.network.virginmedia.net [80.5.161.246]
 13   415 ms   445 ms   434 ms  stkp-cmts-08-gigaether-11.network.virginmedia.net [82.8.210.198]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Re: Portal DDNS

Posted: Mon May 06, 2013 11:53 am
by coolbird
I think the only alternative is to reset the wireless and the RA and start again!

I am in the uk so will try tomorrow, thanks for the help at least you confirmed to me that I am not going senile.

Regards
Dave

Re: Portal DDNS

Posted: Mon May 06, 2013 1:08 pm
by coolbird
I was just checking my skimmer (its a new one and they make me nervous when they new) and I noticed that the RA wasn't dispaying some characters properply so i rebooted it and hey presto everythings working as it should.

Very weird.

Thanks for all your help.

Regards
Dave

Re: Portal DDNS

Posted: Mon May 06, 2013 1:11 pm
by rimai
Cool!

Re: Portal DDNS

Posted: Mon May 06, 2013 1:18 pm
by coolbird
Spoke to soon within 5 minutes it was back to unreachable address.

Will reset tomorrow. :-(

Re: Portal DDNS

Posted: Tue May 07, 2013 10:44 am
by coolbird
I have tried to reset the wifi adapter but failed, instructions say you can use a jumper inside the unit,,,there isnt one!
tried tera term and it will not accept my username and password which i presume is the same as the forum.

the wireless utility said it had reset to defaults but i doubt it didhave tried to run the wifi utility again, installed the ra preloaded code and run the wizard again and everything worked fine until i tried the wifi again, with the wifi attached to the pc with the usb cable i get a slow blinking green and the router says its connected, but when i try and run the wifi setup (press jostick) it just sits there with the wifi adapter fast blinking green and amber.

This is getting very frustrating any ideas would be gratefully received

Dave

Re: Portal DDNS

Posted: Tue May 07, 2013 11:01 am
by rimai
The jumper was replaced by the button.
You can press it instead of placing the jumper.
Tera term doesn't require username and password.
All you need to do is send "$$$" to enter command mode.
At factory settings, it communicates at 9600 baud. Once configured, it communicates at 57600 baud.
If you already have blinking green and router says connected, there is nothing else to be done. It's already setup.

Re: Portal DDNS

Posted: Tue May 07, 2013 11:06 am
by coolbird
rimai wrote:The jumper was replaced by the button.
You can press it instead of placing the jumper.
Tera term doesn't require username and password.
All you need to do is send "$$$" to enter command mode.
At factory settings, it communicates at 9600 baud. Once configured, it communicates at 57600 baud.
If you already have blinking green and router says connected, there is nothing else to be done. It's already setup.
Hi
By the button do you mean the recessed button you press with a paper clip?

my mistake on the tera term I did read that somewhere and forgot :-(

I have re-uploaded the initial memory and ra preloaded and then the wizard so at least my tank is working again but one thing i did notice was that before i restarted the 3rd temp error message on the display was only showin E
and the ra was not responding

Re: Portal DDNS

Posted: Tue May 07, 2013 11:08 am
by rimai
Yes, that button.
How many probes do you have?

Re: Portal DDNS

Posted: Tue May 07, 2013 11:15 am
by coolbird
rimai wrote:Yes, that button.
How many probes do you have?
Just the one, if i can get this going I will be ordering the other 2 and the orp and salinity attachements, except for this wifi problem i like this controller :-) (i am sure its all my own fault anyway)

Re: Portal DDNS

Posted: Tue May 07, 2013 11:21 am
by coolbird
A quick question on uploading the wifisetup to the ra

I am presuming that as my router settings are WPA2 I should be using auth mode 4 or should it be 3???

Thanks
Dave

Re: Portal DDNS

Posted: Tue May 07, 2013 11:26 am
by rimai
Yes, you can use 4.
Basically, from what I've experienced, the module disregard that setting anyway.

Re: Portal DDNS

Posted: Tue May 07, 2013 11:29 am
by coolbird
rimai wrote:Yes, you can use 4.
Basically, from what I've experienced, the module disregard that setting anyway.
Just trying to find a reason for this problem, from my experience it is likely to be something simple that I have overlooked.

Re: Portal DDNS

Posted: Tue May 07, 2013 11:46 am
by coolbird
coolbird wrote:
rimai wrote:Yes, you can use 4.
Basically, from what I've experienced, the module disregard that setting anyway.
Just trying to find a reason for this problem, from my experience it is likely to be something simple that I have overlooked.
So effictively all i have to put in the wifisetup code is my ssid and my passphrase.

do I need to do anything with the wlan_wep_num or wlan_wep_key or do I leave all the rest of the code alone, I havnt been changing any of this

Re: Portal DDNS

Posted: Tue May 07, 2013 11:49 am
by rimai
Yes, but the best option is really the wify utility.
Or, you can use this macro file with Tera Term. This will ensure the settings are all properly setup.

Re: Portal DDNS

Posted: Tue May 07, 2013 11:57 am
by coolbird
rimai wrote:Yes, but the best option is really the wify utility.
Or, you can use this macro file with Tera Term. This will ensure the settings are all properly setup.
OK will give it a try

Re: Portal DDNS

Posted: Tue May 07, 2013 11:58 am
by coolbird
coolbird wrote:
rimai wrote:Yes, but the best option is really the wify utility.
Or, you can use this macro file with Tera Term. This will ensure the settings are all properly setup.
OK will give it a try
JUst one thing do you mean the wifi utility in the reef angel controller setup?