开云体育

Problem has been resolved. I now get a solid 3D fix. The solution: update to the latest revision of GPSD. Revision 3.23.1 As background, I have a Garmin GLO 2 which will support up to four users. A

Tnks Brent, I'm going to test your proposal. 73's Serge ON5MZ

Please note that Fred's recommended StackExchange post comes from March 2018 when maybe PulseAudio was bad news and thus people recommended to remove it. We are now into late 2021 and I would say that

Hi guys, My setup : RASPI 1b raspbian lite no screen ssh ON USB soundcard (C-Media) It used to work with ADEVICE plughw:1,0 very well but one day, during a demo. (of course), I have to change to

This has been helpful to me. I can’t claim to understand it but at least at the moment I am trouble free.

Hi Serge, I have a Pi 3 with two USB sound card interfaces. I see this behavior regularly. The numbering of the interface depends on the ordering of device discovery during boot. Fortunately, there is

The answer may depend on the OS. Are you running on a Mac, Pi, PC, ... ? Robert Giuliano KB8RCO

Does this occur when you are perhaps adding other sound devices such as perhaps an HDMI sound enabled monitor? -- 73, AB1PH Don Rolph

Hi everyone, probably an already solved issue (I hope !!) Everything works well for me, but sometimes I have to correct the direwolf.conf to change ADEVICE plughw:1.0 to 2.0 vice and versa... How to

GPS has been running for at least a day. Define "GPS has been running for at least a day". By default, your GPS puck won't be activated by gpsd and start listening for GPS details until it has a

Hello Fred, Define "GPS has been running for at least a day". By default, your GPS puck won't be activated by gpsd and start listening for GPS details until it has a listening client like direwolf,

As a quick addendum, The Garmin GLO2 supports up to four connected devices. I finally got my Windows PC to connect. I connected to COM4 and within the Device manager I set the Baud to 56700. Using the

Hello David, Hello Fred, I finally connected a BT GPS and am working on adding GPS positioning to Direwolf. One thought here.. is your Raspberry Pi with it's built-in Bluetooth using the hardware UART

Hi Fred, the lock mode is reported in the $GPGSA NMEA sentence that is not shown in your gpsmon output. Check for the generation of that sentence. Fabrizio fmhillhouse@...> ha scritto:

Hi Fred, the lock fmhillhouse@...> ha scritto:

Hello Fred, One thought here.. is your Raspberry Pi with it's built-in Bluetooth using the hardware UART or the software UART (aka MiniUART)? You want to be using the *hardware* one as it's more

GPS has been running for at least a day. What constitutes a “very good” lock? As it is, I don’t believe I will ever see packet data. This is what I get when running gpsmon. Any clues there?

This is actually expected behavior until one has a very good gps lock. Until then it switches between 2D and 3D fixes and every time it shifts, Direwolf reports it. It is not a failure.

I should have added, I have “GPSD” in direwolf.conf. Thanks again! Fred N7FMH Sent: Wednesday, September 29, 2021 10:48 AM To: [email protected] Subject: [direwolf] Repeating "GPSD: Location fix

Greetings, I finally connected a BT GPS and am working on adding GPS positioning to Direwolf. I see a continuous stream of: GPSD: Location fix is now 3D GPSD: Location fix is now 2D GPSD: Location fix