¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: Updating the FLdigi build wiki

 

Thank you that did it.? In KDE, in the Discovery app, settings, checking Sources, did the trick.??
?
Once I did that 'sudo apt build-dep fldigi'? worked.??
?
Instead of aptitude I have just been using apt, wherever I see aptitude.? That seems to do the trick for me...? perhaps the wiki needs a re-write....? something for me to think about.? If I do it I'll post it here and then you guys can do whatever you'd like with it.??
?
I don't know about pulseaudio vs pipewire.??
?
when I do 'pactl info | grep "Server Name" ' I get back?

Server Name: PulseAudio (on PipeWire 1.0.5)

So I guess I am on pipewire with a PulseAudio Wrapper.? In the fldigi configure window I just used PulseAudio and use the Pavucontrol to set the levels. I used to use portaudio which I really liked but it would freeze on mode changes... sometimes so long I'd miss traffic.?


fldigi 4.2.06 crash at end of MFSK64 image send

 

Running fldigi 4.2.06 under Linux Mint 21.3 Cinnamon 6.0.4 - full sysinfo at end if needed.
?
Sent a large color image which was received. As it finished, fldigi closed with the image window. After reopening, the software lost the ability to transmit text - would key the transmitter but not send anything. Finally rebooted the computer to get an ident sent.
?
I don't use image transmission very often. If it's a size issue, the image was a 436kB color image that took about 14 min to send, a portion of a screenshot that included the waterfall of something to share with a net.
?
Similarly, there have been crashes if the image send is aborted before completion. Sometimes killing the fldigi process by pid gets things working again without rebooting the system. That didn't help this time - was able to restart the software but unable to send anything until I finally rebooted the computer.
?
73,
Mark Avery, KE8NHT, Beavercreek, OH, EM79xq
?
System:
? Kernel: 5.15.0-126-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
? ? tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
? ? base: Ubuntu 22.04 jammy
Machine:
? Type: Mini-pc System: ATOPNUC product: ATOPNUC MA90 v: V1.0 serial: <superuser required>
? Mobo: ATOPNUC model: ATOPNUC MA90 v: Version 1.0 serial: <superuser required>
? ? UEFI: American Megatrends v: ASB20008 date: 07/19/2022
CPU:
? Info: dual core model: AMD A9-9400 RADEON R5 5 COMPUTE CORES 2C+3G bits: 64 type: MCP
? ? smt: <unsupported> arch: Excavator rev: 0 cache: L1: 192 KiB L2: 2 MiB
? Speed (MHz): avg: 2583 high: 2603 min/max: 1400/2400 boost: enabled cores: 1: 2603 2: 2563
? ? bogomips: 9582
? Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
? Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] driver: amdgpu v: kernel ports:
? ? active: HDMI-A-1,HDMI-A-2 empty: DP-1 bus-ID: 00:01.0 chip-ID: 1002:98e4 class-ID: 0300
? Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
? ? unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
? Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.0x11.2") s-diag: 1055mm (41.5")
? Monitor-1: HDMI-A-0 mapped: HDMI-A-1 pos: primary,left model: Z1-3 serial: <filter>
? ? res: 1920x1080 dpi: 141 size: 347x197mm (13.7x7.8") diag: 399mm (15.7") modes: max: 1920x1080
? ? min: 640x480
? Monitor-2: HDMI-A-1 mapped: HDMI-A-2 pos: right model: KYY serial: <filter> res: 1920x1080
? ? hz: 60 dpi: 143 size: 340x190mm (13.4x7.5") diag: 398mm (15.7") modes: max: 1920x1080
? ? min: 640x480
? OpenGL: renderer: STONEY (stoney LLVM 15.0.7 DRM 3.42 5.15.0-126-generic)
? ? v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes
Audio:
? Device-1: AMD driver: snd_hda_intel v: kernel bus-ID: 00:01.1 chip-ID: 1002:15b3 class-ID: 0403
? Device-2: AMD Family 15h Audio vendor: Conexant Systems driver: snd_hda_intel v: kernel
? ? bus-ID: 00:09.2 chip-ID: 1022:157a class-ID: 0403
? Device-3: Texas Instruments PCM2901 Audio Codec type: USB
? ? driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-1.2.4:7 chip-ID: 08bb:2901 class-ID: 0300
? Device-4: Generalplus USB Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
? ? bus-ID: 2-3:3 chip-ID: 1b3f:2008 class-ID: 0300
? Sound Server-1: ALSA v: k5.15.0-126-generic running: yes
? Sound Server-2: PulseAudio v: 15.99.1 running: no
? Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
? Device-1: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: N/A
? ? bus-ID: 01:00.0 chip-ID: 8086:15f3 class-ID: 0200
? IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
? Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: AzureWave
? ? driver: rtw_8822ce v: N/A pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0
? ? chip-ID: 10ec:c822 class-ID: 0280
? IF: wlo1 state: up mac: <filter>
? IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
? Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 2-1:2
? ? chip-ID: 13d3:3549 class-ID: e001 serial: <filter>
? Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
? ? sub-v: 6d7d hci-v: 5.1 rev: 19b7
Drives:
? Local Storage: total: 1.4 TiB used: 487.21 GiB (34.0%)
? ID-1: /dev/mmcblk0 model: N/A size: 500 GiB type: SSD serial: <filter>
? ID-2: /dev/sda vendor: Silicon Power model: SPCC M.2 SSD size: 931.51 GiB speed: 6.0 Gb/s
? ? type: SSD serial: <filter> rev: 5A0 scheme: GPT
Partition:
? ID-1: / size: 915.32 GiB used: 486.48 GiB (53.1%) fs: ext4 dev: /dev/sda2
? ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
? ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
? Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
? ? class-ID: 0900
? Hub-2: 1-1:2 info: Advanced Micro Devices Root Hub ports: 4 rev: 2.0 speed: 480 Mb/s
? ? power: 100mA chip-ID: 0438:7900 class-ID: 0900
? Device-1: 1-1.1:3 info: U-Blox AG [u-blox 7] type: Abstract (modem),CDC-Data driver: cdc_acm
? ? interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 1546:01a7 class-ID: 0a00
? Hub-3: 1-1.2:4 info: Texas Instruments TUSB2046 Hub ports: 4 rev: 1.1 speed: 12 Mb/s
? ? chip-ID: 0451:2046 class-ID: 0900
? Device-1: 1-1.2.1:6 info: Silicon Labs CP210x UART Bridge type: <vendor specific>
? ? driver: cp210x interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 10c4:ea60
? ? class-ID: 0000 serial: <filter>
? Device-2: 1-1.2.4:7 info: Texas Instruments PCM2901 Audio Codec type: Audio,HID
? ? driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1 speed: 12 Mb/s
? ? chip-ID: 08bb:2901 class-ID: 0300
? Device-3: 1-1.4:5 info: Microsoft Nano Transceiver v1.0 for Bluetooth type: Keyboard,Mouse,HID
? ? driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 045e:0745
? ? class-ID: 0300
? Hub-4: 2-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
? ? chip-ID: 1d6b:0002 class-ID: 0900
? Device-1: 2-1:2 info: IMC Networks Bluetooth Radio type: Bluetooth driver: btusb interfaces: 2
? ? rev: 1.0 speed: 12 Mb/s power: 500mA chip-ID: 13d3:3549 class-ID: e001 serial: <filter>
? Device-2: 2-3:3 info: Generalplus USB Audio Device type: Audio,HID
? ? driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1 speed: 12 Mb/s power: 100mA
? ? chip-ID: 1b3f:2008 class-ID: 0300
? Hub-5: 3-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
? ? class-ID: 0900
Sensors:
? System Temperatures: cpu: 60.0 C mobo: N/A gpu: amdgpu temp: 60.0 C
? Fan Speeds (RPM): N/A
Repos:
? Packages: 3056 apt: 3051 flatpak: 5
? No active apt repos in: /etc/apt/sources.list
? Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
? ? 1: deb [arch=amd64] http: //dl.google.com/linux/earth/deb/ stable main
? Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
? ? 1: deb http: //packages.linuxmint.com virginia main upstream import backport
? ? 2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
? ? 3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
? ? 4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
? ? 5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
? Processes: 275 Uptime: 46m wakeups: 0 Memory: 30.8 GiB used: 2.77 GiB (9.0%) Init: systemd
? v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.4 inxi: 3.3.13


Re: Bug or "Feature"? Re: fldigi 4.2.06.14 development test version posted at

 

Do you have Config Settings> Misc > Save Parameters> AFC Control checked or not? I did notice at one point that it prevented changing the setting if that was not checked in some modes.


Re: Updating the FLdigi build wiki

 

¿ªÔÆÌåÓý

Hi Greg,

I'm also on Ubuntu 24.04 and use the WIKI build instructions. I have noticed the confusion on some of the steps. My Fldigi sometimes locks up and Top reports the Fldigi CPU utilization is over 100%. I'm not sure if I'm having trouble with the instructions.

I think checking Source code in Software and updates will do the same thing as editing the sources.list. I have all 5 items checked
sudo aptitude build-dep fldigi doesn't work so I skipped this and did the apt-get steps.
When I did the configure and make steps I think some messages came up about pulse audio and pipe wire. I think the new Ubuntu wants to use Pipe Wire. One question is should I configure Fldigi to use Pipe Wire and not Pulse Audio. Also, do I still have to use Pulse Audio Control to adjust the audio levels.

This is the message I get when I install pavucontrol:

$ sudo aptitude install pavucontrol
The following NEW packages will be installed:
? libasound2-plugins{a} libatkmm-1.6-1v5{a} libcairomm-1.0-1v5{a} libglibmm-2.4-1t64{a} libgtkmm-3.0-1t64{a} libpangomm-1.4-1v5{a} pavucontrol pulseaudio{a} pulseaudio-utils{a}
0 packages upgraded, 9 newly installed, 0 to remove and 5 not upgraded.
Need to get 2,995 kB of archives. After unpacking 15.0 MB will be used.
The following packages have unmet dependencies:
?pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu10 is to be installed
????????????????? Conflicts: pulseaudio:i386 but it is not going to be installed
?pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu10 is to be installed
???????????????? Conflicts: pulseaudio:i386 but it is not going to be installed
The following actions will resolve these dependencies:

???? Keep the following packages at their current version:
1)???? pulseaudio [Not Installed]??????????????????????? ?

???? Leave the following dependencies unresolved:??????? ?
2)???? pavucontrol recommends pulseaudio???????????????? ?



Accept this solution? [Y/n/q/?]

I answered Y to accept.

73, Ron NY3J

On 12/16/24 10:08, Greg Cheng - KC3SMW via groups.io wrote:

I recently redid my Linux machine and the newest version of Ubuntu 24.04.1 handles repos differently. Making the the build instructions deprecated.? ?'Sudo apt build-dep fldigi' no longer works because you cannot edit sources.list because it doesn't exist.
?
Is there a list of depends that I can install prior to building FLdigi???
?
I managed to handle it while watching the ./configure.? Each time it failed I read why and then tracked down that dependancy.? ?Rinse and repeat.? ?I am sure I missed a few, FLdigi worked on the nbems net yesterday, but I want to make sure I have the complete program with no features or options missing.??
?
Thanks!


Re: Updating the FLdigi build wiki

 

On Mon, Dec 16, 2024 at 08:08 AM, Greg Cheng - KC3SMW wrote:
Is there a list of depends that I can install prior to building FLdigi???
Hi Greg,
?
I just did a fresh install of Ubuntu 24.04 this morning. I'm not sure where the sources file was moved off to, but you can enable the 'Source code' repository via the Software & Updates application. After you do that, you should be able to continue with the build instructions from the wiki.
?
Attached is a list of what was installed when I did 'apt build-dep fldigi'. I think libxft-dev was still missing from there though, and had to be installed separately?
?
Cheers,
Steve K4RVA


Re: Interfaceing FLDIGI

 

Hi Levente,

On Mon, Dec 16, 2024 at 03:44:48PM +0100, Lev, HA5OGL via groups.io wrote:

I'm working on a log program dedicated to SOTA activations.

great, it's good to see that more and more loggers are available
on Linux! :)

My question if there was an interface I can connect to from my log program?
If so, are there any examples out there how to do that?
yes, Fldigi has a good xmlrpc interface. I've already implemented
that for Tlf (and later HA5CQZ Zoli reworked).

For eg. getting the CALL from Fldigi is here:



Hope this helps - let me/us know if you have any question!


73, Ervin
HA2OS


Updating the FLdigi build wiki

 

I recently redid my Linux machine and the newest version of Ubuntu 24.04.1 handles repos differently. Making the the build instructions deprecated.? ?'Sudo apt build-dep fldigi' no longer works because you cannot edit sources.list because it doesn't exist.
?
Is there a list of depends that I can install prior to building FLdigi???
?
I managed to handle it while watching the ./configure.? Each time it failed I read why and then tracked down that dependancy.? ?Rinse and repeat.? ?I am sure I missed a few, FLdigi worked on the nbems net yesterday, but I want to make sure I have the complete program with no features or options missing.??
?
Thanks!


Interfaceing FLDIGI

 

Dear all, especially David,



I'm working on a log program dedicated to SOTA activations.



This uses the GTK-4 toolkit, and I'm in the middle of adding fancy features like

- Reading the position from GPSd
- Getting the nearest SOTA summit reference
- Getting the QRG from the rig using Hamlib

Things are started to work, but I now want to get data from Fldigi. The data I request are the following:

- Callsign
- QRG
- RST
- Op. Name

My question if there was an interface I can connect to from my log program? If so, are there any examples out there how to do that?


Thanks and 73 de HA5OGL

--
Levente Kovacs
Senior Electronic Engineer

W:


Re: FLDIGI and sequoia. linux

 

¿ªÔÆÌåÓý

Hi John, a notarized version of Fldigi that can be easily installed on MacOS 15 Sequoia is here:


Download the zip file, double clink on it and the app will appear. Drag the app to your Applications folder. Double click on it. You will get a pop up asking if you want to download an app from the internet. Click on yes and the Fldigi app should open.

Alternatively, you can open unnotarized apps by going to the Dock (app bar on the bottom of your screen) and open the System Settings app. Scroll down to Privacy & Security, Then scroll down to security. If you have already attempted to open an unnotarized app, you can there tell the Mac to open it anyway. You¡¯ll to give it your fingerprint and answer if you are sure a couple of times but then the app should open.

Hope this helps.

On Dec 14, 2024, at 3:30?PM, John Wiener via groups.io <jawodms@...> wrote:

I guess I cannot use fldigi on sequoia. Mac wont open it.? Is there a concise step-by-step manual to load linux on my mac and then load fldigi ?
I am basically computer illiterate.? I miss fldigi.
Thanks!
John AB8O


FLDIGI and sequoia. linux

 

I guess I cannot use fldigi on sequoia. Mac wont open it.? Is there a concise step-by-step manual to load linux on my mac and then load fldigi ?
I am basically computer illiterate.? I miss fldigi.
Thanks!
John AB8O


Re: Linux Recommendation - Work is a RHEL/Windows Shop

 

Joel,
?
I ran into the Broadcom driver's problem when installing Ubuntu on an iMac.? ?Not sure about RHEL, but there was an install option in Ubuntu that said something like install optional drivers.? Without checking that box, I had no wifi drivers when Ubuntu booted.? If you can find that choice on RHEL, the drivers are available but have to be enabled. Otherwise, you can do what I did the first time and sneakernet your Mac over to your cable modem, which wasn't very convenient.
?
Mike, N5QAW
?


Re: fldigi 4.2.06.15 developmen t version availabe for testing

 

¿ªÔÆÌåÓý

The answer is yes.? You can find that information in this file:

On 12/14/24 04:20, Asbesto, IW9HGS via groups.io wrote:

Hello, does this version include the recent WEFAX fix to set 288/576 etc etc? 







Re: FLDigi WEFAX settings and LPM: now wefax is broken for some FAX settings #settings #wefax #linux #LPM

 

Ah, I got it. But it opens the same menu. It was way better before... but ok :)

On Sat, Dec 14, 2024 at 1:04?PM gabriele zaverio <iw9hgs@...> wrote:
Ehm, I can't understand where to left-click :(

On Fri, Nov 29, 2024 at 4:51?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
Right click on the left most status bar control.

On 11/29/24 08:34, Asbesto, IW9HGS via wrote:
Can't the setting be put here, kinda as it was before? Tweaking into the modem menu isn't so fast when trying to decode something on the fly :)

shot-2024-11-28_14-50-07.jpg
Something the previous working version of the UX, that was so simple and immediate to use...


On Wed, Nov 27, 2024 at 5:41?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
fldigi-4.2.06.10 posted at


You should be able to change the LPM setting during reception.

Please test and report results.

73, David, W1HKJ


On 11/26/24 02:07, Asbesto, IW9HGS via wrote:
Hello! Meanwhile, I did some research...

First I found this:

in which the WEFAX settings are described as any kind of combination between 288/576 and 30,60,120,240 lpm...

at page 7 of the pdf, Kyodo news is quoted as requiring 60 and 120 lpm / 576 IOC setting:

"Next Tokyo station is JJC, it is Kyodo News Agency. Transmission speed is
60 lpm and IOC 576, sometimes 120 lpm when weather charts are posted."

I also wrote to the owner of the internet site and reached to me, indeed confirming that the setting for 576/120 and 60 are needed in order to receive this station... quoting his email:

"Yes, for Kyodo one needs 576/60. Fldigi removed the line setting from its interface at some point, quite a long time ?ago. What I did, was that I created a copy of Fldigi source code and changed hardcoded 120 to 60. So for Kyodo decoding I would simply run a second altered Fldigi.
So yes, I can confirm this behavior of a removed lines dropdown, as it really was there before."

I think the best course of action is to permit changing the combination of all those parameter as it was before, also as it is described in the wefax standard in the PDF i linked before - I will do it myself but I'm not a skilled programmer anymore (I was a programmer in the late '90 :) )

I will try to receive some transmission to test them asap!

TY

73 de IW9HGS

Gabriele



On Sun, Nov 24, 2024 at 3:14?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
Can you please create a sound file recording of the KYODO NEWS wefax broadcast.? Send it direct to

w1hkj@...

Thank you.

David

On 11/24/24 05:31, Asbesto, IW9HGS via wrote:
I see, but those changes broke the reception of a very interesting radio station (KYODO NEWS). For what I see, this is a bug - something that was working before, now it isn't. :(

On Fri, Nov 22, 2024 at 2:15?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
Those changes were made over 4 years ago.? If you need to reinstall an older version of the software these are available at



73, David, W1HKJ

On 11/22/24 01:01, Asbesto, IW9HGS via wrote:
Hello,?

In FLDigi 4.1.9 that I had on my old computer I was able to set some things about WEFAX that now are disappeared in the newer versions...

I have a new laptop, I installed the recent version of my GNU/Linux OS, and some options are missing.

I don't have anymore the "LPM" setting, the FIR setting nor the 4 bargraph showing START, PHASE, IMAGE... and I think also the "skip phase" is missing.?

The main problem is the "LPM" setting, because I can't set it correctly to receive Kyodo News from Japan.

Kyodo News require IOC576 with 60LPM and I can't set it

What I receive now is basically a half page, the other half is cut away and I can't solve this problem.

Is there some way to get back those settings for?WeFax? I think now it's unusable for KYODO NEWS decoding.?

Thank you

--

73 DE IW9HGS




--

73 DE IW9HGS



--

73 DE IW9HGS



--

73 DE IW9HGS



--

73 DE IW9HGS


--

73 DE IW9HGS


Re: FLDigi WEFAX settings and LPM: now wefax is broken for some FAX settings #settings #wefax #linux #LPM

 

Ehm, I can't understand where to left-click :(

On Fri, Nov 29, 2024 at 4:51?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
Right click on the left most status bar control.

On 11/29/24 08:34, Asbesto, IW9HGS via wrote:
Can't the setting be put here, kinda as it was before? Tweaking into the modem menu isn't so fast when trying to decode something on the fly :)


Something the previous working version of the UX, that was so simple and immediate to use...


On Wed, Nov 27, 2024 at 5:41?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
fldigi-4.2.06.10 posted at


You should be able to change the LPM setting during reception.

Please test and report results.

73, David, W1HKJ


On 11/26/24 02:07, Asbesto, IW9HGS via wrote:
Hello! Meanwhile, I did some research...

First I found this:

in which the WEFAX settings are described as any kind of combination between 288/576 and 30,60,120,240 lpm...

at page 7 of the pdf, Kyodo news is quoted as requiring 60 and 120 lpm / 576 IOC setting:

"Next Tokyo station is JJC, it is Kyodo News Agency. Transmission speed is
60 lpm and IOC 576, sometimes 120 lpm when weather charts are posted."

I also wrote to the owner of the internet site and reached to me, indeed confirming that the setting for 576/120 and 60 are needed in order to receive this station... quoting his email:

"Yes, for Kyodo one needs 576/60. Fldigi removed the line setting from its interface at some point, quite a long time ?ago. What I did, was that I created a copy of Fldigi source code and changed hardcoded 120 to 60. So for Kyodo decoding I would simply run a second altered Fldigi.
So yes, I can confirm this behavior of a removed lines dropdown, as it really was there before."

I think the best course of action is to permit changing the combination of all those parameter as it was before, also as it is described in the wefax standard in the PDF i linked before - I will do it myself but I'm not a skilled programmer anymore (I was a programmer in the late '90 :) )

I will try to receive some transmission to test them asap!

TY

73 de IW9HGS

Gabriele



On Sun, Nov 24, 2024 at 3:14?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
Can you please create a sound file recording of the KYODO NEWS wefax broadcast.? Send it direct to

w1hkj@...

Thank you.

David

On 11/24/24 05:31, Asbesto, IW9HGS via wrote:
I see, but those changes broke the reception of a very interesting radio station (KYODO NEWS). For what I see, this is a bug - something that was working before, now it isn't. :(

On Fri, Nov 22, 2024 at 2:15?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
Those changes were made over 4 years ago.? If you need to reinstall an older version of the software these are available at



73, David, W1HKJ

On 11/22/24 01:01, Asbesto, IW9HGS via wrote:
Hello,?

In FLDigi 4.1.9 that I had on my old computer I was able to set some things about WEFAX that now are disappeared in the newer versions...

I have a new laptop, I installed the recent version of my GNU/Linux OS, and some options are missing.

I don't have anymore the "LPM" setting, the FIR setting nor the 4 bargraph showing START, PHASE, IMAGE... and I think also the "skip phase" is missing.?

The main problem is the "LPM" setting, because I can't set it correctly to receive Kyodo News from Japan.

Kyodo News require IOC576 with 60LPM and I can't set it

What I receive now is basically a half page, the other half is cut away and I can't solve this problem.

Is there some way to get back those settings for?WeFax? I think now it's unusable for KYODO NEWS decoding.?

Thank you

--

73 DE IW9HGS




--

73 DE IW9HGS



--

73 DE IW9HGS



--

73 DE IW9HGS



--

73 DE IW9HGS

shot-2024-11-28_14-50-07.jpg
vdO83G2lEgJp6d9A.png


Re: fldigi 4.2.06.15 developmen t version availabe for testing

 

Hello, does this version include the recent WEFAX fix to set 288/576 etc etc?


Re: Fldigi Lockup

 

¿ªÔÆÌåÓý

Maybe I'm doing something wrong in the build.
I'm thinking of using 73 Linux from KM4ACK.

Ron NY3J


On 12/13/2024 8:04 PM, Richard Jackson, KD8NOA via groups.io wrote:

Hi Ron,

That was the best I have.??

If it is running at 100%, then it is looping on something.? It would probably be helpful to tell the author which module and the instruction addresses that it is looping through but I have no idea at all how to figure that out.??

Richard Jackson
kd8noa
Email address: richard7298@...




Re: Fldigi Lockup

 

Hi Ron,

That was the best I have.??

If it is running at 100%, then it is looping on something.? It would probably be helpful to tell the author which module and the instruction addresses that it is looping through but I have no idea at all how to figure that out.??

Richard Jackson
kd8noa
Email address: richard7298@...



Re: Fldigi Lockup

 

¿ªÔÆÌåÓý

Thanks Richard,

During a net I usually open Fldigi then I open Flmsg to create traffic for the net. I don't use the list feature and don't have transfer direct checked.
I usually leave the Flmsg's that I receive open so I can read them during the net. I also have Flamp open. I forget exactly which version the lockups
started to happen.

The two Pennsylvania nets on Sunday gets pretty busy. Also, the FM net on the local repeater gets busy so Fldigi gets quite a workout.

When I run the top program after the lockup it shows Fldigi running at more than 100% and stays that way until I reboot.

73, Ron NY3J


On 12/13/2024 6:28 PM, Richard Jackson, KD8NOA via groups.io wrote:

Hi Ron,

I run a RPI 4b running bookworm.? I had fldigi lockups.??

Are you opening FLMSG and leaving it open?? That gave me DIGI lockups.? I have configured FLDIGI? to open FLMSG upon receipt of a message.? DIGI hasn't locked up on me since I made that change.??

My digi config: configure | configure dialog | misc | NBEMS data file interface enable, open message folder not enabled, transfer direct not enabled, open with flmsg enabled, open in browser not enabled, the flmsg: field has the path to FLMSG executable, timeout is 2 seconds.??

if digi receives a message flmsg will open.? If I have a checksum?error, there will be a dialog box for that and the file name will be badfile.? If a second message arrives, I get a new flmsg window.? I had maybe 8 or 9 this morning, some with checksum errors.? If I want to save a badfile,?I scroll through the "received messages" window until I find the file name then save with that.??

Richard Jackson




On Thu, Nov 21, 2024 at 8:56?PM Ron NY3J via <rwenig=[email protected]> wrote:
I am running Linux Mint 22 Cinnamon and Fldigi version 4.2.06.09 and I'm
running into a problem.
After a bit of operation Fldigi will lock up. When I check top it tells
me Fldigi is using more than 100% CPU utilization. I have to kill and
restart Fldigi.
This happened with the stable version 4.2.06 and on another Linux Mint
computer. I have no problems on the Windows 11 computer.

Does anyone else have this issue and is there a way I can trouble shoot
this.

I have 7.7 gig of memory and 1 Terra Byte of storage.

73, Ron NY3J







Re: Fldigi Lockup

 

Hi Ron,

I run a RPI 4b running bookworm.? I had fldigi lockups.??

Are you opening FLMSG and leaving it open?? That gave me DIGI lockups.? I have configured FLDIGI? to open FLMSG upon receipt of a message.? DIGI hasn't locked up on me since I made that change.??

My digi config: configure | configure dialog | misc | NBEMS data file interface enable, open message folder not enabled, transfer direct not enabled, open with flmsg enabled, open in browser not enabled, the flmsg: field has the path to FLMSG executable, timeout is 2 seconds.??

if digi receives a message flmsg will open.? If I have a checksum?error, there will be a dialog box for that and the file name will be badfile.? If a second message arrives, I get a new flmsg window.? I had maybe 8 or 9 this morning, some with checksum errors.? If I want to save a badfile,?I scroll through the "received messages" window until I find the file name then save with that.??

Richard Jackson




On Thu, Nov 21, 2024 at 8:56?PM Ron NY3J via <rwenig=[email protected]> wrote:
I am running Linux Mint 22 Cinnamon and Fldigi version 4.2.06.09 and I'm
running into a problem.
After a bit of operation Fldigi will lock up. When I check top it tells
me Fldigi is using more than 100% CPU utilization. I have to kill and
restart Fldigi.
This happened with the stable version 4.2.06 and on another Linux Mint
computer. I have no problems on the Windows 11 computer.

Does anyone else have this issue and is there a way I can trouble shoot
this.

I have 7.7 gig of memory and 1 Terra Byte of storage.

73, Ron NY3J






Re: Fldigi Lockup

 

On Fri, Dec 13, 2024 at 12:43 PM, Bob Cameron, VK2YQA wrote:

At 30-60 minutes it may be another process (like from cron) doing "something" that affects. Might be worth a look at syslog or journal display when it next freezes. Also cat your $HOME/.xsession-errors or just run flrig in a console window.

Thanks Bob, that gives me a few things to look at. I also started flrig from a shell prompt, as you suggested. Now I'll just have to wait. :D
?
There's nothing in cron.d or cron.daily that looks potentially harmful, but I'll have to investigate them a bit more to be sure.

I had some strange flrig problems when the WiFi/cell modem kept resetting, I am assuming from the "interface up/down" scripts. That could have been proven by turning off the external network connection for a while.

You know, that reminds me of something in the past about ModemManager mucking with the serial ports. A couple of years ago, while hunting down a different problem on a different system, I did turn it off at one point but I don't remember if it helped or not. I'll have to look into that some more.
?
Thanks!
Steve K4RVA