Recent Posts

Pages: [1] 2 3 ... 10
WeatherUnderground / Re: WU - Let us know your issues
« Last post by n4khq on Today at 06:38:50 PM »
Thank you WU team.  =D> I have now gone  24-hours and my Rapid fire data has been saved in five minute increments throughout.  The graphs look great.  The webcam updates still leave a little to be desired.

Now, if I could just get the Status update to work, but I am sure that is not a high priority. :lol:


Thanks Mark, can you share your station ID? The thing that will help most now is to catch a webcam that is not working properly in the moment.

Here is one not working
The webcam registration will not stay active and no images have uploaded since the outage started.
Davis Instruments Weather Stations / Re: New Temp / Humidity Sensor
« Last post by Old Tele man on Today at 06:27:38 PM »
The #7346-174 is the 'older' Sensiron SHT15 TH sensor assembly.
Weather Website PHP/AJAX scripting / Re: The wxnwswinter.php
« Last post by gwwilk on Today at 06:15:12 PM »
Thanks, Randy, for helping organize my 'helter-skelter' script 'droppings'. :-)

Remember, this is still labeled as 'Experimental' by the NWS.

Edit 2018 Jan 18 5:30pm CST:  I've turned on North Platte and Rapid City in the script on my site so others won't have to manually do so.
So, does, anybody know what "clock" chip the two consoles use? Same device or different? Is the same device used for internal timing, or are separate clocking sources used?

I raise this question because my experience has been that my VP2 console clock timing was terrible (always losing time) while the replacement VUE console clock seems to be quite accurate.

There isn't a real time "clock" chip in either console.  The processor keeps time with a clock crystal.
A raw crystal? Usually there's a divide-by-N "chip" used to derive the desired 'clock' timing.

Yep, that's what the industry calls a Real Time Clock (RTC) chip. The external "oscillator" is a crystal that is oscillating at many, many, many times faster than the end/desired "clock" output...typically about 10X faster but can vary. The greater the difference between the oscillator input and the clock output, the tighter the operating tolerance (less variance).
the person that this thread is about, not Wim
Weather Website PHP/AJAX scripting / Re: Date on dashboard
« Last post by zmarfak on Today at 05:49:57 PM »
OK, I changed it.
It's ok now.

And now I also know the reason why.

Thanks for the help.
Davis Instruments Weather Stations / New Temp / Humidity Sensor
« Last post by SpHwk on Today at 05:48:07 PM »
So I was checking stats on CWOP and noticed that my humidity sensor's reading were out of whack on my six year old 5162 .  I ordered a new SHT31(7346.070) sensor from Ryan at Scaled Instruments. Got it installed today and calibrated.

Looking back at Ryan's site for the calibration offset I see that there is another sensor, Davis 7346.174 Pro2 Upgraded Digital Temperature Humidity Sensor that looks very similar, although the specs seem slightly inferior to the SHT31.  Does anyone know what the difference in these is? The one I got seems to be a lower model number.
Weather Website PHP/AJAX scripting / Re: Date on dashboard
« Last post by saratogaWX on Today at 05:38:15 PM »
Ok, I'm obviously caffeine deficient..

I read the AJAX code wrong.. it really needs to have ajaxWLwx.js have
Code: [Select]
var showDateMDY = true;     // set to false to show date as dd/mm/yy
due to
Code: [Select]
if(!showDateMDY) { ajaxdateformat = tdate[1]+"/"+tdate[0]+"/"+tdate[2];  }
I'd overlooked (not seen) the ! in the test.  With showDateMDY=true, the code wouldn't execute and since you're already in day/month/year in WeatherLink, the swap of day/month positions wouldn'd happen.  D'oh!  So many double negatives to digest.

With Settings.php $SITE['WDdateMDY'] = false; the wxstatus.php page is showing correctly for the weather data age (whew!)
Personally, I think "normal" temperatures should be defined as a range (such as 52-62), rather than just one number (57). This could be easily figured out using the closest 25th or 20th percentile of temperatures to the so called "normal". On any given day, a temperature could be considered above or below normal, even if it is quite usual. Usually where I live, and probably everywhere else, "average" or "normal" weather only occurs during pattern shifts from cooler to warmer weather and vice-versa. What do you guys think?
I absolutely agree that "normal" when used in the context of weather is best defined as a range and not as a single number.  No self-respecting psychologist or educator would define normal intelligence as an IQ of exactly 100 and thereby immediately relegate all others to above or below normal intelligence. Our imprecise language allows 'average' as a synonym of 'normal', but no self-respecting scientific discipline can embrace such sloppy usage in their work.  Even a "normal" body temperature is defined by a range around 98.6F so that recorded oral temperatures other than 98.6F can still be normal.  In fact, most recorded oral temperatures on normal patients I saw in my 50 years of medical practice missed that 98.6F mark. 

An example of abnormal body temperature:  last month a friend of mine's dog got trapped in a freezing cold irrigation canal in central Nebraska and the man's natural response was to attempt to rescue his dog.  Both were trapped in the icy water, and 45 min. later when they were rescued by emergency responders the man's temperature was 84F.  He's lucky to be alive because prolonged hypothermia to such a degree is often fatal.  Miraculously both man and dog survived.

Ummm... were we talking about body temperature or air temperature?  :-P
(P.S. Wow, 45 minutes in icy cold water. It is definitely a miracle that the man survived.  =D>)
but this person has a usb data logger

This person? Who the OP or Wim? But yes Wim has USB
Pages: [1] 2 3 ... 10