Quantcast
Channel: WXforum.net - WeatherLink/weatherlink.com by Davis Instruments
Viewing all 3603 articles
Browse latest View live

Re: Weatherlink and bogus records

$
0
0
Isn't there a difference between bad data (eg erroneous readings) and corrupt data, corrupt being eg where you get a totally spurious date in a WL record. I'd have guessed that wireless stations were potentially worse for bad data (because there is obviously more scope for wireless reception to be lost than with a cabled station).

OTOH I'm not sure there's any obvious reason why cabled would be any better for corrupt data, which would be generated most likely in the PC, but also perhaps by the console/logger or interference on the logger==>PC link. In fact my guess would be that cabled is actually a little worse for corrupt data because of the extra potential for issues like ground loops.

Re: Weatherlink and bogus records

$
0
0
I only mentioned "cabled" because it's an obvious difference.

Isn't there a difference between bad data (eg erroneous readings) and corrupt data, corrupt being eg where you get a totally spurious date in a WL record. I'd have guessed that wireless stations were potentially worse for bad data (because there is obviously more scope for wireless reception to be lost than with a cabled station).

OTOH I'm not sure there's any obvious reason why cabled would be any better for corrupt data, which would be generated most likely in the PC, but also perhaps by the console/logger or interference on the logger==>PC link. In fact my guess would be that cabled is actually a little worse for corrupt data because of the extra potential for issues like ground loops.

Yes, there's a difference between bad and corrupt data.  Ocala mentioned a 2015 .wlk file - but didn't say what the "file date" was.

A cabled station is likely to be "consistent".  That is, consistently bad or consistently good.  And I can't see why ground loops would cause corrupt data "occasionally" - or at all, for that matter. 

Re: Weatherlink and bogus records

$
0
0
The only bogus records that my wireless setup provides is an occasional bad date that shows in the 'browse' function. Haven't had one for a while as they usually only show up when I'm out of town.  Brick wall

My Bad - Accidentally temporarily changed date on Console

$
0
0
I have a Davis Vantage Pro2 running WeatherLink in Windows XP.  Two days ago, after a power disconnect to the console, I reset the time which was off by several minutes.  I unknowingly accidentally changed the date to 2014.  I did not realize my mistake until last night (Just under two days later).

I corrected the date on the console and tried to delete the 2014-12.wlk file from the directory.  Every time I start the weather bulletin after doing this it downloads 513 records and I end up with a disjunction in my data that stops with the data at 8:30 pm last night when I corrected the time and the jumps ahead to two the same two days in 2014.  Also my new data since then isn't showing up at all.  (I have also tried using the "Browse the Station Data" tab in Weatherlink to delete the 2014 entries, but it always results in the 513 record reload culminating in the 2014 data returning when opening the Weather Bulletin.)  The Weather Bulletin's barograph always show the barometric pressure starting at the time it is opened with no previous record.  (I also tried deleting the dataset.dat and datalist.dat files as you previously had me do for a past problem of a different nature to no avail.)

Is there anything I can do to fix this situation?  Ideally, of course, I would like to have my data from 8:30 last night forward added in and the bogus 2014 data be gone. 

Any help you can provide would be much appreciated.

Re: My Bad - Accidentally temporarily changed date on Console

Re: My Bad - Accidentally temporarily changed date on Console

$
0
0
Create a temp weather station and download the archived data to that.

Weather link fails to plot graphic data

$
0
0
Weatherlink use to plot the graphical data as it meant to plot for 3 days at a time, or so if you go to the graphical data option.

Now it does not plot any graphical data, and if you choose a date, seems locked on June 1st 2000, and no sigh of todays plot data, or any other the 1st June 2000, so plots no data at all, so wondering how to fix it.

Re: Weather link fails to plot graphic data

$
0
0
What data do you see when you browse the DB?

Re: My Bad - Accidentally temporarily changed date on Console

$
0
0
Create a temp weather station and download the archived data to that.

That would preserve the 513 records (2 days +) from the year 2014, but I'm not quite sure how that would be useful.  Are you suggesting using WLKreaderwriter to merge the data?

Re: My Bad - Accidentally temporarily changed date on Console

Re: Weather link fails to plot graphic data

$
0
0
Sounds like the Y2k bug!  :0  Seriously, I don't know.  Have you completely reset the system (power off, batts out, logger out etc.)?

Re: Weather link fails to plot graphic data

$
0
0
Sounds like the Y2k bug!  :0  Seriously, I don't know.  Have you completely reset the system (power off, batts out, logger out etc.)?

Yes. Looks like it's downloading (FSVO 'downloading') but not then storing the data in the database. Agreed, complete reset (except I've never found it necessary to take out the logger, just leave the console fully off for eg 5 mins) and double-check the date-time settings. If all appears OK but still not working then try downloading into a new station.

Re: Weather link fails to plot graphic data

$
0
0
What a hassle having to completely turn off my console, after having to offset wind direction, etc for it to read right in the first place, just will not bother using Weatherlink, but use Cumulus, at least that works fine and plots all the graphs properly.

Re: Weather link fails to plot graphic data

$
0
0
What a hassle having to completely turn off my console, after having to offset wind direction, etc for it to read right in the first place, just will not bother using Weatherlink, but use Cumulus, at least that works fine and plots all the graphs properly.

I think you are  going to find this new hobby of your frustrating.  Wink

Re: Weather link fails to plot graphic data

$
0
0
What a hassle having to completely turn off my console, after having to offset wind direction, etc for it to read right in the first place, just will not bother using Weatherlink, but use Cumulus, at least that works fine and plots all the graphs properly.
I agree. I have officially given up on Weatherlink. It works great for some people but for me it doesn't. This after using it pretty much since 04.
I'll use Cumulus also and DL the data to Weatherlink once a week or so. Sad

Re: Weatherlink Vs Cumulus

$
0
0
Is it possible to run both cumulus and weatherlink at the same time on the same machine without VVP if you have the IP datalogger?

No - the IP logger is _not_ a data server (in the sense of being able to handle multiple simultaneous requests for data from different programs).

Edit: Let me rephrase because there's potential for confusion here since 'weatherlink' can refer to two different things.

If you mean uploading to weatherlink.com (ie the website) at much the same time as feeding data to Cumulus then yes you can do this, provided as Brian says Cumulus is configured to release the IP port at frequent intervals so that the uploads to weatherlink.com can proceed.

But if by weatherlink you mean a copy of the Weatherlink program running on a local PC and taking a feed of live data direct from the logger then no this won't work robustly without VVP. (The logger can't service two simultaneous sets of requests for continuous LOOP data - before long it either stops responding to one set or the other or just locks up in my experience.)

Re: Weatherlink Vs Cumulus

$
0
0
Thanks for the quick responses. I'm not sure if I want to go down this road, but wanted to check on my options.

But if by weatherlink you mean a copy of the Weatherlink program running on a local PC and taking a feed of live data direct from the logger then no this won't work robustly without VVP. (The logger can't service two simultaneous sets of requests for continuous LOOP data - before long it either stops responding to one set or the other or just locks up in my experience.)

Yes, I was thinking about running a local copy of the Weatherlink software alongside Cumulus, not uploading data to weatherlink.com. I would only use Cumulus to upload data to weather underground and CWOP. It sounds like running both programs simultaneously is a bad idea.

Re: Weatherlink Vs Cumulus

$
0
0
I had found it more reliable when running Cumulus only and uploading to Weather Underground, CWOP and others, compared to running Weatherlink only and uploading to Weather Underground and CWOP.  I had considerable trouble with Weatherlink when running both together using VVP but Cumulus was very stable (Windows 7 64 bit).  I use Cumulus full time, and twice a month stop Cumulus for a few minutes and run Weatherlink so that I can maintain the Weatherlink .wlk database that I started with initially.  Why? just because I can!  The datalogger keeps about 17 days of data at my 10 minute interval setting.

Paul

 

Re: Weatherlink Vs Cumulus

$
0
0
I use Cumulus full time, and twice a month stop Cumulus for a few minutes and run Weatherlink so that I can maintain the Weatherlink .wlk database that I started with initially.  Why? just because I can!  The datalogger keeps about 17 days of data at my 10 minute interval setting.

Me, too.  Except I run WUHU and I d/l WL 1/month.

Re: Weatherlink Vs Cumulus

$
0
0
Yes, I was thinking about running a local copy of the Weatherlink software alongside Cumulus, not uploading data to weatherlink.com. I would only use Cumulus to upload data to weather underground and CWOP. It sounds like running both programs simultaneously is a bad idea.

The WLIP can upload data to both WU and CWOP via a relay from weatherlink.com.  The upload rate to WU is every 15 minutes and that is fixed.  I don't know the rate to CWOP.

So with the WLIP, you don't need to be uploading directly to either WU or CWOP as long as you are satisfied with how weatherlink.com handles the relay of your data to them.

As stated previously, WL and Cumulous must alternate access to the archival data within the WLIP logger due to the fact that the WLIP only can handle a single thread at a time. Remember it also has an internal program uploading to weatherlink.com current conditions every minute or so and archival conditions hourly.  Both WL and Cumulous archival downloads would have to contend with this activity.

However, if you are satisfied with archival downloads that are up to an hour behind current conditions, the WL software can be set to download archival records from the weatherlink.com site.  This doesn't interfere in any way with the WLIP's activity  Downloading archive records from weatherlink.com is much, much faster than downloading the records out of the WLIP's internal memory.

If either WL or Cumulous are set to monitor/display the current weather data (LOOPing) from the WLIP, then there has to be a periodic release of the IP port to allow the WLIP to send its uploads to weatherlink.com.  I think WL software must have this release built in (it isn't configurable); whereas, in Cumulous you must configure it.

I think I'm fairly experienced in the use of WLIPs with multiple programs.  I have a meteohub which is essentially a _nix software program looping several WLIPs for current data.  It has pauses built in to allow the WLIPs to upload to weatherlink.com.  I don't know how long and how frequent they are though.  Through out the day I can periodically download archival records with WL.  If I estimate that the download will be longer than 10 pages, then I manually switch the WL software to download from the weatherlink.com site.  If under 10 pages, then probably a download of the latest archives from the internal logger can get though using a built in pause window of the meteohub that happens to be available.

This usually all works quite well.  Sometimes there is a conflict with a WL download directly from the logger and the download has to be re-attempted after it fails the first time.  The only serious problem with this set up occurred last spring when weatherlink.com wasn't accepting uploads from the WLIPs in a timely fashion.  Apparently their servers were congested.  They upgraded the servers and all has been smooth since.
Viewing all 3603 articles
Browse latest View live


Latest Images