Keyboard Shortcuts
Likes
- KM4ACK-Pi
- Messages
Search
Re: No GPS Tool installed on KM4ACK Build-a-Pi?
¿ªÔÆÌåÓýYes, there are prerequisites for gpsd and the tools. K0NEO Sent via the Samsung Galaxy S9, an AT&T 5G Evolution capable smartphone -------- Original message -------- From: "Dennis Blanchard via groups.io" <k1ypp@...> Date: 3/11/24 15:52 (GMT-06:00) Subject: [KM4ACK-Pi] No GPS Tool installed on KM4ACK Build-a-Pi? Here is my current install info: dennis@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
de Dennis, K1YPP |
No GPS Tool installed on KM4ACK Build-a-Pi?
Every video that I see KM4ACK shows going to the "Accessories" menu and selecting the "GPS Tool." For whatever reason my install doesn't have that. Did I miss something when doing the install? I added the little pink GPS dongle he shows but can't figure out how to get it installed.
Here is my current install info: dennis@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
de Dennis, K1YPP |
vara does not install after executing bash vara-on-debian
¿ªÔÆÌåÓýHi ? Vara-on-debian script executes however it seems wine is not installed.? I am not seeing the Vara Setup window . ?Below is the link used to download the Vara-on-debian script. One thing I noticed is that I¡¯m being prompted to ¡°replace VARA FM setup (Run as Administrator).exe? [y]es, [n]o, [A]ll, [N]one, [r]ename: ¡° ?, the same for VARA HF. Did not run across this in the instructional video. ? ¡®¡¯ ? Thanks ? Justin KB2ZVD ? From: [email protected] <[email protected]> On Behalf Of Kelly K7MHI via groups.io
Sent: Friday, March 8, 2024 10:35 AM To: [email protected] Subject: Re: [KM4ACK-Pi] cmake problem solved - new problem with HAMLIB ? What is your rig control are you wanting to use flrig? it appears your trying to connect via network to something which isn¡¯t answering. Flrig is now port 12345 fyi?
|
Re: cmake problem solved - new problem with HAMLIB
¿ªÔÆÌåÓýProblem fixed , thanks? for the help.? Ran rigctld -m 4 before executing direwolf -p.?? ? Justin KB2ZVD ? From: [email protected] <[email protected]> On Behalf Of Kelly K7MHI via groups.io
Sent: Friday, March 8, 2024 10:35 AM To: [email protected] Subject: Re: [KM4ACK-Pi] cmake problem solved - new problem with HAMLIB ? What is your rig control are you wanting to use flrig? it appears your trying to connect via network to something which isn¡¯t answering. Flrig is now port 12345 fyi?
|
OK Kelly, I ran the three commands that you suggested.
(I ran $ sudo apt-get remove libhamlib* without the -y because I wanted to see the removal list.) This command suggested that I follow-up with running?sudo apt autoremove , which I did. The console results are shown below.?How do you recommend that I install a fresh hamlib ? And before I reinstall, do I need to run apt-mark unhold for the packages I previously held? Thanks again, Rob ? KK6JNI ====== rob@pi41:~ $ sudo apt-mark hold libhamlib* [sudo] password for rob:? libhamlib-utils set on hold. libhamlib4 set on hold. libhamlib++-dev set on hold. libhamlib++4 set on hold. libhamlib-dev set on hold. libhamlib-doc set on hold. libhamlib-perl set on hold. libhamlib2-perl set on hold. libhamlib2-tcl set on hold. ====== rob@pi41:~ $ ?sudo apt-mark hold python3-hamlib python3-hamlib set on hold. ====== rob@pi41:~ $ sudo apt-get remove libhamlib* Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'libhamlib2-tcl' for glob 'libhamlib*' Note, selecting 'libhamlib-perl' for glob 'libhamlib*' Note, selecting 'libhamlib++-dev' for glob 'libhamlib*' Note, selecting 'libhamlib4' for glob 'libhamlib*' Note, selecting 'libhamlib++4' for glob 'libhamlib*' Note, selecting 'libhamlib-utils' for glob 'libhamlib*' Note, selecting 'libhamlib-dev' for glob 'libhamlib*' Note, selecting 'libhamlib-doc' for glob 'libhamlib*' Note, selecting 'libhamlib2-perl' for glob 'libhamlib*' Package 'libhamlib++-dev' is not installed, so not removed Package 'libhamlib++4' is not installed, so not removed Package 'libhamlib-dev' is not installed, so not removed Package 'libhamlib-doc' is not installed, so not removed Package 'libhamlib-perl' is not installed, so not removed Package 'libhamlib-utils' is not installed, so not removed Package 'libhamlib2-perl' is not installed, so not removed Package 'libhamlib2-tcl' is not installed, so not removed Package 'libhamlib4' is not installed, so not removed The following packages were automatically installed and are no longer required: ?libfltk1.1 librtaudio6 libvpx-dev raspinfo Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ====== rob@pi41:~ $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: ?libfltk1.1 librtaudio6 libvpx-dev raspinfo 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 2,887 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 282982 files and directories currently installed.) Removing libfltk1.1:armhf (1.1.10-29) ... Removing librtaudio6:armhf (5.1.0~ds1-1) ... Removing libvpx-dev:armhf (1.9.0-1+deb11u2) ... Removing raspinfo (20230123-1) ... Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u7) ... rob@pi41:~ $? ====== rob@pi41:~ $ sudo apt-mark showhold [sudo] password for rob:?
libhamlib++-dev
libhamlib++4
libhamlib-dev
libhamlib-doc
libhamlib-perl
libhamlib-utils
libhamlib2-perl
libhamlib2-tcl
libhamlib4
python3-hamlib |
Re: Wo-We replacement
I have a Wo-We that I bought earlier. I just checked the power plug for it and it indeed says output 19V. However I have been operating the WO-WE off my DC power supply since I received it with no problems. I run most everything in my shack from the DC power supply. I've also tested it off a Powerwerx 30ah LiFePo battery. No problems. The cable runs from the DC plug to the Anderson Power Pole connector on the DC distro panel. You should be fine.?
Kevin, WA4KBM |
Re: xastir issues
Use YAAC.? I started with it when he came out with the first version and never looked back. On Sun, Mar 10, 2024 at 10:31?AM Kelly K7MHI via <kellykeeton=[email protected]> wrote: Try running the following, and install the app again: |
Re: More GPS Winlink Bookworm woes
OK more banging my head against a wall - er troubleshooting. I am actually making a bit of progress. Kelly, per your recommendation, I changed my shell script to the following: #!/bin/bash cd $HOME/patmenu2 ./patmenu exit 0 As I said previously, this is the only way for me to get Pat to work. This seems to work - sort of.? For reference, I am (for now...) using Ardop, but I don't think it will make a difference. When I start the Ardop modem all seems well until I "Select Alias". When I do, it selects the callsign, but not the frequency to send to flrig. If I manually type in the correct frequency in the "Freq:" dialog, then click on the "Target" (gateway callsign) it properly sends the freq to FLrig.? Also if I click "Show RMS list" and select a gateway, it properly fills in the frequency and gateway callsign in Pat and merrily sends the frequency on to FLrig. At least at this point I can finagle things to make it work. Kelly, I know you don't use pat, but I thought it worthwhile to document what I have found so far. Thanks again for your help!! -- Mike WB8ERJ Geeze! What is he up to now? On Sun, Mar 3, 2024 at 10:53?PM Mike Thompson via <wb8erj=[email protected]> wrote:
|
Maybe this is a more precise search. Can you suggest how I could resolve the conflict ?
rob@pi41:~ $ rfindf *libhamlib*
[sudo] password for rob:
/usr/local/lib/libhamlib.so.4
/usr/local/lib/libhamlib++.so.4.0.4
/usr/local/lib/libhamlib++.so.4.0.5
/usr/local/lib/libhamlib.so.4.0.5
/usr/local/lib/libhamlib++.la
/usr/local/lib/libhamlib.so
/usr/local/lib/libhamlib++.a
/usr/local/lib/libhamlib++.so.4
/usr/local/lib/libhamlib.la
/usr/local/lib/libhamlib.a
/usr/local/lib/libhamlib.so.4.0.4
/usr/local/lib/libhamlib++.so
/var/cache/apt/archives/libhamlib4_4.0-7_armhf.deb
/var/cache/apt/archives/libhamlib-dev_4.0-7_armhf.deb
rob@pi41:~ $ |
I did a find *hamlib* to see what files are present, and the list is below. Does this tell you enough to tell me how to proceed to clean up the unnecessary / conflicting files ?
( ?alias rfindf="sudo find / -name "$1"" ) rob@pi41:~ $ rfindf *hamlib* [sudo] password for rob:? /home/rob/Downloads/fldigi-4.1.27/src/include/hamlib.h /home/rob/Downloads/fldigi-4.1.27/src/rigcontrol/hamlib.cxx /home/rob/Downloads/fldigi-4.1.27/scripts/mkhamlibstatic.sh /home/rob/.bap-source-files/fldigi-4.1.25/src/include/hamlib.h /home/rob/.bap-source-files/fldigi-4.1.25/src/rigcontrol/.deps/fldigi-hamlib.Po /home/rob/.bap-source-files/fldigi-4.1.25/src/rigcontrol/hamlib.cxx /home/rob/.bap-source-files/fldigi-4.1.25/scripts/mkhamlibstatic.sh /home/rob/.bap-source-files/hamlib-4.4 /home/rob/.bap-source-files/hamlib-4.4/hamlib.m4 /home/rob/.bap-source-files/hamlib-4.4/bindings/.deps/hamlibpy_wrap.Plo /home/rob/.bap-source-files/hamlib-4.4/bindings/.deps/Hamliblua_la-hamliblua_wrap.Plo /home/rob/.bap-source-files/hamlib-4.4/bindings/.deps/hamlibtcl_wrap.Plo /home/rob/.bap-source-files/hamlib-4.4/bindings/hamlib.swg /home/rob/.bap-source-files/hamlib-4.4/include/hamlib /home/rob/.bap-source-files/hamlib-4.4/hamlib.pc /home/rob/.bap-source-files/hamlib-4.4/src/hamlibdatetime.h /home/rob/.bap-source-files/hamlib-4.4/src/hamlibdatetime.h.in /home/rob/.bap-source-files/hamlib-4.4/hamlib.pc.in /home/rob/.bap-source-files/hamlib-4.4/doc/hamlib.png /home/rob/.bap-source-files/hamlib-4.4/doc/hamlib.css /home/rob/.bap-source-files/hamlib-4.4/doc/hamlib.cfg /home/rob/.bap-source-files/hamlib-4.4/doc/man7/hamlib-primer.7 /home/rob/.bap-source-files/hamlib-4.4/doc/man7/hamlib.7 /home/rob/.bap-source-files/hamlib-4.4/doc/man7/hamlib-utilities.7 /home/rob/.bap-source-files/hamlib-4.4/doc/hamlib.cfg.in /home/rob/.bap-source-files/hamlib-4.4/android/hamlib-compile /home/rob/.bap-source-files/fldigi-4.1.26/src/include/hamlib.h /home/rob/.bap-source-files/fldigi-4.1.26/src/rigcontrol/.deps/fldigi-hamlib.Po /home/rob/.bap-source-files/fldigi-4.1.26/src/rigcontrol/hamlib.cxx /home/rob/.bap-source-files/fldigi-4.1.26/scripts/mkhamlibstatic.sh /home/rob/.bap-source-files/fldigi-4.2.03/src/include/hamlib.h /home/rob/.bap-source-files/fldigi-4.2.03/src/rigcontrol/.deps/fldigi-hamlib.Po /home/rob/.bap-source-files/fldigi-4.2.03/src/rigcontrol/hamlib.cxx /home/rob/.bap-source-files/fldigi-4.2.03/scripts/mkhamlibstatic.sh /home/rob/.bap-source-files/fldigi-4.2.00/src/include/hamlib.h /home/rob/.bap-source-files/fldigi-4.2.00/src/rigcontrol/.deps/fldigi-hamlib.Po /home/rob/.bap-source-files/fldigi-4.2.00/src/rigcontrol/hamlib.cxx /home/rob/.bap-source-files/fldigi-4.2.00/scripts/mkhamlibstatic.sh /home/rob/.bap-source-files/direwolf/cmake/modules/Findhamlib.cmake /home/rob/.bap-source-files/fldigi-4.2.04/src/include/hamlib.h /home/rob/.bap-source-files/fldigi-4.2.04/src/rigcontrol/.deps/fldigi-hamlib.Po /home/rob/.bap-source-files/fldigi-4.2.04/src/rigcontrol/hamlib.cxx /home/rob/.bap-source-files/fldigi-4.2.04/scripts/mkhamlibstatic.sh /home/rob/.bap-source-files/fldigi-4.1.23/src/include/hamlib.h /home/rob/.bap-source-files/fldigi-4.1.23/src/rigcontrol/.deps/fldigi-hamlib.Po /home/rob/.bap-source-files/fldigi-4.1.23/src/rigcontrol/hamlib.cxx /home/rob/.bap-source-files/fldigi-4.1.23/scripts/mkhamlibstatic.sh /home/rob/.bap-source-files/fldigi-4.1.27/src/include/hamlib.h /home/rob/.bap-source-files/fldigi-4.1.27/src/rigcontrol/.deps/fldigi-hamlib.Po /home/rob/.bap-source-files/fldigi-4.1.27/src/rigcontrol/hamlib.cxx /home/rob/.bap-source-files/fldigi-4.1.27/scripts/mkhamlibstatic.sh /home/rob/.bap-source-files/js8call/CMake/Modules/Findhamlib.cmake /usr/local/lib/pkgconfig/hamlib.pc /usr/local/lib/libhamlib.so.4 /usr/local/lib/libhamlib++.so.4.0.4 /usr/local/lib/libhamlib++.so.4.0.5 /usr/local/lib/libhamlib.so.4.0.5 /usr/local/lib/libhamlib++.la /usr/local/lib/libhamlib.so /usr/local/lib/libhamlib++.a /usr/local/lib/libhamlib++.so.4 /usr/local/lib/libhamlib.la /usr/local/lib/libhamlib.a /usr/local/lib/libhamlib.so.4.0.4 /usr/local/lib/libhamlib++.so /usr/local/include/hamlib /usr/local/share/aclocal/hamlib.m4 /usr/local/share/man/man7/hamlib-primer.7 /usr/local/share/man/man7/hamlib.7 /usr/local/share/man/man7/hamlib-utilities.7 /usr/local/share/doc/hamlib /var/cache/apt/archives/libhamlib4_4.0-7_armhf.deb /var/cache/apt/archives/libhamlib-dev_4.0-7_armhf.deb /var/cache/apt/archives/python3-hamlib_4.0-7_armhf.deb rob@pi41:~ $? |
Kelly,
OK, I opened flrig and then ran this command: ? ?$?rigctld -m4 ¡ and terminal returned this error: ? ? ? rigctld: symbol lookup error: rigctld: undefined symbol: network_multicast_server So I went ahead anyway and opened pat and tried the packet modem, the VARA FM modem and the VARA modem, and they all failed with the same QSY / rig control errors as before: ? I¡¯m wondering if there is something fundamental wrong with my Linux73 installation that came about because I installed over the top of a BAP installation of the same apps? I keep getting these same AX25 / rig control errors¡ On a whim, I tried running the Linux73 Update-Tool and it said that VARIM, XASTIR and PACKETSEARCH all NEEDS_UPDATE, so I ran the updater, rebooted and tried pat packet modem again, but the same errors appear. I appreciate the time you¡¯re spending helping me troubleshoot this, what do you think is wrong ? Thanks, Rob ? KK6JNI |
Kelly wrote:
if you set the line in direwolf config to?PTT RIG 4 localhost:12345 ======================== No, same errors. ?I commented out: # PTT RIG 2 localhost:4235 ? ? ? ? ? ?(this was from Jason¡¯s IC-705 videos¡) ¡and added this line below it: PTT RIG 4 ?localhost:12345 Then when I open flrig, it connects to the radio and Conky reports ¡°FLRIG ACTIVE¡± Then when I open Direwolf from the Hamradio menu, it says: ? ? ? Audio device for both receive and transmit: plughw:3,0 (channel 0) ? ? ? Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100sample rate / 3 [ in green text ] ? ? ? Hamlib determined CAT control serial port rate of 0. ? ? ? Ready to accept AGW client application 0 on port 8000 ¡ ? ? ? Ready to accept KISS TCP client application on port 8001 ¡ Conky reports DIREWOLF ACTIVE But then, when I open the pat mailbox in Chromium, I get the same QSY failure message as before: ? ? ? Unable to get frequency from rig my-rig: dial tcp 127.0.0.1:4532 connect connection refused. So I opened Pat Menu to try to test VARA HF. When I clicked ¡°Stop Modems¡± and then ¡°Start VARA Modem (BETA)¡±, I got an error, ¡°It looks like direwolf is running. Stop all modems and try again¡± : So I want back to the direwolf terminal window and did CONTROL-C to stop direwolf. Then when I clicked ¡°Start VARA Modem (BETA)¡±, it started up pat mailbox in chromium, but with the same QSY error when I tried to connect with packet: ? ? ? Unable to get frequency from rig my-rig: dial tcp 127.0.0.1:4532 connect connection refused. Interestingly, the flrig window showed that it was still connected to the radio at the correct frequency, but pat mailbox was not able to set the new frequency in flrig. It seems the problem is between pat winlink and flrig ¡ª they aren¡¯t playing well with each other. Why did you have me change direwolf.conf ?to?PTT RIG 4 ?localhost:12345 from Jason¡¯s PTT RIG 2 localhost:4235 ? It didn¡¯t seem to change anything¡ Rob ? KK6JNI |