开云体育

You can buy the Fe-Pi designed HAT from the new design owners below: https://wb7fhc.com/about-the-fe-pi.html --David KI6ZHD

Direwolf is really very forgiving on RX levels but the general guidance is that it's average receive level is around 50. I can't comment on how the alsamixer setting might look within in a zoomed in

Ok.. that takes the iffy Raspberry Pi USB stack out of the running. When no PTT is configured, it's assume you're using VOX or using a sound device like a Signalink that asserts PTT for you. Per the

The error came on a older x86_64 KUbuntu desktp homebrew computer, with the motherboard sound card, and no PTT setting (VOX).? Direwolf has "no clue' how the PTT is being handled. In fact, the

Hello Alejandro, I would recommend to start with confirming that your HT can hear your Direwolf station (XE1GNU-1) beacons. Per your configuration, those beacons should be sent every 5 minutes. Is

Hello Rob, If you google the following term: direwolf "Transmit timing error: PTT is on" "mSec too long" You'll see a few hits and one one of these talks about the issue being known on non-Raspberry

I used the config file you proposed and it appears to be behaving now. I am getting an error 1.7-dev-A that is????? Transmit timing error: PTT is on 104 mSec too long.? I am using VOX (no PTT

I bumped into this when trying to run two separate instances of direwolf. One for VHF and one for HF. In that case I would see a collision on port 8001. After digging around a bit I found that the way

Hello Roger, Ok.. and btw, I've created a Github issue to track this issue for you: https://github.com/wb2osz/direwolf/issues/342 --David KI6ZHD

In addition, I connected both TCP ports using APRSIS32 [0L] KB8RCO-2>APWW11,WIDE1-1,WIDE2-1:@173559h4209.35N/08346.30W1 EXPERIMENTATION[1L] KB8RCO-2>APWW11,WIDE1-1,WIDE2-1:@173559h4209.35N/08346.30W1

I just compiled V1.7 and tried to change the TCP KISS port.As stated, the 'default' port does not change, however when specifying a port, it looked like this: Dire Wolf DEVELOPMENT version 1.7 A

Thanks, David I did revert to 1.6 stable version and all is well.? Just thought I'd give the new beta a spin- Appreciate your reply and confirmation. Roger, N1XP

Hi direwolf community, I'd like to introduce my open source project, TNC exporter ( https://github.com/rouyng/tncexporter ) , which provides a legible, information-dense and customizable interface to

Hello, I compiled on a raspberry pi zero W direwolf 1.6 as indicated in the manual, my intention is to configure an aprs repeter (digipeater). The problem is that when I turn on a handheld radio with

This bug was supposedly fixed in direwolf 1.6 by adding 250ms before gpio initialization. I'm still observing it on a raspberry pi zero.? Does anyone have a workaround or defensive code/patch to make

Hello Roger, I just tested it and I see what you're seeing. Ultimately, this seems to be a bug with v1.7 so unless you specifically need the BETA v1.7 release, please use the released v1.6 version. --

The numbering system is typically done through libraries.I would assumevthat since you are usjng something other than a Pi, you are compiling Direwolf on that device.? This could/should have a

Thanks Robert, The information you quote is specific to the RPI and I want to use the "GPIO" config command on a Odroid-C4 (another SBC; see https://www.hardkernel.com/shop/odroid-c4/ and

Ian, I use a GPIO pin to disable the transmitter. My Igates are at VHF contest sites, and the APRS frequency is close enough to the frequencies used for contesting to interfere with contesting. So I

Found more information in the manual at: https://raw.githubusercontent.com/wb2osz/direwolf/master/doc/User-Guide.pdfSection 9.2.12 (Page 78 & 79) ??? TXINH GPIO 17? TXINH GPIO -17As with PTT,