You must set up your communication panel again so make a note of your comport and baud rate settings before you uprade. If you are running HeavyWeather, make a note of the filepaths. If you are running Peet, check your mode switch. Also fixed issue with WeatherLink automation that was introduced in a previous version. When switching from one Vantage Pro protocal to another, it would lock up. I fixed this issue. If the comport selection failed, it would revert back to Com 1.
This was fixed. Added functionality to add the high windspeed received from the Davis VantagePro2 into the graphs. Added troubleshooting capability for WMR archive data.
I have not been able to reproduce this, but I added a feature where it displays the first archived data point, the most current live reading, and the current record being downloaded, so we can troubleshoot this issue.
Continuation of the effort in P If you closed the WMR communication window and reopened, the archive records would not be updated.
Some users of VantagePro2 serial data loggers are reporting slow update rates or lock-ups. The only change for serial communication was a change in the timeout method incorporated by Davis. To test this theory, I reverted back to the old timeout method for serial communication only. P62 — P On some computers, the Wunderground 5-Day Forecast panel would crash.
I never figured out why but changing the number of cities from 4 to 3 eliminated the problem. The panel must be too complex to load on some computers. I hope this limitation in functionality will not hurt too many people. More changes to the WMR download archive transition state. The difficulty arises because this station sends download data and real time data at the same time and there is no flag sent by the WMR that tells us when the download is complete, so I used to base this on timing between the first real time record equalling the last archive record time, but due to USB buffering, the first real time record could represent old data and therefore the download record was incomplete it would assume there were no more archive records.
I fixed this by setting a 20 second timeout for the archive records. The assumption is after 20 seconds, if there are no more archive records, the software makes the assumption that there are no more records left since they usually come in second bursts. Some users are complaining that the rate of change and intergration features are not working properly. It may be an issue with clocking on the computer which is speculation at the moment.
To view the one second clocking, select Help Internet Status from the menubar. At the bottom of the panel is a one second timer update. It should be close to one second. Only dates between the years and will be accepted. Otherwise, it throws out the data. Solved a very random issue with the WMR download. It turns out that if you set the archive interval in the console to 2 minutes as an example , it may capture data 1, 3, 5, 7, 9,..
However, if you set the database interval to 10 minutes in Virtual Weather Station, it records to the database every 0, 10, 20, 30, 40, and 50 minutes after the hour. This is not an issue with real time data collection since it is constantly updating. I changed the software such that it will record all archive downloads. In the case above, it will update every 2 minutes in the database during the archive download and every 10 minutes during real time data capture.
To avoid this confusion, set your database interval and the weather station archive interval to the same value. This is now a message in the status bar.
It will still relaunch HW. There was an issue where if you selected the option to restart the software after 30 minutes of lost communication, it could restart the software over and over again if it took a while for the software shutdown to occur. Increased the HeavyWeather no sensor update status message from 1 minute to 3 minutes after startup.
Sometimes it takes a few minutes for the sensor to report. Added a one second timer function. Select Help Internet Status. If this timer is grossly in error not reading close to 1 second , we found this to be a clocking issue with the AMD processor.
Addressed WMR date and time issue. Fixed Metar text file crashing issue. Corrected weather station link on web pages for newer model weather stations. Fixed issue with error reporting for Davis Classic Weather Stations. Correcting issues with spikes in data with WMRA. This is caused by an errant archive record not a problem with Virtual Weather Station, this is a problem with the data logger.
Some stations report separate wind gust. If this value is bad out of range it was not getting trapped by the Range Limits select Settings Range Settings. Now the sotware sets the gust limits to the same values as the wind speed limits. The TCPIP version of the WeatherLink data logger requires that the Virtual Weather Station stop communicating with the data logger for 5 seconds once per minute so that it will upload the data to www.
The software now attempts to reopen 10 times instead of only once. Readdressing issues in P Some users are reporting lockups so added the timeout each time the port is reopened as an attempt to solve this. Added feature to determine what records are being downloaded from the VantagePro2 archive memory. See P I now close and open the comport on every read cycle so the logger can talk to WeatherLink. In P80, there was an issue where the software would lose communication when it tried to reopen the comport, so it now tries on every read and write cycle.
Fixed issue with Smart Forecast not being initialized at start up. Updated support for new Radio Shack Weather Station. Updated manual to reflect new weather station. Rolled revision so customer could install. There was an issue with multiple display images popping up the first time the display is modified due to an initialization issue fixed. One specific customer mentioned FTP operation was hanging yet communication continues.
I do believe this is being caused by the operating system and internet function timeouts, but I created a workaround. The program will restart in the event any operating state exceeds the Max Connect Time. To set these parameters: a. If this time exceeds the Max Connect Time minutes , also on this panel, the program will restart when stuck in an operating state. With the CWS, it only calculates the daily rain and not the total rain, like other stations.
This offset is updated on a daily basis and throughout the day is calculated by adding this offset to the current daily rain. This calcuation of total rain is then used to calculate daily, hourly and monthly rain. Added functionality to determine why excessive data is being downloaded from the WMR weather station. If you are having problems with random data being downloaded from archive memory, send me this file and I will review it.
Send the file to ed ambientweather. Another stab at fixing CWS rain issue. Added functions for Rainwise and Columbia that drops out of download state if the OK flag is missed and the maximum number of download records are exceeded. There has been an ongoing problem with calculating daily, monthly and yearly rain. To provide some background, most weather stations do not calculate this data, so VWS must calculate it.
Since rain is always increasing, this is not an issue, it will always be the minimum value at midnight. Addressing Columbia Weather Stations. Total rain still not correct. Also, does not stop downloading records. Make sure run it for a few days and make sure rain is accumulating. Supports the new Vantage Vue by Davis Instruments. Troubleshooting datbase update issues. This error occurred when I updated compilers. I have contacted our compiler manufacturer National Instruments to resolve this issue and they are researching it for me.
Version Fixed crashing issue with Version p New compiler caused issue New compiler now supports Windows 7. Next, select the WS-2xxx series weather station as the weather station type.
Crashing issue was back. Found it to be the 5-Day Forecast panel. Not sure why but reduced the number of five day forecast selections from 3 to 1. Not sure if this is a windows issue or a compiler issue, because the actual code is not crashing. I apologize to those that use more than one forecast location. Added jpeg file error notifications in status bar. One user can not determine why he an not generate jpeg files. Bracketed bad dates better by only allowing downloads within 2 years of current computer or system date.
Crashing continues. Still appears to be related to 5 Day Forecast panel. I deleted this panel and built in from scratch, changing some of the presentation of the data. You will have to set this panel up again, which involves setting the timer, and entering your location.
Sorry folks, this has been a real pain to solve. In the latest version of Heavy Weather, they changed their executable filename and location. Now I have the user find the actual file instead of the directory. If you need to correct this, Under Communication Communication, rebrowse to the HeavyWeather file location.
Fixed issues with daily, monthly and yearly rain. Prevented 0. VWS now throws out any zero rain value. I used to debouce it 5 cycles but that did not always work.
Also changed the Settings Rainfall panel to make it easier to edit daily, monthly and yearly values. Updated database from 20, points to 50, points. There was a bug in Version p13 that would give you an error message that the database was exceeded.
A couple of users are experiencing high and low summary read and write errors. You can send this file to me: ed ambientweather. Also, the summary files were only written once per day and at shutdown, and if you did not gracefully shut VWS down, you would lose this data. I now write this data once per minute. Power down and restart the computer. If you are connecting through a USB hub as opposed to direct USB connection, connect directly to eliminate issues with the hub.
Turn off all screen saver applications, which can interrupt USB data. Turn off all power save options. Select the Hibernate Tab and make sure the hibernate checkbox is unchecked. Turn off all USB power save features. Right click on each entry unless you know which one is correct , select Properties , and under the Power Management tab , uncheck the selection to Allow the computer to turn off this device to save power.
Contact the USB to serial converter manufacturer and make sure you are running the latest drivers. Not all converters are created equal. Also Consider Virtual Weather Station is crashing.
0コメント