Recent Posts

Pages: [1] 2 3 ... 10
1
More cost-effective sending it out? Okay... $100 for a POS fan that cost $5 to make, and last just as long. Insane.
2
Of course I know nothing of your situation, but the 24/7 VP2 is a breeze to work on. Very simple. If you're able, I'd buy what I needed (and have many times) from Scaled Instruments, Scientific Sales, ect. and service it yourself. No doubt, you'll save considerable $.

I know how to work on them just fine; the 250 refurb is WAY more cost effective than parts and pieces.  Look on Scaled.  I replaced the fan--at 100 dollars US--and put new nimh batteries in the sensor suite last month (and have torn the entire thing down several times to work on it).  I wanted to do this way earlier, but this is still WAY more cost effective IMO.
3
Of course I know nothing of your situation, but the 24/7 VP2 is a breeze to work on. Very simple. If you're able, I'd buy what I needed (and have many times) from Scaled Instruments, Scientific Sales, ect. and service it yourself. No doubt, you'll save considerable $.
4
I know this is an extremely old post, but here is some updated info I received from Davis regarding the overhaul (as they call it) of the VP2/VP2+

As of 03 May 2024:

Quote
There are 2 different classes of the Vantage Pro 2.
 
Depending on the class you have, the cost will be either $190 for the Vantage Pro and Pro+ without a fan aspired radiation shield. This is the normal unit that most people have.
 
The other class would we is if the unit does have a fan aspired radiation shield. The cost for these is $250. You can identify these if you count the plates under the unit. If there are more than 5, your unit is fan aspired.
 
 
 
The overhaul does include all parts and labor.
You would pay shipping for both directions.
 
We would have the unit in house for approx 10 business days.

EDIT:  I wonder if they'll complain if I send my 24 hour aspirated version in without a fan?  I just bought a new one last month and I'd rather not waste money and at the very least have a spare on hand.  It's just got about 2 weeks on it right now.
5
Weather Display / Re: Logfile blank after sudden PC restart
« Last post by meteosanjuan on Today at 03:32:06 PM »
Well fixed, between the backup and the option that has weather display (which I didn't know about) to extract the data from the Davis data logger, I have been able to reconstruct the monthly logfile.

 [tup]
6
I know this is an extremely old post, but here is some updated info I received from Davis regarding the overhaul (as they call it) of the VP2/VP2+

As of 03 May 2024:

Quote
There are 2 different classes of the Vantage Pro 2.
 
Depending on the class you have, the cost will be either $190 for the Vantage Pro and Pro+ without a fan aspired radiation shield. This is the normal unit that most people have.
 
The other class would we is if the unit does have a fan aspired radiation shield. The cost for these is $250. You can identify these if you count the plates under the unit. If there are more than 5, your unit is fan aspired.
 
 
 
The overhaul does include all parts and labor.
You would pay shipping for both directions.
 
We would have the unit in house for approx 10 business days.
7
Custom Website Templates / Re: Wide/Narrow
« Last post by vinesweather on Today at 12:18:49 PM »
Yes, for the homepage with ajax-dashboard6.php.  This is due to some issues with the inclusion of images that are too wide for the actual area alotted so the browser tries to 'make it all fit' as best it can.  If you look at other pages in your site, they fit the 800px narrow setting just fine.

You'll need to tweak the image sizes for the included images (radar map under forecast should be 230px wide specified) and maybe reduce the width of the blitzortung map.
Your cloud-base.php has two errata :
Quote
Deprecated: Implicit conversion from float 46.5 to int loses precision in /home/mcdconcepts/public_html/cloud-base.php on line 987
Warning: Trying to access array offset on value of type null in /home/mcdconcepts/public_html/cloud-base.php on line 1005
and those are preventing display of the cloud-base image.

Also, there may be an unclosed table or div as the row with the blitzortung map shows an extra (blank) cell on the right, and that shouldn't be there.

Thanks Ken. I'll work on those tonight, actually it's now morning lol.

Many thanks for your help.
8
Custom Website Templates / Re: Wide/Narrow
« Last post by saratogaWX on Today at 12:01:44 PM »
Yes, for the homepage with ajax-dashboard6.php.  This is due to some issues with the inclusion of images that are too wide for the actual area alotted so the browser tries to 'make it all fit' as best it can.  If you look at other pages in your site, they fit the 800px narrow setting just fine.

You'll need to tweak the image sizes for the included images (radar map under forecast should be 230px wide specified) and maybe reduce the width of the blitzortung map.
Your cloud-base.php has two errata :
Quote
Deprecated: Implicit conversion from float 46.5 to int loses precision in /home/mcdconcepts/public_html/cloud-base.php on line 987
Warning: Trying to access array offset on value of type null in /home/mcdconcepts/public_html/cloud-base.php on line 1005
and those are preventing display of the cloud-base image.

Also, there may be an unclosed table or div as the row with the blitzortung map shows an extra (blank) cell on the right, and that shouldn't be there.
9
Custom Website Templates / Re: Wide/Narrow
« Last post by vinesweather on Today at 11:20:07 AM »
Try changing the weather-screen-green-narrow style for body to
Code: [Select]
body {
  color: black;
  background-color: #F3F2EB;
  font-family: verdana, helvetica, arial, sans-serif;
  font-size: 73%;  /* Enables font size scaling in MSIE */
  margin: auto;
  padding: 0;
  width: 800px;
}

It kinda worked. Everything is out of alignment though
10
It's not the NWS outages, but the change of weather.gov to new hosting/design.  Some of the features previously existing are possibly deprecated, and that includes the XML  They are trying to move all automated data requests to api.weather.gov and highly favor JSON outputs.  It also may be that the MapClick request for graphical is just 'broken' and not yet fixed, but the best option is to switch to using api.weather.gov for the future.  See those docs at https://www.weather.gov/documentation/services-web-api

see https://www.weather.gov/idp/forecastmigration for details regarding the migration of weather.gov to their IDP framework.
Pages: [1] 2 3 ... 10