开云体育

Alas, this is a bug. It will be fixed in the next build of YAAC (to be released next week). Andrew, KA2DDO author of YAAC

Hello Jean-Pierre, There is a program called ldsped that can connect to your ax25 interface and provide an AGWPE compatible interface that YAAC can use. Ldsped would share the serial port in this

New YAAC user here, so pardon me if this is a repeat or common question.? In the blacklist function, I added a station to this list.? After adding the station, I am unable to delete the station from

The question mark icon is for stations with unknown positions. A station that sends a status message, telemetry, or positionless weather report first (as far as your station newly listening is

I see periodic objects show up with the icon of a gray circle with a red question mark. They are many miles from their actual location. Clicking on the icon gives me a box of either seemingly garbage

Note that you can't share the TNC between YAAC and javAPRSSrvr; only one program can own the serial port connected to the TNC. Assuming you're going to have YAAC control the TNC, create a port of

No, it's a code bug. YAAC is receiving the query from your browser, but the min-webserver thread is hanging instead of sending the reply. I have the fix for the next build. I hope to put the next

I'm not able to access the mini webserver either (Debian 10). I haven't tried in 1-2+ years, so I couldn't say when it became an issue on my system. Via 'netstat -tea' I see that tcp6 under port

Regarding your two questions in order: 1. It will only show an acknowledgement on the Messages window if the fellow ham actually sends a reply (either manually or via Auto Acknowledgement feature of

HOWDY GUYS; On sending a msg to a fellow ham, does this program show a reply from the other station? Also what does OPEN NET? mean on the message board. TNX POB/K8LEN

That's the thing. There are many variables and a wide range of experiences. Sure, in some events, I can be dispatched to a location, set up there and stay for the duration, pack up and go home and out

Okay, here is a system recap. Mobile installation: * Raspberry Pi 3B+ running up to date Raspbian Buster OS * TNC-Pi hat mounted on RPi * Official Raspberry Pi 7" Touchscreen Display, Screen

I want to make one thing absolutely clear here. I most certainly am not putting down Andrew or discrediting his work in any way. Yes, I have had a hard time understanding parts of it, but that is more

Frankly, I didn't think status would be changing that rapidly when I designed the UI. The events I was working, I would be "En Route" going to the event, "In Service" the whole time I was there, and

Let's get this thread back on the correct subject line. Michael, please describe the hardware and O/S platform that you are using. What O/S (Windows, Linux, etc.) are you running? What is the screen

I’ve been following this topic with interest as I have been using APRS since it started in ‘92 and downloaded it from BBS’s! It sounds to me that Bob Bruninga’s original APRS would suit your

I’ve been following this topic with interest as I have been using APRS since it started in ‘92 and downloaded it from BBS’s! It sounds to me that Bob Bruninga’s original APRS would suit your

This is an interesting idea. To me, the MicE status has always been a useless piece of information *because* it was too difficult to change the status and most (all but DOS APRS?) clients don't

Okay, I am new to this. I am happy you have $600 for a new radio for APRS, I do not. To begin with, I have to use existing or low cost equipment. For my desired purpose, I am using equipment dedicated

-‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Yep, that worked! *sigh* Thanks!