Re: Heads up: New Raspberry Pi OS Bookworm 12.2 OS upgrade breaks Direwolf v1.7 GPIO pin access
Thanks for the heads up.
Just did an update on a Pi 4 with Bookworm and DW 1.8a and ran into this. At least I know why. Fortunately, I was just adding some blinky lights so it's not a show stopper today.
Dave
|
Heads up: New Raspberry Pi OS Bookworm 12.2 OS upgrade breaks Direwolf v1.7 GPIO pin access
Hello Everyone,
Just as a heads up but Raspberry Pi OS Bookworm received a major
update earlier this week which includes the
Linux 6.6.20 kernel and many other changes:
??
In this new OS update, the classic way of interfacing with GPIO
pins has now been DEPRECATED and this breaks Direwolf
v1.7 if you use GPIO pins to assert the PTT line to your radio,
light up an LED with the DCD signal, etc.? The solution was
already
committed to the Direwolf DEV branch back in November 2023 which
will eventually become Direwolf v1.8.? You can read up
about that and how to both recompile DIrewolf and reconfigure your
direwolf.conf file to use this new gpiod interface here:
??
I'm happy to report things are working for me with this new code
but I felt compelled to report this as this
very disruptive change coming in the middle of the Bookworm OS
lifecycle is going to create some pain for
some people.? I'm also updating my Raspberry Pi docs and automated
build script later to day to reflect this
change.
--David
KI6ZHD
|
Re: Direwolf as just a receiver
Hi Jon,
Thanks a lot for all advices. I will read them again carefully and
put them into practice and see what happens.
Best regards
On 3/11/24 18:29, Jon Dea (AA4JM)
wrote:
toggle quoted message
Show quoted text
John,
Building from Andrew's advice and towards verifying that your
igate is uploading data you could explore one or both methods
below.? Hope this helps & 73, Jon
1)
Have direwolf send igate statistics to the APRS-IS using
IBEACON.? This will show the numbers of packets, distinct
stations, etc are actually being heard over RF and uploaded to
the APRS-IS.
IBEACON sendto=IG delay=30 every=30
Since this data will probably scroll past in the terminal, you
can then observe your statistics in the raw packets at findu.com
or at the equivalent aprs.fi resource:
The IBEACON command usage and its output values are described in
the "Successful-APRS-IGate-Operation.pdf" document at WB2OSZ's
github site.
2)
a. Find the APRS-IS server that your instance of Direwolf is
connected to by noting the packets at the findu.com or aprs.fi
resource above.? The server name comes after qAC, and before the
: .? It can also be found in Direwolf's terminal but it will
likely scroll by without being noticed.? The servers can
automatically change depending on load and internet traffic
conditions.
b. Find your server in the left column on this status page:? ????
Click on your server in the left column.
c. The status page for your APRS-IS server will open, search
this page for your callsign-ssid.? There will be plenty of
details accumulating since your station connected to this
server.? Some of the details will be the number of packets that
your station has uploaded, how many minutes or seconds ago your
station last uploaded a packet (Last in), and an idea of how
many packets that you uploaded were duplicates of packets
already uploaded by another igate (Packets Rx).
|
Re: Trouble: DietPi Nano Pi Neo+Direwolf
Can you do basic audio playback or recording with
tools like aplay and arecord?
--David
KI6ZHD
On 03/13/2024 12:15 PM, Dr. Sergey
Ievkov wrote:
toggle quoted message
Show quoted text
Hello OMs!
Now I’m trying to launch a couple of audio modems on the basis
of a Nanopi single-board computer (I started with direwolf, but
still in terms of ardop), so that I can connect to them via
Wi-Fi from android applications via TCP\IP and work in FX.25 and
Winlink.
The Nano Pi has a built-in audio card with pins to which I
planned to attach an interface and a radio.
While I can’t start the sound, using the direwolf as an example,
I do the following and get an error:
root@DietPi:~# arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC
PCM Codec-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
root@DietPi:~# cat /proc/asound/cards
0 [Codec ? ? ? ? ?]: H3_Audio_Codec - H3 Audio Codec
H3 Audio Codec
root@DietPi:~# nano /root/direwolf.conf
ADEVICE plughw:0,0
CHANNEL 0
MODEM 1200
root@DietPi:~# direwolf
Dire Wolf DEVELOPMENT version 1.8 A (Mar ?9 2024)
Includes optional support for: ?cm108-ptt dns-sd
Dire Wolf requires only privileges available to ordinary users.
Running this as root is an unnecessary security risk.
…
Audio device for both receive and transmit: plughw:0,0 ?(channel
0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample
rate / 3, DTMF decoder enabled.
…
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
DNS-SD: Avahi: Failed to create Avahi client: Daemon not running
Audio input device 0 error code -5: Input/output error
…
Audio input device 0 error code -5: Input/output error
Terminating after audio input failure.
root@DietPi:~#
Any ideas? Maybe some package is missing?
I would appreciate any help with this project.
73!
|
Trouble: DietPi Nano Pi Neo+Direwolf
Hello OMs! Now I’m trying to launch a couple of audio modems on the basis of a Nanopi single-board computer (I started with direwolf, but still in terms of ardop), so that I can connect to them via Wi-Fi from android applications via TCP\IP and work in FX.25 and Winlink. The Nano Pi has a built-in audio card with pins to which I planned to attach an interface and a radio. While I can’t start the sound, using the direwolf as an example, I do the following and get an error: root@DietPi:~# arecord -l **** List of CAPTURE Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0] Subdevices: 1/1 Subdevice #0: subdevice #0 root@DietPi:~# cat /proc/asound/cards 0 [Codec ? ? ? ? ?]: H3_Audio_Codec - H3 Audio Codec H3 Audio Codec root@DietPi:~# nano /root/direwolf.conf ADEVICE plughw:0,0 CHANNEL 0 MODEM 1200 root@DietPi:~# direwolf Dire Wolf DEVELOPMENT version 1.8 A (Mar ?9 2024) Includes optional support for: ?cm108-ptt dns-sd Dire Wolf requires only privileges available to ordinary users. Running this as root is an unnecessary security risk. … Audio device for both receive and transmit: plughw:0,0 ?(channel 0) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3, DTMF decoder enabled. … Ready to accept AGW client application 0 on port 8000 ... Ready to accept KISS TCP client application 0 on port 8001 ... DNS-SD: Avahi: Failed to create Avahi client: Daemon not running Audio input device 0 error code -5: Input/output error … Audio input device 0 error code -5: Input/output error Terminating after audio input failure. root@DietPi:~# Any ideas? Maybe some package is missing? I would appreciate any help with this project. 73!
|
Re: Direwolf as just a receiver
John,
Building from Andrew's advice and towards verifying that your igate is uploading data you could explore one or both methods below.? Hope this helps & 73, Jon
1)
Have direwolf send igate statistics to the APRS-IS using IBEACON.? This will show the numbers of packets, distinct stations, etc are actually being heard over RF and uploaded to the APRS-IS.
IBEACON sendto=IG delay=30 every=30
Since this data will probably scroll past in the terminal, you can then observe your statistics in the raw packets at findu.com or at the equivalent aprs.fi resource:
http://www.findu.com/cgi-bin/raw.cgi?call=EB2BRA-10&time=1&start=3
The IBEACON command usage and its output values are described in the "Successful-APRS-IGate-Operation.pdf" document at WB2OSZ's github site.
2)
a. Find the APRS-IS server that your instance of Direwolf is connected to by noting the packets at the findu.com or aprs.fi resource above.? The server name comes after qAC, and before the : .? It can also be found in Direwolf's terminal but it will likely scroll by without being noticed.? The servers can automatically change depending on load and internet traffic conditions.
b. Find your server in the left column on this status page:? ???? Click on your server in the left column.
c. The status page for your APRS-IS server will open, search this page for your callsign-ssid.? There will be plenty of details accumulating since your station connected to this server.? Some of the details will be the number of packets that your station has uploaded, how many minutes or seconds ago your station last uploaded a packet (Last in), and an idea of how many packets that you uploaded were duplicates of packets already uploaded by another igate (Packets Rx).
|
Re: Direwolf as just a receiver
Notice the digipeat path on the packets you are receiving by RF; the digipeat alias has already been consumed. This indicates you are not receiving the original Object transmissions from ED2ZAD-3, but a digipeated copy. So there was probably an I-gate that was close enough to ED2ZAD-3 to hear the original transmission and get it to the APRS-IS backbone before your station heard the digipeat of the packet. Since the APRS-IS backbone is deliberately designed to suppress duplicates, you will never be the first I-gate to relay those particular stations to the backbone. However, you did NOT configure your station to be a receive-only I-gate, which is why you are seeing the [ig>tx] messages. So you are I-gating some traffic (which is why you are being given responses to send to that station) but you are not the first I-gater. I don't see a IGTXVIA directive in your configuration, but it might be implied because you did specify IGTXLIMIT. If you want to actually see traffic I-gated by your station, it has to be traffic that no other I-gate can hear (so no one can beat you to the backbone with the packets). For example, a low-power HT beaconing right next to your I-gate, so no one else could receive it. Hope this helps. Andrew, KA2DDO ________________________________________ From: [email protected] < [email protected]> on behalf of John <eb2bra@...> Sent: Saturday, March 9, 2024 5:27 PM To: [email protected]Subject: [direwolf] Direwolf as just a receiver Hi Everybody, I have started up a new Direwolf iGate, but my intention is that the iGate works a receiver, and no as transmiter. The issue is that my iGate show all the time this messages: [ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE:;R6-C4FM *092115z4312.41N/00216.95Wr145.750MHz T797 -060 FM / C4FM R.C zaria Digipeater WIDE1 (probably EA2TZ-3) audio level = 58(14/8) __|||||__ [0.4] ED2ZAD-3>APMI06,EA2TZ-3,WIDE1*:;ED2YAT *092115z4317.38N/00302.03Wr438.900MHz T123 -760 FM ASRABI Object, "ED2YAT", Repeater, SQ3PLX N 43 17.3800, W 003 02.0300, 438.900 MHz, -7600k, PL 123.0 FM ASRABI [ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE:;RF85_FM *092115z4318.53N/00138.15Wr51.850MHz T000 -060 FM R.C zaria Digipeater WIDE1 (probably EA2TZ-3) audio level = 55(14/8) __|||____ [0.3] ED2ZAD-3>APMI06,EA2TZ-3,WIDE1*:;RF85_FM *092115z4318.53N/00138.15Wr51.850MHz T000 -060 FM R.C zaria Object, "RF85_FM", Repeater, SQ3PLX N 43 18.5300, W 001 38.1500 51.850MHz T000 -060 FM R.C zaria [ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :PARM.Vin,Rx1h,Dg1h,Eff1h,Temp,O1,O2,O3,O4,I1,I2,I3,I4 [ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :UNIT.Volt,Pkt,Pkt,Pcnt,C,On,On,On,On,Hi,Hi,Hi,Hi [ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :EQNS.0,0.075,0,0,10,0,0,10,0,0,1,0,0,0.5,-64 [ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :BITS.11111111,Telemetria but no RX>IG message. If I go to the aprs page I see that there is no message from my iGate to the network. This is my conf file. ADEVICE plughw:1,0 CHANNEL 0 MYCALL EB2BRA-10 MODEM 1200 AGWPORT 8000 KISSPORT 8001 PBEACON delay=1 every=30 overlay=S symbol="digi" lat=43^16.19N long=002^11.14W power=5 height=2 gain=1 comment="APRS VHF en pruebas" via=WIDE1-1 IGSERVER euro.aprs2.net IGLOGIN EB2BRA-10 22179 PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=43^16.19N long=002^11.14W comment="APRS VHF en pruebas" IGTXLIMIT 6 10 What is wrong ? Thank you in advance.
|
Direwolf as just a receiver
Hi Everybody,
I have started up a new Direwolf iGate, but my intention is that the iGate works a receiver, and no as transmiter.
The issue is that my iGate show all the time this messages:
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE:;R6-C4FM? *092115z4312.41N/00216.95Wr145.750MHz T797 -060 FM / C4FM R.C zaria
Digipeater WIDE1 (probably EA2TZ-3) audio level = 58(14/8)??? __|||||__
[0.4] ED2ZAD-3>APMI06,EA2TZ-3,WIDE1*:;ED2YAT?? *092115z4317.38N/00302.03Wr438.900MHz T123 -760? FM?? ASRABI
Object, "ED2YAT", Repeater, SQ3PLX http://microsat.com.pl/
N 43 17.3800, W 003 02.0300, 438.900 MHz, -7600k, PL 123.0
? FM?? ASRABI
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE:;RF85_FM? *092115z4318.53N/00138.15Wr51.850MHz? T000 -060 FM? R.C zaria
Digipeater WIDE1 (probably EA2TZ-3) audio level = 55(14/8)??? __|||____
[0.3] ED2ZAD-3>APMI06,EA2TZ-3,WIDE1*:;RF85_FM? *092115z4318.53N/00138.15Wr51.850MHz? T000 -060 FM? R.C zaria
Object, "RF85_FM", Repeater, SQ3PLX http://microsat.com.pl/
N 43 18.5300, W 001 38.1500
51.850MHz? T000 -060 FM? R.C zaria
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :PARM.Vin,Rx1h,Dg1h,Eff1h,Temp,O1,O2,O3,O4,I1,I2,I3,I4
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :UNIT.Volt,Pkt,Pkt,Pcnt,C,On,On,On,On,Hi,Hi,Hi,Hi
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :EQNS.0,0.075,0,0,10,0,0,10,0,0,1,0,0,0.5,-64
[ig>tx] ED2ZAD-3>APMI06,TCPIP*,qAC,T2FRANCE::ED2ZAD-3 :BITS.11111111,Telemetria
but no RX>IG message.
If I go to the aprs page I see that there is no message from my iGate to the network.
This is my conf file.
ADEVICE? plughw:1,0
CHANNEL 0
MYCALL EB2BRA-10
MODEM 1200
AGWPORT 8000
KISSPORT 8001
PBEACON delay=1? every=30 overlay=S symbol="digi" lat=43^16.19N long=002^11.14W power=5 height=2 gain=1 comment="APRS VHF en pruebas" via=WIDE1-1
IGSERVER euro.aprs2.net
IGLOGIN EB2BRA-10 22179
PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=43^16.19N long=002^11.14W comment="APRS VHF en pruebas"
IGTXLIMIT 6 10
What is wrong ?
Thank you in advance.
|
Re: CM108 PTT randomly interferes with the mouse
*FACE PALM* It turned out to be the 10k resistor between COS and ground!
David's comment about the volume pin being miswired turned out to be the key to my discovery.? I saw that all of the cm108 ptt mods that include COS, have COS connected to pin48 on the cm108 chip (some with diode, some without). Pin48 happens to be defined as "volume down" on the cm108 datasheet. That clue led me to compare the COS circuit from several different mod schematics. I noticed most of them did not include that 10k resistor between cos and gnd. Unfortunately I followed one of the guides that did include the resistor. Not sure how/why this worked for the author of the article? I assume there may be some additional components on the COS line that aren't shown which make it work for the author (besides ground, which was also omitted from the guide).
Anyhow, after I removed that 10k resistor the volume dropping after the first tx is gone. I am 99.9% certain from all of this testing/research that the problem is now permanently fixed. Of course I will report back if not, but I think it's a safe time for me to kill this confusing thread. Thanks to all who gave me feedback. Also David, I think your comment about the vol pin is the key that led to the fix... so if you want that rpi ptt just let me know. It works 100% I swear!
|
Re: Packet filtering question
Noah - the filter in WB2OSZ's post works for me, but you can also use data types and symbols to filter by, as Jon pointed out.
|
Re: CM108 PTT randomly interferes with the mouse
I’ve been running a Pi5 with direwolf for a little over a month now. That’s running multiple direwolf instances on both VHF and HF without issues. Note this setup was running on a Pi4 for years and a Pi3 before that. ?
A couple notes. Initially with the Pi5 I was seeing stalls in my ssh terminals (I don’t have a GUI on this Pi). That was due to an insufficient power supply. Once I moved to a power supply sufficient for the Pi5 that went away.?
Also, not on a pi, but on a PC. We have a gaming keyboard that absolutely cannot handle RFI. I had an APRS digipeater sitting in the same room as my kid’s gaming PC and every time the digi would transmit the keyboard would stop working for a few seconds. I ended up moving that digi to another room in the house and that keyboard has been happy since.
For what it’s worth.?
-Brent WG0A
|
Hi Chris,
I don't know how others have their VARA-Direwolf set up, but on my system VARA HF and SoundModem both share the same soundcard with no issues with audio in/out.?
No issues here, either, using QtSoundModem and VARA HF on a Wndows 10 desktop. I'm using a Signalink, so there's no issue with PTT sharing. I understand it's BPQ's interlock feature that prevents transmitting on multiple ports at the same time.
It seems the same setup should work with Direwolf, except I'm not sure about DW running packet and IL2P at the same time on different center frequencies.
73, Lee K5DAT?
|
Re: Packet filtering question
Yeah I really need to do this for one local in my area that has his trailer set to broadcast every 5min and isn't comfortable changing his Tiny track setting's/ letting me change them
I want to either Not broadcast over RF maybe Internet as well or I read we can do a rule changing the 2-1 to stop the rebroadcast.?
|
Re: CM108 PTT randomly interferes with the mouse
I wanted to mention that cm108 mod site does omit ground... the author does in fact connect ground to his radio gnd as shown in another photo of the repeater build. In my case I did add a wire to radio ground as well.
Also David, WRT your last sentence... that is exactly the hopeful statement I was looking for, that others are operating pi5 without deal breaking issues. I figured it should work eventually... just need to sort out the gremlins at play.
|
Re: CM108 PTT randomly interferes with the mouse
Hello David, it seems your post didn't refresh in my browser before I posted. Thanks for taking the time to read this lengthy and starting to get confusing thread. I quickly realized that you are right, pi5 will need bookworm, period. I was using Xorg, because wayland is broken. WRT the potential miswiring of the cm108... I definitely have the correct pin (pin 13) on the CM108 wired to PTT. The PTT does work fine otherwise. Also, the slider that's dropping is actually the one for my ic7300, not the cm108. For reference, here's the mod I used:??As you can see the photos, schem, and text are very clear, no possible confusion with pinouts I think. I copied the mod exactly, with the addition of a doide on COS (which isn't used here anyways). I agree it could still be RFI I suppose... and that's an awesome idea for a test. Unfortunately I have already verified that my stupid uv5r will tx out of range. It's not just lighting up, but actually putting out RF into my attenuators and tinySA when I tested on a NOAA freq. What I can do is put my 100W dummy load on for a test... but that doesn't guarantee no rfi. For VNC client, I'm using realvnc because I'm accessing from my iphone, ios tablet, and a win11 pc. I read some good stuff about like tiger and other clients, but the ios stuff doesn't offer it. Any other ideas for clients? Also, yes the vnc session continues to operate... keyboard still works through vnc. I can also ssh in when it happens, and htop shows normal loading for the apps at play (~13% or so). I haven't thought to look at journalctl yet though. What might this show?
|
Re: CM108 PTT randomly interferes with the mouse
Hello Kevin,
You might be able to get Bullseye going on an Rpi5 but the reality
is that Bullseye won't be getting kernel updates for much longer
as they always switch to the new OS shortly after a new OS
release.? I always recommend to use the newest Raspberry Pi OS
version available to maximize it's support lifetime.? No doubt,
Bookworm has a lot of changes in it which makes it frustrating to
adapt to but I haven't heard of any blockers making people unable
to adopt it.
--David
KI6ZHD
On 03/07/2024 05:02 PM, KO6BLZ wrote:
toggle quoted message
Show quoted text
Not sure exactly what happened but shortly after the
fresh reinstall of bookworm 64, after getting things
compiled/installed and going headless... the desktop resolution
got borked in a weird way. While doing this work a buddy informed
me that I can actually use bullseye 32 by first installing on a
pi4 then updating. After updates I guess the kernel becomes pi5
compatible, and the sd card will now boot with pi5. I'm trying
this now.
|
Re: CM108 PTT randomly interferes with the mouse
Not sure exactly what happened but shortly after the fresh reinstall of bookworm 64, after getting things compiled/installed and going headless... the desktop resolution got borked in a weird way. While doing this work a buddy informed me that I can actually use bullseye 32 by first installing on a pi4 then updating. After updates I guess the kernel becomes pi5 compatible, and the sd card will now boot with pi5. I'm trying this now.
|
Re: CM108 PTT randomly interferes with the mouse
Hello Kevin,
I reviewed this long thread and here are a few thoughts:
? - The Raspberry Pi 5 *requires* Raspberry Pi Bookworm (or
similar generation OSes) for the required firmware, HW support,
etc.? Going to anything older will probably never work right.
? - For your crashing VNC issues, are you using Wayland or Xorg??
You might try switching back to Xorg as a test:?
? - For your volume slider issue, this sounds like the common
symptom of miswiring your CM108 device.? Are you using a Digirig
device??
.?
Even if you aren't, Google around and you will find many other
reports about this where you are probably connecting your radio's
PTT to the CM108 VOLUME DOWN GPIO pin by accident.
? - For the mouse in vnc not responding" issue, I know you don't
feel this is RFI related but it sure seems like it.? Please note
that when you compare to other "programs" not having this issue,
remember those radios probably aren't transmitting on the same
frequencies / bands that Direwolf would be.? Anyway, some more
questions / thoughts:
?? a) Beyond of putting your radio to low RF power (which can also
still create RFI), try putting your radio in VFO mode and to a
frequency the radio will not transmit on.? With this, you should
be able to test but there will be ZERO RF being sent which should
help isolate your issue more
?? b) What VNC client are you using??? Are you sure the VNC
session is still operating?? Sounds like VNC keyboard still works
since you can still reboot the Pi.? If you disconnect and
re-connect a VNC session, is the mouse still frozen?
?? c) Can you SSH into the Rpi5 once this VNC issue comes up??
What is the load on the Rpi5?? Anything show up in the logs about
this (sudo journalctl)?
--David
KI6ZHD
On 03/07/2024 09:33 AM, KO6BLZ wrote:
toggle quoted message
Show quoted text
Well I was just reminded why bullseye on pi5 didn't go
well... it didn't go at all. Now I recall correctly it was
actually bookworm 32bit that didn't go well. The rpi imager app
does not even offer bullseye for pi5. So I'm guessing it would be
a bit of a battle to get that installed. I will just try to
procede again with bw64, but this time I will only do things that
I know had to be done to get things working, and no other side
experiments. This hosed install, I did mess with pulseaudio and a
few other things that could have caused problems. I'll more
carefully document every single step I do in this process, and
report back with the results.
|
Re: Packet filtering question
Benson, one could also filter by data type and/or station symbol depending on the need (in case you hadn't considered).
by station symbol (WEATHER Station):
FILTER 0 0 ! s:/_
by data type (Weather Report):
FILTER 0 0 ! t:w
everything mentioned here & by John, strung together with "&" should you need to use the budlist, type, and symbol filters all at once:
FILTER? 0? 0 ! b/call-ssid & ! s:/_ & ! t:w
I have frequent aircraft activity and have been in areas before w/ routine balloons, so I filter for those symbols too (! s:/' & ! s:/0).? The filter feature is pretty powerful and flexible, just takes a little experimentation & reading to see everything possible (thanks John!).
Jon
|
Re: CM108 PTT randomly interferes with the mouse
Well I was just reminded why bullseye on pi5 didn't go well... it didn't go at all. Now I recall correctly it was actually bookworm 32bit that didn't go well. The rpi imager app does not even offer bullseye for pi5. So I'm guessing it would be a bit of a battle to get that installed. I will just try to procede again with bw64, but this time I will only do things that I know had to be done to get things working, and no other side experiments. This hosed install, I did mess with pulseaudio and a few other things that could have caused problems. I'll more carefully document every single step I do in this process, and report back with the results.
|
John
Benson
Brent WG0A
Noah