Re: Problemm running fldigi on Raspberry Pi
The difference in fldigi
compilation will be negligible.? Linking will be a very little
bit longer, but you should be able to measure that even on the
Pi.? The header files are necessary for the compilation to
correctly use the hamlib API.? Memory usage should be very
similar, whether using a static .a file or load the shared .so
at run time.
David
On 4/10/24 09:11, Johnny, IZ8EWD via
groups.io wrote:
toggle quoted message
Show quoted text
Sorry, another question.
fldigi needs static hamlib? Because usually i compile only the
shared libraries in order to short the computation time.
|
Re: Problemm running fldigi on Raspberry Pi
Sorry, another question.
fldigi needs static hamlib? Because usually i compile only the shared libraries in order to short the computation time.
|
fldigi 4.2.04.10 development release posted at
Latest change:
commit d93f4b89c44d0cd17e66bd926fa793f3742f51ed
Author: dave-w1hkj <w1hkj@...>
Date: Wed Apr 10 07:07:29 2024 -0500
RSID Min Bandwidth
??? * add user adjustable bandwidth for minimum RsID detection
range.
This will allow up to 16 simultaneous THOR-11 signals (channels) to
be contained in a passband of 200 to 3400 Hertz spaced at 200 Hertz
intervals.? This change is in support of the development and testing
of emergency digital communicators that can be easily interfaced to
Android devices.
73, David, W1HKJ
|
Re: Problemm running fldigi on Raspberry Pi
That is correct.? Make sure
that libudev and libxft were both included with build-dep as
those are now required libraries.
David
On 4/10/24 06:00, Johnny, IZ8EWD via
groups.io wrote:
toggle quoted message
Show quoted text
Dave,
thanks for your reply.
If I understand well, I have to use the build-dep command to be
sure that all the libraries are available.
After that I can remove the old hamlib 4.0 installed from the
Bullseye repository and replace with the latest 4.6 github
snapshot as I need.
Then proceed with fldigi compilation.
|
Re: Problemm running fldigi on Raspberry Pi
Dave,
thanks for your reply.
If I understand well, I have to use the build-dep command to be sure that all the libraries are available.
After that I can remove the old hamlib 4.0 installed from the Bullseye repository and replace with the latest 4.6 github snapshot as I need.
Then proceed with fldigi compilation.
|
Re: Problemm running fldigi on Raspberry Pi
fldigi builds without error
using the either the hamlib 4.6 archive source, or the latest
pull from the hamlib remote git repository.
As you probably already know, avoiding library conflicts is not
the responsibility of the target application, but the person
doing the compilation.
- remove all of the hamlib
library installation.? Do this using apt-get, aptitude, or
the synaptic.? You need to be sure that the .a, .so and all
header files are not on your system.
- download and install the
latest 4.6 tar.gz file, or clone the hamlib git repository
- compile and install
hamlib 4.6
./configure && make && sudo make install
The Pi build instructions:
? works
correctly on my Pi3, Pi4, and Pi5
Synaptic being used to
"remove all" references to hamlib 4.3.x
fldigi build info after
successful installation of latest hamlib built from git
repository clone:
73, David, W1HKJ
|
Re: Problemm running fldigi on Raspberry Pi
Hi Cliff,
I will post the make output asap.
Some observations:
- There was a change in the hamlib library, some reference were converted to pointers, so older version of fldigi doesn't compile. I try with the last issue of 4.1.27 and it doesn't complie.
- If I install hamlib from the Bullseye repository, I'm not able to replace it by compiling the last 4.6, applications see the ones installed by the apt, I have to remove this one to make visible the 4.6.
- Actually, when I compile fldigi using the guide I posted??, there aren't warning or errror for missing libraries.
|
Re: [winfldigi] flamp 2.2.11.14 development version posted
All builds completed on EPEL 8 through Fedora Rawhide:
Thanks, Richard
KF5OIM
|
flamp 2.2.11.14 development version posted
at
Author: kk5vd <kk5vd@...>
Date:?? Tue Apr 9 16:45:37 2024 -0500
??? Compatibility/Modem Switch
?? ?
???? * Add leading linefeed to [bxx:end] tags
???? * Add delay to allow FLDIGI the time to switch modems.
Author: kk5vd <kk5vd@...>
Date:?? Sun Mar 3 19:49:04 2024 -0600
??? Document/GUI/Header Modem/Default Modems
???? * Update User Manual for recent changes.
???? * Estimated Relay transmit time not updating on TX panel
modem change.
???? * Header Modem using interval timer RX state delay,
corrected.
???? * Olivia Modem Names to Uppercase.
???? * Remove redundant TX_SEGMENTED check.
???? * Add code for relay repeat counters, interval timer.
Author: dave-w1hkj <w1hkj@...>
Date:?? Sun Jan 7 10:20:11 2024 -0600
??? font browser
?? ?
????? * update font browser class to use std::list vice
??????? computed array size to enumerate system fonts
Author: kk5vd <kk5vd@...>
Date:?? Sun Jan 28 15:45:52 2024 -0700
??? Tabs/Relay Options/GUI/Fluid
???? * Save selected Tab panel state on exit
???? * Restore selected panel on restart.
???? * Corrected Widget Event Settings (FLUID).
???? * Add Header/Data Repeat Counters for Relay file
transmissions.
???? * Add transmit time widget for relay files.
???? * Move relay auto save checkboxes to config panel.
???? * Corrected default Olivia modem tag names.
???? * Add code to correctly restore RX panel data on file
selection changes.
Should resove the incompatibility issue? between 2.2.11 and
2.2.11.13
73, David, W1HKJ
|
Re: Minor bug - Re: [nbems] flamp 2.2.11.13 development version posted at
Bob,
I was not able to confirm the issue. However, I added a small delay to the calling code to switch the modem using FLAMP. If you have the ability to compile code you can download a snapshot of the source code here.
and test it, otherwise going to wait awhile for more possible issues before we release another development version.
Robert.
|
Re: Problemm running fldigi on Raspberry Pi
If you can find a newer one then can't you install that to replace the older one?
Please post the errors you got in the "make" so we can see the issues.
toggle quoted message
Show quoted text
On Apr 9, 2024, at 15:13, Johnny, IZ8EWD via < js.slave@...> wrote:
If I use apt build-dep as suggested in the fldigi wiki, it install also an old version of libhamlib4 and I don't want to use it.
|
Re: Problemm running fldigi on Raspberry Pi
If I use apt build-dep as suggested in the fldigi wiki, it install also an old version of libhamlib4 and I don't want to use it.
|
Re: Problemm running fldigi on Raspberry Pi
Looking at your link it doesn't mention the libraries that are probably missing. Following the details on the link I sent and you'll see what I mean.
toggle quoted message
Show quoted text
I recommend this link as it's what I use and works every time. I've been compiling on my Pi for years.
On Apr 9, 2024, at 13:25, Johnny, IZ8EWD via < js.slave@...> wrote:
I compile from source fldigi 4.2.04 in my Raspberry Pi, Bullseye 32 bit. There are some warnings, but at the end the compile and installation works.
But when I run the software, after the configuration wizard it crashes.
The log file in the .fldigi folder is empty, so I cannot share any info.
The step followed to compile it, are described in this page
I use hamlib 4.6 beta.
If I download the fldigi available on the Debian repository, v.4.1.18, it works well but uses hamlib 4.0.4 and I need the 4.6.
Can someone help me to have fldigi working?
|
Re: Problemm running fldigi on Raspberry Pi
I recommend this link as it's what I use and works every time. I've been compiling on my Pi for years.
toggle quoted message
Show quoted text
On Apr 9, 2024, at 13:25, Johnny, IZ8EWD via < js.slave@...> wrote:
I compile from source fldigi 4.2.04 in my Raspberry Pi, Bullseye 32 bit. There are some warnings, but at the end the compile and installation works.
But when I run the software, after the configuration wizard it crashes.
The log file in the .fldigi folder is empty, so I cannot share any info.
The step followed to compile it, are described in this page
I use hamlib 4.6 beta.
If I download the fldigi available on the Debian repository, v.4.1.18, it works well but uses hamlib 4.0.4 and I need the 4.6.
Can someone help me to have fldigi working?
|
Problemm running fldigi on Raspberry Pi
I compile from source fldigi 4.2.04 in my Raspberry Pi, Bullseye 32 bit. There are some warnings, but at the end the compile and installation works.
But when I run the software, after the configuration wizard it crashes.
The log file in the .fldigi folder is empty, so I cannot share any info.
The step followed to compile it, are described in this page
I use hamlib 4.6 beta.
If I download the fldigi available on the Debian repository, v.4.1.18, it works well but uses hamlib 4.0.4 and I need the 4.6.
Can someone help me to have fldigi working?
|
Don't think the DE-19 works with Linux! Never got it going with my Raspberry Pi. ?Bo W4GHV since '54
|
David,
? ? I rolled my G90 back from 1.8 to 1.79b3 out of sheer frustration.? 1.79b3 does a mediocre job communicating the amount of SWR to display on FLRIG, but did work.? V1.8 pegged SWR at my Xubuntu install regardless of the actual SWR. Xiegu may say they emulate the Icom CI-V, but the IC-7100's I used to have worked perfectly with FLRIG.?
? ?Between lack of firmware support and little or no factory service I have replaced my G90 with a Yaesu FT-450D and relegated the G90 to POTA service.?
|
I recently reinstalled Xubuntu onto a laptop of mine as the previous Ubuntu installation was getting clunky and bloated. I just tried to hook up my G90 to flrig to do remote control and in prep for digital modes. Before this I updated the head unit to firmware version 1.80 (previously head and body were both at 1.79b3). I'm using the DE-19 card as the interface. Now when trying to connect to it flrig never initializes the radio, it just never sees it. Here's a list of things I've tried:
*Changed settings, including stop bit settings, echo, RTS/DTS voltage. Baud has always been set to 19200.
*Added dialout group to my user as the tty device is assigned to that group. And yes, rebooted after to ensure it was in my profile.
*Removed brltty to avoid it subsuming the UART device when plugged in.
*Tried the old Icom 7000/7100 setting, no joy.
All the software I'm running is from PPA, no hand compiling.
I'm fearing that I may have to roll the firmware back on the head to 1.79b3 but this seems like a drastic step. Anyone have any thoughts?
|
Running FSQ Now on 30 Meters
Greetings,
Active on 10.144+1500hz with FSQ. Spotting heard stations to pskreporter.
73 de Ted, AB8FJ
EM79
|
Re: flrig 2.0.05.32 development version posted
You're welcome. If you still see issues be sure to bring them up. Dave does his best to weed them out.
toggle quoted message
Show quoted text
On Apr 5, 2024, at 08:19, Philip Rose, GM3ZZA via < gm3zza@...> wrote:
Hi Cliff,
I am running .32. And yes I did have the poll bandwidth button
unchecked. I've checked it now. I still saw some anomalies, but it
seems a lot more robust.
Thanks 73 Phil GM3ZZA
On 04/04/2024 17:52, Cliff, AE5ZA
wrote:
Phil,
You post says 2.0.5.32 in the subject. You are
running that version, correct? Older versions had issues with
reading BW.
Phil,
Check that you have polling for BW on in
flrig. It works fine here. In CW mode can change
filters and BW manually on the 7300 and flrig
follows.?
Same test in USB-D and all is good as
well.
On Apr 4, 2024, at 10:54, Philip
Rose, GM3ZZA via
< gm3zza@...>
wrote:
It's
the filter width display in flrig that doesn't
agree with the IC-7300. Then I think somehow
what flrig thinks is the width gets written
back to the IC-7300.?
I
did much testing this afternoon and never did
flrig change the width if I changed it on the
IC-7300 by changing the filter number.
|
Dave, W1HKJ
Richard Shaw, KF5OIM
Bo, W4GHV
David Eddleman, K5RNL