开云体育

Hi All, On my second Direwolf installation.? Previous was in a tracker. Loved it.?? This time I'm working on an iGate to potentially be used in APRS tactical messaging applications.? In my use

Hey Thomas, I know what you're asking and the best I can tell, this change shouldn't impact the HIDRAW functionality. This change specifically impacts just the INPUT GPIO going through the libinput

Hi Greg, I believe the practice of using Volume Up/Down inputs on soundcard interfaces started with Allstar looking for a way to detect CTCSS and CoS signals from the radio. I wouldn't call it either

Personally, I hate applying a software fix to a hardware problem, or vice versa. Does anyone know why they would connect the Volume Down pin to something associated with Squelch in the fist place? I

Hi David, If you tell the kernel to ignore the CM108 as a human input device (HID), is Direwolf still able to use the CM108 GPIO pins for PTT ? It's okay if you don't know, I can try it here when I

I've been thinking about this issue and knew there had to be a way to have Linux IGNORE the "volume down" GPIO signal on the CM108 chip via SOFTWARE. Doing a lot of research, I've found the following

I have just confirmed that if you set the SA818 squelch to zero and do not use CTCSS, the SQ (squelch) output from the SA818 (pin1)? which is connected via D1 to the VOLDN input (pin 48) of the CM108

APRS digipeaters and connected mode packet radio digipeaters behave differently. There are two different configuration commands for the two types of digipeaters. 73, John WB2OSZ

Thank you John! I was stuck on trying to get DIGIPEAT to work. Never made it down that far in the user guide having used direwolf for APRS up until this point. 73, VE3ECI Greg

This is explained in the direwolf User Guide, section 10.3.1, "Enable Connected Mode Digipeater. 73, John WB2OSZ

I'd like to configure direwolf to digi repeat like a packet repeater interfaced to a transceiver tuned to a packet frequency. Can direwolf be configured to do this? If so, please point me in the that

Starting over fixed it. I don't know what I missed the first time, but it is running perfectly now. I should have tried that a couple days ago... Arnold, KQ6DI

I have a Pi 3A, 3B, 3B+ all running Bookworm and Direwolf 1.8, and all work fine. It's only this attempt at another 3B giving me issues, so something odd happened. I think my best option is to

Just to follow up: I have confirmed that the SHARI board indeed has COS output signal from the SAS18 radio tied to the "volume down" pin 48 on the CM108 chip: /g/SHARI/message/975 If

hello Grayson, Ok.. that pretty much proves that your SHARI board has the COS signal tied to the "volume down" button. That's bad and must be fixed as you want to run your radio with open squelch for

Turning on the squelch did fix this issue now the volume stays put, now I'm kind of having a different issue. My second identical setup still doesn't receive anything but its volume gets turned down

It sounds like an RFI problem I had once. The transmit RF is getting into the sound card, making it think that the "volume down" button was being pressed and held down. Key the transmitter and you can

Try turning up the squelch on your radio unit the receiver shuts down. I bet the "volume down" issue will stop. Utimately, I would imagine the SHARI board is wired the same way as the DINAH board so

Even with direwolf stopped I am still unable to increase the volume. I did notice that the USB chip is actually a CM108B that has a different pinout from the CM108, while the volume down is still pin

A more specific thread on this DINAH issue which is probably wired similar to your Pi HAT: /g/DINAH/topic/sqelch_open_attached_to/91808019 --David KI6ZHD