Keyboard Shortcuts
Likes
- Linuxham
- Messages
Search
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Hi Dave,
?
Good point. I agree that we are probably looking for something obscure. I checked again, and there is definitely no space in that command line. Not sure it got there; maybe my OCR again.
?
[Desktop Entry]
Name=flamp (right radio) GenericName=Amateur Multicast Protocol Client/Server Comment=Amateur Radio Communications Exec=flamp -ti "Flamp (right radio)" --config-dir $HOME/.nbems-right --xmlrpc-server-port 7363 Icon=flamp Terminal=false Type=Application Categories=HamRadio; ?
pi@nexuspi:~ $ flamp -ti "Flamp (right radio)" --config-dir $HOME/.nbems-right --xmlrpc-server-port 7363
autosend 715 pi@nexuspi:~ $? ?
pi@nexuspi:~ $ netstat -an | grep 736
tcp ? ? ? ?0 ? ? ?0 0.0.0.0:7363 ? ? ? ? ? ?0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ?? tcp ? ? ? ?0 ? ? ?0 0.0.0.0:7362 ? ? ? ? ? ?0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ?? tcp ? ? ? ?0 ? ? ?0 127.0.0.1:50562 ? ? ? ? 127.0.0.1:7363 ? ? ? ? ?ESTABLISHED tcp ? ? ? ?0 ? ? ?0 127.0.0.1:7363 ? ? ? ? ?127.0.0.1:50562 ? ? ? ? ESTABLISHED unix ?3 ? ? ?[ ] ? ? ? ? STREAM ? ? CONNECTED ? ? 16736 ? ? pi@nexuspi:~ $? ?
Very mysterious. Thanks for having a look. I'm happy to do any further testing that you might find helpful. 73.
Chris Doutre KC9AD
? |
|
Re: Fldigi ver4.2.06 and 4.2.06.21
¿ªÔÆÌåÓýA CNAME DNS record would probably do it. Problem is that Dave may want the site hostname for something else, or he'd be giving it up and no longer have DNS authority over it. You may be able to get away with making a local host declaration
on your PC though ie directs to 72.52.250.187
(however you OS does it) On 13/3/25 20:31, Dave, G?WBX via
groups.io wrote:
|
|
Re: Fldigi ver4.2.06 and 4.2.06.21
¿ªÔÆÌåÓýThanks Bob VK2YQA. Re:-? "I'd suggest discarding 4.2.06.21 in favour of 4.2.06.24 for any further testing." I'll progress that today, and report back later I hope, though it's just been decided by "management" that I'm fetching and carrying furniture later today. Regards. Dave G0WBX. (PS: In other news, the old w1hkj.com site, sometimes redirects
to a UK Sundial website!?? I don't suppose Dave 'HKJ could arrange
for a proper auto redirect to his new .org site to be
implemented?)
|
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
On Wed, Mar 12, 2025 at 06:42 PM, Chris Doutre - KC9AD wrote:
Hi Chris,
?
One more thing -- is the space really there in the config-dir parameter, as quoted there (2x)?? It's shown as
?
$HOME/.nbems- right
?
and I think you want
?
$HOME/.nbems-right
?
and also in the Desktop file:
?
Exec=flamp -ti "Flamp (right radio)" --config-dir $HOME/.nbems- right --xmlrpc-server-port 7363
?
?
That is, before the "r" in "right". I'm not being pedantic here, nor nit-picking, but I figured we are looking for something non-obvious, so I am asking these questions.?
?
Thanks for posting all of your error messages and config files and so forth. It helps immensely when trying to troubleshoot!
?
Dave |
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Hi Dave, ? That space after the -- was a figment of my OCR software. Once I figured out how to copy and paste directly from Linux to Windows, I saw that the space wasn't actually there. So here's what the file actually looks like: ? [Desktop Entry] ? ?So, that desktop file is still not working, but when I enter that exact command, with or without the quotes, I get the same results. FLAMP starts, but shows ¡°NOT CONNECTED¡±. flamp -ti "Flamp (right radio)" --config-dir $HOME/.nbems- right --xmlrpc-server-port 7363 However, your comment got me thinking, ¡°What if there is something else wrong with that command?¡± So I did another test: Start FLDigi (left radio). pi@nexuspi:~ $ netstat -an | grep 736 tcp??????? 0????? 0 0.0.0.0:7363??????????? 0.0.0.0:*?????????????? LISTEN???? tcp??????? 0????? 0 0.0.0.0:7362??????????? 0.0.0.0:*?????????????? LISTEN???? pi@nexuspi:~ $
pi@nexuspi:~ $ i@nexuspi:~ $ flamp -ti flamp-right --config-dir $HOME/.nbems-right --xmlrpc-server-port 7363 ? FLAMP works like a champ, showing "CONNECTED" except that FLAMP (right) is transmitting on the (left) radio instance of FLDigi. Here¡¯s the netstat: pi@nexuspi:~ $ netstat -an | grep 736 ? So, I have something that works, but it still puzzles me.? ? PS: The "random inputs" was something I was typing myself to indicate that the software was ignoring my inputs. I guess I wasn't the clearest I could be on that. ? Anyway, thanks for your interest. So much to learn. 73. Chris Doutre KC9AD |
|
CTY-3508 Country Files - 12 March 2025
The Country (CTY) Files were updated on 12 March 2025:
For installation instructions, start at: Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: Here are the release notes: 12 March 2025 (CTY-3508) VER20250312, Version entity is Bangladesh, S2 Added/changed Entities/Prefixes/Callsigns: * EG60GURU is Spain, EA * TO1Q is Guadeloupe, FG * TX9A is Austral Islands, FO/a * FO/F4LYI is Marquesas Islands, FO/m * GS4WAB/P is Scotland, GM * KT4XL is United States, K in CQ zone 4, ITU zone 8 * NS9I is United States, K in CQ zone 5, ITU zone 8 * K6JPB and KZ7MFL are both Alaska, KL * LU9DCA/D is Argentina, LU * RA0QK/8 is Asiatic Russia, UA9 Removed Entities/Prefixes/Callsigns: * EA2EZ/P in Spain, EA * TX7W in Austral Islands, FO/a * TX100REF and TX7WW in Marquesas Islands, FO/m * KJ5APX in Hawaii, KH6 * R9FCS/4 and R9JQ/6 in European Russia, UA * RT2F/P in Kaliningrad, UA2 Though I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, |
|
flrig alpha and icom ic-7760
Hi,
I'm playing with this and, at first look, IC-7760 seems compatible with IC-7610 handling, so for any brave souls here is a patch to test: To be applied on top of git://git.code.sf.net/p/fldigi/flrig pu/df branch. ps. power levels are interpolated, so could incorrectly reflect real power -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org ) |
|
Re: Fldigi ver4.2.06 and 4.2.06.21
¿ªÔÆÌåÓýHi Dave AFC is not relevant to all modes. Back in the 4.2.06.alpha evolutions I mentioned to the forum that it wasn't working, but was indicating "on" with the multicarrier PSKR modems. RSID action was also involved as it kind of replaces AFC action. RSID Squelch and MFSK AFC were patched only last month. (see Changelog) ie 4.2.06.24 has some associated changes. As I recall that also involved "more" greying out of the AFC button when it wasn't active. I'd suggest discarding 4.2.06.21 in favour of 4.2.06.24 for any further testing. Cheers Bob VK2YQA On 13/3/25 03:43, Dave, G?WBX via
groups.io wrote:
|
|
Fldigi ver4.2.06 and 4.2.06.21
¿ªÔÆÌåÓýHi. Running on LMDE 6 all up-to-date, on a 4 core Intel platform with
8G of RAM. Fldigi 4.2.06.21 (alpha) has a buggy AFC feature. It's been flaky since I first tried it, but intermittently the control (lower right, under the T/R button) would be "Greyed Out" so unable to change it's state.? The "greyed out" LED sort of indicates AFC is disabled, but in truth it is enabled and causes problems with noisy MFSK signals, where it can wander off to a neighbouring QRM signal. Restarting Fldigi used to (most, but not all times) fix it, but now the control is permanently disabled, but the behind GUI AFC functionality is still running, and I'm unable to turn that off..
ver4.2.06 (release.)? It's AFC seems to mostly work as "normal".?? With no changes to the perfs files.?? That is, as configured, they both use the same files in the default location just fine, but the .21 Alpha version is very confused about if it has an enabled AFC control, or not.? Plus as above, when the on/off control is disabled, the AFC functionality is running! Everything else seems OK, as far as what I've used anyway.??
Though the logic of what modes allow the AFC to be used, I haven't
fathomed yet.
I can only conclude the AFC On/Off control Enable/Disable in 4.2.06.21 is buggy, so have reverted to the release version. 73. Dave G0WBX.
|
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Hi Chris,
?
I am glad it is working better. I know we are getting into the weeds a little, but looking at your command lines shown here, it seems that you have a space character between the double dash and the option, that is
?
-- config-dir
?
instead of
?
--config-dir
?
Am I?seeing that correctly?
?
These will, of course, have different meanings to the command line parser, which in the first case will see it as two separate arguments and probably fail. For many built-ins the double dash often means no more commands follow such as this (from man page):
?
grep -- -e filename.txt
?
This is how you search for "dash e" in a file instead of having grep think that you are telling it "-e".
?
Could I ask you to try it one more time with the " " removed between the "--" and the parameters? (Twice).? And I wonder if those are the 'random inputs' that the program is squawking about....
?
73,
Dave
? |
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
PROGRESS!!
?
First of all, thanks to everyone who chimed in on this. This is my first linuxham post and your responses made me feel really welcome.
Second, I am now on the air with FLAMP. Here's an update.
As a test, I switched to the left radio option, which uses the default xmlrpc port of 7362. FLAMP is now working perfectly, sort of.
Symptom 1: I still have the symptom where the menu button doesn't launch FLAMP. Symptom 2: However, I can launch FLAMP from the terminal window and it works perfectly. Symptom 3: The cli prompt does not return as long as FLAMP is running. In fact, I get update messages as FLAMP transmits files, so I assume this is normal: pi@nexuspi:~ $?flamp -ti "Flamp (left radio)" --config-dir $HOME/.nbems-left --xmlrpc-server-port 7362 autosend 715 Here is the netstat output while FLAMP is running: pi@nexuspi:~ $ netstat -an | grep -e 736
tcp ? ? ? ?0 ? ? ?0 0.0.0.0:7362 ? ? ? ? ? ?0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ?? tcp ? ? ? ?0 ? ? ?0 127.0.0.1:7362 ? ? ? ? ?127.0.0.1:60666 ? ? ? ? ESTABLISHED tcp ? ? ? ?0 ? ? ?0 127.0.0.1:48544 ? ? ? ? 127.0.0.1:7362 ? ? ? ? ?ESTABLISHED tcp ? ? ? ?0 ? ? ?0 127.0.0.1:7362 ? ? ? ? ?127.0.0.1:48544 ? ? ? ? ESTABLISHED tcp ? ? ? ?0 ? ? ?0 127.0.0.1:60666 ? ? ? ? 127.0.0.1:7362 ? ? ? ? ?ESTABLISHED pi@nexuspi:~ $ ?
Since I only have one radio connected to my Nexus DR-X, I can live without the right-radio option. So, I will keep the desktop file issue on the back burner for now and get back to OTA file transfers using FLAMP. 73 all, and thanks again.
?
Chris Doutre KC9AD
?
|
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
¿ªÔÆÌåÓýThanks. I just gave that a try, with a few variations, and they all seemed to work the same way. ? The FLAMP command is accepted, FLAMP starts, displays ¡°NOT CONNECTED¡± (with the correct window title bar text), and then seems to hang, waiting (for ?). The command line prompt does not re-appear. I can enter random text with no effect. When I enter ^C to terminate the command and retrieve the prompt, the FLAMP window closes. I have attached the debug.log. ? pi@nexuspi :~ $ flamp -title flamp-right -- config-dir /home/pi/. nbems-right -- xmlrpc-server-port 7363 ^C pi@nexuspi :~ $ flamp -title "flamp-right" -- config-dir /home/pi/.nbems-right -- xmlrpc-server-port 7363 ignored random input ^C pi@nexuspi :~ $ flamp -ti "Flamp (right radio)" -- config-dir /home/pi/.nbems-right -- xmlrpc-server-port 7363 ignored random input ^C pi@nexuspi :~ $ flamp -ti "Flamp (right radio)" -- config-dir /home/pi/.nbems-right -- xmlrpc-server-port 7363 ignored random input ^C pi@nexuspi :~ $ ? Thanks again. 73. Chris KC9AD ? ? From: [email protected] <[email protected]> On Behalf Of Dave, KZ1O via groups.io
Sent: Tuesday, March 11, 2025 1:54 PM To: [email protected] Subject: Re: [linuxham] New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not. ? Give it a try without those parentheses. They might be falsely interpreted by the shell. ? To be sure, make it flamp-right or something shorter, no spaces or special characters. (If it doesn't help, you can change it back.) ? ? |
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Give it a try without those parentheses. They might be falsely interpreted by the shell.
?
To be sure, make it flamp-right or something shorter, no spaces or special characters. (If it doesn't help, you can change it back.)
?
? |
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
¿ªÔÆÌåÓýI tried another test: ? Start FLDigi, leave it running, Start FLMsg, leave it running, ? Run netstat -an | grep -e 7362 -e 7363 Results: tcp??????? 0????? 0 0.0.0.0:7363??????????? 0.0.0.0:*?????????????? LISTEN???? tcp??????? 0????? 0 127.0.0.1:7363????????? 127.0.0.1:43990???????? ESTABLISHED tcp??????? 0????? 0 127.0.0.1:43990???????? 127.0.0.1:7363????????? ESTABLISHED ? Also, when I run flamp from the command line, I do not get the next cli prompt. flamp -ti "Flamp (right radio)" --config-dir $HOME/.nbems-right --xmlrpc-server-port 7363 ? Almost like there is a parameter missing from that command. ? Thanks again for any guidance. Chris KC9AD ? ? From: [email protected] <[email protected]> On Behalf Of David Ranch, KI6ZHD via groups.io
Sent: Monday, March 10, 2025 5:09 PM To: [email protected] Subject: Re: [linuxham] New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not. ?
|
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
David, thanks for getting back so soon. My responses are below.
?
On Mon, Mar 10, 2025 at 05:09 PM, David Ranch, KI6ZHD wrote:
netstat -an | grep -e 7362 -e 7363tcp ? ? ? ?0 ? ? ?0 0.0.0.0:7363 ? ? ? ? ? ?0.0.0.0:* ? ? ? ? ? ? ? LISTEN? ?
Yes, I start FLDigi first, then FLMsg, then (I try to start) FLAMP.
?
Chris Doutre KC9AD |
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
¿ªÔÆÌåÓýHello Chris,
Is Fldigi running when you run Flamp?? It's required.
That's not a shell script.. that's just a GUI menu definition for Flamp meant to be used by the LXDE desktop manager
Ok.. these are meaningful tests and results.? If Fldigi is running and you go to the terminal and run: ? netstat -an | grep -e 7362 -e 7363 Does it show any output?? As an alternative, if you have lsof installed, try running: ? sudo slof -nPi | grep fldigi and send us the output. --David KI6ZHD |
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
On Mon, Mar 10, 2025 at 04:11 PM, Chris Doutre - KC9AD wrote:
Here is the FLMsg desktop script: Correction: It should say:
Here is the FLDigi desktop script:
?
Sorry about that.
Chris KC9AD |
|
New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Hello All,
?
I'm a brand new member of linuxham. I'm a Linux "user", not really an admin of any kind.
?
I have been running the FLDigi suite under Linux on a Raspberry Pi for several years. I was using an old image that was given to me. It was perfectly functional until it wasn't. So I recently rebuilt the system from scratch using Steve Magnuson's method 1 (RPi Imager). ? (This procedure uses 32-bit Bullseye).
?
It took a while on my RPi 4, but it all seemed to go correctly. But this installation script has not been updated in years and Steve has left the building. So I am concerned that this old script may be building a system that is not compatible with newer versions of the FLDigi suite programs. Is there anyone who can inspect my scripts and see if they contain incorrect syntax? I would be eternally grateful for any guidance.
?
During testing, I noticed the following:
The system boots and runs normally.
Using the menu buttons, Fldigi starts and works perfectly; I am able to send FSQ and MT63.
Flmsg starts and runs perfectly. I am able to send a message using MT63.
FLAMP will not start. When I click the FLAMP menu option, nothing happens.
If I try to run the FLAMP (right radio) script from usr/share/applications directory, nothing happens. Here is the script:
?
[Desktop Entry]
Name=flamp (right radio)
GenericName=Amateur Multicast Protocol Client/Server Comment=Amateur Radio Communications Exec=flamp -ti "Flamp (right radio)" --config-dir $HOME/.nbems-right --xmlrpc-server-port 7363 Icon=flamp Terminal=false Type=Application Categories=HamRadio; ?
Also, if I run FLAMP from the terminal command line:
flamp -ti "Flamp (right radio)" --config-dir $HOME/.nbems-right --xmlrpc-server-port 7363
?
Then FLAMP will start but will display "NOT CONNECTED".
I tried changing the port to 7362 and restarting FLAMP, it started but still did not connect.
?
Here is the FLMsg desktop script:
[Desktop Entry]
Name=Fldigi (right radio) GenericName=Amateur Radio Digital Modem Comment=Amateur Radio Sound Card Communications Exec=sh -c '/usr/bin/trim-fldigi-log.sh "yesterday"; fldigi --config-dir /home/pi/.fldigi-right -title "Fldigi (right radio)" --flmsg-dir /home/pi/.nbems-right' Icon=fldigi Terminal=false Type=Application Categories=HamRadio; ?
Is this a known problem? Or should I be digging deeper? Thanks for any guidance. 73.
?
Chris Doutre KC9AD
|
|
Re: #flrig Switching from CW to FT8 leaves filter width at 500 Hz
#flrig
I was thinking about this. Why are we setting bandwidth for a rig like IC7300? The algorithm appears to set the bandwidth as follows: Have we seen this mode? Set the bandwidth to last time; Else set it to the default for that mode. The IC7300 remembers the filter and bandwidth for each mode even across being powered down. I, for one, would like to keep the bandwidth I've set for a mode. If I set a bandwidth of 3.6 kHz, I don't want flrig to change this back to the default 3.0 kHz next time I switch on. The CI-V command has a setting to use default filter when setting mode. Could this be used instead? 73 Phil GM3ZZA |
|
Re: #flrig Switching from CW to FT8 leaves filter width at 500 Hz
#flrig
All I can see is that the mode_bwA is getting corrupted when I change the CW bandwidth. The CW, CW-R, LSB, LSB-D, USB and USB-D values are all getting set to 9 (500 Hz). I set a breakpoint on IC7300.cx:def_bandwidth and peeked the values as I was changing mode from the dropdown list.
They also seem to be corrupted on the rig as well. But I need to devise a more rigorous experiment as I may be getting into a cycle of cause and effect. But it's time to start making Sunday dinner. I did notice that as I changed the bandwidth on the CW filter it went to the sharp edge filter from the smooth edge filter. This seemed to be the rig doing this. 73 Phil GM3ZZA |
Philip Rose, GM3ZZA