Thanks!
On Thu, Jan 20, 2022 at 1:34 PM Tom Russo wrote:
>
> On Thu, Jan 20, 2022 at 02:07:41PM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> > OK, I'll modify the xastir_udp_client documentation to note that injecting
> > objects or items into Xastir using the
On Thu, Jan 20, 2022 at 02:07:41PM -0700, we recorded a bogon-computron
collision of the flavor, containing:
> OK, I'll modify the xastir_udp_client documentation to note that injecting
> objects or items into Xastir using the same callsign/SSID as Xastir's will
> cause Xastir to own the object
OK, I'll modify the xastir_udp_client documentation to note that injecting
objects or items into Xastir using the same callsign/SSID as Xastir's will
cause Xastir to own the object and retransmit it in the same way that it does
objects created via its interface.
On Thu, Jan 20, 2022 at 01:49:09PM
On Thu, Jan 20, 2022 at 1:01 PM Curt Mills wrote:
>
> Where it can be and advantage is if you're trying to inject
> objects/items into Xastir from some other interface, using
> xastir_udp_client to do this injection.
>
That works and I have made use of it during bike events to translate SPOT
I have not played with Xastir for some time, but yes that side-effect did
exist as I remember using it. I would also agree it occurred only when
using the same callsign and ssid as the Xastir instance.
Brett KQ9N
On Thu, Jan 20, 2022 at 1:33 PM Curt Mills wrote:
> Yes, that description of how
Yes, that description of how they get adopted fits my fuzzy
recollection of same. Perhaps others who have used that side-effect
feature can comment.
It'd be good to add a blurb to the man-page about the possibility, so
people don't get confused when things work differently than they
expect.
On
On Thu, Jan 20, 2022 at 11:13:52AM -0800, we recorded a bogon-computron
collision of the flavor, containing:
> Commented-out lines: Seems to be a common complaint of yours these
> days.
As someone who's day job involves maintaining an enormous legacy software
package written by some dozen
Thinking about that another few seconds, the "Those of us who aren't
as accomplished with Git" bit probably means just myself, as we have
only three developers at present.
On Thu, Jan 20, 2022 at 11:13 AM Curt Mills wrote:
>
> Commented-out lines: Seems to be a common complaint of yours these
>
Commented-out lines: Seems to be a common complaint of yours these
days. Those of us who aren't as accomplished with Git, not using it
everyday, tend to keep possibly-useful code around in this form. Feel
free to get rid of such lines, at the expense of making it harder for
some of us to look up
The code is pretty hard to read and is peppered with blocks of commented-out
code that have been that way since 2005. There used to be some attempt to
treat the injected stuff as third-party only if its callsign was different
from Xastir's, but all that is commented out and stuff injected by
It's fuzzy in my memory now, but I believe there may be a side-effect
in Xastir as well (which can be taken advantage of in some cases)
where if the call and SSID are the same as the Xastir instance when
injecting packets in via xastir_udp_client, Xastir can take up
re-transmitting those packets
Resurrecting an ancient thread, because Dj opened an issue on GitHub about it
this week, and I tracked down what is happening here. I'm following up to
the original thread to clear up the misunderstanding and get the answer into
the mailing list archive where it could presumably be found in web
On 10/30/2020 1:07 AM, Steven Morrison wrote:
> I can configure the WeeWx program to generate a report and send it to
the xastir Pi, but how can i receive that report and transmit it in xastir?
I'm doing it as follows in Linux (Raspberry Pi) with both WeeWx and
Xastir running on the same
On 1/11/20 10:31 am, Liz wrote:
On Fri, 30 Oct 2020 08:26:41 -0500
Steven Morrison wrote:
Can you explain how you do this?
On 10/30/2020 4:17 AM, Liz wrote:
On Fri, 30 Oct 2020 00:07:19 -0500
Steven Morrison wrote:
Another approach would be to read the new weather entries sent
to
On Fri, 30 Oct 2020 08:26:41 -0500
Steven Morrison wrote:
> Can you explain how you do this?
>
> On 10/30/2020 4:17 AM, Liz wrote:
> > On Fri, 30 Oct 2020 00:07:19 -0500
> > Steven Morrison wrote:
> >
> >> Another approach would be to read the new weather entries sent
> >> to APRS-IS for my
You might take a look at:
https://github.com/weewx/weewx/wiki/cwxn
and
https://www.wxforum.net/index.php?topic=38817.0
On Sat, Oct 31, 2020 at 12:57:31AM -0500, we recorded a bogon-computron
collision of the flavor, containing:
> Thanks for the info. I'll investigate it further.?? I'm
Thanks for the info. I'll investigate it further. I'm running a Davis
Vantage Pro 2, with Weewx reading the weather station console and
forwarding the data to the NWS CWOP program. I should be able to create
a report to create the wxnow.txt report.
On 10/30/2020 3:24 PM, Tom Russo wrote:
I
I can't explain what Liz is doing, but Xastir supports "wxnow.txt" format
weather reports in a somewhat kludgy way. Does your weather station by
any chance support such a format?
The trick is to run a little perl kludge I wrote that masquerades as a
Davis Meteo database server --- but instead of
Can you explain how you do this?
On 10/30/2020 4:17 AM, Liz wrote:
On Fri, 30 Oct 2020 00:07:19 -0500
Steven Morrison wrote:
Another approach would be to read the new weather entries sent
to APRS-IS for my callsign and transmit them from that report.
I'm still doing that. When I'm driving
On Fri, 30 Oct 2020 00:07:19 -0500
Steven Morrison wrote:
> Another approach would be to read the new weather entries sent
> to APRS-IS for my callsign and transmit them from that report.
I'm still doing that. When I'm driving and see my weather displayed I
know that everything in the chain is
20 matches
Mail list logo
