No worries Tom. :)
Thanks again.
Aaron Vogel
818-268-3981
aaron.vo...@gmail.com
-
On Thu, Jan 18, 2018 at 10:48 AM, Tom Henderson wrote:
> My apologies Andrew. I had only folowed the link in your second email, and
> completely missed the first. Hopefully the info
My apologies Andrew. I had only folowed the link in your second email,
and completely missed the first. Hopefully the info from Curt was on the
nose and has you back on track.
I have a FT1XD I was able to use to test, so I was able to generate
packets locally that Xaster was the first to
Okay, excellent, so THAT was the question I needed to ask. Yes, that MIGHT
be the thing then. Here in the Bay Area there's s many digis around
that the likelihood of hearing a WIDE1-1 is pretty low.
Okay, so that wasn't terribly clear I guess but glad it is now.
This does still work for me,
On Thu, 18 Jan 2018, Aaron Vogel wrote:
I guess I have another, perhaps more fundamental question: how do I control
_what_ gets digipeated? For example, if I want it to act as a fill-in and
only digipeat WIDE1-1... where would I tell it to do this? If I wanted it
to digipeat everything... where
Tom,
If you take a look at the screen grab linked in my first email you'll see
"Digipeat?" is in fact checked. The TNC doesn't really do any digipeating
like others do, it's just a serial comm device.
The 30-min-interval beacon does show up in my TNC log and in the activity
view. The other thing
First thing is to check the obvious. Did you check the "Digipeat?" box
on the KISS TNC interface? Or is it a full TNC that does digipeating on
its own? If so, the digipeater may need to be configured.
Also, my setup does digipeat, but the outbound digipeated transactions
do not show in the
Do you have Smart Beaconing enabled? I think it enables by default and anyway
if smart beaconing is enabled, the setting Posit Tx Interval in
File|Configure|Timing is inoperative. This may be unrelated to your problem
but it stumped me nonetheless when I was setting xastir up.
Just a