Topic: can't download data without errors - solved

[m77]

I'm on WL 6.0.3 and sometimes have to reboot my logger (batteries out, AC out, power up, back in etc) after my school network goes down.

Recently I can't download data from home (diff network) nor from school (same network) as i get an error message after about 3 pages downloaded. It says that there are 513 pages too - although there should only be about 5!

when i try to download from WL.com this works ok, the only problem being the logger doesn't upload to wl.com during network downtime, so i get less data back - it's better to get it from the logger.

i have tried rebooting the logger, and have checked for wlk files with strange names.
i have tried deleting every wlk file with no luck so i have replaced them again.

it's firing data to wl.com absolutely fine and also runs a bulletin ok (the live dashboard)

is there a way i can just try to get a download of a specific time rather than the whole lot again?
what else can i try please?

thank you

[dalecoy]

is there a way i can just try to get a download of a specific time rather than the whole lot again?
what else can i try please?

1.  No
2.  Verify that the date and time on the console and on the computers are identical.
3.  Try checking the .wlk files in both places (there are lots of discussions elsewhere in this forum that will give you details, if you look for them).
4.  Probably - if you have accurately described the situation involving two different computers - you will have to delete all of the data stored in the logger.  Once again, there are discussions elsewhere.

[m77]

Thanks. I have looked at other discussions here about deleting wlk files. Not sure what else I can try with that?
I will check to see but I'm pretty sure that the logger date and time are accurate and are the same as the PC time.

[m77]

Hi there.

I tried again today with no luck.

Batteries out. Power off. Logger connector out. Wait ten mins.
Walk through setup.
Delete wlk files in the between.

The software still gives an error after about 20 pages.

Any ideas or specific hints? I've tried what I can find elsewhere.

[dalecoy]

Batteries out. Power off. Logger connector out. Wait ten mins.

Delete wlk files in the between.

What do you mean by "Logger connector out"? (the logger has 2 connectors)

What do you mean by "Delete wlk files in the between".
(Vagueness is not helpful)

Exactly what .wlk files do you have - and what are the dates (file dates - not the name) on those files?

Did you find discussions about deleting some .dat files (and do that)?

Does this problem really occur on TWO different Windows machines?  If so, you're going to have to "clear" all of the data on the logger.  That's what I said yesterday.

[m77]

Hi Dale. Thanks for your reply.

I mean the square logger pin out thing that connects the IP Ethernet to the logger itself. The thing with pins in. Sorry for lack of techy terms here.

The wlk files don't have name dates in the future, like mentioned elsewhere, eg 2016. They all seem to be in order.

By "in between" I meant that I deleted all wlk files in between powering the logger down and powering it back up.

I believe that there were two dat files mentioned and yes I also deleted those.

When you say "clear the logger" I am not sure how to do this.

Yes it's definitely the same on two separate Windows machines. One on the network at work, the other at home using the Internet rather than a local network.
Thanks.

[dalecoy]

I mean the square logger pin out thing that connects the IP Ethernet to the logger itself. The thing with pins in. Sorry for lack of techy terms here.

I would have preferred that you remove the logger from the console, but ........

The wlk files don't have name dates in the future, like mentioned elsewhere, eg 2016. They all seem to be in order.

By "in between" I meant that I deleted all wlk files in between powering the logger down and powering it back up.

I asked for the "dates (file dates - not the name) on those files" - but if you actually deleted all of the .wlk files, then that's not an issue.

When you say "clear the logger" I am not sure how to do this.

One easy way is to use WeatherLink to "set the date and time on the console".  Make a minor change, then change it right back.  When you confirm that, you will be asked if you want to clear the data.  Say yes.

Note that this operation will lose all of the historical data in the logger.  But if you've tried everything else, that "should" fix your problem.

Please let us know.

[m77]

Logger.
Console.
Right! Thanks.

Yes I recall that the dates of the wlk files were all the same and all recent (maybe the time I tried to download?) don't know if that helps the jigsaw?

I will try the other things that you suggest and post again.
Thank you.

[m77]

One easy way is to use WeatherLink to "set the date and time on the console".  Make a minor change, then change it right back.  When you confirm that, you will be asked if you want to clear the data.  Say yes.

ok, solved!

i actually just changed the clock by a minute but did NOT select "clear data"

the first download worked a treat. thanks all, especially Dalecoy.

[dalecoy]

And that worked for all of the computers involved to download the data?

[m77]

Will test the one at work tomorrow when I return.

[dalecoy]

i actually just changed the clock by a minute but did NOT select "clear data"

Did you just change it by a minute from what it previously was and then not change it back?

Or change it by a minute from what the current computer time was?

Or what?

[m77]

I changed it by a minute but didn't change it back.

[m77]

nope, doesn't work in school. says 100% to download and times out after about 4 pages .

i changed the clock but didn't delete the data (I need to download it at home before i do that).

[dalecoy]

nope, doesn't work in school. says 100% to download and times out after about 4 pages .

I'm not surprised.  What you are trying to do is technically difficult - even if you happen to have had success in the past.  It requires the same "time reference" on two computers.  They probably must be synchronized within fractional seconds, as well as having the same "idea" of the data times on the logger.

[m77]

So if I synchronise my home PC with the logger it should give it a better chance of being smooth.

[dalecoy]

So if I synchronise my home PC with the logger it should give it a better chance of being smooth.

That wasn't what I said, but feel free to try it. 

[m77]

Ah you meant synch two PCs?
Makes me wonder why there is a multi machine license for say 20 machines?!

[m77]

Bit of a follow up to this issue that I hope helps somebody a little.
I have realised that when/if you get an error message when downloading data with WL, instead of hitting cancel immediately, let it run for its standard 20 retries.
Once they've failed, hit cancel.
This way the successful data before the error is actually downloaded. If you hit cancel before 20 retries NONE of it is.
This approach allows you to download in small chunks bit  by bit.
Sorry if this is old news but it was useful for me today!

[dalecoy]

Just to make sure that I'm understanding what you are trying to do:

You are "connecting" two different PCs to one WeatherLinkIP logger, using WeatherLink software.

("connecting" above is meant to include at least downloading data from the logger, and perhaps other functions).

Is that what you're doing?  If not, please clarify - because I'm a bit confused.

[m77]

i use two machines to download the data (not simultaneously). I open WL on one and download data. I close WL.
Then a week later i may do the same on another machine.

[dalecoy]

i use two machines to download the data (not simultaneously). I open WL on one and download data. I close WL.
Then a week later i may do the same on another machine.

Assuming you mean "download data from the logger", that's what I thought. 

As far as I know, that is not a "Davis-supported" procedure.  Of course, if it works for you, that's great. 

But I don't know the internals of the software or firmware, so I apologize for trying to help you solve a problem when I really didn't have a clue.