开云体育

Well, 1. What is the fixed station location configured in your beacon? Per chance, is it where your station is displayed? 2. Is your beacon configured to actually _use_ the GPS information to

Andrew, I did check the GPS from the FTM-400 that shows the correct location and the GPS data YAAC is showing they basically match. I do not know why it shows my shack in a different location. Also

Andrew, thank you for showing how to install YAAC on an M1MAC. ?I have it running and showing data from my FTM-400. I also have a USB GPS plugged into my Mac but there its putting me in the wrong

Andrew, Thanks for the information and guidance. There are several hams across the area looking to revive packet and improve what is left of a once strong aprs network across northeast MS and

Greetings. Regarding running one or two copies of YAAC for APRS and BBS at the same time: that is entirely up to you. You should be using separate radio ports anyway (typed for either APRS or raw

I have installed YAAC on my Win10 system and completed the initial setup. I’am playing with it, reading help files and doing my best to understand it before I go live with it. I have tried several

Andrew, Actually the build we use at MB7UXX DIGI/IGATE is the 11 August 2022 build, not v177 as I said before and DIGI works in it! So when we updated from this build to v178 DIGIpeating was

On the failing systems, please export the configuration file to XML and email me the file, so I can check your configuration, and ensure something didn't "fix" your configuration to turn off

Hi Andrew, DIGIpeating on 177 works. Our local DIGI/IGATE MB7UXX is running version 177 in a Raspberry Pi right now! Yesterday I tried to upgrade it to 178 and after I did, DIGI was broke. Same

Hmmm... did it still work in build 177? I didn't make any changes to the digipeat logic in 178, but there were some changes in 177. Also, are you still configured for digipeating (i.e., digipeat

Ah? I just test mind now and seem not getting digipeat Ve2pcq Le sam. 1 oct. 2022 à 05:49, Demetre - M0SUY/SV1UY <demetre.sv1uy@...> a écrit :

Hi all, After upgrading to beta v178 I noticed that the DIGI does not work anymore. Am I the only one having this problem? 73 de Demetre M0SUY

On the AGWPE or KISSoverTCP port between YAAC and DireWolf, is the port enabled for transmit? If not, then YAAC will not send any outgoing packets through that port. This capability is there to allow

I am working on an experimental build of my system. it is a RPI4 for its better video resolution running Direwolf and YAAC with a NWDigital draws board. ?Using direwolf as digipeater it works well

Hi Dave, Thanks for reply OM, I fixed it after Andrew reminded me about th e dialout group. I hadn't used LINUX for a long time and I had forgotten! Now it works FB! 73 de Demetre M0SUY

You probably need to start YAAC, "AFTER" connecting/pairing/binding the device to the computer, and verifying what ports the system creates and makes available. At least, with Linux Mint, that's what

Hi Andrew, Thanks a lot for your help. I had forgotten about the group dialout. Once I included myself to this group now YAAC works in my LinuxMint Desktop FB FB FB! Now to find a way for the

The RF comm device can't be persistent because you don't have the device up 24/7 connected to your Linux system. Every time the Bluetooth device (or the laptop) powers off, you will lose the

Hi there, I just did this and now there is a device rfcomm1 created in /dev directory. Any idea How do we make this persistent at every startup? Now I see my APRS Voyager being connected when I click

After you have paired the radio with the Mint computer try running: *hcitool scan * which should show you the mac address of the controller in the radio. Next run: *sudo rfcomm connect /dev/rfcomm1