Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

Wi-Fi Hotspot WX Station


cellectronic Nov 7, 2010 06:58 PM

Hello Guys
I am toying with the idea of installing a CR10X based weatherstation in a Wi-Fi hotspot.
Theory: CR10X station with serial/TCP converter connected to a wireless bridge to gain access to the hotspot.

I have this set up and on test in my workshop.
I use a Dyndns.org account so that in Loggernet I configure the setup as a TCPIP connection and speccify in settings my accountname and port number. I have opened the relevent ports in my router but am unable to connect to the logger.
If I substitute my Dyndns details in Loggernet setup for the IP of the serial/tcpip and port no. I can connect , so it appears all is working locally.
I am not sure if it is possible to log into the station via Dyndns because I would be attempting to connect to the station from an outside source which I have instigated locally !!
I did leave it setup and running in my workshop and took my laptop for a drive to a local hotspot but could not make the connection, possibly because that hotspots relevent ports were closed.
Any help would be appreciated , Thanks in advance.
Steve.


Sam Nov 8, 2010 01:15 AM

Can you give us a sense of syntax you are using?

http://my.website.com:6785

or

my.website.com:6785


cellectronic Nov 8, 2010 05:26 PM

Hi Sam , Thanks for the response, The syntax is seismet.dyndns.org:1025
I have verified my dyndns.org account is functional by another means and can access my system no trouble.
Loggernet has not informed me IP address is bad so I am not sure what is happening.
Regards.


Sam Nov 8, 2010 06:27 PM

That appears correct. And we regularly access sites using dyndns and dynalias. Under LoggerNet->Setup->IPPort->Hardware, try unchecking "Cache IP Address". Make sure that "TCP Listen Only" is NOT checked.

I assume that "seismet.dyndns.org" was an example as I could not ping that address. If you are using Windows, open the command line and verify/check the output of the following commands

1) ping seismet.dyndns.org
You want to see something like:
Reply from XXX.XXX.XXX.XXX: bytes=32 time=230ms TTL=230

2) tracert seismet.dyndns.org
You want to see something like:
1 <1 ms <1 ms <1 ms XXX.XXX.XXX
2
...(etc)
19 1026 ms 842 ms 1276 ms name.mycingular.net [XXX.XXX.XXX.XXX]

Trace complete.


cellectronic Nov 8, 2010 07:19 PM

Hi Sam,
I tried to ping seismet.dyndns.org and I get "request timeout"
Tracert responce is "1 30 ms 29 ms 29 ms 88-108-0-1.dynamic.dsl.as9105.com [88.108.0.1]"
Thats on line 1 the other lines inform me "request timed out".

I think If I can get a sucessful ping then that would solve the problem. The seismet address is the actual address so you should be able to ping it.
Regards.


cellectronic Nov 8, 2010 10:49 PM

Hi Sam, I have traced the problem to DynDns not updating my IP, Although it is set to auto-update via my router.
I will keep an eye on it and may install their software IP-updater if the router auto-update fails again.
Many thanks for your help.
Regards.

Log in or register to post/reply in the forum.