Depends on a lot of things. Like who placed the spot and where that person is located. Spots placed from a European station may not be heard at your location. My DX Cluster filters are set to only

I’d not considered a port conflict. Best advice yet. Thanks!!!!

Kevin, You may be unintentionally trying to use one port on the 991 for both applications and getting a port conflict. The FT-991A has two independent ports on the back, one USB and the other serial.

I believe that I got mine working using OmniRig. However my setup is a bit different... I am using Win4Yaesu to run multiple programs concurrently, and couldn't get JS8CALL to work with it either. I

JS8Call has hamlib built-in statically -- you can't upgrade Hamlib alone. It has a very old version of Hamlib Mike W9MDB

I've been through every setting on my FT-991A, JS8, FLDIGI and FLRIG and still I cannot have FLDIGI and JS8 open at the same time. Even when selecting FLRIG as the "radio" in JS8, it keeps throwing a

That will work for the instance of \n. You would need other escape sequences for \t \b etc. Code review is always good for the gray matter. 😉 The

Thank you A LOT Dave for digging this deeply in the issue. I was going crazy trying to find where the issue was within the Python libraries, etc. Good to know that it is a design choice of FLDIGI,

I modified the event logger in fldigi to show the hex characters received from the Python interpreter This is on a Linux machine. Behavior is idential

You might want to learn how to build from source: https://sourceforge.net/p/fldigi/wiki/osx_howto/ that will give you the ability to execute using lldb, the MacOS

It is the file: fldigi-4.1.23_BS.dmg downloaded from https://sourceforge.net/projects/fldigi/files/fldigi/ >> cksum fldigi-4.1.23_BS.dmg 2046818309 14831010 fldigi-4.1.23_BS.dmg

Python (and all other software) is will interpret \n as either LF or CR/LF -- it's OS dependent \n is "new line" -- whatever that takes on the device being used. Windows is well known to need CR/LF

Are you building the fldig app from source or using one of the dmg's ? David On 11/30/22 06:59, makkiato via groups.io wrote:

Thanks Michael but that is not the point of my question. My goal is to have an arbitrary binary sequence as input, and to send it out *as is* with FLDIGI, without any modifications. Remark: Of

Use \r instead of \n Mike W9MDB On Wednesday, November 30, 2022 at 06:48:22 AM CST, makkiato via groups.io

Thank you Dave for the kind reply. I am using FLDIGI (ver. 4.1.23, the latest version) for MacOSX. I am interacting with the XMLRPC using Python3. The following sequence of commands (from standard

fldigi does not convert the \n to \r\n during execution of the text.add_tx_bytes method. What software are you using to create the string message send

Hello, I am trying to play a bit with FLDIGI's RPC. I see a strange behaviour. Basically when adding a string of BYTES to the TX-widget, using the method "text.add_tx_bytes" Any occurrence of the

Great! Enjoy. It's a mystery, but sometimes the config file gets corrupted and then strange things happen. 73, Cliff, AE5ZA

Yep. That worked! Thanks KO4HNB Tom