开云体育

Greetings, I've got fldigi configured to listen on port 8001, TCP/IP, Listen/Bind, Auto Connect/Retry. In YAAC, I configure a KISS-over-TCP port, localhost, 8001. Sometimes when I save the port it

Vicinity plotting isn't disabled on a per-station basis after-the-fact. It is part of the before-the-fact overall configuration of your YAAC station (and is a saved part of the configuration so you

Andrew, I would rather they not show unless a position was received. Having to tick something in configuration after the fact is a step or two I don't feel the used needs to have to do. Chris

Actually, the digipeater symbol with a red question mark on it has a different meaning. This indicates a "stealth" digipeater (or I-gate) which has not (as far as YAAC is concerned) sent a position

I treat question marks in the star icon usually as a corrupted report. When I see them they usually are not where they are supposed to be and I delete the station manually. I see them all the time. I

Can someone please help me understand what I'm seeing here? I have my filter set to only show stations from KISS-over-TCP. I see no incoming packets in the raw packet sniffer, yet N7LF-10 has shown up

Greetings. Alas, there is no such functionality in YAAC. Given the cost of re-rendering the background street and/or terrain layers of the map, and how spastic it would make the map look on a

Hi All, I'm currently testing Yaac with Robust Packet on HF, and it would be most useful to be able to Center automatically to the last station heard.on the RF port. I've looked in the documents / FAQ

It looks like all is ok now, doe you agree? Joe Sent: December 9, 2023 11:39 To: [email protected] Subject: Re: [yaac-users] YAAC wont digipeat Thanks Andrew. That was the problem. Too much data in

Thanks Andrew. That was the problem. Too much data in this old head and sometimes it gets lost. 73, de Ian VE3EP ________________________________ Sent: December 8, 2023 5:31 PM To:

On your RF port (AGWPE or Serial_TNC), which digipeat aliases did you choose to be used on that port? Digipeating doesn't happen automatically on every RF port; it has to be configured on a

I googled it and found I could easily install JRE with $ sudo apt update $ sudo apt install default-jdk I checked that all was OK with $ java --version -- -- Bill AA6BD

I must have changed something, but I don't know what. The following is set under the digipeat tab: ALIAS ??????WIDE 1-1 checked ????????????WIDE 2-2 checked

And you notice both of you said "Raspberry Pi 3B+", not "Pi 1A" or "Pi Zero". That was an annoying "feature" that the Raspberry Pi Foundation (or whoever manages the Raspbian distro) built the newer

Compiled perfectly here also on Raspberry Pi 3B+ running Bookworm 64: uname -m aarch64 Jerry

Works fine on an RPi 3B+ with Debian 12 here: $ uname -m armv7l $ wget https://www.ka2ddo.org/ka2ddo/YAAC.zip --2023-12-05 12:26:31-- https://www.ka2ddo.org/ka2ddo/YAAC.zip Resolving www.ka2ddo.org

Error messages can sometimes be rather arcane, but they are always indicative of the problem.

Michael. Your experience and findings are indeed valuable.? I suspect many will, if not have already, hit that issue, and many will just give up. I for one appreciate you documenting your struggle.

I was setting this up on an existing RPi system. At the time, when I started, I was unaware of specifically which model of RPi I was using. It was in a case that was difficult, and, at the time,

So why do you expect results on armv6l,when it "clearly" states that armv7l is required? I'll agree that the case insensitivity may cause confusion.