¿ªÔÆÌåÓý

Michael WA7SKG <wa7skg@...> says:

My APRS station is up 24/7 in my shack with a Linux computer connected
to a TNC to a radio. I have a USB sound dongle connected to another USB
port on the computer I use for things like copying ISS SSTV pictures.
I'd like to use that to also monitor other packet frequencies for things
like WinLink and BBS traffic. That leads to some questions.

Will yaac display non-APRS data (WinLink, packet, BBS, etc.) in the Raw
Packet Sniffer window?

Easily, as long as the data is in AX.25 frames. YAAC was specifically designed
as a packet sniffer (since that is basically how APRS works), and I used YAAC's
Raw Packets display to help me debug the higher-level processing of APRS
packets. YAAC won't necessarily _interpret_ the packets for you in other
protocols, but it will display the raw data.

What software would I use for this? I have used AX25 Listen to watch
packets from the command line. I have also played with Direwolf a bit.

Just use the same setup in YAAC you've used before. Direwolf will also display
all packets, but, again, being optimized for APRS and OpenTRAC, it won't do
much interpretation of non-APRS packets.

What kind of port would I configure for this? I don't see AX25 or
Direwolf options. The only software modem I can identify on the Port
Type list is AGWPE, which is Windows only and won't work here.

Direwolf speaks both the KISS-over-TCP and AGWPE socket protocols
(there are other software TNC programs besides DireWolf and the
original AGWPE which also emulate the AGWPE socket protocol, such
as the UZ7HO soundmodem). Note that YAAC doesn't have _any_
software TNC built into it; it just can interface to software TNCs running
in different processes on the same (or separate) computers using those
port types.

Is this feasible within yaac? Or should I use some other viewer type
application? Any suggestions on what that application would be? I'm
looking for something that would be a small window on the screen (like
the Raw Packet Sniffer), not a CLI thing, preferably with a way to save
the received packet list.

It is quite feasible in YAAC, and you can use most of the display modes and
filters to help analyze non-APRS packet data (for example, vicinity plotting
may help you locate non-APRS stations if their digipeaters send APRS-formatted
position beacons). I can't recommend any other programs because I couldn't find
any back when I started writing YAAC; that's why I put all that raw packet analysis
stuff into YAAC in the first place.

Regarding saving the packets: that's trivial. One checkbox in the expert-mode
Configuration dialog turns on received packet logging in YAAC (transmitted
packet logging is always turned on). You can also save to file from any of the
tabular views that have a menu toolbar.

Thanks.

You're welcome. Hope this helps.

Andrew, KA2DDO
author of YAAC

My APRS station is up 24/7 in my shack with a Linux computer connected to a TNC to a radio. I have a USB sound dongle connected to another USB port on the computer I use for things like copying ISS SSTV pictures. I'd like to use that to also monitor other packet frequencies for things like WinLink and BBS traffic. That leads to some questions.

Will yaac display non-APRS data (WinLink, packet, BBS, etc.) in the Raw Packet Sniffer window?

What software would I use for this? I have used AX25 Listen to watch packets from the command line. I have also played with Direwolf a bit.

What kind of port would I configure for this? I don't see AX25 or Direwolf options. The only software modem I can identify on the Port Type list is AGWPE, which is Windows only and won't work here.

Is this feasible within yaac? Or should I use some other viewer type application? Any suggestions on what that application would be? I'm looking for something that would be a small window on the screen (like the Raw Packet Sniffer), not a CLI thing, preferably with a way to save the received packet list.

Thanks.

--
73,
Michael WA7SKG

"Any day you do not learn one new thing is a wasted day."

Looks like you typed Kilo Alpha 2 Delta Delta Zero instead of Oscar. :-)

The site is up; I checked from at least 3 places. However, if your browser or proxy server is caching the stale certificate, you might need to do a Shift-refresh of the page.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of Richard Beggs <richard.n0eb@...>
Sent: Saturday, February 19, 2022 7:07 PM
To: Andrew Pavlin
Subject: [yaac-users] YAAC

Still can not reach ka2dd0.org<>?

--
Thank You and God Bless [¡`]
Richard

The ka2ddo.org website is back on line with proper (and up-to-date) SSL certificates.

________________________________________
From: [email protected] <[email protected]> on behalf of Jesse - VE7KOD <ve7kod@...>
Sent: Saturday, February 19, 2022 3:59 PM
To: [email protected]
Subject: Re: [yaac-users] Port

Andrew...

Your amazing!

Thank you

Andrew...?

Your amazing!

Thank you

Yes, I do. My webserver SSL certificate expired, and although I obtained the new one, I forgot to install it.

Taking care of it now...

Andrew, KA2DDO
author of YAAC and owner of the ka2ddo.org website

________________________________________
From: [email protected] <[email protected]> on behalf of Jesse - VE7KOD <ve7kod@...>
Sent: Saturday, February 19, 2022 3:18 PM
To: [email protected]
Subject: Re: [yaac-users] Port

Ps..

Anyone know what's going on with the website?

[cid:[email protected]]

Ps..

Anyone know what's going on with the website?

Fantastic.. thank you Dave!

The USB device was plugged in, obviously forgot to add my user to the dialout group.

73
Jesse

You have to have the device connected before you click the Add button, in the 'Add Port' selection and setup dialogue, that you get to from the 'Ports' tab in the Expert Mode 'Configure' dialogue.

In fact, in general most other software needs the devices present and correct, before you even launch them!? Not many allow you to re-plug stuff and in effect refresh the list they know about.

Also you need to be a member of the OS's "dialout" group.

If you've not already done that, you need to (in a terminal session.)

$ sudo adduser $LOGNAME dialout

( $LOGNAME is a Debian system variable that contains your current active login username.)

You username password will be asked for, when correctly entered the system will either tell you you are already a member of the dialout group, or add you to it.

If the latter, all should then be good.

73.

Dave G8KBV.? Currently YAAC 1.0-beta165 on Linux Mint 19.3




--
Created on and sent from a Unix like PC running and using free and open source software:

Fresh debian install and using serial TNC port with an RT-Systems USB-K5G cable for my d710.
Worked great on Raspberry pi os.

When I plug in the cable, the os detects it and adds /dev/ttyUSB0

Perfect.. thank you Andrew!?

Thanks for the info on the NB option.

So if I run the GUI on start-up and select Close window, the process will still be running in the background?
How do I get back to the GUI after I close window?

That could also be DCS (Digital Code Selection), where the number is a digital code burst instead of a low frequency audio tone. Does the same functionality as CTCSS tones, but differently.

________________________________________
From: [email protected] <[email protected]> on behalf of Greg D <ko6th.greg@...>
Sent: Saturday, February 12, 2022 1:57 PM
To: [email protected]
Subject: Re: [yaac-users] Close window vs exit

!!!!!

I've always wondered why there seemed to be a duplicate set of tones
(same tone, different selection index) in a number of the radios. Is
this why?

Greg KO6TH


Andrew P. wrote:

2. The NB checkbox (thanks for pointing out that I have to add that to the help files!) indicates that you are using narrow-band modulation (NBFM instead of FM); there is a not-very-well-used extension to the CTCSS tone indicator when reporting a frequency in a beacon or object that also indicates use of FM versus NBFM (capital 'T' versus lowercase 't' before the PL tone number).

!!!!!

I've always wondered why there seemed to be a duplicate set of tones (same tone, different selection index) in a number of the radios. Is this why?

Greg? KO6TH


Andrew P. wrote:

Regarding your questions:

1. Closing a YAAC window only stops YAAC if there are no other windows open. Note that "open" includes ones that are iconified to your task bar. All the windows have to be gone completely for YAAC to shut down (and there was a bug I thought I fixed, where formerly you could close the last window and the backend would still be running; that should be fixed.....).

2. The NB checkbox (thanks for pointing out that I have to add that to the help files!) indicates that you are using narrow-band modulation (NBFM instead of FM); there is a not-very-well-used extension to the CTCSS tone indicator when reporting a frequency in a beacon or object that also indicates use of FM versus NBFM (capital 'T' versus lowercase 't' before the PL tone number).

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Jesse - VE7KOD <ve7kod@...>
Sent: Saturday, February 12, 2022 1:04 AM

YAAC running on raspberry pi with my d710, works great.
Two things:
1) When I select close window, does that terminate the process?
2) On the beacon tab; there is a check for NB. I can't find anything in the documentation what this does.

Love this software, thank you

73
Jesse
VE7KOD

YAAC running on raspberry pi with my d710, works great.?
Two things:
1) When I select close window, does that terminate the process?
2) On the beacon tab; there is a check for NB. I can't find anything in the documentation what this does.

Love this software, thank you

In setting up YAAC following a fresh run of KM4ACK's Build-A-Pi scripts, it appears that APRS packets coming into YAAC via a "Yaesu" port are all being timestamped as 00:00 local time.? In the attached photos, note that the "Last Heard" age in the listing of stations heard is the same number of hours/minutes as the clock at the top right of the RasPi desktop.? All of those packets were received via a "Yaesu" port which is configured as depicted in the 2nd attached photo.? As depicted, the incoming packets arrive in the yy/dd/MM format, and the Yaesu port is configured to match.? The one station in the "Last Heard" list which displays correctly is my own station location, which is derived from a GPSD port, so I suspect the issue is somewhere in the Yaesu port time-stamping routine.? Has anyone else experienced this issue?

OS:? Raspberry Pi OS (Buster)
Computer:? Raspberry Pi 4 (4GB)
YAAC Version:? 1.0-beta171