• After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.

    I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.

    For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.

    From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.

    Sincerely, Jeff D.

Another Weather Station Question... Data Locked for Two Days?

czenzel

EF2
Joined
Oct 2, 2008
Messages
106
Location
Florida
On my wireless weather station I have a problem that I just noticed and it fixed itself over the day.

I have a Vantage Pro 2 Plus station and my history database and Weather Underground received data that was "Locked" for two days and only barometric pressure was reporting properly.

I have attached screenshots for reference.

Does anybody know why this might have happened? Did my machine just need a reboot to fix it?
 

Attachments

  • wxStationGraphAllDay1.jpg
    wxStationGraphAllDay1.jpg
    11.4 KB · Views: 50
  • wxStationGraphAllDay2.jpg
    wxStationGraphAllDay2.jpg
    11.8 KB · Views: 58
The station does not talk to Wunderground - or anybody. The station talks only to your software. The culprit is always the software, unless your datalogger went bad.

What software are you using ? Weatherlink ?

If so, just go back in the history and look at the recorded data from there. If it's looking good (meaning there's normal data - not the same data over and over), just send back the data to Wunderground the same way (choosing start time/end time), and your wunderground station will be updated with the valid data.

But remember 99.9% of the time, the error is with the software - not the station.
 
The station does not talk to Wunderground - or anybody. The station talks only to your software. The culprit is always the software, unless your datalogger went bad.

What software are you using ? Weatherlink ?

If so, just go back in the history and look at the recorded data from there. If it's looking good (meaning there's normal data - not the same data over and over), just send back the data to Wunderground the same way (choosing start time/end time), and your wunderground station will be updated with the valid data.

But remember 99.9% of the time, the error is with the software - not the station.

It seems my software was messed. The history in Virtual Weather Station also shows bad data, but the Vantage Pro 2 console is still working great and the transmitter outside is working.

I am using Virtual Weather Station (latest build on their site) with Weatherlink USB on the actual VP2 Console.

Should I be doing a general reboot everyday to clear the system such as a reboot at 4am? 5am?

I am glad to hear it might not be my station. The data is messed up in my history tables on the local machine and Weather Underground.

I guess it is something I will have to let go for now and watch closer to make sure all the sensors and software is back online.

Thanks for your help!
 
What you could try - before clearing the datalogger.

Shutdown the virtual station software, and start weatherlink (the software that came with your station). At startup, it will transfer all the data from the datalogger. From there you can update back wunderground to get that database with valid data (choosing specific period of data from the menu to only update the erronus data).

Once that's done, shutdown weatherlink and go back to your usual software setup.

As for the error itself, it might be a synchronization error at some point between the datalogger, the software and the database.

To prevent that, make sure there's enought delay between records - that is usually set in your software, not on your console - remember the console is slave and only cares about the station's sensors. All exchange are managed by the datalogger and the software. The data is pickup by the software requesting it from the datalogger. I've never seen bad data in a datalogger, all the problem i've seen with the data were from the software not being able to handle error conditions at some point (overload, buffer underrun, buffer overflow), and messing up its own database with bad data (bad data being created by the software itself... catch22).

If you have that issue again or often, try asking for guidance from the Ambiant Virtual Weather station forum. I'm sure someone in that group of users will be able to set you up with such issue. Read that thread on that forum ( http://www.wxforum.net/index.php?topic=8034.0) or search the Ambiant forum with the word ''corrupted'', you'll find a lot of answers.

Good luck.

Additional detail : in your database, try to find the last valid record before the error. Then remove all the bad records following it until the next good record (about two days of bad data from what you said). After that, you might be able to regain those records if they are still on the datalogger. That will fix your database.
 
Last edited by a moderator:
I found the issue. It wasn't the console or datalogger, but the Integrated Sensor Suite (ISS) outside corrupted and Davis is sending me a new one. I did their Power Reset on the ISS but it keeps trying to "R" Resync or "L" lost signal.

They said it is most likely my ISS that is causing problems communicating with the console.

Thanks for everyone's help to try and pinpoint the issue!
 
Back
Top