<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
I just started writing the manual about a day ago and there's not
much coherent information beyond my notes yet. I should have
something readable soon.<br>
<br>
The analog output is voltage, 0-3.3 volts. I thought about adding a
4-20 mA output but that might end up being another version - I'm
trying to keep this one simple. The MCU had a 10-bit DAC available
so the voltage output got added on as a bonus.<br>
<br>
As it stands right now, the default output from the RS-232 output
(available both in TTL and RS-232 levels on different pins) has a
simple CSV output with a fixed number of fields to make it really
easy to parse. It reports instantaneous, 2-minute, 10-minute, and
custom averaging periods in m/s for wind and mm for rain, plus MPH
and inches. Rain totals are 1-hour, 24-hour, and since manual reset.
It also reports time in minutes since the last rain detection.<br>
<br>
The Modbus RTU registers offer more options. It's set up as a matrix
of parameters and units so you can get any of the measured
parameters in any of the available units, which also include KPH and
knots for wind. In addition to the custom averaging period there are
also registers that will give you the average (or total, for
rainfall) since the last read of the register, so the master can
control the period just by setting its polling rate. There are some
additional holding registers for stuff like fault detection.<br>
<br>
To set up the analog output, you configure it with a source register
number, min, and max. If you set max lower than min it inverts the
output. So for example you might select "2 minute wind average in
knots" as the source and set the range from 0 to 20, and 0 knots
will produce 0 volts and 20 knots will produce 3.3 volts.<br>
<br>
The alarm output isn't done yet, but it'll be configured through
several registers that'll form a matrix of AND and OR conditions, so
for example you could set the alarm to be active when the 10-minute
wind average is over 15 knots and the 2-minute wind direction
average is between 45 and 180 degrees.<br>
<br>
Scott<br>
N1VG<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/13/2024 10:00 AM,
<a class="moz-txt-link-abbreviated" href="mailto:n6lrv@outlook.com">n6lrv@outlook.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:IA2PR20MB755301DF601C111BD320BC4CEC5A2@IA2PR20MB7553.namprd20.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div class="elementToProof"
style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Scott,</div>
<div class="elementToProof"
style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The project you're working on now is of interest to me. Will the
analog output be voltage or current? Can you share a link for
the WR-01 details?</div>
<div class="elementToProof"
style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks,</div>
<div class="elementToProof"
style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Gary</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif"
style="font-size:11pt" color="#000000"><b>From:</b> aprssig
<a class="moz-txt-link-rfc2396E" href="mailto:aprssig-bounces@lists.tapr.org"><aprssig-bounces@lists.tapr.org></a> on behalf of Scott
Miller <a class="moz-txt-link-rfc2396E" href="mailto:scott@opentrac.org"><scott@opentrac.org></a><br>
<b>Sent:</b> Wednesday, November 13, 2024 9:43 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:aprssig@lists.tapr.org"><aprssig@lists.tapr.org></a><br>
<b>Subject:</b> Re: [aprssig] Recommendation for remote APRS
weather station</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span
style="font-size:11pt;">
<div class="PlainText">You can add an external DS18S20 or
DS18B20 sensor to the ADS-WS1.<br>
<br>
We've also got a new ADS-WS2 in the works but it's not
likely to be out <br>
before Christmas. The WS2 will still do 1-wire but the
main focus is on <br>
Modbus RTU since that lets you do much longer cable runs
more reliably <br>
and there are a ton of sensors out there across all price
ranges.<br>
<br>
At the moment I'm busy finishing up the new WR-01
wind/rain sensor <br>
interface - it's a waterproof box that connects to the
same wind and <br>
rain sensors as the WS1 and provides RS-232 and Modbus RTU
over RS-485 <br>
outputs, plus an analog output and alarm output. It makes
it a lot <br>
easier to connect the sensors to an embedded device or a
PLC.<br>
<br>
Scott<br>
N1VG<br>
<br>
On 11/13/2024 8:50 AM, Jason Winningham wrote:<br>
> I’m planning a remote APRS weather station. What are
the current best options for the sensor hardware?<br>
><br>
> The obvious (for me anyway) first choice is an Argent
setup, but there’s no outdoor temperature sensor housing
included in that kit. I know the Davis was recommended at
one time, but their APRS specific interface seems to have
been discontinued. I found an Ambient Weather unit that
looks OK, but I haven’t checked into interfacing to APRS
systems.<br>
><br>
> Really not thrilled with excessively complex
solutions requiring RTL-SDR and a pi.<br>
><br>
> I have an old FC-301 and a few old HTs that are radio
candidates (we’ve got a good APRS network, I won’t need
much power to get out from this particular hilltop).<br>
><br>
> Any general recommendations or lessons learned from
those who have operated “mountaintop” setups would be
appreciated. This one is a hilltop site only half a mile
off the road in Alabama, but I’d like to do it right.<br>
><br>
> thanks,<br>
> Jason<br>
> kg4wsv<br>
><br>
><br>
> _______________________________________________<br>
> aprssig mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br>
> <a
href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
<br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br>
<a
href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
</div>
</span></font></div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a>
<a class="moz-txt-link-freetext" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a>
</pre>
</blockquote>
<br>
</body>
</html>