My driver should work on your setup without too much modification. You could eliminate the perl script and your listen pipeline script would need to be constructed more like the ncat / ngrep based example I give in my readme so it produced its output on a socket. It's also easy enough to alter the driver to read from a named pipe, in fact that's how I started, but things ended up being a little simpler doing the simple socket server.
If you don't adopt my driver, I'd suggest checking out how I ended up decoding wind direction. Someone in the weewx-users mailing list reverse engineered the way directions are encoded, and it isn't a simple linear conversion. I converted the values to binary and it looks like each bit maps to either an individual switch in the sensor, or some simple meshing of switches. I didn't go so far as to try to model the physical hardware though and just used a python dictionary as a lookup table.
The wind fix wasn't in the original release I announced yesterday, but its there now if you visit the page and click the download link again.
If you don't adopt my driver, I'd suggest checking out how I ended up decoding wind direction. Someone in the weewx-users mailing list reverse engineered the way directions are encoded, and it isn't a simple linear conversion. I converted the values to binary and it looks like each bit maps to either an individual switch in the sensor, or some simple meshing of switches. I didn't go so far as to try to model the physical hardware though and just used a python dictionary as a lookup table.
The wind fix wasn't in the original release I announced yesterday, but its there now if you visit the page and click the download link again.