Getting started with YAAC

#4

Got it loaded in a Linux Mint computer. Using an MFJ-1274 TNC with RAM upgrade and latest (1.1.9) TNC-2 firmware. I went through the configuration wizard and set everything up, proper serial port, speed, etc. With the Serial_TNC port page, I hit the TEST PORT button and see the data coming from the TNC. The text is somewhat garbled and each line overwrites the previous line, making it hard to read. I see callsigns, site aliases, and seemingly random characters. But I get no data showing on the map. I check View > Raw Packets and nothing shows on the window.

Xastir shows all kinds of data, so I know the TNC and radio configurations should be right.

Any ideas where to check?

tnx es 73,
Michael WA7SKG

Re: Still working on the next build of YAAC

Ronny Julian

#3

Andrew this is the best program written on a dare I've ever seen!? Thanks for your efforts!? ?I promote it everytime APRS comes up as a topis.? Ronny K4RJJ

Show quoted text

On Tue, Dec 17, 2019 at 11:13 AM Andrew P. <andrewemt@...> wrote:

Greetings, all.

Just letting everyone know the new YAAC mailing list and the YAAC software author aren't dead yet (although I am declaring the old mailing list dead now). I'm still cleaning up the code after debugging and fixing a _very_ annoying GUI rendering issue introduced by a recent patch to the Java runtime, plus usual bugfixes, and some updates to support large-scale events as discussed on the aprssig@... mailing list a couple of weeks ago. But I hope to have build 143 of YAAC out before Christmas. Whether the large-scale event support plugin will be ready by then is a different question.

Also, for all those who have asked for the ability to copy YAAC configurations from one system to another, I have reluctantly (i.e., dragged kicking and screaming :-) started implementing an experimental means to re-import a YAAC configuration saved by the File->Configuration->Export to XML File option. The difficulties were in ensuring that callsign-SSID assignments weren't duplicated on multiple active stations by negligence, and accounting for operating system changes (i.e., no /dev/tty devices on Microsoft Windows or COMn ports on Linux) during the transfer, while still making it generic to support arbitrary additional configuration data from plugins (and enhancing all relevant plugins to support it). It's a big issue.

So, you'll have an upgrade with some big new features soon.

It's been a long road since I first officially released YAAC back in 2012. Thanks, all, for making it worth the effort.

Andrew Pavlin, KA2DDO

author of YAAC

Re: Still working on the next build of YAAC

#2

Andrew

I am not a developer. But I have 4 Raspberry Pis working as a master and 3 workers with Kubernetes. I am trying to learn some basic python , git hub, gitops (a method not a tool) and so on. So take it from me I get how hard you have worked and appreciate? your efforts. Being a newly wed I assume you have different distractions than yacc.?

Peace

Scott Sheppard??

On Tuesday, December 17, 2019, 11:13:33 AM EST, Andrew P. <andrewemt@...> wrote:

Greetings, all.

Just letting everyone know the new YAAC mailing list and the YAAC software author aren't dead yet (although I am declaring the old mailing list dead now). I'm still cleaning up the code after debugging and fixing a _very_ annoying GUI rendering issue introduced by a recent patch to the Java runtime, plus usual bugfixes, and some updates to support large-scale events as discussed on the aprssig@... mailing list a couple of weeks ago. But I hope to have build 143 of YAAC out before Christmas. Whether the large-scale event support plugin will be ready by then is a different question.

Also, for all those who have asked for the ability to copy YAAC configurations from one system to another, I have reluctantly (i.e., dragged kicking and screaming :-) started implementing an experimental means to re-import a YAAC configuration saved by the File->Configuration->Export to XML File option. The difficulties were in ensuring that callsign-SSID assignments weren't duplicated on multiple active stations by negligence, and accounting for operating system changes (i.e., no /dev/tty devices on Microsoft Windows or COMn ports on Linux) during the transfer, while still making it generic to support arbitrary additional configuration data from plugins (and enhancing all relevant plugins to support it). It's a big issue.

So, you'll have an upgrade with some big new features soon.

It's been a long road since I first officially released YAAC back in 2012. Thanks, all, for making it worth the effort.

Andrew Pavlin, KA2DDO

author of YAAC

Still working on the next build of YAAC

#1

开云体育

Greetings, all.

Just letting everyone know the new YAAC mailing list and the YAAC software author aren't dead yet (although I am declaring the old mailing list dead now). I'm still cleaning up the code after debugging and fixing a _very_ annoying GUI rendering issue introduced by a recent patch to the Java runtime, plus usual bugfixes, and some updates to support large-scale events as discussed on the aprssig@... mailing list a couple of weeks ago. But I hope to have build 143 of YAAC out before Christmas. Whether the large-scale event support plugin will be ready by then is a different question.

Also, for all those who have asked for the ability to copy YAAC configurations from one system to another, I have reluctantly (i.e., dragged kicking and screaming :-) started implementing an experimental means to re-import a YAAC configuration saved by the File->Configuration->Export to XML File option. The difficulties were in ensuring that callsign-SSID assignments weren't duplicated on multiple active stations by negligence, and accounting for operating system changes (i.e., no /dev/tty devices on Microsoft Windows or COMn ports on Linux) during the transfer, while still making it generic to support arbitrary additional configuration data from plugins (and enhancing all relevant plugins to support it). It's a big issue.

So, you'll have an upgrade with some big new features soon.

It's been a long road since I first officially released YAAC back in 2012. Thanks, all, for making it worth the effort.

Andrew Pavlin, KA2DDO

author of YAAC