Recent Posts

Pages: [1] 2 3 ... 10
WeatherCat General Discussion / Re: 120 Days Without Issue
« Last post by xairbusdriver on Today at 02:06:47 AM »
Nothing personal, but how can we be sure you didn't Photoshop that image. [computer] cmu:-)
Dear Xipper and WeatherCat network troubleshooters,

Unfortunately I have never tried to setup Internet access so I can't help you.  You appear to have provided all the necessary connections, so I hope someone else will spot something.  In the meantime, you might look over the troubleshooting tips on the WeatherCat Wiki:

Perhaps something there will help you out.

Cheers, Edouard

Thanks for the reference to the troubleshooting guide, at first I thought I had solved it.  The documentation refers to configuring both TCP and UDP, my configuration lacked UDP as I have to write duplicate rules for everything to support it and just never did (though it did as-is previously).  I added the UDP rules and one of the iOS clients worked...but then it stopped. 

It seems that while the instructions imply that WeatherCat Server is listening on 5 ports on both UDP and TCP (49250-49254), it is in fact not actively doing so.  In fact the service isn't listening on UDP at the additional UDP rules are probably of zero value, but I'll leave them to save having to add them back if I am proven wrong.  However according to the OS X IP stack:
lsof -n -i4TCP | grep Weather
WeatherCa 78214 username   11u  IPv4 0x4593ab83e15788c5      0t0  TCP *:49252 (LISTEN)
WeatherCa 78214 username   82u  IPv4 0x4593ab83e15788c5      0t0  TCP *:49252 (LISTEN)

The additional detail here is that, apparently on service startup WeatherCat Server actually only binds to one of the possible 5 TCP ports...and it seems that on restart it may pick a different one.  I am guessing that the clients then have to try to connect to all 5 ports trying to find which one the server is actually listening on, and depending on how a given firewall implements these port forwarding it may take a long time for the "invalid" ports to timeout.

There has got to be a better way to do this, in my case it takes 2+ minutes for WeatherCat client to find the correct TCP port out of the 5 to use.  This would even be worse if it was using 49254 as it would take that much longer for the client to walk the TCP ports. 

What I don't understand is why it need so pick from a range of 5 TCP ports, rather than just using 49250 every time.  Once the client does detect what TCP port is active it caches that detail and at least allows easy refreshing (for some period of time)...but having it take 2 minutes, or possibly 4 or 5 minutes, the "first time" seems rather costly in terms of mobile app experience.
WeatherCat General Discussion / Re: 120 Days Without Issue
« Last post by pbeaudet on Today at 12:53:07 AM »
I forgot add my screenshot....

WeatherCat General Discussion / Re: Simple Webpage Image Size
« Last post by xairbusdriver on Yesterday at 11:45:52 PM »
"I see that this is your first post" Oops! I missed that! I was thinking we already had a "curry" something or other here ("bcurry"?)! Maybe you are a relative? Whatever, Welcome AboaRd, curry!

My second assumption (the first being that you were already a member [blush] furst erer of thee day!) was that you were talking about the WX Pref->On-Line->Simple web, which does have a checkbox for including a webcam image, Edouard. As I've said, I've never asked WC to create a "Simple web" page, but I assume it uses/includes the dimensions selected in the popup menu in that section of the Prefs.

By the way, what browser are you using?

Perhaps, curry, if you could upload a screen capture of your page in your browser we could help. Even better would be the source of that page. Most browsers have a menu item (try shift-command-u in Safari) to allow you to see the actual html in a page. You may have to enable the "Develop" Menu in Safari's Prefs to enable that keyboard shortcut.
Dear Xipper and WeatherCat network troubleshooters,

I am having problems getting WeatherCat clients to work via the Internet (applies to both iOS clients and OS X client). 

Unfortunately I have never tried to setup Internet access so I can't help you.  You appear to have provided all the necessary connections, so I hope someone else will spot something.  In the meantime, you might look over the troubleshooting tips on the WeatherCat Wiki:

Perhaps something there will help you out.

Cheers, Edouard
Dear currymac, X-Air, and WeatherCat Welcome wagon,

I see that this is your first post to the WeatherCat forum, so by all means welcome! . . .

Can someone tell me what image size and resolution is required so that WeatherCat does not "alter to fit" on it's simple webpage?

Unfortunately, I do not understand your question exactly.  Most of us have some sort of custom website, so we don't run the simple web.  As I recall, it doesn't display the webcam image as is.  Are you starting with the simple web HTML and modifying it to display your webcam image?

Normally, HTML doesn't scale images unless the code to insert the image includes image dimensions and these are different from the actual image size.  Could you tell us how you are attempting to insert your webcam image?  That would help us understand your problem.

Once more welcome to the WeatherCat forum!  :)

Cheers, Edouard  [cheers1]
iOS Client Help / Re: Issues getting WeatherCat client to work over Internet
« Last post by Xipper on Yesterday at 10:22:50 PM »
On OSX WeatherCat Client i finally found some logs:

Nov 20 14:21:07 TheBadApple WeatherCatClient[77507]: Looking-up WeatherCat Server...
Nov 20 14:21:07 TheBadApple WeatherCatClient[77507]: Found the machine - getting details...
Nov 20 14:21:07 TheBadApple WeatherCatClient[77507]: Server details: x.x.x.x on port 49250
Nov 20 14:21:29 TheBadApple WeatherCatClient[77507]: ***Packet timed out. Socket 64***
Nov 20 14:21:29 TheBadApple WeatherCatClient[77507]: Server is not responding. Retrying...

iOS Client Help / Issues getting WeatherCat client to work over Internet
« Last post by Xipper on Yesterday at 10:20:01 PM »
I am having problems getting WeatherCat clients to work via the Internet (applies to both iOS clients and OS X client).  I have port forwarding setup to send the ports from the public IP on my router to the desktop that WeatherCat runs on.  They work if using "local network", however anytime they are set to use the Internet URL they fail and unfortunately there is zero feedback in any of the clients other than a generic failed to connect error.

If I use nectat (nc) to perform test connections across all of the required TCP ports I get the same response against the NAT as I do directly against the desktop.  This seems to suggest that it should work, however none of the clients actually read the data.

Is there any path of seeing why the client isn't accepting the data?

As an example, if I netcat port 49251 on the public IP and the desktop I get the same data:

nc 49251

nc <public address> 49251

I can provide the URL via private message for debug if that helps, just don't want to share it in any Google index sites.
WeatherCat General Discussion / Re: Simple Webpage Image Size
« Last post by xairbusdriver on Yesterday at 06:32:37 PM »
My version of WC Prefs shows two choices for a Simple Web Webcam picture: 320 x 240 and 640 x 480.

Those are pixel dimensions, the "resolution" can mean two different things, the actual image file size or whatever the display device is set to. The file size is simply the product of the two dimensions; ~76,800 bytes for the smaller and ~307,200 bytes for the larger. Each of these files will have extra bytes for details needed for the OS and file attributes used by other things.

Many refer to those two numbers as their "resolution". Most camera makers use the number of pixels on their sensors as their "resolution", the higher the number, the better, according to them. ;)

When viewing these images we need to tale into account the pixels per inch of the display device. Originally, the Macintosh broke the current rules by offering 92 pixels per inch and offering text at that same "point" size! "Points" defined text sizes in printing, the first Mac's now made it possible "what you see (on-screen) is what you get (on paper)"!

So, on-screen "resolution" is now way beyond 92 pixels per inch, your phone probably has well over 300 pixels per inch! If a web page specifies the dimensions of an image, it is easy for the browser to convert the 320 x 240 image so it will be more than barely an inch wide on your high resolution device.

As to your second question, I have no idea what you are talking about! I have never created a "Simple Web" page with WC. Most browsers will simply display n image at the dimensions provided in the file unless they are specified in the img tag or an appropriate CSS file. However, most browsers will change the displayed resolution, usually with command "+" or "-" keystrokes. Command "0(zero)" will usually return the resolution to the default setting.

Hopefully The Manual has some info on that "alter to fit" or others here will have some useful info and an answer.
Weather Hardware/Measurement / Arduino
« Last post by The Grand Poohbah on Yesterday at 05:59:49 PM »
I recently discovered the Arduino Uno, an inexpensive (<$8) and versatile micro controller that's programmable in C. There are a lot of hardware add-ons available and the software libraries are free and abundant. My first project is to animate multi-colored LED strips for an outdoor Christmas decoration.

One strong feature of the Arduino is its ability to interface with the outside world. It has built-in digital and analog connectors for sensing and controlling in real time. I was wondering if anyone is using the Arduino with WeatherCat and weather stations.
Pages: [1] 2 3 ... 10