WUHU Software

This page is provided as an alternative download page for the WUHU application and support files.

Overview:

The Weather Underground / HeavyWeather Uploader (WUHU) group is primarily intended for users of the Personal Weather Stations (PWS) who wish to upload their weather data to weather servers (Weather Underground and CWOP) via the Internet. WUHU can also be used without uploading data to weather servers for use in stand alone Home Automation Systems.

Supported Stations with Direct Serial Support: WS2308, WS2310, WS2315, WS3600, Oregon Scientific WMR-968s, WMR100, WMR200, Davis VP2, Vue, Weather Monitor II, Weather Wizard III, and other stations.

La Crosse Stations: For La Crosse HeavyWeather users (WS-23XX) this software requires the use of HeavyWeather Beta 2.0 or later that support the export file currdat.lst. HeavyWeather must be running at all times in order for this program to retrieve the current weather data from the weather station. La Crosse weather stations (WS-2300, WS-2305, WS-2310, WS-2315, WS-3600, and WS-3610) all use the HeavyWeather application. These units are also distributed under the Weather Channel name brand. WS-23XX and WS-36XX users have the option of running WUHU in direct serial mode. In this mode, Heavyweather is no longer required. The newer La Crosse 281X stations require special versions of Heavweather Pro called Heavyweather Pro 2800.

For Weather View 32 Pro users: This software requires you to be uploading to the Weather Underground. WUHU monitors data sent to Weather Underground and then sends that data to CWOP. In order for this to work your station must have the following sensors: Wind Direction, Wind Speed, Wind Gust, Humidity, Temperature, 1 Hour Rainfall, Air Pressure, and Dew point. See the Readme.txt file for detailed instructions.

Support for WV32 minute database monitoring: Allows Base and Standard Edition users to upload to the weather servers.

WUHU now supports Virtual Weather Station: I believe that owners of the Standard Edition will be able to upload to Weather Underground and CWOP. If your version supports CSV exports on an interval, this software should work for you. See Readme.txt for more information.

This software requires one of the following Operating Systems: Windows NT 4.0 (Service Pack 3), Windows 2000, Windows XP or later (users have reported success using Vista and Win7 as well). You can use Windows 98 if you use direct serial access (versus file monitoring that relies on other software).

---

Online User Manual:

http://www.lissproductions.org/wuhu_manual

---

Software Download

Before attempting to install WUHU, read this important installation notes:

Install Note #1: When you run the install.exe application it may conflict with other running applications like Outlook or other applications and / or services. If you experience a lock-up when running the installer, perform a fresh reboot and terminate other applications (including those in the tray) that might be causing the conflict. It may be necessary to boot in to Safe mode to install the software if the problem application or service cannot be found. Note that I recently discovered that instances of the Google Chrome browser can also block the installer.

Install Note #2: If you are using a USB to Serial adapter to interface with the console, beware that there are many manufacturers and in turn software drivers associated with these devices, some are quality products, others are complete junk. If you are using a La Crosse console, these require that the USB to serial adapter support hardware handshaking (RTS and DTR lines used to create a virtual ground). If you purchase a $5 adapter off e-Bay, it may or may not support hardware handshaking. I would recommend the IOGEAR GUC232A USB1.1 to Serial/ PDA Converter Cable adapter available at newegg.com or Amazon for about $30 (or less). Also get the latest driver off their web site. If you have a bad / cheap USB adapter, this can lead to the Blue Screen of Death under Windows (Kernel Dump and irrecoverable Lock-Up). This is not an application problem, this is a Windows / USB device driver problem!

Support:
If you have questions, please join the Yahoo group and post your questions there. While I do not mind helping users in personal email (or on other weather forums), there are many experienced users than can help you in this Yahoo Group. If there is a problem that requires a software modification, we will have a trail of diagnosis and solutions in the Yahoo group messages.  There is an Internet link within the application to this Yahoo Group. If you do not wish to receive every email from the Yahoo group, you can set the email frequency to Special Notices in which case you will receive very limited notifications from the group. See the link ‘Edit Membership’ in the Yahoo Group to modified your email settings. Click the following icon to join the WUHU software user group now:

 

Donate Using PayPal:

(Click filename link to download .zip file. Run the Install.exe that is stored within the zip file to install the program)

WUHU216_32_B221.zip - (Current Release) (1, 0, 216, 221) Refreshed 2-23-2014, 4:15 PM EST)

Enhancements in this version from the previous release:

1) Added support for Weather For You. See http://www.weatherforyou.com/pws/ for more info.

2) Added support for new Weather Underground upload data.

 winddir - [0-360 instantaneous wind direction]
 windspeedmph - [mph instantaneous wind speed]
 windgustmph - [mph current wind gust, using software specific time period]
 windgustdir - [0-360 using software specific time period]
 windspdmph_avg2m  - [ 2 minute average wind speed mph]
 winddir_avg2m - [0-360 2 minute average wind direction]
 windgustmph_10m - [mph past 10 minutes wind gust mph ]
 windgustdir_10m - [0-360 past 10 minutes wind gust direction]
 indoortempf - [indoor temperature F]
 indoorhumidity - [indoor humidity %]

Note: windgustmph will always equal windgustmph_10m as the meaning of gust determined by WUHU (and CWOP) is the highest wind speed over the past 10 minutes.

See: PWS - Upload Protocol

3) I have separated the CWOP upload interval from the general interval. The CWOP interval is now 10 mins (600 seconds). You can manually adjust in the INI file by tweaking the following setting:

[CWOP Settings]
UploadInterval=600

You do not need to manually enter a value for this setting, if it is not found, the default of 600 (10 minutes) will be applied. In any case, the value is there if you want to tweak it. For now, a minimum of 600 seconds is enforced since they do not want data any faster than that.

Note that if you hit stop and change your general interval back to 300 (as it was a couple days ago), the upload values may seem a bit off. Suffice it to say the next time you run WUHU, the uploads should be correct.

The general interval now applies to non-rapid fire WU, AWEKAS, and Hamweather uploads. The minimum allowed value is 300 seconds (as it was before). I am not sure what each of the servers is expecting, but I would guess 5 minutes is probably as fast as they want the data.

Another CWOP option that I have added will cause WUHU to manually flush the DNS cache just prior to the next upload to CWOP. This may or may not fix the problem on some systems where the rotate servers TTL DNS entry is being ignored by Windows. The DNS flush will only be performed on Windows 2000 machines or later (98 and NT series do not use a DNS cache). Please let me know if the rotate server was not working for you previously but works when testing this beta version.

To enable the flush DNS feature, you must add the following key to your INI using Notepad:

[CWOP Settings]
FlushDNSEnabled=1

Note: above key is set to value of one, not a lower case L.

4) Added the following METAR fields to the extended currdat.lst output:

[WUHU]
METAR_time = "211658Z"
METAR_wind = "20203G07KT"
METAR_temperature = "M07/M12"
METAR_QNH_pressure = "Q1033"

5) Fixed a problem with 10 minute gust reported to Weather Underground.

6) Modified the code that handles the CWOP rotate server by manually performing the IP round-robin myself rather than relying on Windows to do it.

7) Added a randomization routine to further enhance the load balancing between IPs assigned to a single hostname (ex. rotate.aprs.net, cwop.aprs.net)

8) Fixed minor rainfall calculation error related to reading console history.

9) Added log statements for background upload thread.

10) Fixed a problem with the user interface where if the user changed the station type, all of the other user data was lost.

11) Allowed template replacement strings to be used in the observation remark data. This is in turn uploaded to CWOP and WU.

12) Added built-in FTP actions. See action screen for usage.

13) Added a few critical sections to prevent file write/read access violations.

14) Preserved user settings for statistics between runs.

15) Fixed potential problem where the user enters and invalid range for the statistics display. When this happens, the program will lock up until the user acknowledges the pop-up dialog box that displays a warning. This pop-up dialog has been removed.

16) Added a chart legend to chart displays when a single chart is displayed (zoomed).

17) The solar radiation reading on Campbell CR100s was interpreted as KW/M^2. The meaning is now W/M^2.

18) Removed spaces from user specified CWOP server strings.

19) Reset zoom on graphs when graph window is re-opened.

20) Removed all warnings to AWEKAS unless the word 'warning' is found in one of the remarks (for sky conditions or weather conditions).

21) Added feature to ignore wind speeds from a particular direction and speed. In the tweak screen, in the ignore wind speeds edit box, you can enter 57.0@0 to ignore 57.0 readings when the accompanying wind direction is zero. This is useful with certain station that generate bogus winds speeds from a particular direction.

22) Added a couple of new fields in the Wedaal.txt output file (when enabled). This only affects users uploading wetter-board.de. I did not include the solar radiation field.

23) Fixed a bug that was related to the 'disable all rainfall reporting'. When the rainfall reporting was re-enabled, the old rain total was still reported.

24) Added wildcard file support to FTP uploads. With a single FTP action you can upload any number of files matching the wildcard string you supply.

25) Changed the destination for Hamweather uploads from Hamweather.com to PWSweather.com.

26) Added Delta/Hi low tool tips showing the time between the high and low and the rate of change calculation from the high to low.

27) If the log window flashing option is enabled, the try icon will not begin flashing until after the history retrieval is completed successfully. Previously the log window would flash because of notifications from the retrieval process.

28) If the station type is one that uses file monitoring, at start-up, the file that is being monitored is posted to the log.

29) Fixed the problem with wind direction for Honeywell stations using file monitor mode.

30) Changed CWOP upload rate from 10 minutes down to 5.

31) Increased pressure change threshold over 10 minutes from 0.05 InHg to 0.10 InHg

32) Decreased process priority from High to Normal. Threads will continue to be 'above normal' in the 'normal' priority class.

33) Added a 500ms sleep after FTP transfers to allow server to finish writing files.

34) Added support for the Davis Classic stations, Weather Monitor II, Weather Wizard III. If you have problems with these stations, please post message in the Yahoo group.

35) Fixed a bug in the template processing. The bug might have resulted in the template not being fully processed.

36) Added tweak option to include zero (or calm) wind speed readings in to the calculations used for wind speed averaging.

37) Added code to reset the rainfall reference and bucket counter if all rainfall reporting is disabled then re-enabled. Applies to WS-23XX and WS-36XX La Crosse models only.

38) Addressed a problem with the data import for Honeywell TE923 stations and the new release of the Honeywell software.

39) Modified the rain calculations for the TE923. The "RainCount" column actually appears to be just rainfall total in mm. The newer software supports fractions of a mm (.7mm resolution) where the old software supported only 1mm resolution.

40) Perhaps improved the problem where WUHU was minimized but did not have a window and did not minimize to the system tray. When this happened, the user had to kill WUHU from the task manager process list. Also fixed a bug with the tray icon flashing when new log messages were added.

41) Revised the WS-23XX and WS-36XX rainfall calculations yet again. Hopefully that problem is solved.

42) Added support for standby. When the computer goes to standby, the threads in WUHU go idle. When the computer comes out of standby, the console history is read again.

43) The error checking window on the wind chill was increased in case of very cold weather and high winds.

44) Fixed problem where low temperatures combined with high winds could result on out of range wind chill readings.

45) Fixed problem with Legacy Davis console (WMII for example) where negative temperatures or dew point readings would result in error reports.

46) Added file monitoring support (currdat.LST) for the La Crosse WS-2810. La Crosse software does not report absolute pressure. Relative pressure + Tweak offset is used to populate the absolute pressure readings. The best you can expect is an offset from Relative pressure.

47) Fixed a problem with the built-in ftp functions where the user name or password contained an @ symbol.

48) Added routines to attempt to detect the location of the currdat.LST file when WS-2810 Heavyweather Professional 1.0 is used. This location can be different based on the operating system that is used.

49) Added Wind Rose that displays the previous wind speed and direction readings seen over the past 10 minutes. The higher the label, the newer the reading.

50) Added a file logging option to the log screen. When this is enabled, all log messages are saved to 'WUHU Log.txt' in the WUHU progam folder. You can also edit the INI file and specify a different path and filename for the log file.

51) Save all logging options to the INI file so that they do not reset to default values between runs.

52) Decreased the pressure window used to detect bogus pressure readings from 0.10 InHg to 0.05 InHg. This pressure window applied to the average reading over the past 10 minutes and compared to new readings. If the new reading is not within the acceptable range, the new reading is rejected.

53) If the user attempts to graph a large history file, they are present with the option of breaking up the file in to monthly history files.

54) Added full support for WeatherBug. This required re-arranging the screen to attempt to keep within the 1024x768 screen limit. Some of the useful internet links were deleted.

55) Fixed a minor shutdown issue related to threading.

56) Attempted to improve the readability of the temperature and humidity linear gauges under the gauge screen.

57) Removed check for default printer at startup. This should no longer be needed with the new Teechart control.

58) Changed temperature gauge text color from bold blue to normal black.

59) Fixed a problem where minimizing the main WUHU interface would cause a lock of of the GUI. The problem was traced to an issue with Shell.dll.

60) Attempted to address a problem where the main GUI screen would not minimize to the tray.

61) Increased communication timeouts for Davis legacy systems (WMII, Wizard). This was required for slower systems.

62) Increased the pressure error checking window from 0.05 InHg over 10 minutes to 0.12 InHg after a storm rolled in and the rapid pressure change was mistaken for bad data.

63) A new variable was added to the INI file to substitute the comma for the period (example: 29,10  versus 29.10). This is used only when processing templates. You must exit WUHU before editing the WUHU Configuration.INI file.

Example:

[General Settings]

...

Template Decimal Comma Separator = 1

64) When the Virtual Weather Station (VWS) file monitor mode is used, and a solar radiation sensor is detected (column 28 of the CSV file), this data will be collected and uploaded with other weather data.

65) Removed the collection of the Extra Sensors if a Davis Weather Monitor II is used. Even though the Davis DLL call was returing 0 values for some of the extra sensors, this was not correct.

66) Modifed the criteria for storing new records when a Davis VP2 (or Vue) is used to catch momentary increases in the Wind Gust.

67) Moved the configuration data to it's own screen. This significantly reduced the size of the main screen.

68) Modified the Davis console type data retrieval code so that the absolute pressure is not polled on every update. For whatever reason, the request to update the absolute pressure data was taking anywhere from 1 to 2 seconds. This was affecting the ability of WUHU to miss gust data on the Vue.

69) Switched the Davis DLL to the latest version. Added call to retrieve the 10 minute gust using a new API call.

70) Davis Stations - Added code to force an update of the relative and absolute pressure readings every 30 seconds.

71) Addressed a problem with Davis units equipped with solar sensors. The solar radiation history data was not properly being read from the console at startup.

72) Fixed a bug with Davis VP2 and Vue where the cached gust speed in MPH was aciddently set to the metric value resulting in 1.6 increase in the wind speed.

73) Added console battery checking, transmitter battery checking, transmitter weak battery, and reception status data to the log when a Davis VP or Vue is used and Show Console Com. Errors is checked in the log.

74) Discovered that the new Davis DLL used to communicate with VP2, Vue, and newer stations was changing the basic units used by the console by writing to the firmware on the console. This would cause consoles that were configured to use Metric units to be converted to English units. Why Davis would have made such a fundemental change to the API I do not know. WUHU was modified so that it deals with whatever units are configured on the console and never allows the units to be changed. This required fairly major surgery to the history retrieval routines and the "live" data collection. Thanks Davis Weather!!

75) Added support to generate output files that can be imported in to YoWindow  and FWI Calc.

Here are the INI settings that can be entered in to the WUHU Configuration.INI file to accomidate the generation of these files.

[YoWindow]
YoWindowReportFile=C:\temp\Yotest.xml
YoWindowUseMetric=0

Note: The METAR observations are not yet implemented, only the current weather station data is used at this time.

[FWI Calc]
FWICalcReportFile=C:\temp\FWICalc.txt
FWICalcUseMetric=0
FWICalcUseRainTotal=0

Note: Remember to always exit WUHU and edit the INI file Notepad only.

76) Added addtional YoWindow support variables. These include UV index, solar radiation, snow depth, snow rate, visibility, and others.

To set these additional YoWindow variables, you will use the Observation screen.

a) Snow Depth - If this is non-zero, YoWindow switches to the Winter mode.

b) Snow Rate - This is set my selecting either light snow (-SN), moderate snow (SN), or Heavy Snow (+SN) in the weather conditions section. METAR does not allow the user to specify the snow fall rate. I have selected the translated inch per hour based on the best information I could find on the subject.  If you have a better idea, let me know.

c) Lightning is created by adding Thunderstorm (TS) to the observations. -TS creates slow lightning, +TS creates fast lightning.

d) There is a new Visibility entry box on the observation screen in the Sky reporting. Enter miles. You can enter fractional miles like 1/2, the result woult be 1/2SM in the report filed. SM stands for Statute Miles.

e) In the Sky conditions, the conditions of Clear, Few, Scattered, Broken, and Overcast are translated to the correct types for YoWindow. The altitude is not used. So if you generate FEW000 (0 elevation, which should never really be true), this will still be transfered to YoWindow correctly.

f) As soon as you click save settings in the observation window, the YoWindow XML file will be output immediately. You can press F5 when using the YoWindow application to force it to re-read the XML file immediately. If you do not hit F5 from within the YoWindow application, you would need to wait to see the results in YoWindow which could take up to 5 mins.

77) All local files like Weddal.txt, WXNow.txt, YoWindow.XML, etc, will be output once per minute.  This cannot be modified.

78) Added a new Setup page called "Miscellaneous". On that screen, you can click a button to edit your INI file settings. If you modify the file, all program settings will be reloaded from the INI after you exit Notepad.

79) Fixed a problem with YoWindow cloud cover descriptions that were absent from the .XML file.

80) Added code at startup to check how long Windows was giving applications to shut down when a users logs off or shuts down the computer. This is a registry value and defaults to 5 seconds. WUHU increases this value to 10 seconds as it may need a bit more time to quit communicating with certains stations (like Davis over USB).

81) Added support for Growl. Here are the INI settings:

[Growl]
GrowlProtocol=GROWL_TCP
GrowlServer=
GrowlPassword=

The only required setting is the GrowlProtocol, it must be set to either GROWL_TCP or GROWL_UDP. If this setting is not found in the INI file, Growl is not enabled.

If you do not include a password, no password will be used for Growl notifications.

If the Server is left blank, localmachine is assumed.

82) Fixed a problem with Davis VP and Vue where the conversion from Metric to English was not working correctly if the console was programmed to use metric. 

83) Fixed a problem where during shut down, several of the child dialog boxes were displayed during a shut down operation.

84) Changed the WUHU tray icon from a snowflake with an H to a transparent W.

85) Added a short cut to the Weather Underground forecast page under the Internet links.

86) Removed a double-activation of the console failure alarm.

87) Added support for the WMR100 and the WMRS200. Note that the WMRS200 is not to be confused with the WMR200 that is a newer station. The WMRS200 and older units use the same protocol as the WMR100. Support for the WRM200 should be added shortly.

88) Corrected a problem where on startup WUHU was treating the older Dave consoles like the WMII as a newer Davis unit (Pro or Vue).

89) Added support for extra sensor alarms that are configured via the INI file.

90) Added option to synchronize the Davis consoles with the PC clock time. This feature is enabled via the INI file setting:

[General Settings]

DAVISVP2 Sync Console Clock=1

91) Added option to synchronize the Davis consoles with the PC clock time. This feature is enabled via the INI file setting:

[General Settings]

WS23XX Sync Console Clock=1

There is one caveat when using the clock sync option with the WS-23XX units. Due to the change in the rules of daylight saving time, when the console time is set, the time is in the form of Coordinated Universal Time (UTC) and not local time. Because the WS-23XX console were manufactured prior to the new daylight saving time rules:

Start and end dates vary with location and year. Since 1996 European Summer Time has been observed from the last Sunday in March to the last Sunday in October; previously the rules were not uniform across the European Union.[28] Starting in 2007, most of the United States and Canada observe DST from the second Sunday in March to the first Sunday in November, almost two-thirds of the year.[31] The 2007 U.S. change was part of the Energy Policy Act of 2005; previously, from 1987 through 2006, the start and end dates were the first Sunday in April and the last Sunday in October, and Congress retains the right to go back to the previous dates now that an energy-consumption study has been done.[32]

http://en.wikipedia.org/wiki/Daylight_saving_time

Given that the WS-23XX firmware was created using the old daylight time saving rules, even though the correct time in UTC is set, what you see on the display may different from your PC time depending on time of year. These periods where the time may differ is basically the gaps of time between the old rules and the new rules. Eventually, the PC clock will change automatically when daylight saving time starts and ends so the clocks will match up at some point in time. The thing to remember is that even though the console display may be an hour off, it's internal time keeping is in terms of UTC that will be correct.

For more information about UTC time, see:

http://en.wikipedia.org/wiki/Coordinated_Universal_Time

92) In regard to the new WS-23XX time sync option... Today (11/3/2010) I discovered an issue where the history might not be read correctly even though the consoles UTC time was set correctly. This is due to the fact that the WS-23XX consoles store the history time stamp in local time (stupid concept) and that is based on the consoles old day light saving rules.

To remedy, the consoles local time is compared to the PC local time and the history record time stamp is adjusted accordingly. This adjustment is needed where there are gaps between the old rules (pre-2007) and the new rules. We happen to be in one of those gaps until the first Sunday of this month. I have verified that the PC will match the console after this coming Sunday when we "fall back".

On a side note, the changing of the day light saving rules is extremely expensive and fraught with potential problems especially for embedded systems that can not, or are not, able to update their firmware to accommodate for rule changes. This is why we should never allow politicians to make technical decisions!! Leave the darn rules alone from now to the end of time I say!!

93) Bug fix for YoWindow.XML. The solar radiation field is supposed to be a percentage (0-100.0) and this was reported incorrectly. The maximum solar radiation field from the weather station is assumed to be 1800.00 W/M^2. This value was chosen as this is the maximum reported by the Davis units.

94) Added a way to simplify uploading the YoWindow.XML file to up to 3 different FTP servers. 3 new INI entries were added to accommodate this:

[YoWindow]

YoWindowFTPFile1=

YoWindowFTPFile2=

YoWindowFTPFile3=

Each of these new entries contains an FTP upload action that can be used to upload the YoWindow.XML file to a server. The format of the FTP command is the same as those used with action files:

ftp://User:Password@Server.com[:port[P]] [BINARY | ASCII] "localfile" "remotefile" … [BINARY | ASCII] "localfile" "remotefile"

Field descriptions

User – FTP user name

Password – FTP password

Server.com – The FTP server to connect to

[:port[P]] – The FTP Port to connect to and whether to use Passive mode. The port is assumed to be the default of 21, and passive mode is not used. Passive mode may be required if you have firewall issues.

[BINARY | ASCII] – Optionally can change the file upload mode to binary or ASCII mode, binary mode is assumed. You can change modes between each local file and remote file pair.

"localfile" "remotefile" – The local file name on the PC to upload and the path and remote file that the file is uploaded to. You can have any number of local file and remote file pairs. Since most users will be uploading a single YoWindow.XML file to the server, only one pair of local and remote file specifications are needed.

Example:

YoWindowFTPFile1= ftp://myusername:mypassword@comcast.net "C:\Program Files (x86)\YoWindow\YoWindow.xml" "\YoWindow.XML"

This will upload the file C:\Program Files (x86)\YoWindow\YoWindow.xml to the server with the remote file name \YoWindow.XML using binary transfer mode (default).  Note that \YoWindow.XML specifies that the file is uploaded to the root folder on the server. The name of the server is comcast.net, the user name is myusername, the password is mypassword. The FTP client connects to the default port of 21 and passive mode is not used.

To use passive mode you would specify (note that the port must be specified even if the default port 21 is used):

YoWindowFTPFile1= ftp://myusername:mypassword@comcast.net:21P "C:\Program Files (x86)\YoWindow\YoWindow.xml" "\YoWindow.XML"

Each of the INI entries can specify a different server and different remote files. This will allow you to upload your YoWindow.XML file to up to 3 different servers. If more servers are needed, please let me know.

95) Added the capability to reset the rain total for stations that support this function (All Davis, WS-23XX, WS-36XX).

This feature has been tested on a Davis VP2 and a La Crosse WS-23XX. If you test this feature with a WS-36XX or WMII, Wizard, or other legacy Davis units, please let me know. If the test does not work, please tell me what rain total you attempted to set and what the console’s rain total changed to.

The reset rain total function is accessed by clicking the button “Rain Total” in the stats area that was previously only a label.

If WUHU is not overriding the rain fall calculations (1Hr, 24Hr) in the tweaks screen, it will depend on the station type as to whether or not the console resets these value or retains them. To play it safe, you might want to only reset the rain total when there is no rain over the past 24 hours.

96) With the help of Dan Brown, we debugged the new WS-36XX rainfall reset / set function. What made this possible at all was a contribution by a software develop Jean-Marie Pacquet who had figured out how to properly write to the WS-36XX console memory. Many thanks to Dan and Jean-Marie.

97) Added a verification dialog when the user select the Clear Log feature in the log screen.

98) Added support for the Oregon Scientific WMR200 including ability to read log data. If you have a WMR200 please report any problems that you encounter. The low-level protocol packets are visible if you check “Show Console Com. Errors” in the log screen.

99) Added limited support for extra temperature and humidity sensors for those models that support extra sensors. If you hover over the Current Data temperature reading, you will see a list of the reports from the extra sensors. The same is true for humidity if your sensors support humidity. Dewpoint and apparent temperature are also derived from the combination of temperature and humidity if supported by the sensor.

100) A hover-over for apparent indoor temperature can be seen by hovering the cursor over the current indoor reading edit box.

101) Changed the expected response from the PWSWeather.com server. Previously, the response was ‘OK’, the new response seen from the servers was ‘Data Logged and posted in METAR mirror’. Since the return code had changed, the result was Internet timeout errors being reported since WUHU did not see a proper acknowledgement of the upload.

102) Added a new variable to the [General Settings] section of the INI file that allows you to choose the units for wind speed on the main display.

Example: Change the wind speed units to Meters Per Second.

[General Settings]

Display Wind Units=MPS

Allowable values are MPH, KPH, MPS, FPS (Feet Per Second).

103) The calculation for Indoor apparent temperature was modified to match NOAA indoor comfort index tables.

104) For a WMR200, if a Stop request is made, a stop stream request is sent to the console so that it stops sending log data. This is useful if you want to interrupt the logger download and exit WUHU but not lose logger data. The logger is not able to detect a loss of communication (PC side) so it will keep streaming log data unless it is told to stop.

105) Added support for Weekly extremes in the WUHU Extremes.INI file.

106) Added a method to retrieve values from the WUHU Extremes.INI file for use in template processing.

There are 3 different types of sections in this file:

1) All time extremes. This section is denoted by [AllTime Extremes] and never changes.

2) Yearly extremes. This section is denoted by the Year number in brackets like [2010] for example.

3) Weekly extremes. This section is denoted by the Year and the week number in the form of [2010_week_48] where 2010 is the year and the week is 48 out of a possible 53.

Normally to use these variables, you would use a replacement string like this:

Yearly High Temperature: %[2010]Outdoor Temperature High%

This works however as the year changes, you would need to recode the [2010] to [2011].

To simplify the task, there are 6 new replacement strings that you can use to simplify the template to automatically change based on the current time of the year:

%Year%, %Month%, %Week%", %LastYear%, %LastMonth%, LastWeek%

So to code the above example to automatically change with the year, you would write:

Yearly High Temperature: %[%Year%]Outdoor Temperature High%

Weekly sections require both the Year and the Week number. To do this, you would code:

Weekly High Temperature: %[%Year%_week_%Week%]Outdoor Temperature High%

Note that you cannot really make use of the %LastMonth% until you have accumulated a couple months of data in the extremes file. These sections were not created in previous version; you will just have to wait to make use of them.

If someone was looking for a useful utility to code, you could scan through the history files and create these sections automatically so that they are available now based on your historical data. I doubt I will have time to do so.

More examples:

Weekly High Temperature: %[%Year%_week_%Week%]Outdoor Temperature High% @%[%Year%_week_%Week%]Outdoor Temperature High DateTime%

Monthly High Temperature: %[%Year%_%Month%]Outdoor Temperature High% @%[%Year%_%Month%]Outdoor Temperature High DateTime%

   Year High Temperature: %[%Year%]Outdoor Temperature High% @%[%Year%]Outdoor Temperature High DateTime%

AllTime High Temperature: %[AllTime Extremes]Outdoor Temperature High% @%[AllTime Extremes]Outdoor Temperature High DateTime%

Together these would produce something like:

Weekly High Temperature: 43.4 @Mon Nov 29 21:11:07 2010

Monthly High Temperature: 63.7 @Sat Nov 13 14:36:29 2010

   Year High Temperature: 43.5 @Mon Nov 29 14:21:39 2010

AllTime High Temperature: 98.8 @Wed Jul 07 15:11:49 2010

107) Added the ability to swap the vertical axis on the charts. To do this, double click the chart, select the Swap Axis button.

108) Fixed an application shutdown issues that could cause the program to terminate abnormally.

109) Added support for a UNIX UTC “C” style timestamp in the [time2] section.

110) Added support for the UV and Solar Radiation sensors in the [extra_sensors] section.

111) Added two new sections to the currdat.lst extended output, [yesterday_extremes] and [yesterday_averages]. This section will only be output if the setting “Hours of weather data in memory” is set to 48 hours or greater. This settings is located in the Setup/General Settings.

112) Added a method to simplify the FTP command in the action file.

If you specify the following section in the WUHU Configuration.INI file:

 

[FTP]

Server=myftpserver.com

User=myusername

Password=mypassword

Port=21P

 

Note: Always exit WUHU before editing this file!

 

Then you can use the form:

 

ftp://"C:\Heavyweather\Example.txt" "/Example.txt"

 

If the Port is not specified in the INI file, then port 21 is used and passive mode is not enabled.

 

You may also continue use the long form:

ftp://myusername:mypassword@myftpserver.com "C:\Heavyweather\Example.txt" "/Example.txt"

113) A new optional section was created in the WUHU Configuration file that will allow you to add your own custom data to the currdat.lst file. Once these values are in the currdat.lst file, you can then use them in your templates.

To use this new optional feature, create a new section called [User]. In this section, you can place any number of custom entries.

 

Example:

 

[User]

Latitude = 37.776771

Longitude = -122.391070

StationName = Heath's Weather Station

AnythingYouWant = This is a test

 

You can add as many variables in this section as you want.

 

When currdat.lst is generated, this is a section called [user] that will contain all of the variables that you had specified in the WUHU Configuration.INI file's [User] section.

 

Example:

 

[user]

Latitude = "37.776771"

Longitude = "-122.391070"

StationName = "My Weather Station"

AnythingYouWant = "This is a test"

 

These can then be used in templates like:

 

%[user]AnythingYouWant%

 

114) Fixed a serious semaphore dead lock condition that could cause the entire application to freeze up during template processing. If you are processing templates, please install this update immediately.

 

115) During template processing, if a variable in the form of %[section]variable% cannot be resolved, the string will be replaced with “N/A” a common abbreviation for “Not Available”.

 

116) Added a new [General Setting] option to limit the rate that the currdat.lst is written. With the extended data enabled, this file has grown to over 1000 lines of text. To limit the frequency that this file is generated, add the following key and specify the minimum time in seconds between writes of the currdat.lst file:

 

[General Settings]

.

.

Write Currentdat Delay=30

 

In the above example, the currdat.lst will be generated at 30 second intervals or more.

 

117) Clean up low-level USB routines for the Oregon Scientific WMR100 and WMR200 models.

 

118) Improved the WMR200 communications handling. Fixed a bug related to rainfall tracking.

 

119) Improved WMR200 logging functions.

 

120) When WUHU is minimized to the task bar, you can hover over the WUHU Icon (W) to determine which station is supported by that particular instance of WUHU. This is useful if you are running multiple copies of WUHU on a single machine supporting multiple station types.

 

121) When using file monitoring mode and selecting the Change button to browse for the currdat.LST file, all hidden folders and files will be shown during browsing for the file. This is needed if HW Pro stores the currdat.LST file in the C:\ProgramData folder on newer Windows operating systems where the folder is hidden.

 

122) Trimmed white space from user setup data in case a leading or trailing space was accidently added to user data.

 

123) Improvements made to WMR200 protocol related to logging.


124) Added the ability to chart extra temperature and humidity channels. Click here to download instructions.

125) Added a Rainfall total offset in tweak screen. This can be used when the console rain total is reset but the user needs to maintain a rainfall total that is representative of the total before the reset. When the offset is used, all rainfall reporting is disabled. The user must then wait for the next update from the console, go back in to the tweak screen, and un-check the Disable All Rainfall reporting check box.

126) Fixed a problem with Easyweather.dat file monitoring related to the Wind Direction where North was incorrectly reported.

127) Fixed a problem where an incorrect password for some of the weather servers did not result in an error message posted in the log.

128) Added a patch to work around a bug in the Davis DLL 2.42 or incorrect documentation related to unit conversion.

129) Fixed a problem in the currdat.lst output related to the METAR temperature (Temp/Dewpoint).

130) Added code to allow action files to be invoked from other actionfiles.

131) Changed the output format of the ZWNTANA Report File as requested by Dimitris (meteo at otenet.gr).

    day-month-yearwithcentury

    time24hr

    outsideTempC

    hi OutsideTempC

    low OutsideTempC

    outsideHumidity

    barometerHPA

    windSpeedKPH

    hi WindSpeedKPH

    windDirectionDegrees

    dailyRainMM

    monthlyRainMM

    totalRainMM

    rainRateMM

132) In the data integrity checking routine, the lowest allowed outdoor temperature was change from -40F to -58F.

133) Added TE923 extra sensor support. Added UV and Temperature and Humidity channels 1-4.

134) Added a new variable in the [YoWindow] section of the configuration file that will control when the YoWindow.XML file is uploaded when you use the YoWindowFTPFile1, YoWindowFTPFile2, and YoWindowFTPFile3 settings to upload the YoWindowXML file. Note that this does not affect other methods of FTPing the file like actions executed by 'On Weather Update' actions. 

[YoWindow]

...

YoWindowUseGeneralUploadInterval=1

Note: Set this variable to a non-zero value (the above examples sets this to one).

135) Fixed a problem with item #102 (above). Display Wind Units was not being stored in the correct format.

136) Changed the labels on the wind rose to show the time that each reading was made  with MM:SS format.

137) Fixed a minor issue with the daily rainfall calculation where new rainfall might be detected exactly at midnight and the calculated value might fluctuate between two values, one that includes the new rainfall and one that does not.

138) When swithing between graphing the current weather data in memory and history files, not all of the chart axes were automatically scaling correctly.

139) Added tweak option to round wind speed up or down to the nearest MPH or KPH. This affects data sent to servers, not data displayed.

140) Added a check on startup to compare the Relative to Absolute pressure ratio. If the current Relative / Absolute pressure ratio changes by +/- 5% of the old ratio, a caution message is generated in the log to warn the user that the Relative Pressure may need to be recalibrated. The new ratio is the accepted so this message will be entered in to the log only one time if the Relative Pressure was indeed reset.

Example: 

Sat Jun 18 20:06:38 2011 > **CAUTION**: The Relative to Absolute pressure ratio (1.19) has changed significantly from previous value of (1.00). Check to see if the Relative Pressure on the console needs to be set.

141) Fixed a problem with processing of the optional [user] section in the currdat.lst.

142) Added a new optional INI setting that will enable the writing of the tweaked rainfall total (and in turn the "new" rainfall value) in the history.dat records. This only applies the rainfall tweak when you have specified a multiplier other than 1.0000 for the rainfall in the tweak screen.

In the General Settings section of the INI file, add the following:

[General Settings]

Write Tweaked Rainfall Data to Historydat=1

Notes:

1) If you are writing the tweaked value to the history data, there is no record of the actual console rain total (console rain total) in the history.dat.

2) I would recommend that if you use this new option that you create a new history.dat file. Otherwise, the "new rainfall" value in the history.dat records will not be correct until your tweaked rainfall total exceeds previously recorded rain totals found in the file.  To be safe, start a new history.dat!

143) Reverted to older versions of the Silicon Labs DLLs provided by Davis with the Vantage Pro SDK v2.4.2.

144) Added support for replacement strings in FTP file naming.

145) Added a history file action to allow you to execute template files on each history record read from the console.

146) Set the Weather Underground and Weatherbug rapid-fire updates to 2.5 secs regardless of station type.

147) Manually calculated storm alert when using currdat.lst file monitoring and the HW application fails to report the storm alert value (%[storm_alarm]number% is -1)

148) Addressed memory leaks that could occur file there was an exception during file I/O.  Thanks to David Lipper for discoverying and reporting the memory leak.

149) Fixed monthly rainfall calculation reported in the currdat.lst output by WUHU.

150) If the station type is a Oregon Scientific (WMR968, WMR100, WMR200) and a sensor does not report in on time, the data is considered to be no longer valid and will not be uploaded to the weather servers.

151) Modified the startup code that determines the process name and path of the WUHU executable launched by Windows. The current working directory is then set to the same location as the launched program. This is helpful if the WUHU.exe has been renamed or the process has been launched by another application that is not setting up the current working directory for the process.

152) Allow the General Upload interval (under General Settings) to be lowered to 5 seconds.

153) Added support for MetOffice WOW. See http://wow.metoffice.gov.uk

154) If the wind sensor is disabled, uploads to WeatherBug will report 0.0 for all wind speed fields and 0 for all wind direction fields.

155) There was a problem with masking FTP passwords when copying from the Log to the clipboard. That problem has been corrected.

156) Fixed an issue where the MetOffice ID was not being logged correctly at start-up.

157) Changed the CWOP header from TCPXX* to TCPIP*.

158) CWOP encoding for solar radiation was incorrect. Although lead character was changed from uppercase L to lower case, the number sent was the solar radiation value when it should have been the solar radiation value minus 1000. The result is a 3 digit value.

159) Fixed serveral WMR200 log messages. Some should have only been written to the log if console com. errors was enabled.

---

Other Downloads

heavyweather2beta_setup_us.exe - U.S. Version - Heavy Weather Beta 2.0 Setup (WS23xx users, Required for WUHU when using Heavy weather).

heavyweather2beta_setup_uk.exe - U.K. Version - Heavy Weather Beta 2.0 Setup (WS23xx users, Required for WUHU when using Heavy weather).

Audibles.zip - Pre-configured audible voice alerts for WUHU. This is an Add-on. Not required.

sendEmail-v152.zip - Command line application that allows you to send e-mails. Can be used as a WUHU action. This is an Add-on. Not required.

Wheres James WebCam Publishing Software - Freeware Web Cam publishing software. Not related to WUHU.

(My weather conditions at Weather Underground)

 

Related Links:

http://banners.wunderground.com/cgi-bin/banner/ban/wxBanner?bannertype=WeatherStationCount&weatherstationcount=KMIBRIGH4

www.awekas.at