Recent Posts

Pages: [1] 2 3 ... 10
This is my Davis FARS vs Meteoshield standard temp graph for yesterday. They are mounted about a foot apart and both housing a SHT31 sensor w/sensirion filter. Not real impressed, although I'm not surprised as I get very little wind here.

FARS= Blue
Meteo= Orange

afternoon wind ~ 1.5 mph

 [ You are not allowed to view attachments ]
I looked at data logger from yesterday and these were the recorded highs. So only .2 between the 7714 and Pro.
When you do the mean the PRO shield actually was cooler than the 7714.

PRO-        79.6
Standard- 80.6
7714-       79,4
FARS-       78.9

Lows today

Pro-          55.6
Standard- 55.5
7714-       56.1
FARS-      55.7
There is actually another method for the WS-2902A to publish to CWOP but it is more complicated. But it is cheaper than getting the ObserverIP, WS-1000-BTH and Meteobridge (WeatherBridge).

This other method to publish to CWOP mostly requires the use of a computer (an old one you already have lying around, or a cheap one, or it is popular to use a Raspberry Pi because they are cheap, small and take up little space.) Then add some software. You'll also need an old router that can run custom firmware or get a cheap router capable of running WRT or Tomato.

The software you need for the computer is WeeWx. You'll need to use the WeeWx interceptor driver to capture data being sent by the WS-2902A display console via the custom router as it sends to Weather Underground. Once WeeWx has this data it can then publish to a number of services including CWOP. And WeeWx will then also pass along the intercepted data to Weather Underground.

In concept the above paragraph explains how it works without getting too technical. But in reality to accomplish all of that it is complex. Because it requires a whole lot more technical experience. You'll need Linux experience, router configuration experience, and networking experience to redirect Weather Underground traffic to the WeeWx computer. Keep in mind that this custom router does not replace your existing router. It sits between your display console and the WeeWx computer. But there are a lot of guides and write ups. But you probably won't find all the information in one place. And if you are a real network guru and you already have a managed layer 3 switch on your network then you won't need the router with custom firmware as you'll program your layer 3 switch to do the redirection to the WeeWx computer.

It is much easier and convenient to use the first method in my prior post, although probably more expensive.

WeatherLink by Davis Instruments / Re: 2.0 announced
« Last post by johnd on Today at 07:51:23 AM »
Well at the moment I can't even steel my own data even knowing the account and password due to multiple occurrences in multiple accounts.

Not quite sure how you've managed to get the same station in more than account (unless it's an EM station, but I thought you had regular VP2s?). But from now on the principle will be:

Every station will have a single identified owner - in other words it will be owned by a single specific account.

With a Pro account it will be possible to share that station's data with other accounts (within limits) by following the sharing procedures. Sharing means two things really: being able to access the station's Bulletin directly; and being able to download that station's archive data.

But difficult to comment further without knowing the details of your issue.
Wonderful description... Thanks  UU
Weather Website PHP/AJAX scripting / Re: Pollen Count
« Last post by colonieweather on Today at 06:36:03 AM »
Looks like Nasacort now removed their pollen count API…

My main focus has been primarily on daytime performance but looking at nightime you can see the 7714 doesn't perform as well as the BARANI DESIGN Helix shields. They may come together around sunrise still couple hours away still but the passive 7714 has lagged all night.  [ You are not allowed to view attachments ]
I would hardly consider an Apogee TS-11 or a Davis as a reference instrument ... but of course, I understand that your scientists are much smarter than the hobbyist from Rotronic, E+E and everybody else by that matter.

Even being a forum for enthusiasts, there is no justification for spreading ignorance !!! Quite the opposite, you should do a job to educate and raise awareness.

@CW2274, your comments about problems associated with an air temperature measurement exposed to solar radiation are certainly valid.  This would normally be a big problem.  Fortunately, we (METER, formerly Decagon and UMS) have good scientists on staff that are aware of these issues.  The ATMOS 41 has a pyranometer to measure solar radiation and an anemometer to measure wind speed, both of which are primary factors that control solar heating of the temperature sensor.  By doing a simple energy balance calculation, we were able to develop an algorithm to correct the air temperature measurement. 

We validated the correction against a high-end Apogee TS-11 aspirated radiation shield and found a 95% confidence interval of +/- 0.42 °C in the corrected ATMOS 41 air temperature measurement under all sky conditions.  To provide some frame of reference, we included an air temperature measurement made in a typical non-aspirated radiation shield (Davis Instruments) and found a 95% confidence interval of +/- 0.66 °C.  These results give us a lot of confidence that the ATMOS 41 air temperature measurements are actually more accurate than those made in a typical non-aspirated radiation shield.  The experiment and results have been presented at the American Society of Agronomy and American Geophysical Union meetings, and will be presented at the European Geosciences Union meeting next month.  We would be happy to send you the presentation if you’re interested.
Weather Web Resources / Re: Looking for Beta Testers
« Last post by doubleohwhatever on Today at 03:47:05 AM »
Absolutely. I'm sending you a PM now with the details!
If you have the correct credentials then it should work - I've just checked the XML option and it works fine for me.

But it's very easy to have a minor error in the way that the overall URL string is assembled, eg a space between the '=' sign and the following data item (there should be no spaces). Unless the syntax of the URL string is _exactly_ correct then the platform will return an error.
Pages: [1] 2 3 ... 10