开云体育

Finally got some video: https://drive.google.com/drive/folders/1Xw_p-PEWuNAnrdY48D8XrHd8zHB1j937?usp=sharing You can see that the settings are to keep me centered, the GPS is active, version is up to

You know, pointing all that out, maybe I don't need the commands exposed.? I'm having problems getting YAAC to make my radio transmit at the moment so I'll have to get back to you if I find out

Andrew: Thanks for the comprehensive response......m,y answers also step by step *1. You say that when you use a SignaLink (and presumably some modem software like DireWolf), everything works

Hi Brian, For clarification, the Rx audio out of the rig goes to all of the ports, regardless of what mode you're using. It's the Tx side that is specific to wherever the PTT is coming from. But, from

Greg:? Thanks for your response.? ? Yes, I am using the dedicated 'packet' 6 pin DIN for all connections. On the "TNC" side of the packet cable I have pinned PTT to DB9 Pin 3, TX Data to Pin 1, RX

Adding to Andrew's note... Where is the audio coming into the 847, compared to where the source of PTT is? The 847 uses the port where PTT is asserted to decide which port to listen to for transmit

Let's look at your issues, step by step. 1. You say that when you use a SignaLink (and presumably some modem software like DireWolf), everything works perfectly. So that says, when you are using the

HI; I've been trying to resolve a problem for two weeks. I have spent dozens of hours on the phone With Kantronics thinking it was a hardware problem; recent test results are proving otherwise.

Do you actually need an emulator for the full functionality of TNC2 command mode while in YAAC? The setup commands should already be done for your local hardware (TXDELAY, etc.), so you shouldn't need

Though I use numerous Raspberry Pis for different projects (including ham radio), I would like to interface my computer with a KISS TNC and be able to connect to a BBS through a terminal program.? My

That is a message I added recently to report when you are using an APRS-IS filter that depends upon your station telling the APRS-IS backbone where you are located, but you aren't actually sending a

Greetings, Been running YAAC for several years, Debian Linux, Kenwood D710. I have three profiles: one for terrestrial APRS, one as a digipeater, and one for satellite (ISS) work. I'm getting a

Weeellllll.... None, if I'm painfully honest.? I've only had it up a few hours off and on over the last few days.? I'm still trying to learn as much as I can about "Best practices" settings before I

That is an interesting concept. In theory, your assumption is correct; if you are running a sat-gate and a sat user is transmitting within direct receive range of you, it is possible that you could

I've been running an iGate for about 8-10 years now, but have just recently moved to YAAC running on Raspberry Pi with a TNC-Pi.? I love this software, so easy to use. Anyway, I sort of inherited an

Ah, you're talking about supplemental IS-to-RF forwarding. This is a special case, used only in limited circumstances, to forward Internet APRS packets that don't meet the normal transmit-capable

Is there a way for my Analog iGate to Digipeat beacons sent by YSF stations? Meaning when my YAAC iGate see there is packet sent from YSF station into APRS-IS, rebroadcast it as Analog.

Ah, that make sense. I have make sure RF beacon and APRS-IS beacon happens at different time. I just want to probe RF path to a distance iGate.

Well, your own station should be able to see any echo-backs from local digipeaters in the traffic you receive from RF, assuming you are using a non-empty digipeat path (if you don't authorize

Ah, that make sense. When I have both beacon on, only the Internet beacon shows up which made me believe the over-the-air beacon was not sent. However, I do want my RF beacon to show up, so that I