开云体育

If you look through the direwolf.conf file (example file) you will find examples of how to assign functions to pins.In each case, there is an example for a serial port and one for GPIO.Examples:

Evening all, I've been reading through the direwolf RPI doco, specifically interested in the use of the GPIO pins for PTT, TX INHIBIT and DCD. I'm planning on using a different SBC (Odroid-C4) which

Sleeve, Shield, regardless. The way the mechanical attachment of a shielded (sleeved, if you will) cable to the connector nearly demands (and certainly benefits from) the shield being placed in the

TRRS is not Tip-Ring-Ring-SHIELD, but Tip-Ring-Ring-SLEEVE. On most devices, the Sleeve is the mic input.? This allows for it to be compatible between headsets with a mic and without a mic.? Those

I hope so, too. It may be a while; the problem appears to have "gone away" since rebuilding the interface cable, but I've saved the instructions in a text file on the Pi's desktop in case it "comes

Just restore. You don't even need to reboot unless something is messed up with the system. I'd like to hear your results! Hopefully it works out!

New install of Direwolf dev1.7 does not allow changing KISSPORT? FROM 8001. My CONF file, direwolf.conf: ADEVICE plughw:1,0 ACHANNELS 1 CHANNEL 0 MYCALL N1XP MODEM 1200 AGWPORT 8003 KISSPORT 8004

Much appreciated. No rush as I'm a few months off implementing this feature. Thank you for your assistance.

I implemented this on a simple connected packet TNC hat I made but with no real plans to use it. I think it held responses in a a que and then let them go once TX INHIBIT was cleared. However, I don't

i discover that in a cbeacon whit dest=id work for that. thanks

Ah! Cool. Saved. So, when this happens again, simply do the restore and reboot? It will be interesting to compare the values in the backup file, to see if my theory about an illegal volume value is

Hi all, I'm hoping someone can explain how direwolf reacts to the TX inhibit input. When it is active the function clear (i.e no transmissions can occur) but I can't find anything in the manual that

In terminal, to save the current audio file settings as a file use.. "sudo alsactl --file /home/pi/alsa.backup store" To restore... "sudo alsactl --file /home/pi/alsa.backup restore" If you don't need

Hi Michael, and anyone else who might be following this... I've rebuilt the cable that goes between the audio dongle and the radio for better shielding, which I should have done in any event. Very

aprs.fi can show the comment, lastt status and last beacon. The text of last beacon... how set in direwolf? i try differents solutions in the beaconing lines, but i can?t set this field. the status i

Some caps may help. But if it's that sensitive, it may be better to try a different sound card chipset. I'd try the CM108. They seem far less problematic with RF.

Michael - NA7Q wrote: Yeah, this is looking more and more like the issue. The wiring is simply a pin-to-pin connection, speaker to mike, and mike to speaker. Common ground for everything. It's

Interesting. I don't know what chipset is in that dongle. Many chipsets have volume switches that are built into the audio lines. When grounded, they trigger the switch to go down or up. It sounds

Hello Robert and al. Yes, more than I needed to get going. Problem has been solved - hopefully - but this is what I did. Step 1: on PC1 make Direwolf beacon every 5 seconds. Make a line connection

Michael - NA7Q wrote: Greg, I have had the same issue, only rebooting always fixed it. However I have had A LOT more issues with Direwolf, and sound cards in general with Buster. I'd suggest going