开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Linuxham
  2. Messages
Expanded Topics Messages Polls
Date
Re: Teamviewer on Debian Trixie etc.

 

I found a website on the Linux Mint group that set up?an X11 server on my portable machine. I'm able to log in via VNC. Do you think I can find it on my 75-year-old brain?

73

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU ? VOICE


Winlink:?va7dgp@...
Subject://wl2k ? ? ? ? ?

ALLSTAR ?530780
Hamshack Hotline
5971
Mid-Island Phone Mesh
2210
2232

? ? ? ? ? ? ? ? ? ?


On Thu, Apr 24, 2025 at 5:40?AM Rick KD8WCK via <rademattia=sbcglobal.net@groups.io> wrote:
I concur with Neil. When I installed Teamviewer on Ubuntu I was horrified at the background processes that it installed silently. It took hours to remove all the garbage.

I would not recommend Teamviewer on any platform.






--
Don Poaps
VA7DGP: data
VA7QU:? ?voice
Re: Teamviewer on Debian Trixie etc.

 

I concur with Neil. When I installed Teamviewer on Ubuntu I was horrified at the background processes that it installed silently. It took hours to remove all the garbage.

I would not recommend Teamviewer on any platform.
Re: Teamviewer on Debian Trixie etc.

 

or dwagent by dwservice.net

73
Danny, K5CG
HH 550-0609
SKCC 14257

From: "Neil Hanlon, N1HAN" <neil@...>
To: "linuxham" <linuxham@groups.io>
Sent: Wednesday, April 23, 2025 6:10:18 AM
Subject: Re: [linuxham] Teamviewer on Debian Trixie etc.

Adrian, all,

I would advise against using TeamViewer, as it currently has concerning security issues, and might as well be malware.

I suggest using RustDesk instead. It's an open-source alternative that you can trust.

73, Neil



On Wed, Apr 23, 2025, 07:01 Adrian Fewster, VK4TUX via <vk4tux=gmail.com@groups.io> wrote:
Had to install Teamviewer to help a ham friend the other day, but got caught out by the policykit-1 dependency not available, as Trixie now uses pkexec & polkitd instead.
?
I had to rebuild the latest debian/Ubuntu deb from Teamviewer ;
?
adrian@debian:~$ ?cd /home/adrian/Downloads
adrian@debian:~/Downloads$ dpkg-deb --raw-extract teamviewer_15.64.3_amd64.deb teamviewer
adrian@debian:~/Downloads$ sed -i "s/policykit-1/pkexec, polkitd/" teamviewer/DEBIAN/control
adrian@debian:~/Downloads$ fakeroot -- dpkg-deb --build teamviewer teamviewer-rebuilt.deb
dpkg-deb: building package 'teamviewer' in 'teamviewer-rebuilt.deb'.
adrian@debian:~/Downloads$ sudo apt install ./teamviewer-rebuilt.deb
Note, selecting 'teamviewer' instead of './teamviewer-rebuilt.deb'
Installing:
?teamviewer

Summary:
?Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 1
?Download size: 0 B / 123 MB
?Space needed: 413 MB / 1,568 GB available

Get:1 /home/adrian/Downloads/teamviewer-rebuilt.deb teamviewer amd64 15.64.3 [123 MB]
Selecting previously unselected package teamviewer.
(Reading database ... 628311 files and directories currently installed.)
Preparing to unpack .../teamviewer-rebuilt.deb ...
Unpacking teamviewer (15.64.3) ...
Setting up teamviewer (15.64.3) ...
Processing triggers for mailcap (3.74) ...
Processing triggers for desktop-file-utils (0.28-1) ...
Processing triggers for hicolor-icon-theme (0.18-2) ...
Processing triggers for gnome-menus (3.36.0-2) ...
Processing triggers for mate-menus (1.26.1-1) ...
Processing triggers for dbus (1.16.2-2) ...
adrian@debian:~/Downloads$ ?


This executed fine and works well.
?
73
?
vk4tux
Re: Teamviewer on Debian Trixie etc.

 

Adrian, all,

I would advise against using TeamViewer, as it currently has concerning security issues, and might as well be malware.

I suggest using RustDesk instead. It's an open-source alternative that you can trust.

73, Neil



On Wed, Apr 23, 2025, 07:01 Adrian Fewster, VK4TUX via <vk4tux=gmail.com@groups.io> wrote:
Had to install Teamviewer to help a ham friend the other day, but got caught out by the policykit-1 dependency not available, as Trixie now uses pkexec & polkitd instead.
?
I had to rebuild the latest debian/Ubuntu deb from Teamviewer ;
?
adrian@debian:~$ ?cd /home/adrian/Downloads
adrian@debian:~/Downloads$ dpkg-deb --raw-extract teamviewer_15.64.3_amd64.deb teamviewer
adrian@debian:~/Downloads$ sed -i "s/policykit-1/pkexec, polkitd/" teamviewer/DEBIAN/control
adrian@debian:~/Downloads$ fakeroot -- dpkg-deb --build teamviewer teamviewer-rebuilt.deb
dpkg-deb: building package 'teamviewer' in 'teamviewer-rebuilt.deb'.
adrian@debian:~/Downloads$ sudo apt install ./teamviewer-rebuilt.deb
Note, selecting 'teamviewer' instead of './teamviewer-rebuilt.deb'
Installing:
?teamviewer

Summary:
?Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 1
?Download size: 0 B / 123 MB
?Space needed: 413 MB / 1,568 GB available

Get:1 /home/adrian/Downloads/teamviewer-rebuilt.deb teamviewer amd64 15.64.3 [123 MB]
Selecting previously unselected package teamviewer.
(Reading database ... 628311 files and directories currently installed.)
Preparing to unpack .../teamviewer-rebuilt.deb ...
Unpacking teamviewer (15.64.3) ...
Setting up teamviewer (15.64.3) ...
Processing triggers for mailcap (3.74) ...
Processing triggers for desktop-file-utils (0.28-1) ...
Processing triggers for hicolor-icon-theme (0.18-2) ...
Processing triggers for gnome-menus (3.36.0-2) ...
Processing triggers for mate-menus (1.26.1-1) ...
Processing triggers for dbus (1.16.2-2) ...
adrian@debian:~/Downloads$ ?


This executed fine and works well.
?
73
?
vk4tux
CTY-3512 Country Files - 22 April 2025

 

The Country (CTY) Files were updated on 22 April 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:

22 April 2025 (CTY-3512)
VER20250422, Version entity is Vanuatu, YJ

Added/changed Entities/Prefixes/Callsigns:

* TX5U is French Polynesia, FO
* TO974REF is Reunion Island, FR
* MM0PLX/P is Scotland, GM
* GB1GLJ and GB8MD are both Wales, GW
* IR0IABJ is Sardinia, IS
* KQ6KC is in CQ zone 4, not CQ zone 5
* AB1U, K9WWW, KC0BRA, KC9C, KQ2X, N5NPD, W0DNR, W0OIT and WE8RV are all United States, K in CQ zone 3, ITU zone 6
* N7ML and W0YKS are both United States, K in CQ zone 4, ITU zone 6
* AA7TJ, AB9TS, K1CPT, K2TKB, K3LKS, K6LJ, K7TRT, K9LTX, K9TF, KA8GIM,
KC9GNK, KC9JIK, KD9OFG, KF7HIL, KK7VXK, KN4SLP, N9DMT, N9SEO, NA9DM, NE9U,
W2EH, W9BED, W9JAB, WA7AFV, WJ9O and WT9Q are all United States, K in CQ zone 4, ITU zone 7
* AE4JM, AG4H, K3JWI, K4AZE, K4WNY, KB3KYH, KD4CXE, KE4VQM, KG5UN,
KK4PC, KM4CRB, KM4ECH, KM4HQE, KO4OSL, KO4VJN, KQ4FBF, KQ4MYC, KQ4RLN,
KW4OV, KY4DMD, N4KWX, N6XBP, NB6O, NT4M, W4BQN, W4FCL, W4FXZ, W4JHV, W4YPW,
W4YTO, W5SGL, W6JSL, W7BAZ, W7XB, WA6GYC, WB4MSN, WF5X and WN1R are all United States, K in CQ zone 4, ITU zone 8
* AD7JL, AI5SM, AJ6TE, K0CHA, K0DVH, K5JSG, K5KIP, K6HLC, KA7HBH, KB6QPI,
KB8NUF, KC9LC, KE8AE, KE8ZZH, KI8GM, KM7SAD, N0CK, N0GJR, N6ZFO, N8JAA,
N8OYY, N8SLT, N8XT, N9MXI, W8KXW, WD9GMK, WF8D and WT9Y are all United States, K in CQ zone 5, ITU zone 8
* KN4FTF is Hawaii, KH6
* K7VRK and KD3AXV are both Alaska, KL
* 5P0WARD/C, 5P0WARD/D, 5P0WARD/F, 5P0WARD/G, 5P0WARD/H, 5P0WARD/I,
5P0WARD/J, 5P0WARD/K, 5P0WARD/U, 5P0WARD/V and 5P0WARD/W are all Denmark, OZ
* TA1AO/4 is Asiatic Turkey, TA
* R8FF/P and RV9CDW/6 are both European Russia, UA
* R0KA/9 is Asiatic Russia, UA9 in CQ zone 18
* RX0TX/P is Asiatic Russia, UA9 in CQ zone 18, ITU zone 32
* VK7IAN/4 is Australia, VK in ITU zone 55

Removed Entities/Prefixes/Callsigns:

* EM1UTQ and RI1ANV in Antarctica, CE9
* EA9ADD in Spain, EA
* TO3Z in Guadeloupe, FG
* GS4WAB/P in Scotland, GM
* IQ0AK/P in Sardinia, IS
* AB9NE, AC4CA, AC4ZH, AE0CW, AI4LU, K0EMT, K0SB, K1NA, K1WTF, K2OO,
K3IFR, K3PS, K3TD, K4NO, K4PKM, K4YA, K5WK, K5WP, K5XI, K6ND, K7TAR, KB9JJA,
KC8GCR, KD5DD, KE5MHV, KI8I, KJ5AZV, KM4CRC, KO4O, KO4YIN, KS9W, N3BUO,
N3CY, N3LHQ, N4KCD, N7DH, N8ELA, N8JRT, N8LA, N9OHW, NG5U, NJ0U, NN7W,
W0MHK, W0SX, W3GW, W4BCG, W8MC, W8NUD, WA2IVD, WA4KY, WA4MLD, WA9KIA, WB4GHZ,
WM4U and WQ3U in United States, K
* KB7YEJ, KJ7UFK, N8YAK and W8OES in Alaska, KL
* K4W in Puerto Rico, KP4
* R25BLIN and UB8M/1 in European Russia, UA
* VK9YB in Norfolk Island, VK9N

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>,

Re: FLDIGI - RTTY output to Serial Device

 

This is untested, but give it a try. It uses the XML interface that is included in fldigi (and I think it was made so that you could do exactly what you are wanting to do!)
?

Make sure you have:

  • Python 3

  • pyserial installed (pip install pyserial)

  • Fldigi running, in RTTY mode, with XML-RPC enabled

  • /dev/ttyUSB0 accessible, permissions set (you may need to add your user to the dialout group)

?
Python script follows:
?
import xmlrpc.client
import serial
import time
# Connect to Fldigi XML-RPC
fldigi = xmlrpc.client.ServerProxy("http://localhost:7362")
# Configure serial port for ASR33
ser = serial.Serial(
? ? '/dev/ttyUSB0',
? ? baudrate=110, ? ? ? ? # ASR33 typical speed
? ? bytesize=serial.SEVENBITS,
? ? parity=serial.PARITY_NONE,
? ? stopbits=serial.STOPBITS_TWO,
? ? timeout=1
)
def main():
? ? print("Starting RTTY-to-ASR33 relay...")
? ? previous_text = ""
? ? try:
? ? ? ? while True:
? ? ? ? ? ? # Get current received text from Fldigi
? ? ? ? ? ? current_text = fldigi.main.get_rx_text()
? ? ? ? ? ? # Find new characters
? ? ? ? ? ? if current_text != previous_text:
? ? ? ? ? ? ? ? new_chars = current_text[len(previous_text):]
? ? ? ? ? ? ? ? for char in new_chars:
? ? ? ? ? ? ? ? ? ? if char.isprintable() or char in '\r\n':
? ? ? ? ? ? ? ? ? ? ? ? print(f"Sending: {repr(char)}")
? ? ? ? ? ? ? ? ? ? ? ? ser.write(char.encode('ascii', errors='ignore'))
? ? ? ? ? ? ? ? ? ? ? ? ser.flush()
? ? ? ? ? ? ? ? ? ? ? ? time.sleep(0.1) ?# Adjust for ASR33 mechanical response
? ? ? ? ? ? ? ? previous_text = current_text
? ? ? ? ? ? time.sleep(0.1) ?# Polling interval
? ? except KeyboardInterrupt:
? ? ? ? print("\nStopping...")
? ? finally:
? ? ? ? ser.close()
if __name__ == "__main__":
? ? main()
?
Re: kcat (kachina 505dsp) used to play nice with fldigi but now not so much

 

OK after some head scratching and deep reading, the fix is simple. kcat uses obsolete method main.get_frequency. The new method is rig.get_frequency. I changed that in src/support/xml_io.cxx and now all is well.
?
Dave W1HKJ - below is the patch. Just a two line change.
Hey, would you be willing to put kcat up on github with your other stuff?
?
73 - Bill N7DZ
?
diff --git a/src/support/xml_io.cxx b/src/support/xml_io.cxx
index 6397de8..d2464e5 100644
--- a/src/support/xml_io.cxx
+++ b/src/support/xml_io.cxx
@@ -44,7 +44,7 @@ static const char* rig_take_control ? ? = "rig.take_control";
?static const char* rig_release_control ?= "rig.release_control";
?
?// these are get/set
-static const char* main_get_frequency ? = "main.get_frequency";
+static const char* rig_get_frequency ? = "rig.get_frequency";
?static const char* main_set_wf_sideband = "main.set_wf_sideband";
?static const char* rig_set_frequency ? ?= "rig.set_frequency";
?static const char* rig_set_mode ? ? ? ? = "rig.set_mode";
@@ -83,7 +83,7 @@ void open_rig_xmlrpc()
? ? ? ? XmlRpcValue nil(XmlRpc::nil);
? ? ? ? status_query = new XmlRpcValue;
? ? ? ? const char* status_methods[] = {
- ? ? ? ? ? ? ? main_get_trx_state, main_get_frequency,
+ ? ? ? ? ? ? ? main_get_trx_state, rig_get_frequency,
? ? ? ? ? ? ? ? rig_get_mode, rig_get_bandwidth
? ? ? ? };
? ? ? ? for (size_t i = 0; i < sizeof(status_methods)/sizeof(*status_methods); i++) {
?
Re: FLDIGI - RTTY output to Serial Device

 

Once the port is configured, could you perhaps ln -s the file .fldigi/talk/output.txt in your home directory to your serial device /dev/ttyUSB0? Everything's a file in Linux.
Re: FLDIGI - RTTY output to Serial Device

 

开云体育

In the Misc section of the FLDIGI configuration you can choose 'RX text capture' and enable 'rx text stream' in the window that pops up.?
That stream goes by default to .fldigi/talk/output.txt in your home directory. The best is to write a little script in bash or another of your?
favourite languages as you need to set the serial port speed, open output.txt and read it in a loop to see or new characters are appended?
to that file and copy/output those to your serial device.

Boudewijn VE3TOK


On 4/18/25 13:48, Bob Roswell, KC3KCS via groups.io wrote:

Nice!? That is a bit easier to use, and I did not find it.? Any way to redirect that directly to the serial port? (USB)

?

From: linuxham@groups.io <linuxham@groups.io> On Behalf Of David Ranch, KI6ZHD via groups.io
Sent: Friday, April 18, 2025 1:29 PM
To: linuxham@groups.io
Subject: Re: [linuxham] FLDIGI - RTTY output to Serial Device

?

You don't often get email from linuxham-fld@....



Look at the $HOME/.fldigi/talk/textout.txt file

--David
KI6ZHD

On 04/18/2025 10:02 AM, Bob Roswell, KC3KCS via wrote:

Greetings:

?

I have setup an RTTY -> phone -> modem ->ASR-33 demo here at the Computer Museum @ System Source (Hunt Valley, MD) ()

?

I am taking an RTTY Feed, (for example ) and feeding the sound into a telephone handset.

?

When the handset is in a modem (I am just using the modem microphone since I don't think we have a modem for 45baud, Baudot) the sound goes into the sound card and is decoded by fldigi.

?

I have not figured out how to easily get the text (which appears on fldigi screen) to the serial port which goes to the teletype.

?

I have hacked it by logging the RTTY text to a file, and then I am using a Python script to clean up the log file and print on the ASR-33.? Hoping to find a way to simplify and pipe the rtty signal directly to /dev/ttyUSB0.

?

Thanks

Bob

?

(More details, not really important for the question, but here is the setup)

Raspberry Pi 5, with USB sound dongle:

mplayer gets rtty feed.? Sound redirected from HDMI to USB Sound Dongle that is wired to old school Dial-up telephone.? When phone goes off hook, we hear the RTTY signal from the phone earpiece.

Earpiece is set in acoustic modem.? just used the microphone which is wired back into microphone input on USB sound dongle.? Fldigi decodes RTTY, and logs to /home/pi/.fldigi/fldigiyyyymmdd.log

Python opens the file, skips two the end, the cuts the beginning of each line which logging info, and it sends the ASCII text to a USB->Serial Dongle.? ASR-33 has a 3rd party card to take RS-232 as input instead of Current loop.

?

?

?

?

-- 
There is nothing permanent except change
 
                                Heraclitus

Re: FLDIGI - RTTY output to Serial Device

 

开云体育



Nice!? That is a bit easier to use, and I did not find it.? Any way to redirect that directly to the serial port? (USB)


Sure:
?? cat textout.txt > /dev/ttyUSB0

--David
KI6ZHD


?

From: linuxham@groups.io <linuxham@groups.io> On Behalf Of David Ranch, KI6ZHD via groups.io
Sent: Friday, April 18, 2025 1:29 PM
To: linuxham@groups.io
Subject: Re: [linuxham] FLDIGI - RTTY output to Serial Device

?

You don't often get email from linuxham-fld@....



Look at the $HOME/.fldigi/talk/textout.txt file

--David
KI6ZHD

On 04/18/2025 10:02 AM, Bob Roswell, KC3KCS via wrote:

Greetings:

?

I have setup an RTTY -> phone -> modem ->ASR-33 demo here at the Computer Museum @ System Source (Hunt Valley, MD) ()

?

I am taking an RTTY Feed, (for example ) and feeding the sound into a telephone handset.

?

When the handset is in a modem (I am just using the modem microphone since I don't think we have a modem for 45baud, Baudot) the sound goes into the sound card and is decoded by fldigi.

?

I have not figured out how to easily get the text (which appears on fldigi screen) to the serial port which goes to the teletype.

?

I have hacked it by logging the RTTY text to a file, and then I am using a Python script to clean up the log file and print on the ASR-33.? Hoping to find a way to simplify and pipe the rtty signal directly to /dev/ttyUSB0.

?

Thanks

Bob

?

(More details, not really important for the question, but here is the setup)

Raspberry Pi 5, with USB sound dongle:

mplayer gets rtty feed.? Sound redirected from HDMI to USB Sound Dongle that is wired to old school Dial-up telephone.? When phone goes off hook, we hear the RTTY signal from the phone earpiece.

Earpiece is set in acoustic modem.? just used the microphone which is wired back into microphone input on USB sound dongle.? Fldigi decodes RTTY, and logs to /home/pi/.fldigi/fldigiyyyymmdd.log

Python opens the file, skips two the end, the cuts the beginning of each line which logging info, and it sends the ASCII text to a USB->Serial Dongle.? ASR-33 has a 3rd party card to take RS-232 as input instead of Current loop.

?

?

?

?
Re: FLDIGI - RTTY output to Serial Device

 

开云体育

Nice!? That is a bit easier to use, and I did not find it.? Any way to redirect that directly to the serial port? (USB)

?

From: linuxham@groups.io <linuxham@groups.io> On Behalf Of David Ranch, KI6ZHD via groups.io
Sent: Friday, April 18, 2025 1:29 PM
To: linuxham@groups.io
Subject: Re: [linuxham] FLDIGI - RTTY output to Serial Device

?

You don't often get email from linuxham-fld@....


Look at the $HOME/.fldigi/talk/textout.txt file

--David
KI6ZHD

On 04/18/2025 10:02 AM, Bob Roswell, KC3KCS via wrote:

Greetings:

?

I have setup an RTTY -> phone -> modem ->ASR-33 demo here at the Computer Museum @ System Source (Hunt Valley, MD) ()

?

I am taking an RTTY Feed, (for example ) and feeding the sound into a telephone handset.

?

When the handset is in a modem (I am just using the modem microphone since I don't think we have a modem for 45baud, Baudot) the sound goes into the sound card and is decoded by fldigi.

?

I have not figured out how to easily get the text (which appears on fldigi screen) to the serial port which goes to the teletype.

?

I have hacked it by logging the RTTY text to a file, and then I am using a Python script to clean up the log file and print on the ASR-33.? Hoping to find a way to simplify and pipe the rtty signal directly to /dev/ttyUSB0.

?

Thanks

Bob

?

(More details, not really important for the question, but here is the setup)

Raspberry Pi 5, with USB sound dongle:

mplayer gets rtty feed.? Sound redirected from HDMI to USB Sound Dongle that is wired to old school Dial-up telephone.? When phone goes off hook, we hear the RTTY signal from the phone earpiece.

Earpiece is set in acoustic modem.? just used the microphone which is wired back into microphone input on USB sound dongle.? Fldigi decodes RTTY, and logs to /home/pi/.fldigi/fldigiyyyymmdd.log

Python opens the file, skips two the end, the cuts the beginning of each line which logging info, and it sends the ASCII text to a USB->Serial Dongle.? ASR-33 has a 3rd party card to take RS-232 as input instead of Current loop.

?

?

?

?
Re: FLDIGI - RTTY output to Serial Device

 

开云体育


Look at the $HOME/.fldigi/talk/textout.txt file

--David
KI6ZHD


On 04/18/2025 10:02 AM, Bob Roswell, KC3KCS via groups.io wrote:

Greetings:
?
I have setup an RTTY -> phone -> modem ->ASR-33 demo here at the Computer Museum @ System Source (Hunt Valley, MD) ()
?
I am taking an RTTY Feed, (for example ) and feeding the sound into a telephone handset.
?
When the handset is in a modem (I am just using the modem microphone since I don't think we have a modem for 45baud, Baudot) the sound goes into the sound card and is decoded by fldigi.
?
I have not figured out how to easily get the text (which appears on fldigi screen) to the serial port which goes to the teletype.
?
I have hacked it by logging the RTTY text to a file, and then I am using a Python script to clean up the log file and print on the ASR-33.? Hoping to find a way to simplify and pipe the rtty signal directly to /dev/ttyUSB0.
?
Thanks
Bob
?
(More details, not really important for the question, but here is the setup)
Raspberry Pi 5, with USB sound dongle:
mplayer gets rtty feed.? Sound redirected from HDMI to USB Sound Dongle that is wired to old school Dial-up telephone.? When phone goes off hook, we hear the RTTY signal from the phone earpiece.
Earpiece is set in acoustic modem.? just used the microphone which is wired back into microphone input on USB sound dongle.? Fldigi decodes RTTY, and logs to /home/pi/.fldigi/fldigiyyyymmdd.log
Python opens the file, skips two the end, the cuts the beginning of each line which logging info, and it sends the ASCII text to a USB->Serial Dongle.? ASR-33 has a 3rd party card to take RS-232 as input instead of Current loop.
?
?
?
FLDIGI - RTTY output to Serial Device

 

Greetings:
?
I have setup an RTTY -> phone -> modem ->ASR-33 demo here at the Computer Museum @ System Source (Hunt Valley, MD) ()
?
I am taking an RTTY Feed, (for example ) and feeding the sound into a telephone handset.
?
When the handset is in a modem (I am just using the modem microphone since I don't think we have a modem for 45baud, Baudot) the sound goes into the sound card and is decoded by fldigi.
?
I have not figured out how to easily get the text (which appears on fldigi screen) to the serial port which goes to the teletype.
?
I have hacked it by logging the RTTY text to a file, and then I am using a Python script to clean up the log file and print on the ASR-33.? Hoping to find a way to simplify and pipe the rtty signal directly to /dev/ttyUSB0.
?
Thanks
Bob
?
(More details, not really important for the question, but here is the setup)
Raspberry Pi 5, with USB sound dongle:
mplayer gets rtty feed.? Sound redirected from HDMI to USB Sound Dongle that is wired to old school Dial-up telephone.? When phone goes off hook, we hear the RTTY signal from the phone earpiece.
Earpiece is set in acoustic modem.? just used the microphone which is wired back into microphone input on USB sound dongle.? Fldigi decodes RTTY, and logs to /home/pi/.fldigi/fldigiyyyymmdd.log
Python opens the file, skips two the end, the cuts the beginning of each line which logging info, and it sends the ASCII text to a USB->Serial Dongle.? ASR-33 has a 3rd party card to take RS-232 as input instead of Current loop.
?
?
?
Re: kcat (kachina 505dsp) used to play nice with fldigi but now not so much

 

Tried a couple earlier versions, including 4.1.17 from 2020. Same behavior as the newest version. So I guess it's nothing in the new code that broke it. And maybe I'm dreaming that it ever worked...
?
Pasted below are a few log lines that show the behavior. You can see that kcat is trying to increment the frequency up, but if I'm interpreting the log correctly, fldigi keeps pushing it back to 14070.?
Interesting lines underlined and bold.
?

I: [20:59:21] network/xmlrpc.cxx : 2232 : execute
? ? rig.get_freq: 14070000.000000
V: [20:59:21] network/xmlrpc.cxx : 2365 : execute
? ? rig.get_mode: LSB
V: [20:59:21] network/xmlrpc.cxx : 2450 : execute
? ? rig.get_bandwidth: 1000
V: [20:59:21] network/xmlrpc.cxx : 2215 : execute
? ? rig.set_frequency: 14071000
V: [20:59:21] network/xmlrpc.cxx : 1909 : execute
? ? main.get_trx_state: RX
I: [20:59:21] network/xmlrpc.cxx : 2232 : execute
? ? rig.get_freq: 14070000.000000
V: [20:59:21] network/xmlrpc.cxx : 2365 : execute
? ? rig.get_mode: LSB
V: [20:59:21] network/xmlrpc.cxx : 2450 : execute
? ? rig.get_bandwidth: 1000
V: [20:59:21] network/xmlrpc.cxx : 2215 : execute
? ? rig.set_frequency: 14072000
V: [20:59:21] network/xmlrpc.cxx : 1909 : execute
? ? main.get_trx_state: RX
I: [20:59:21] network/xmlrpc.cxx : 2232 : execute
? ? rig.get_freq: 14070000.000000
V: [20:59:21] network/xmlrpc.cxx : 2365 : execute
? ? rig.get_mode: LSB
V: [20:59:21] network/xmlrpc.cxx : 2450 : execute
? ? rig.get_bandwidth: 1000
V: [20:59:22] network/xmlrpc.cxx : 2215 : execute
? ? rig.set_frequency: 14073000
V: [20:59:22] network/xmlrpc.cxx : 1909 : execute
? ? main.get_trx_state: RX
?
and so on
?
Bill N7DZ
Re: Fldigi 4.2.06.27 (was Re: [winfldigi] RX/RTX Character Set)

 

开云体育

Hi Dave.

Not seeing the accumulated logs (and a lot of other problems) maybe a result of that change some years ago to use $HOME/.fldigi/.fldigi when it was previously just $HOME/.fldigi

eg my older installation in $HOME/.fldigi/fldigi.prefs defines the macro files as;

last_macro_file:/home/xxxx/.fldigi/macros/macros.mdf

Whereas some experimental configs add an extra "'.fldigi". eg

last_macro_file:/home/xxxx/.fldigi.experimental/.fldigi/macros/macros.mdf

(The .nbems directory also gets put in the later .fldigi structure)

Also check fldigi_def.xml for every reference to a file/directory location, that is valid for your installation. Mine for example are;
<THOR_AVATAR_IMAGE_FILE>/home/xxxx/.fldigi/avatars/vk2yqa.png</THOR_AVATAR_IMAGE_FILE>
<CTYDAT_PATHNAME>/home/xxxx/.fldigi/</CTYDAT_PATHNAME>
<XMLRIGFILENAME>/home/xxxx/.fldigi/rigs/IC-9100-D.xml</XMLRIGFILENAME>
<LOGBOOKFILENAME>/home/xxxx/.fldigi/logs/logbook.adif</LOGBOOKFILENAME>
<WEFAXSAVEDIR>/home/xxxx/.fldigi/wefax/</WEFAXSAVEDIR>
<KML_SAVE_DIR>/home/xxxx/.fldigi/kml/</KML_SAVE_DIR>
<AUTO_PROG3_PATHNAME>/home/xxxx/bin/logsn3</AUTO_PROG3_PATHNAME>

Oh and make sure you haven't merged an old and new tree together. There would normally be nothing except .fldigi and .nbems directories within the newer $HOME/.fldigi one. Any mixing might explain the lack of logfile visibility too.

As an in initial check in a shell box, cd to the directory you want to check and;

find . -print

Then post the output here along with fldigi.prefs and fldigi_def.xml. Check that there is only one file of that name in your tree. (Pls verify nothing personal/private gets posted)

Hope this makes sense!

Cheers Bob VK2YQA

On 17/4/25 06:16, Dave, G?WBX via groups.io wrote:

Hi again.

OK, I've tried every which way and then some.

I can get the new .07 alpha to restore my station and operator details, the view window layout (including the "show all 48 macros" setting) etc.

But it still flatly refuses to use any pre existing macro definition file, or accumulated Log data file?

And yes, I know Linux is case sensitive.? Ive been copying the needed files "as is" between backup folders and the same location(s) in the new .fldigi folder tree.? (That the new .07 does create.? And I think that is the problem, it creates new, overwriting what was there.)

What do you need from me to debug this?

Or...? What specific instructions do you have to install an alpha, but retain the pre-existing settings and logs etc.

73.

Dave G0WBX.
Re: kcat (kachina 505dsp) used to play nice with fldigi but now not so much

 

I found Dave's archive of tarballs. I'll try some of those to see if going back fixes this.

kcat (kachina 505dsp) used to play nice with fldigi but now not so much

 

I use kcat all the time and it works great. I use fldigi only now and then. But I built fldigi from source yesterday, to get all the new-and-improved, all looked clean. But now doesn't work with kcat.
?
I wish I had tried this before blowing away my old fldigi. I can't say what version it was, or if for sure it would have worked yesterday. But it used to work.
?
fldigi version 4.2.06
kcat version 1.2.5
?
Sequence & Symptoms:
- start fldigi
- some alsa lib errors, JackShmReadWritePtr messages
- some complaints about not being able to open sockets
- But it starts up and shows a nice normal looking window.
- start kcat - no indicated issues
?
I start fldigi in a terminal window and after starting kcat I can see that the two are talking over the xmlrpc link, constant streaming of freq/band/mode messages in the fldigi terminal window that look ok.
Frequency, mode, bandwidth are the same in both gui windows.
If I change mode or bandwidth on kcat, fldigi tracks. Likewise if I change mode or bandwidth from fldigi, kcat tracks.
===> If I try to change frequency from kcat, it won't, meaning it briefly shows the changed frequency then jumps back.
===> If I change frequency from fldigi, fldigi updates the display as if normal, but nothing happens on the kcat end (stays stuck on same freq as when started).
If I close fldigi, kcat can then manage the frequency as normal. So it would seem fldigi is not allowing kcat to change frequency.
?
I think this setup worked a few months ago. kcat has not changed. fldigi has changed.?
I would try building a downlevel fldigi to test against but I don't know how, and can't find instructions.
?
Any suggestions appreciated.
?
Bill N7DZ
?
Re: Fldigi 4.2.06.27 (was Re: [winfldigi] RX/RTX Character Set)

 

开云体育

Hi again.

OK, I've tried every which way and then some.

I can get the new .07 alpha to restore my station and operator details, the view window layout (including the "show all 48 macros" setting) etc.

But it still flatly refuses to use any pre existing macro definition file, or accumulated Log data file?

And yes, I know Linux is case sensitive.? Ive been copying the needed files "as is" between backup folders and the same location(s) in the new .fldigi folder tree.? (That the new .07 does create.? And I think that is the problem, it creates new, overwriting what was there.)

What do you need from me to debug this?

Or...? What specific instructions do you have to install an alpha, but retain the pre-existing settings and logs etc.

73.

Dave G0WBX.
CTY-3511 Country Files - 12 April 2025

 

The Country (CTY) Files were updated on 12 April 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 April 2025 (CTY-3511)
VER20250412, Version entity is Balearic Islands, EA6

Added/changed Entities/Prefixes/Callsigns:

* II0GDF/9 and IQ6CC/9 are both Sicily, *IT9
* TO3E is Martinique, FM
* WC8L is in ITU zone 7, not ITU zone 8
* WC8L is in CQ zone 4, not CQ zone 5
* KH6KK is Guam, KH2
* KI7KPB and N6MHR are both Alaska, KL
* LW3EMP/I is Argentina, LU
* R1961AG, R1994YU, R1996VK, R2014NC and R80DGZ are all European Russia, UA
* VK/M0LEP/P is Australia, VK in CQ zone 29, ITU zone 58

Removed Entities/Prefixes/Callsigns:

* VK0AI in Antarctica, CE9
* GB0GGR and GB5AG in Scotland, GM
* K0DSC, KO4NOL and W0ERJ in United States, K
* KG7IAL and KG7JSU in Hawaii, KH6
* AG6PI and K7HJK in Alaska, KL
* N7BPT in Puerto Rico, KP4
* LU1VJK/V, LU5DLH/D, LU7ETZ/D, LU9EI/D, LW2EAS/D and LW6DR/D in Argentina, LU
* R0QAW/P and R4FBJ/0/P in Asiatic Russia, UA9
* UT1KY/WAP and UT7UA/WAP in Ukraine, UR
* LU1ZI in South Shetland Islands, VP8/h

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 kill when connect to FLdigi

 

When I connect fldigi to be controlled via flrig (ft-817), flrig closes unexpectedly. It even opens the window to report the problem via bugzilla.
?
I can only use Flrig if I am disconnected from FLdigi.
?
Fldigi:?
Enable Flrig xcvr Control with fldigi as client
Flrig PTT meus modem
?
Has anyone experienced this and managed to fix it?
?
Fedora 41 XFCE
Fldigi 4.2.06
Flrig 2.0.05
41 - 60 of 53997