I made a couple of new enchancements to the program.

Wind speed and direction uploaded to the weather servers are now
averaged. The method uses weighted averages (using vectors). This
should produce more accurate results. Previously, only the last
sample that was read was sent to the servers. Samples received in the
last 5 minutes are used in these calculations.

As a side note, I recently wired up my console rather than use the
wireless interface. The updates are much faster on the console and on
the Heavyweather screen however the currdat.lst file is updated only
once per minute. I put in a request to Lacrosse to update the
currdat.lst file whenever the data changes rather than the once per
minute updates. If this file were updated every 8 seconds, the
average wind speed and direction calculations would probably be much
more accurate.

Also added to this version, I added the ability to pass the weather
data to an action. For instance, you can send the temperature,
humidity values to your own application or batch file. See the
updated Readme.txt for more information.

I may added the capability to launch a generic action whenever the
currdat.lst file has been updated. If anyone has a need for this let
me know.

Sorry,

   I meant to post this link to the radiation shield that I modeled mine
after.

http://weather.overflow.net.au/station/stevenson.html

David,

   I mounted my temperature/humidity sensor under the eve of my house.
I also built a radiation shield. I modeled mine after the one
shown under this link: http://www.wxqa.com/shields.html Also, CWOP
has a page on radiation shields http://www.wxqa.com/shields.html

   Even with the radiation shield, and keeping it out of the direct
sunlight, I am still seeing readings that are a couple of degrees
higher than surrounding stations at times. It did improve my readings
that were about the same as yours (6 degrees or higher).

   Personally, I do not think a radiation shield will cure the problem
100% if it is explosed to direct sunlight, but I could be wrong.

   One final thing you might consider, I have noticed that some of the
radiation shields offered by Davis also use a small fan (solar
powered I believe) to keep the radiation shield vented. If you have a
power outlet nearby, you could add a small DC fan.

   I have considered adding a temperature offset to WUHU to correct
the problem. That would be fine except that would skew the other
readings such as dewpoint, windchill, that come from the unit. I made
add offsets for all these values if push comes to shove. Any ideas?

   Let me know if I can help.

--- In wuhu_software_group@yahoogroups.com, "david wynn"
<dgwynn@b...> wrote:
>
> Hi all
> With my station I am continually recording temps that are around 6
degrees
> higher than the local met office that is less than a kilometre
away. I
> originally had the sensor up a mast around 3 metres from ground
level and
> have since moved it down to around 1.5m off the ground and enclosed
the
> sensor within a plastic milk crate shrouded with 1 layer of 90%
white shade
> cloth but the daytime temps are consistently higher at around the
same temp
> difference.
> Does anyone have any ideas short of dropping the whole thing off
its mast
> and relocating the sensor, mast  and instruments into a less than
desirable
> location the will affect all the other sensors? Im using a 2310 in
wireless
> mode
> Any help or suggestions would be appreciated
> david
> -----Original Message-----
> From: wuhu_software [mailto:wuhu_software@y...]
> Sent: Tuesday, 12 April 2005 2:33 PM
> To: wuhu_software_group@yahoogroups.com
> Subject: [wuhu_software_group] WUHU 1.0.12
>
>
>
> I had noticed that there was a race condition between the start up
of
> HeavyWeather and WUHU where erroneous data was uploaded to the
weather
> servers.
>
> This condition only occurred at boot time or when HeavyWeather was
re-
> started but WUHU was not.
>
> The program now waits until the HeavyWeather data has settled before
> data is uploaded.
>
>
>
>
>
>
>
>   _____
>
> Yahoo! Groups Links
> *         To visit your group on the web, go to:
> http://groups.yahoo.com/group/wuhu_software_group/
>
> *         To unsubscribe from this group, send an email to:
> wuhu_software_group-unsubscribe@yahoogroups.com
> <mailto:wuhu_software_group-unsubscribe@yahoogroups.com?
subject=Unsubscribe>
>
> *         Your use of Yahoo! Groups is subject to the Yahoo! Terms
of
> Service <http://docs.yahoo.com/info/terms/> .

I had noticed that there was a race condition between the start up of
HeavyWeather and WUHU where erroneous data was uploaded to the weather
servers.

This condition only occurred at boot time or when HeavyWeather was re-
started but WUHU was not.

The program now waits until the HeavyWeather data has settled before
data is uploaded.

Well, just download it and everything is working super,,

I had no problems with the wind or rain ... lucky so far..

miguel

On occasion, I am seeing a bogus 24Hr Rain reading. Verified on the
HeavyWeather screen.

Anyone else seeing this?

More cabling issues?

I have attempted to mask the bogus wind speed readings. These
readings happen due to poor cabling. If you want to fix your cabling,
see "Kenneth Lavrsen's WS2300 Wind Sensor Modification " in the links
section.

In order to mask the problem, I implemented the following algorithm:

If a wind speed of over 57 MPH is detected, and the average windspeed
over the past 10 minutes is < 10 MPH, ignore the reading and use the
last sample.

It should be extremely rare for a real 57 MPH wind speed to be
detected during a period of low wind speed (unless the eye wall of a
hurricane is passing overhead in which case a bad wind speed reading
is probably the least of your worries).

I know this method is not perfect, but it should mask most of the
bogus wind speed readings.

If you have any suggestions how this might be improved, let me know.

I updated WUHU to create Internet links on the main WUHU screen.

These links provide quick access to your stations data on the Weather
Underground and CWOP as well as other useful links.

Make sure if you are using Zone alarm (or possibly other software
firewalls) that WUHU has rights to launch other processes. If you
have problems let me know.

I am not sure if anyone has noticed, but Heavyweather Beta 2.0 is a
CPU hog. My guess is that they did a poor job implementing the serial
I/O routines and are rapidly polling the serial port for characters.
On this particular machine (900Mhz AMD), it is eating up about 20% of
the CPU at any given time.

If you reduce Heavyweather's priority, your other applications will
be more responsive.

If you are running NT 4.0/2000/XP, you can go to the task manager and
then click Processes, right click Heavyweather, select Set Priority,
select Below Normal priority. Windows will warn you about changing
the priorities, click yes to finish. Unfortunetly you will have to
set the priority back to below normal each time you re-boot.

Another method that can be used is to create a batch file to startup
Heavyweather.

Here is the contents of the .cmd file that I use:

@echo off
start /SEPARATE /BELOWNORMAL "" "heavy weather.exe"

Save the file in the HeavyWeather Directory (C:\HeavyWeather), and
call it something like "Startup HeavyWeather.cmd"

Add a shortcut to "Startup HeavyWeather.cmd" in your startup folder.

When the computer starts, HeavyWeather will be started with a below
normal priority.

All,

I have uploaded a new version with a couple of minor tweaks.

1) The 1.0.9 will prompt the user at initial startup to ask whether
or not they want to run WUHU has a stand alone application (no uploads
to Weather Underground or CWOP). This is intended for users who wish
to use the Actions and Alerts functions of WUHU without connecting to
the Internet. The user is only prompted if no weather server account
informaiton is defined in the configuration file.

2) I noticed that during the reboot of my computer, the first update
from Heavyweather to the currdat.lst file was incomplete (some of the
fields were set to zero, outdoor temp for instance). This resulted in
bogus data being uploaded to the weather servers. To correct this
condition, data is not uploaded until the 2nd update of currdat.lst.

All,

I have uploaded a new version of WUHU to the files section (v1.0.7).

This version will allow you to specify audibles and execute
applications when weather station data criteria are met. Actions can
be used to send e-mails or invoke other applications.

If you are going to use these new features, *please* read the updated
WUHU Readme.txt (search for Alerts within) to understand how the
alerts are configured and what all of the available options are.
Although I have tried to make this interface as simple as possible,
you must understand the basic underlying concepts of actions and
alerts in order to use them effectively.

The fastest way to take advantage of the audibles to to download the
add-on 'Preconfigured Audibles1.zip' and 'Preconfigured
Audibles2.zip'. Follow the instructions in the ReadMeFirst.txt stored
in 'Preconfigured Audibles1.zip'. This file had to be split as Yahoo
limits the size of uploads. 'Preconfigured Audibles2.zip' contains
more sound files.

These sound files and instructions are *not* required for the new
version to work, they simply allow you to quickly have a set of
conditions and specified audio files (no Actions have been
preconfigured). I have not yet written code to merge .ini files, and
I do not want to overwrite your configuration data, so you have to
manually merge the stuff if you want to use it. Again, see the ReadMe
stored in 'Preconfigured Audibles1.zip'.

If you choose, you can define all of your audibles yourself. Just
install the new application then click 'Alerts' from the main screen.

If you are interested in sending e-mail based upon weather
conditions, this version will allow you to do so. In the updated WUHU
Readme.txt file, there are instructions for how to accomplish this.
There is a new command line application file in the file area called
sendEmail-v152.zip that will will need if you want to send emails.

I look forward to your feedback (hopefully positive!)

> From: wuhu_software [mailto:wuhu_software@...]
>
>   I would suspect that there is some type of resource conflict such
> as multiple devices attempting to be "com1", like modems or other
> devices.
>
> Another problem may be a shared IRQ conflict. If possible, do not
> share the com port IRQ with another device. If other devices are
> sharing the same IRQ, and they cannot be moved to other IRQs, try
> removing the device from the computer.

Thanks for your suggestions. I highly doubt it is a conflict though
because I currently have no other devices on the COMs. Device Manager
doesn't report a conflict either. But nonetheless I'll reverify this
info.

Also, I'll give the FIFO buffer mod a shot too. Frankly not too hopeful
here either as I can talk to the weather station (with FIFO buffers on)
but only after that manual uninstall of the com port and reboot.
Definitely worth a shot though.

Just as a reference, I thought Microsoft's knowledge base article
#283063 had similarities to this problem, though not exactly (and it was
Win2K, not XP). I did however try the registry change to no avail.

I'll also have to look into that IO Gear USB/Serial you mentioned.

Again, thanks for the input, I'll explore a little more.

Jim

E-MAIL CONFIDENTIALITY NOTICE:  The contents of this e-mail message and any
attachments are intended solely for the
addressee(s) and may contain confidential and/or legally privileged information.
If you are not the
intended recipient of this message or if this message has been addressed to you
in error, please
immediately alert the sender by reply e-mail and then delete this message and
any attachments. If you
are not the intended recipient, you are notified that any use, dissemination,
distribution, copying, or
storage of this message or any attachment is strictly prohibited.

James,

   I have heard of others on the Internet that have experienced the
same problem that you have. You are not alone.

   I would suspect that there is some type of resource conflict such
as multiple devices attempting to be "com1", like modems or other
devices.

Another problem may be a shared IRQ conflict. If possible, do not
share the com port IRQ with another device. If other devices are
sharing the same IRQ, and they cannot be moved to other IRQs, try
removing the device from the computer.

Finally, another device may be using the I/O addresses used by com1.
Make sure there are no I/O conflicts (especially with modems). See
your BIOS settings to determine which addresses are used, see device
manager devices for potential conflicts.

   If all attempt fail, I would try a different USB to serial device.
I have used one made by IO Gear without difficulty.

----

Here is a snippet from a page I found on the net:

A) In most PCs, Com Ports can be enabled or disabled through the
BIOS. If appropriate, confirm that the Com Ports are enabled.

B) Com Port conflicts can arise when a Port's IRQ or I/O addresses
are being shared by another device such as an internal modem, mouse,
scanner, or other external peripheral. The standard IRQ and I/O
address's are listed below:

Com Port   I/O address        IRQ
           (8 bytes needed)
----------------------------------
COM1      O3F8                4
COM2      O2F8                3
COM3      O3E8                4
COM4      O2E8                3

C) IRQ or I/O addresses can be changed via the following procedures:

1)click on the ` START MENU `
2) Select ` SETTINGS `
3) Select ` CONTROL PANEL `
4) Click on the ` SYSTEM ICON `
5) Select the ` DEVICE MANAGER ` tab.
6) Select ` PORTS (COM & LPT) `
7) Select the appropriate Com Port.
8) Click on ` PROPERTIES `
9) Adjust the Port settings accordingly.
10) Restart Windows

D) If the above procedures yield no success and the Com Port seems to
be set up properly and free of conflicts it may be necessary to
disable FIFO buffers on your PC Com Port.

1) click on the ` START MENU `
2) Select ` SETTINGS `
3) Select ` CONTROL PANEL `
4) Click on the ` SYSTEM ICON `
5) Select the ` DEVICE MANAGER ` tab.
6) Select ` PORTS (COM & LPT) `
7) Select the appropriate Com Port.
8) Click on ` PROPERTIES `
9) Select the ` PORT SETTINGS ` tab.
10) Select ` ADVANCED `
11) Uncheck the box titled ` USE FIFO BUFFERS `
12) Restart Windows

I made a few small changes today. The new file is version 1.0.6.

I modified the WU metar upload portion so that the data will be
uploaded for a period of one hour from the time the observation is
made (rather than erasing it at the top of the hour). Since this is
not a real metar report, it does not make sense to clear it at the
top of the hour. If reporting the metar data for a different time
period is desirable, let me know (maybe user conigurable?).

I also added the ability to add remarks to the cloud and weather
reporting areas. I added this for more advanced users who want to
upload an advanced remarks section. I was going to create sepeate
screen for entering all possible remarks, but that seemed like a lot
of effort for the few that might use that feature. WU does seem to
just capture whatever you send in this area and display it (for
instance TORNADOS IN AREA should work). I am not sure if they limit
the size of this string or not.

***Please refrain from uploading any data that is not part of the
Metar specification in this area (HI MOM for instance). We would not
want WU to prevent us from using this field for real observations.

For whatever reason, WU does not seem to change the current
conditions icon based on wheather or not you are providing the
current conditions (cloud, weather). In my case, current conditions
are taken from a nearby airport. It may be that only weather stations
providing real metar data are used for this purpose. As far as I can
see, it just adds a new column in the history data when it is
reported. This is still a useful feature I think, especially if
severe weather conditions exist, in which case you could pass that
information on to others (if they view your history data).

Well, that is it for now, let me know if you have any recommendations.

Thanks.

Based on the description of Metar data given here:

http://www.faa.gov/avr/afs/afs400/sec02.pdf

I have created a new version (1.0.5) that will upload observed data
to WU. There is a new button in on the main screen
titled 'Observations'.

After you make your observations, you must hit the 'Create Report'
button for the corresponding section (Sky or Weather Conditions). The
string that is display in the box will be the string sent to WU. If
there is no string in the box, an empty field is sent to weather
underground (for example if both strings are empty, it
sends '&clouds=&weather=').

In the http request, it uses the fields for &clouds and &weather in
order to report this data. I am not certain how WU will interpret the
data. Please give me some feedback if you are able to test it. Since
I could find no information on the WU site, I cannot be certain of
the format they expect (for instance, do they support elevation and
cloud types (TCB and CB)?

In order to keep the information timely, I erase these fields at the
top of the hour. If you want to generate another report for that
hour, you need to hit the "Create Report" button in the observation
screen. According to the above Metar document, observations are to be
observed at 45 mins after the hour and reported until the end of the
hour. The program will report the observations you make from the time
you enter them until the end of the hour.

If you have any suggestions or have some testing feedback, please let
me know.

Thanks.

Mark,

Below is an example I used to code the upload to WU.

I am not sure what the meaning of these two fields are:

weather - [text] -- metar style (+RA)
clouds - [text] -- SKC, FEW, SCT, BKN, OVC

I could allow the user to enter the cloud cover, but when would it
clear? It seems like it should be a timely report and should maybe be
cleared after a couple hours?

Also, I do not have any info in metar style (+RA), any info would be
appreciated.

---

Here is an example that I found:

usage
action [action=updateraw]
ID [ID as registered by wunderground.com]
PASSWORD [PASSWORD registered with this ID]
dateutc - [YYYY-MM-DD HH:MM:SS (mysql format)]
winddir - [0-360]
windspeedmph - [mph]
windgustmph - [windgustmph ]
humidity - [%]
tempf - [temperature F]
rainin - [rain in]
dailyrainin - [daily rain in accumulated]
baromin - [barom in]
dewptf- [dewpoint F]
weather - [text] -- metar style (+RA)
clouds - [text] -- SKC, FEW, SCT, BKN, OVC
softwaretype - [text] ie: vws or weatherdisplay
debug:/weatherstation/updateweatherstation.php

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the wuhu_software_group
group.

   File        : /WUHU 1.0.4.zip
   Uploaded by : wuhu_software <wuhu_software@...>
   Description : WUHU 1.0.4 - 16 Bit Setup - Added itself to Startup folder on
Install, Minimizes to the tray.

You can access this file at the URL:
http://groups.yahoo.com/group/wuhu_software_group/files/WUHU%201.0.4.zip

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/help/us/groups/files

Regards,

wuhu_software <wuhu_software@...>

HeavyWeather Review and Publish do not support uploads to CWOP. I
have written an application that will upload your weather data from
HeavyWeather Beta 2.0 to CWOP.

Download the WUHU project in the files area, read the Readme.txt.

Thanks.

--- In wuhu_software_group@yahoogroups.com, "champion6633"
<champion6633@y...> wrote:
>
> Hello,
> I am trying to setup HW publisher.  I have the review and
> publisher.  Does CWOP now support FTP?  How do I set this up?  I
> have a station ID of CW2754.  Thanks,
> Champ Clark

Hello,
I am trying to setup HW publisher.  I have the review and
publisher.  Does CWOP now support FTP?  How do I set this up?  I
have a station ID of CW2754.  Thanks,
Champ Clark

Mark,

Here is a piece of my currdat.lst file:

[time]
start = 3320324022
start_date_string = "Sun Mar 20 11:13:42 2005"
last_actualisation = 3320326738
last_actualisation_date_string = "Sun Mar 20 11:58:58 2005"
next_actualisation = 3320326798
next_actualisation_date_string = "Sun Mar 20 11:59:58 2005"


I was using the key "last_actualisation_date_string" to extract the
time, that key was not present in your file.

I need to use the key "last_actualisation", which is present in both
files. I do not yet know the binary format of that value (3320326738).

Thanks.

--- In wuhu_software_group@yahoogroups.com, <mail@s...> wrote:
> I'm using a WS3600 which is the European version but should be no
different in data output.
>
>
> Mark
>
> On 20/03/2005 16:37:23, wuhu_software_group@yahoogroups.com wrote:
> > I have received a bug report from a user attempting to use the
WS3610
> >
> > with this software.
> >
> >
> >
> > The user reported the run-time error (file and line #) and sent
my a
> >
> > copy of his currdat.lst file.
> >
> >
> >
> > I believe the problem is that the "last actualisation" fields I
was
> >
> > using are not present in the file.
> >
> >
> >
> > To resolve the problem quickly, I just use the current time and
data
> >
> > from the PC clock rather than the entry in the currdat.lst file.
> >
> >
> >
> > I will need to figure out the binary encoding scheme is used for
the

I have received a bug report from a user attempting to use the WS3610
with this software.

The user reported the run-time error (file and line #) and sent my a
copy of his currdat.lst file.

I believe the problem is that the "last actualisation" fields I was
using are not present in the file.

To resolve the problem quickly, I just use the current time and data
from the PC clock rather than the entry in the currdat.lst file.

I will need to figure out the binary encoding scheme is used for the
following field so I can revert back to using the currdat.lst file:

[time]
last_actualisation = 3320325357 << this field is encoded. Not time_t.

For now the patch is available in version 1.0.2 in the files section.

Thanks for the feedback!

I fixed the problem,,,
the command.com on the system32 in windows was corrputed.. now its
working great..

so, i install and everything working good..

miguel




--- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@y...> wrote:
>
>
> Miguel,
>
> Unfortunetly I am using installshield 5.1 Pro to create the setup
> application. According to the installshield website, versions
prior
> to 5.5 create a 16 bit program only.
>
> I did find instructions for making a 32-bit by hacking it a bit.
>
> I have uploaded a 32-bit setup version in the files area.
>
> Inside the zip, there is an Install.exe versus the normal
Setup.exe.
>
> Please test and let me know if it works.
>
> Thanks.

Miguel,

Unfortunetly I am using installshield 5.1 Pro to create the setup
application. According to the installshield website, versions prior
to 5.5 create a 16 bit program only.

I did find instructions for making a 32-bit by hacking it a bit.

I have uploaded a 32-bit setup version in the files area.

Inside the zip, there is an Install.exe versus the normal Setup.exe.

Please test and let me know if it works.

Thanks.

If you are able to run a version of HeavyWeather Beta 2.0, you may be
able to use this software with other Lacrosse weather stations (2310
and 2315 work correctly).

Here is an example of the contents of the currdat.lst file output by
my version of HeavyWeather Beta 2.0:

---

[header]
programm_name = "heavy weather"
programm_version = "Ver. 2.0 beta release"
file_name = "currdat.lst"
file_format_version = "ver. 1.0"

[time]
start = 3319801703
start_date_string = "Mon Mar 14 10:08:23 2005"
last_actualisation = 3320113792
last_actualisation_date_string = "Fri Mar 18 00:49:52 2005"
next_actualisation = 3320113852
next_actualisation_date_string = "Fri Mar 18 00:50:52 2005"

[weather_picture]
comment = "-1=not valid, 0=rain, 1=cloud, 2=sun"
number = 0

[weather_tendency]
comment_1 = "-1=not valid,            0=no change of air pressure"
comment_2 = " 1=air pressure rising,  2=air pressure falling"
number = 2

[indoor_temperature]
deg_C = "23.4"
deg_F = "74.1"

[outdoor_temperature]
deg_C = "-0.8"
deg_F = "30.5"

[indoor_humidity]
percent = "19"

[outdoor_humidity]
percent = "65"

[dewpoint]
deg_C = "-6.6"
deg_F = "20.1"

[windchill]
deg_C = "-0.8"
deg_F = "30.5"

[wind_speed]
mps = "0.0"
kmh = "0.0"
mph = "0.0"
knt = "0.0"
bft = " 0"

[wind_direction]
deg = "112.5"
name = "ESE"

[rain_total]
mm = "0.0"
inch = "0.00"

[rain_24h]
mm = "0.0"
inch = "0.00"

[rain_1h]
mm = "0.0"
inch = "0.00"

[pressure_absolute]
hpa = "982.9"
inHg = "29.02"

[pressure_relative]
hpa = "1016.9"
inHg = "30.02"

[storm_alarm]
comment = "-1=not valid, 0=storm alarm not activ, 1=storm alarm activ"
number = 0

WUHU is now listed on the CWOP page.

See http://cwop.info for more information.

Changed wind gust calculation to the following:

The NWS considers gust to be the maximum unaveraged wind measured
over the last 10 minutes.  The 10 minute period is independent of the
data reporting period.  So, if the reporting time is every hour at
the top of the hour, only the wind during the 50 to 60 minute period
is used in the gust determination.  If you report every 5 minutes,
you use the maximum of the peak wind for the past two data periods.

The software is available in the Files section (1.0).

If you are having any difficulties (program crashes, etc) or you have
an enhancement request, please post your message here.

Thanks to Miguel for suggesting the CWOP upload capability as well as
Beta testing.