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.rimai wrote:Can you access your controller using web browser?
http://ipaddress:2000
Confusing
Dave
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.rimai wrote:Can you access your controller using web browser?
http://ipaddress:2000
Hirimai wrote:I got the same results.
Are you behind a proxy of some sort?
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.
Hirimai 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.
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)rimai wrote:Yes, that button.
How many probes do you have?
Just trying to find a reason for this problem, from my experience it is likely to be something simple that I have overlooked.rimai wrote:Yes, you can use 4.
Basically, from what I've experienced, the module disregard that setting anyway.
So effictively all i have to put in the wifisetup code is my ssid and my passphrase.coolbird wrote:Just trying to find a reason for this problem, from my experience it is likely to be something simple that I have overlooked.rimai wrote:Yes, you can use 4.
Basically, from what I've experienced, the module disregard that setting anyway.
OK will give it a tryrimai 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.
JUst one thing do you mean the wifi utility in the reef angel controller setup?coolbird wrote:OK will give it a tryrimai 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.
I am not sure thats the problem it sets up ok with this and reports that it opens port 2000, but that said when i try and run the firmware update i get an error.rimai wrote:This utility:
http://forum.reefangel.com/viewtopic.php?f=15&t=345
Ok then all it leaves me with the thought that I am doing something wrong when I am uploading the wifisetup code!!!rimai wrote:That may be related to the recent change on the firmware 4.00
I have not updated the wifi utility for that.
It requires a two step process as described in their manual and here:
http://www.rovingnetworks.com/FAQs/How_ ... y_versions
This update will also disable the WPS feature and enable the SoftAP with built-in webserver for config changes.
The internal webserver for config changes is awesome!!! Too bad they are sharing the same idle timer... We use timer of 3 seconds and it is not long enough to do anything.
I've been in touch with them and they said that more config options will be implemented, but there is no real timeframe for that.
enigma32 is working on a new type of remote connection, so let's see what he comes up with.
I reset the RA and the wifi, although the wifi was a bit of a problem, I tried the tera term method and the terminal just displayed what could best be described as jibberish, to make matters worse the reset button on the wifi adapter did not work, once pressed the adapter just continued to blink green slowly.coolbird wrote:Ok then all it leaves me with the thought that I am doing something wrong when I am uploading the wifisetup code!!!rimai wrote:That may be related to the recent change on the firmware 4.00
I have not updated the wifi utility for that.
It requires a two step process as described in their manual and here:
http://www.rovingnetworks.com/FAQs/How_ ... y_versions
This update will also disable the WPS feature and enable the SoftAP with built-in webserver for config changes.
The internal webserver for config changes is awesome!!! Too bad they are sharing the same idle timer... We use timer of 3 seconds and it is not long enough to do anything.
I've been in touch with them and they said that more config options will be implemented, but there is no real timeframe for that.
enigma32 is working on a new type of remote connection, so let's see what he comes up with.
Hirimai wrote:You don't need to run the wifi setup code.
If you already have it setup on the wifi utility, you are all set.
The wifi setup code is just another option to get it setup, but you already have it setup by using the wifi utility.
Would you be able to help me understand where my mistake was in the manual that makes it confusing and people just think that they need to run the code too after they used the wifi utility?
There are 4 setup methods explained in the manual.
1. Setting up your Reef Angel Wifi Attachment using WPS Push-Button
2. Setting up your Reef Angel Wifi Attachment using the Wifi Utility
3. Setting up your Reef Angel Wifi attachment using your Reef Angel Controller
4. Manual Setup of your Reef Angel Wifi attachment
Maybe I should just say "Jump to section: Connecting your Reef Angel Wifi attachment to the Head Unit" at the end of each method??
Is it the piece I'm missing?
Uploading the test code
1. Start your Arduino software
2. Open the wifi test setup code by going to menu File->Sketchbook->Example Codes and selecting WifiTestCode
3. Upload the code to your Reef Angel Controller.
4. After uploading the code, disconnect the USB-TTL converter cable and connect your wifi attachment. For more information on how to connect the wifi attachment, please refer to “Connecting your Reef Angel Wifi attachment to the Head Unit” in this manual
Yeprimai wrote:Are you referring to this?Uploading the test code
1. Start your Arduino software
2. Open the wifi test setup code by going to menu File->Sketchbook->Example Codes and selecting WifiTestCode
3. Upload the code to your Reef Angel Controller.
4. After uploading the code, disconnect the USB-TTL converter cable and connect your wifi attachment. For more information on how to connect the wifi attachment, please refer to “Connecting your Reef Angel Wifi attachment to the Head Unit” in this manual