Re: next beta build#201 of YAAC, created 2024-Jul-14
The upgrade.jar is invoked automatically when you use the Help menu's Check for Updates and it finds a new version to download. Once the new version's zip file is downloaded, the upgrade.jar file is invoked to install the zip file's contents; some operating systems (such as Microsoft Windows) will not allow a running program to be overwritten, so the separate upgrade program does the overwriting of YAAC with the newer code version. In short, upgrade.jar should never be invoked manually. Hope this helps. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Jamie H <wa7jh@...> Sent: Monday, July 15, 2024 9:49 PM To: [email protected]Subject: Re: [yaac-users] next beta build#201 of YAAC, created 2024-Jul-14 Are there instructions for the "Upgrade.jar"? Jamie Hughes WA7JH (360) 340-8886 -----Original Message----- From: [email protected] < [email protected]> On Behalf Of Andrew P. Sent: Sunday, July 14, 2024 5:07 PM To: [email protected]Subject: [yaac-users] next beta build#201 of YAAC, created 2024-Jul-14 next beta build#201 of YAAC ("Yet Another APRS Client"), created 2024-Jul-14 downloadable from or changes and updates include: 1. increase regression test coverage for GPS package. 2. ensure blinkenlight-launched port configuration editor won't fail to dismiss if there is an error in opening the revised port. 3. fix debug logging logic in TopoLayer. 4. fix shutdown race condition in port close for APRS-IS ports. 5. prevent deleting SRTM files if download errors occur when downloading updated files. 6. fix documentation for MADIS weather checks. 7. Add GPSD JSON tests to GPS unit tests. 8. improve AREDN plugin debug logging. also fix obstruction calculations to account for SRTM tile cells that do not contain elevation data. 9. another attempt to fix timing in unit test for marineports plugin port connector class so false failures don't occur. 10. add PNG icon images for creating startup shortcuts on platforms that don't support Microsoft Windows ICO files.
|
Re: next beta build#201 of YAAC, created 2024-Jul-14
Are there instructions for the "Upgrade.jar"?
Jamie Hughes
WA7JH
(360) 340-8886
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Andrew P. Sent: Sunday, July 14, 2024 5:07 PM To: [email protected]Subject: [yaac-users] next beta build#201 of YAAC, created 2024-Jul-14 next beta build#201 of YAAC ("Yet Another APRS Client"), created 2024-Jul-14 downloadable from or changes and updates include: 1. increase regression test coverage for GPS package. 2. ensure blinkenlight-launched port configuration editor won't fail to dismiss if there is an error in opening the revised port. 3. fix debug logging logic in TopoLayer. 4. fix shutdown race condition in port close for APRS-IS ports. 5. prevent deleting SRTM files if download errors occur when downloading updated files. 6. fix documentation for MADIS weather checks. 7. Add GPSD JSON tests to GPS unit tests. 8. improve AREDN plugin debug logging. also fix obstruction calculations to account for SRTM tile cells that do not contain elevation data. 9. another attempt to fix timing in unit test for marineports plugin port connector class so false failures don't occur. 10. add PNG icon images for creating startup shortcuts on platforms that don't support Microsoft Windows ICO files.
|
next beta build#201 of YAAC, created 2024-Jul-14
next beta build#201 of YAAC ("Yet Another APRS Client"), created 2024-Jul-14
downloadable from
or
changes and updates include:
1. increase regression test coverage for GPS package.
2. ensure blinkenlight-launched port configuration editor won't fail to
dismiss if there is an error in opening the revised port.
3. fix debug logging logic in TopoLayer.
4. fix shutdown race condition in port close for APRS-IS ports.
5. prevent deleting SRTM files if download errors occur when downloading
updated files.
6. fix documentation for MADIS weather checks.
7. Add GPSD JSON tests to GPS unit tests.
8. improve AREDN plugin debug logging. also fix obstruction calculations
to account for SRTM tile cells that do not contain elevation data.
9. another attempt to fix timing in unit test for marineports plugin
port connector class so false failures don't occur.
10. add PNG icon images for creating startup shortcuts on platforms that
don't support Microsoft Windows ICO files.
|
Sounds good. Definitely a good idea to get the second station working, to make sure you're running the correct audio levels to not distort the modem tones. Those old hardware TNCs are picky about
matching amplitudes for the two tones and not invoking audio compression in the transceivers.
Hi
Andrew many tnx for the advice.?
I followed your advice and the TNC 220 appears to be going into KISS mode when I run YAAC instead of me having to manually put it into KISS mode.
I have set it up as an APRS beacon (60 secs intervals just for testing) and the STA and TX lights are coming on as I would expect and the 2M TXR is TXing and I can hear packet tones on a handy.
My problem is there is only one other active APRS stn in my area about 10 miles away but there is a mountain between us so the path is vy difficult.? He is decoding nil but that my well be due to the poor path.
I need to set up a 2nd portatable APRS stn to see if my packets can actually be decoded.
That's my next step getting YAAC running on a RPi with my other TNC a Paccom TNC 320.
Will report the results.
73
Dave
GM4NFI
|
Hi
Andrew many tnx for the advice.?
I followed your advice and the TNC 220 appears to be going into KISS mode when I run YAAC instead of me having to manually put it into KISS mode.
I have set it up as an APRS beacon (60 secs intervals just for testing) and the STA and TX lights are coming on as I would expect and the 2M TXR is TXing and I can hear packet tones on a handy.
My problem is there is only one other active APRS stn in my area about 10 miles away but there is a mountain between us so the path is vy difficult.? He is decoding nil but that my well be due to the poor path.
I need to set up a 2nd portatable APRS stn to see if my packets can actually be decoded.
That's my next step getting YAAC running on a RPi with my other TNC a Paccom TNC 320.
Will report the results.
73
Dave
GM4NFI
|
Re: Beacon "Comment" Question
More specifically to answer the otiginal poster's question:
The /W1 (the "1" is part of it) indicates that the station sending the beacon is configured as a WIDE1-1 fill-in digipeater. Additional abbreviations would be inserted with delimiting commas if your station supported more New-N
aliases, such as ",MD7" if your station would digi for the state-wide Maryland-only alias.
Hope that helps.
Andrew, KA2DDO
author of YAAC
Everything you ever wanted to know about APRS packets and more. ?
toggle quoted message
Show quoted text
Greetings YAAC Braintrust,
On every APRS station that I have using YAAC as a client within the comment of the beacon there is a ",/W" in front of the text (). This does not affect any of the operations
of the beacon from what I can see. This text is obviously not present within the YAAC beacon tab, however I can see it within Direwolf transmit beacons which of course makes it to APRS.fi too. Anybody have information on what this is and is purpose?
Here is some station information which came from the one linked above.
1) YAAC Version 1.0-beta198(21-May-2024)
????? a) Port 1: AGWPE
????????? Direwolf Beacon: [0L] WA5SON-2>APJYC1,WIDE1-1,WIDE2-1:/123300h2957.21N/09616.88W#,/W1 ?wa5son@...<0x0d>
????? b) Port 2: APRSIS
2) OS: Raspbian 11 (Bullseye)
3) Kernel: Linux 6.1.21-v8+
73
Brian WA5SON
Hockley, TX
|
Thanks Lynn. Good to have.
___
Sent from my two-way wrist watch
73 de W3AB/George
On Jul 11, 2024, at 03:33, Lynn Deffenbaugh < kj4erj@...> wrote:
toggle quoted message
Show quoted text
Here's the map that I intended to include in my first response from
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
PS.? The Send button on the earlier message must have pressed itself.?? That's my story and I'm sticking to it!
On 7/10/2024 11:51 PM, Andrew P. wrote:
Note the original poster has a G callsign (assigned to the United Kingdom) and a .uk email address. I don't think he's on our side of the pond. :-)
Anybody remember what the national APRS frequency is over there? Also note the the UK highly restricts automated station licenses, so there are very few digipeaters to forward more distant packets. Other users have commented on the scarcity of RF-hearable packets in certain parts of the United Kingdom, and the original poster didn't provide a more precise station location.?
Andrew, KA2DDO
author of YAAC
No traffic on 144.390 MHz?
___
Sent from my two-way wrist watch
73 de W3AB/George
On Jul 9, 2024, at 16:58, Dave GM4NFI < djcleckie@...> wrote:
I am trying to get an old Paccom TNC 220 which I built from kit in the 1980's working as a KISS TNC.
I am running YAAC under Ubuntu 24.04 on a dedicated PC with on "old type" RS 232 port which appears as /dev/ttyS5
The TNC 220 is working fine as a Command mode TNC using PUTTY to enter commands all seems normal working as it did in the 1980's.
It has a KISS mode which I never previously needed so I am unsure how well it is implemented.
I want to use it as a KISS TNC with YAAC.
I set the radio ?and terminal BAUD both to 1200
Word Length to 8
KISS ON
Restart
TNC 220 lights flash in correct sequence to indicate it has entered KISS mode.
I use the the configuration wizard to configure YAAC - so far so good.
I add a Serial KISS TNC and configure it. /dev/ttyS5 what I was using with Putty when I use it as a command type TNC.
When I press the TEST Port button a blank command window opens.
If I deliberately enter an invalid/non-existant port e.g. /dev/ttyS6 (when it should be /dev/ttyS5) then I get the error "Unable to bring up Test-Port for Serial_TNC" but when I enter a correct port I get the blank command window .
>From this I assume indicates YAAC has detected a KISS TNC?
The on-line help states the ... "Test Port" button provides a means of verifying that you have connected to the correct place; it opens a terminal window connected to the configured serial port so that you can manually test the TNC for the desired operation. To complete testing, close the terminal window."
My question is "What do I enter in this window to "Manually test the TNC?"
What should I see/do in this window to test that the TNC is operating correctly?
There is no packet traffic in my area for it to decode.
What commands should I enter in this command window to test the TNC?
73
|
Re: Beacon "Comment" Question
Everything you ever wanted to know about APRS packets and more. ?
Greetings YAAC Braintrust,
On every APRS station that I have using YAAC as a client within the comment of the beacon there is a ",/W" in front of the text (). This does not affect any of the operations of the beacon from what I can see. This text is obviously not present within the YAAC beacon tab, however I can see it within Direwolf transmit beacons which of course makes it to APRS.fi too. Anybody have information on what this is and is purpose?
Here is some station information which came from the one linked above.
1) YAAC Version 1.0-beta198(21-May-2024)
????? a) Port 1: AGWPE
????????? Direwolf Beacon: [0L] WA5SON-2>APJYC1,WIDE1-1,WIDE2-1:/123300h2957.21N/09616.88W#,/W1 ?wa5son@...<0x0d>
????? b) Port 2: APRSIS
2) OS: Raspbian 11 (Bullseye)
3) Kernel: Linux 6.1.21-v8+
73
Brian WA5SON
Hockley, TX
|
The UK APRS frequency is 144.800.? There are quite few digipeaters in the UK - I manage three of them in the southeast corner of the country.? There has recently been a liberalization of the OFCOM (=FCC) regulations of amateur radio, and is now easier to get a digipeater licensed.? The power limit for stations is now 1KW,, up from 400W.? There is limited permission of airborne stations, making it legal for APRS equipped balloons to overfly the country.? I general, the new regulations are a valuable step forward.
Bob G0BUX / W0BUX East Sussex, UK
On 11/07/2024 04:54:22, Andrew P. <andrewemt@...> wrote:
Note the original poster has a G callsign (assigned to the United Kingdom) and a .uk email address. I don't think he's on our side of the pond. :-)
Anybody remember what the national APRS frequency is over there? Also note the the UK highly restricts automated station licenses, so there are very few digipeaters to forward more distant packets. Other users have commented on the scarcity
of RF-hearable packets in certain parts of the United Kingdom, and the original poster didn't provide a more precise station location.?
Andrew, KA2DDO
author of YAAC
No traffic on 144.390 MHz?
___
Sent from my two-way wrist watch
73 de W3AB/George
On Jul 9, 2024, at 16:58, Dave GM4NFI < djcleckie@...> wrote:
I am trying to get an old Paccom TNC 220 which I built from kit in the 1980's working as a KISS TNC.
I am running YAAC under Ubuntu 24.04 on a dedicated PC with on "old type" RS 232 port which appears as /dev/ttyS5
The TNC 220 is working fine as a Command mode TNC using PUTTY to enter commands all seems normal working as it did in the 1980's.
It has a KISS mode which I never previously needed so I am unsure how well it is implemented.
I want to use it as a KISS TNC with YAAC.
I set the radio ?and terminal BAUD both to 1200
Word Length to 8
KISS ON
Restart
TNC 220 lights flash in correct sequence to indicate it has entered KISS mode.
I use the the configuration wizard to configure YAAC - so far so good.
I add a Serial KISS TNC and configure it. /dev/ttyS5 what I was using with Putty when I use it as a command type TNC.
When I press the TEST Port button a blank command window opens.
If I deliberately enter an invalid/non-existant port e.g. /dev/ttyS6 (when it should be /dev/ttyS5) then I get the error "Unable to bring up Test-Port for Serial_TNC" but when I enter a correct port I get the blank command window .
From this I assume indicates YAAC has detected a KISS TNC?
The on-line help states the ... "Test Port" button provides a means of verifying that you have connected to the correct place; it opens a terminal window connected to the configured serial port so that you can manually test the TNC for the desired operation.
To complete testing, close the terminal window."
My question is "What do I enter in this window to "Manually test the TNC?"
What should I see/do in this window to test that the TNC is operating correctly?
There is no packet traffic in my area for it to decode.
What commands should I enter in this command window to test the TNC?
73
|
Here's the map that I intended to include
in my first response from
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
PS.? The Send button on the earlier message must have pressed
itself.?? That's my story and I'm sticking to it!
On 7/10/2024 11:51 PM, Andrew P. wrote:
toggle quoted message
Show quoted text
Note the original poster has a G callsign
(assigned to the United Kingdom) and a .uk email address. I
don't think he's on our side of the pond. :-)
Anybody remember what the national APRS frequency
is over there? Also note the the UK highly restricts automated
station licenses, so there are very few digipeaters to forward
more distant packets. Other users have commented on the scarcity
of RF-hearable packets in certain parts of the United Kingdom,
and the original poster didn't provide a more precise station
location.?
Andrew, KA2DDO
author of YAAC
No traffic on 144.390 MHz?
___
Sent from my two-way wrist watch
73 de W3AB/George
On Jul 9, 2024, at 16:58, Dave GM4NFI
< djcleckie@...>
wrote:
I am trying to get an old Paccom TNC 220 which I built from
kit in the 1980's working as a KISS TNC.
I am running YAAC under Ubuntu 24.04 on a dedicated PC with
on "old type" RS 232 port which appears as /dev/ttyS5
The TNC 220 is working fine as a Command mode TNC using
PUTTY to enter commands all seems normal working as it did
in the 1980's.
It has a KISS mode which I never previously needed so I am
unsure how well it is implemented.
I want to use it as a KISS TNC with YAAC.
I set the radio ?and terminal BAUD both to 1200
Word Length to 8
KISS ON
Restart
TNC 220 lights flash in correct sequence to indicate it has
entered KISS mode.
I use the the configuration wizard to configure YAAC - so
far so good.
I add a Serial KISS TNC and configure it. /dev/ttyS5 what I
was using with Putty when I use it as a command type TNC.
When I press the TEST Port button a blank command window
opens.
If I deliberately enter an invalid/non-existant port e.g.
/dev/ttyS6 (when it should be /dev/ttyS5) then I get the
error "Unable to bring up Test-Port for Serial_TNC" but when
I enter a correct port I get the blank command window .
>From this I assume indicates YAAC has detected a KISS
TNC?
The on-line help states the ... "Test Port" button provides
a means of verifying that you have connected to the correct
place; it opens a terminal window connected to the
configured serial port so that you can manually test the TNC
for the desired operation. To complete testing, close the
terminal window."
My question is "What do I enter in this window to "Manually
test the TNC?"
What should I see/do in this window to test that the TNC is
operating correctly?
There is no packet traffic in my area for it to decode.
What commands should I enter in this command window to test
the TNC?
73
|
IIRC, UK APRS frequency is 144.800 along
with most, if not all, of EU.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 7/10/2024 11:51 PM, Andrew P. wrote:
toggle quoted message
Show quoted text
Note the original poster has a G callsign
(assigned to the United Kingdom) and a .uk email address. I
don't think he's on our side of the pond. :-)
Anybody remember what the national APRS frequency
is over there? Also note the the UK highly restricts automated
station licenses, so there are very few digipeaters to forward
more distant packets. Other users have commented on the scarcity
of RF-hearable packets in certain parts of the United Kingdom,
and the original poster didn't provide a more precise station
location.?
Andrew, KA2DDO
author of YAAC
No traffic on 144.390 MHz?
___
Sent from my two-way wrist watch
73 de W3AB/George
On Jul 9, 2024, at 16:58, Dave GM4NFI
< djcleckie@...>
wrote:
I am trying to get an old Paccom TNC 220 which I built from
kit in the 1980's working as a KISS TNC.
I am running YAAC under Ubuntu 24.04 on a dedicated PC with
on "old type" RS 232 port which appears as /dev/ttyS5
The TNC 220 is working fine as a Command mode TNC using
PUTTY to enter commands all seems normal working as it did
in the 1980's.
It has a KISS mode which I never previously needed so I am
unsure how well it is implemented.
I want to use it as a KISS TNC with YAAC.
I set the radio ?and terminal BAUD both to 1200
Word Length to 8
KISS ON
Restart
TNC 220 lights flash in correct sequence to indicate it has
entered KISS mode.
I use the the configuration wizard to configure YAAC - so
far so good.
I add a Serial KISS TNC and configure it. /dev/ttyS5 what I
was using with Putty when I use it as a command type TNC.
When I press the TEST Port button a blank command window
opens.
If I deliberately enter an invalid/non-existant port e.g.
/dev/ttyS6 (when it should be /dev/ttyS5) then I get the
error "Unable to bring up Test-Port for Serial_TNC" but when
I enter a correct port I get the blank command window .
>From this I assume indicates YAAC has detected a KISS
TNC?
The on-line help states the ... "Test Port" button provides
a means of verifying that you have connected to the correct
place; it opens a terminal window connected to the
configured serial port so that you can manually test the TNC
for the desired operation. To complete testing, close the
terminal window."
My question is "What do I enter in this window to "Manually
test the TNC?"
What should I see/do in this window to test that the TNC is
operating correctly?
There is no packet traffic in my area for it to decode.
What commands should I enter in this command window to test
the TNC?
73
|
Beacon "Comment" Question
Greetings YAAC Braintrust,
On every APRS station that I have using YAAC as a client within the comment of the beacon there is a ",/W" in front of the text (). This does not affect any of the operations of the beacon from what I can see. This text is obviously not present within the YAAC beacon tab, however I can see it within Direwolf transmit beacons which of course makes it to APRS.fi too. Anybody have information on what this is and is purpose?
Here is some station information which came from the one linked above.
1) YAAC Version 1.0-beta198(21-May-2024)
????? a) Port 1: AGWPE
????????? Direwolf Beacon: [0L] WA5SON-2>APJYC1,WIDE1-1,WIDE2-1:/123300h2957.21N/09616.88W#,/W1 ?wa5son@...<0x0d>
????? b) Port 2: APRSIS
2) OS: Raspbian 11 (Bullseye)
3) Kernel: Linux 6.1.21-v8+
73
Brian WA5SON
Hockley, TX
|
Note the original poster has a G callsign (assigned to the United Kingdom) and a .uk email address. I don't think he's on our side of the pond. :-)
Anybody remember what the national APRS frequency is over there? Also note the the UK highly restricts automated station licenses, so there are very few digipeaters to forward more distant packets. Other users have commented on the scarcity
of RF-hearable packets in certain parts of the United Kingdom, and the original poster didn't provide a more precise station location.?
Andrew, KA2DDO
author of YAAC
No traffic on 144.390 MHz?
___
Sent from my two-way wrist watch
73 de W3AB/George
toggle quoted message
Show quoted text
I am trying to get an old Paccom TNC 220 which I built from kit in the 1980's working as a KISS TNC.
I am running YAAC under Ubuntu 24.04 on a dedicated PC with on "old type" RS 232 port which appears as /dev/ttyS5
The TNC 220 is working fine as a Command mode TNC using PUTTY to enter commands all seems normal working as it did in the 1980's.
It has a KISS mode which I never previously needed so I am unsure how well it is implemented.
I want to use it as a KISS TNC with YAAC.
I set the radio ?and terminal BAUD both to 1200
Word Length to 8
KISS ON
Restart
TNC 220 lights flash in correct sequence to indicate it has entered KISS mode.
I use the the configuration wizard to configure YAAC - so far so good.
I add a Serial KISS TNC and configure it. /dev/ttyS5 what I was using with Putty when I use it as a command type TNC.
When I press the TEST Port button a blank command window opens.
If I deliberately enter an invalid/non-existant port e.g. /dev/ttyS6 (when it should be /dev/ttyS5) then I get the error "Unable to bring up Test-Port for Serial_TNC" but when I enter a correct port I get the blank command window .
From this I assume indicates YAAC has detected a KISS TNC?
The on-line help states the ... "Test Port" button provides a means of verifying that you have connected to the correct place; it opens a terminal window connected to the configured serial port so that you can manually test the TNC for the desired operation.
To complete testing, close the terminal window."
My question is "What do I enter in this window to "Manually test the TNC?"
What should I see/do in this window to test that the TNC is operating correctly?
There is no packet traffic in my area for it to decode.
What commands should I enter in this command window to test the TNC?
73
|
No traffic on 144.390 MHz?
___
Sent from my two-way wrist watch
73 de W3AB/George
I am trying to get an old Paccom TNC 220 which I built from kit in the 1980's working as a KISS TNC.
I am running YAAC under Ubuntu 24.04 on a dedicated PC with on "old type" RS 232 port which appears as /dev/ttyS5
The TNC 220 is working fine as a Command mode TNC using PUTTY to enter commands all seems normal working as it did in the 1980's.
It has a KISS mode which I never previously needed so I am unsure how well it is implemented.
I want to use it as a KISS TNC with YAAC.
I set the radio ?and terminal BAUD both to 1200
Word Length to 8
KISS ON
Restart
TNC 220 lights flash in correct sequence to indicate it has entered KISS mode.
I use the the configuration wizard to configure YAAC - so far so good.
I add a Serial KISS TNC and configure it. /dev/ttyS5 what I was using with Putty when I use it as a command type TNC.
When I press the TEST Port button a blank command window opens.
If I deliberately enter an invalid/non-existant port e.g. /dev/ttyS6 (when it should be /dev/ttyS5) then I get the error "Unable to bring up Test-Port for Serial_TNC" but when I enter a correct port I get the blank command window .
From this I assume indicates YAAC has detected a KISS TNC?
The on-line help states the ... "Test Port" button provides a means of verifying that you have connected to the correct place; it opens a terminal window connected to the configured serial port so that you can manually test the TNC for the desired operation. To complete testing, close the terminal window."
My question is "What do I enter in this window to "Manually test the TNC?"
What should I see/do in this window to test that the TNC is operating correctly?
There is no packet traffic in my area for it to decode.
What commands should I enter in this command window to test the TNC?
73
|
Re: next beta build#200 of YAAC, created 2024-Jun-08
I have 2 instances of YAAC running on different raspberry pi machines. The upgrade on a pi 4 running bookworm works using the " check for updates" selection from within YAAC. The upgrade on an older pi3 running bullesye downloads the updated files but fails to install. I notice that the 2 machines have very different versions of java running. On the bookworm machine I get:
$ java -version
openjdk version "17.0.11" 2024-04-16
OpenJDK Runtime Environment (build 17.0.11+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.11+9-Debian-1deb12u1, mixed mode, sharing)
on the bullseye machine:
$ java -version
openjdk version "11.0.23" 2024-04-16
OpenJDK Runtime Environment (build 11.0.23+9-post-Raspbian-1deb11u1)
OpenJDK Server VM (build 11.0.23+9-post-Raspbian-1deb11u1, mixed mode)
I am not sure if this is relates to the update problem. Both machine seem to run YAAC OK; it's just I cannot update the bullseye machine.
How do I update the older machine?
John, NX2I
|
From your description, it sounds like you used Putty to put your TNC into KISS mode, then told YAAC you had a KISS-only TNC, so it wouldn't take the TNC out of KISS mode when you opened the Test Port window or shut down YAAC.
I would recommend instead leaving your TNC in command mode before starting YAAC, and changing your Serial_TNC port configuration to specify the KISS command for TNC2-compatibles (which your TNC220 appears to be).
Then, when you start YAAC, you should see at that time the light-blinking pattern of your TNC switching to KISS mode. When you open the Test Port window, the TNC will be switched back to command mode (so you can do something with it in the window),
and returned to KISS mode when you close the Test Port window.
Also, I would recommend changing the serial port baud rate up to 9600, so there is less latency about forwarding received packets from the TNC to YAAC (and vice versa). The radio side would stay at 1200 baud.
Hope this helps.
Andrew, KA2DDO
author of YAAC
I am trying to get an old Paccom TNC 220 which I built from kit in the 1980's working as a KISS TNC.
I am running YAAC under Ubuntu 24.04 on a dedicated PC with on "old type" RS 232 port which appears as /dev/ttyS5
The TNC 220 is working fine as a Command mode TNC using PUTTY to enter commands all seems normal working as it did in the 1980's.
It has a KISS mode which I never previously needed so I am unsure how well it is implemented.
I want to use it as a KISS TNC with YAAC.
I set the radio ?and terminal BAUD both to 1200
Word Length to 8
KISS ON
Restart
TNC 220 lights flash in correct sequence to indicate it has entered KISS mode.
I use the the configuration wizard to configure YAAC - so far so good.
I add a Serial KISS TNC and configure it. /dev/ttyS5 what I was using with Putty when I use it as a command type TNC.
When I press the TEST Port button a blank command window opens.
If I deliberately enter an invalid/non-existant port e.g. /dev/ttyS6 (when it should be /dev/ttyS5) then I get the error "Unable to bring up Test-Port for Serial_TNC" but when I enter a correct port I get the blank command window .
From this I assume indicates YAAC has detected a KISS TNC?
The on-line help states the ... "Test Port" button provides a means of verifying that you have connected to the correct place; it opens a terminal window connected to the configured serial port so that you can manually test the TNC for the desired operation.
To complete testing, close the terminal window."
My question is "What do I enter in this window to "Manually test the TNC?"
What should I see/do in this window to test that the TNC is operating correctly?
There is no packet traffic in my area for it to decode.
What commands should I enter in this command window to test the TNC?
7
|
Greetings.
Did you visit my website at
On that web page, did you scroll down to the "Installing YAAC" section and click on the link for the zip file?
Andrew, KA2DDO
author of YAAC
|
I am trying to get an old Paccom TNC 220 which I built from kit in the 1980's working as a KISS TNC.
I am running YAAC under Ubuntu 24.04 on a dedicated PC with on "old type" RS 232 port which appears as /dev/ttyS5
The TNC 220 is working fine as a Command mode TNC using PUTTY to enter commands all seems normal working as it did in the 1980's.
It has a KISS mode which I never previously needed so I am unsure how well it is implemented.
I want to use it as a KISS TNC with YAAC.
I set the radio ?and terminal BAUD both to 1200
Word Length to 8
KISS ON
Restart
TNC 220 lights flash in correct sequence to indicate it has entered KISS mode.
I use the the configuration wizard to configure YAAC - so far so good.
I add a Serial KISS TNC and configure it. /dev/ttyS5 what I was using with Putty when I use it as a command type TNC.
When I press the TEST Port button a blank command window opens.
If I deliberately enter an invalid/non-existant port e.g. /dev/ttyS6 (when it should be /dev/ttyS5) then I get the error "Unable to bring up Test-Port for Serial_TNC" but when I enter a correct port I get the blank command window .
From this I assume indicates YAAC has detected a KISS TNC?
The on-line help states the ... "Test Port" button provides a means of verifying that you have connected to the correct place; it opens a terminal window connected to the configured serial port so that you can manually test the TNC for the desired operation. To complete testing, close the terminal window."
My question is "What do I enter in this window to "Manually test the TNC?"
What should I see/do in this window to test that the TNC is operating correctly?
There is no packet traffic in my area for it to decode.
What commands should I enter in this command window to test the TNC?
73
|
Where is the download link? I can't fond it anywhere.
|
Thanks. I will look and see what I missed -------------------- From: "Danny K5CG" <k5cg@...> Reply-To: < [email protected]> To: "yaac-users" < [email protected]> Sent: July 2, 2024 at 10:10 AM EDT Subject: Re: [yaac-users] APRS IS PASSCODE
?
Expert Mode
Ports Tab
?
?
Click Edit or Add the bottom.
?
?
APRS-IS Password in that box there.
?
73
Danny, K5CG
HH 550-0609
SKCC 14257
?
From: "Christopher Rose" <kb8uih88@...> To: "yaac-users" < [email protected]> Sent: Tuesday, July 2, 2024 8:57:55 AM Subject: [yaac-users] APRS IS PASSCODE
?
Hi, where is the passcode supposed to be entered in YAAC for the server? I am not communicating with any server and am confused about what needs to be done to make that happen. Thanks in advance for your help. KB8UIH
|
Jamie H
Dave GM4NFI
GEO BADGER
Brian WA5SON