开云体育

Hello KJ7PLR, The RTS cable doesn't do sound. No image attached but I would expect PTT would work but that's it. Correct. You need a sound device to use. Refer to the Direwolf UserGuide doc but it's

Hello Trip, What sound devices did you use? Anything specific about the cabling between the sound device and the radio? Any Isolation transformers in there? Those are VERY bad for higher bandwidth

Good Morning. I'm relatively new to direwolf, learning the ropes. So much possibility and an amazing piece of software. RaspberyPi4 Type 1 USB <-> Yaesu 857D CAT mini din, using an RTSystems USB-62C

RE: Testing Direwolf(DW) and UZ7HO Soundmodem(SM) at 1200/2400/3600/4800b with common MIC feed radios. Radios:? Kenwood?? TM-281 and TK-762(VHF) Audio In and Out: MIC and Speaker connects. TK-762

I try contacting people when I can as well with maybe 50% luck. Here is a filter I use at a specific site where I only want to digipeat if the position is within 16 km of the point, or it is Messages,

Travis, yes, tried several times with nice approach, and of course that I have my email to beacons... Still nothing. I even offered him to give him for free complete digi with Rpi3 plus direwolf, all

I tried that with a gentleman running WIDE14,14 He was all but receptive. -Michael Sent: Monday, March 8, 2021 3:10 PM To: [email protected] Subject: Re: [direwolf] How to block specific call? Honest

Honest question. Not trying to be combative as I've learned something in this thread and am thankful for it. Have you reached out to the offending station to offer guidance/suggestions? As someone who

Or, you could use ! b/callsign1/callsign2/etc... to block individual stations.If you do not like digipeating weather data, use ! s/_ to block the weather station symbol.Section 9.6 of the User Guide

That is an easy one.After your digipeater definition add a filter like this: FILTER 0 0 ! d/callsign1/callsign2/etc... You can use this to block one, or more digipeaters.I use ! d/* to block all

Hi all, Direwolf works great for years now without any hickups. Eventually, there are some "experts" with a little or none awareness that they abuse radio traffic with their so called perfect

Yes, I know that but your subject line implies that you already know the problem is in the AX.25 stack and that might/probably not be the case. I am using native Linux AX.25 stack with Dire Wolf

Tnx for the reply's.? I will do some testing and post results. Trip - KT4WO

Hello Trip, Per the 2400-4800-PSK-for-APRS-Packet-Radio.pdf document, the "B" modem is the one you should use. Neither version of this modem is superior as it's just a difference in starting "phase".

Research needs to be done.

Hello Basil, The issue here is *connected* AX.25 session so your Winlink connections would be impacted. APRS would not be impacted since it's unconnected traffic and still works fine. The way the

That should have been 4800 bit modem.

I would like to add a 2nd port (on 440Mhz) at a local mtn. top node-- As I have users that use UZ7HO I would like to be compatible for them. I see there are (2) 2400 modes--A and B in UZ7HO. From the

I am NOT seeing your described symptom on various (7) Raspberry Pis running the Linux AX.25 stack with Winlink, APRS & Chattervox at 1200 & 9600 baud. My hardware is mainly RPi 4's and sound cards

Hello Everyone, I wanted to check with the larger community to see if others are experiencing system crashes when making connected AX.25 sessions. I have confirmed that this is NOT an RFI thing and