开云体育

Although I see a lot of good in the AGW protocol, it does add an extra layer. Why not just use KISS over TCP/IP.Then you are using the standard protocol for hardware TNCs.There is a lot of code (and

Hello John, While Martin's response is spot on for communicating packets from the Direwolf TNC to the Xastir APRS application, maybe you're wanting something different? Can you describe what you

i do wx like greg says, via aprsis. sending via rf only would require pushing it via the direwolf kiss api. you can generate the weewx WX aprs packet with this,

Hello. So. weewx is writing out a text file eve then APRIS32 (on a Win computer) is sending it RF! I was hoping to have just the RPi do everything, send it to DireWolf then to radio.. Sent from my

I have my weather station configured to write to the text file (wxnow.txt or something like that), where aprsis32 picks it up for sending out to IS and RF as KO6TH-15. I found that the particular

Xastir and other software uses AGWPE to talk to Direwolf. The protocol is fairly well defined. Implementing a client isn't trivial, but it's not super-hard either, as long as you're familiar with

Is there a document detailing how to write programs such as Xasitr that make API calls to direwolf? John Tarbox WA1KLI

Hello, Anyone also running a weewx WX station and sending WX packets from WX out as RF via DireWolf? I’ve had a weewx WX station running for years, but it send the WX CWOP packets out as APRS-IS.

Oh, it can get worse. I was using a USB audio dongle to interface to a mobile rig, and RF got into the cable. It caused the system (a Pi 3b) to think the Volume Down button had been pressed, causing

Still looking for a fix on this. Workaround has been fine so far. As long as it shows last in the list it will select it.

It's a concern with every radio (RF getting into logic/wires).? With *HT*'s is a disaster!?? I've seen RF lock up my pi/audio in all of my radios.? The ftm100 in the truck a couple of times, the

Yeah, it’s a pretty common issue. After I posted basically the same exact question a few weeks ago, seen it raised again at least once before yours. At least you now know what’s causing it and

My thanks to JK and David Ranch. The dreaded RFI seems to strike again. I have beads on every line. I turn the transceiver off. System is stable. beacon triggers at appropriate intervals. Power

Ah ok. I had the same, also eve using ferrite chokes. Is the radio just an HT right by it? I’m using an external N9TAX now and have no more issues, but still have the hat coming. I found out

Yes, a usb audio dongle, with ferrite beads on all wires.

I had this trouble quite a while back and I found the final thing to do after checking RF plug fitting, adding ferrites, checking earths and swr was to make sure the computer data/CAT cables from the

Hello Don,

I was getting exact errors. RFI was causing the USB audio to disconnect. Fixed it by separating the radio further, using some choked, etc, but also have a Fe-Pi clone (audio hat) enroute. Are you

OK I have DINAH working smoothly on a Raspberry PI 3 running direwolf and all is working well. I have now built from scratch on PI Zero (PI3 compiles don't always work o PI Zero) and I get the

I have a direwolf configuration on a Raspberry PI 3 with digipeating. I configure APRSIS32 to connect to the Direwolf kiss port. Digipeating is not enabled in the APRSIS32. The system still