开云体育

Morning Nigel, Thanks for the reply.... but I'm still not gellint the requied location.... I changed the PBeacon statement to: PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=55^94

<rover.bob123@...> wrote: They are the degrees of your location, so you are saying that you are located at 42 degrees and about 56 minutes north.Which just happens to be the latitude

Thank you, Bob and all.? I have discovered that the current version? of Direwolf does indeed support PTT on the ICOM USB port. I changed the PTT line to PTT COM8 DTR I changed the USB Send setting

Morning from a cold, wet and windy Scotland.... I've built an iGate with Pi3+ and and Icom RX but I can't get my location on show on aprs.fi properly... I've tried Lat/ Long and UTM. My Pbeacon

Hello KG7ASX, Please review your Windows 11 Event logs around that timeframe of the Direwolf failure and see if there any specific USB or other issues. This still seems like an RFI or cabling issue

Thank you for the responses. Some encouraging progress! I completed the following steps: 1. I rebooted my machine 2. Changed the performance mode to "best performance" per Jerry's suggestion 3.

Jerry: Did you see this same issue with a Digirig device or just some other USB-based sound device? I've been thinking more about this issue as I hate to give up in defeat but one other

I had the same issue and I found that an ac line cable in the wall was next to the digirig. I moved it a foot away and been running fine. I can also trigger this by using the audio devices setting in

Yeah.. it sounds like you're doing the right thing here. Hmmm... I don't know what else to say. There is something clearly not right on your computer between the OS, the Digirig, and Direwolf. I

Responding to David Ranch: - "disconnect the Digirig, go into the Windows Device Manager too and REMOVE the CM108 driver." - I'm not sure I'm doing this correctly.? In Device Manager, under "Sound,

Eric/David/John/Greg Shot in the dark that may be worth a look. I don't know the Windows audio system at all, but the behaviour might also be explained by some (other) process grabbing the audio

Hello Eric, You mentioned that Direwolf would work if configured to use a different sound device. Because of that, I'm now thinking this could be a CM108 Windows driver issue. All I can think of

Thank you again for the responses; Responding to WB2OSZ: Question 1: ?Is the Digirig connected directly to the computer or is there a USB hub in between? - The Digirig Lite is connected directly to

"David Ranch via groups.io" <direwolf-groupsio@...> writes: I may be totally confused but have also been seeing problems about USB-C ports. It almost feels like USB-C ports are

Hello Eric, Hmmm... very perplexing and I'm thinking this is a USB subsystem issue. Are there any other USB ports on your computer you can try... ideally NOT with a USB-C connector? The world of

Thanks again for your response. My computer specs follow: Processor: 12th Gen Intel(R) Core(TM) i3-1215U ? 1.20 GHz Installed RAM: 32.0 GB (31.7 GB usable Operating System: Windows 11 Home I'm

The Windows audio code hasn't been touched for years so it is extremely unlikely that using version 1.8 would be any different. Rather than using audio device numbers, which can change, like

Hello Eric, Ok.. that's very odd as a lot of people have been successful with the digirig units. I see in your first post that you have a Digirig-Lite version but I can't imagine that would change

Hi Bob Yes the documentation is a little confusing as modem design has evolved. The current default of MODEM 300 creates 9 "B" modems roughly 30Hz apart. This handles HF stations that may be

Great.? Many thanks for the solution.? I have confirmed the settings in the IC-7300 manual for Remote.Now, I have one last issue.? When I execute Direwolf, I get this message I used the settings