Fldigi slow to respond

[rbduck]

I use Thetis, Fldigi and Fldigi UDP. I had a much earlier version of Fldigi which worked fine but was a CPU hog. 25-30% most of the time. I updated to version 4.2.06.17. The new version uses less than 1% utilization all the time. BUT, it is very slow to respond to frequency changes. If you click on a specific frequency, it works fine. If you use the VFO (mouse wheel) the frequency on the app will go to zero. In a second or two it catches the correct frequency on Fldigi. The old version never did this. A fast wheel spin would slide through the frequencies with no latency.

Has anyone had this issue or know what might be changed to eliminate it? I'm reading the Fldigi book , but keep falling asleep. May be a New Year's thing. Happy new year!

[w-u-2-o]

Ruben--I just upgraded my version of Fldigi to 4.2.0.6 (the release version, no .17 on the end). I can't duplicate your problem. However I may be setup differently from you. In particular I don't know what "Fldigi UDP" is.

In Fldigi I have rig control set up as follows:

Rig type "FlexRadio/ANAN PowerSDR/Thetis (Stable)
Device 127.0.0.1:1881
PTT via Hamlib command
Sideband Rig mode

The rest of it doesn't matter.

In Thetis I have the TCP/IP CAT server enabled with a bind port of 127.0.0.1:1881

You can, of course, use the default port number, there is no magic about using 1881.

Note that all app's that use a recent version of Hamlib can be set up this way, there's no longer any need for virtual serial ports.

[rbduck]

Thanks Scott. I've had this installed a few days and I didn't notice the issue until today. I'll keep digging and reading. I may learn something. I use it to talk between Thetis, the HFAUTO app and Fldigi. I bet some timing setting has changed somehow. By me? I hope not

I've yet to completely uninstall Fldigi and reload it.
Thanks again.

[KC2QMA]

I am interested in getting into digital modes and would like to get a basic fldigi setup with Thetis.
Is there a setup guide anywhere for setting up fldigi with Thetis.
Any help would be greatly appreciated

[rbduck]

Ruben--I just upgraded my version of Fldigi to 4.2.0.6 (the release version, no .17 on the end). I can't duplicate your problem. However I may be setup differently from you. In particular I don't know what "Fldigi UDP" is.

In Fldigi I have rig control set up as follows:

Rig type "FlexRadio/ANAN PowerSDR/Thetis (Stable)
Device 127.0.0.1:1881
PTT via Hamlib command
Sideband Rig mode

The rest of it doesn't matter.

In Thetis I have the TCP/IP CAT server enabled with a bind port of 127.0.0.1:1881

You can, of course, use the default port number, there is no magic about using 1881.

Note that all app's that use a recent version of Hamlib can be set up this way, there's no longer any need for virtual serial ports.

Scott,

Thank you fr your help. That is an interesting setup I have not considered. I will try that and see if I can get rid of the latency. I'll let you know how it goes.

[rbduck]

Ruben--I just upgraded my version of Fldigi to 4.2.0.6 (the release version, no .17 on the end). I can't duplicate your problem. However I may be setup differently from you. In particular I don't know what "Fldigi UDP" is.

In Fldigi I have rig control set up as follows:

Rig type "FlexRadio/ANAN PowerSDR/Thetis (Stable)
Device 127.0.0.1:1881
PTT via Hamlib command
Sideband Rig mode

The rest of it doesn't matter.

In Thetis I have the TCP/IP CAT server enabled with a bind port of 127.0.0.1:1881

You can, of course, use the default port number, there is no magic about using 1881.

Note that all app's that use a recent version of Hamlib can be set up this way, there's no longer any need for virtual serial ports.

Scott,
I finally had an opportunity to try your suggestion. There must be something magic in Port 1881. When I enter that port and select "reconnect", Fldigi completely shuts down and disappears.

[w-u-2-o]

Did you try the default port number in Thetis instead?

[rbduck]

Did you try the default port number in Thetis instead?

I tried the default port also. I'll get a handle on this or bust. I also tried numerous other ports.

(correction)I got it under Com 15. The latency in Fldigi has disappeared. Thanks again Scott. I just had to keep at it until something worked. The hamlib page only uses com ports. The result was very little latency.

[w-u-2-o]

Glad you got it working!

The hamlib page does support TCP/IP. All app's that use hamlib support TCP/IP as long as they use a version of hamlib newer than June 2022. See this topic: viewtopic.php?f=22&t=4249&p=28188 (thank you Mike, W9MDB!)

You may have configured it wrong, or maybe there is a Windows firewall issue. Here are some screenshots from my setup.

Capture.JPG (106.75 KiB) Viewed 1582 times

Capture2.JPG (85.78 KiB) Viewed 1582 times

[rbduck]

Is Hamlib a separate app? Sorry for the questions. I'm new to the digital scene.

(I found Hamlib) I thought I found it anyway. I downloaded and installed ver 4.6. There is no executable or icon. Is this right?

[w-u-2-o]

Hamlib is a software library that can be used by app developers to enable CAT comm's with a huge list of radios. It is not a separate app. Hamlib is used by Fldigi, WSJT-X and numerous other digi and logging app's.

Fldigi offers a choice of flrig, hamlib, and rigcat. Here's my setup in Fldigi.

Capture.JPG (92.66 KiB) Viewed 1554 times

[rbduck]

Hamlib is a software library that can be used by app developers to enable CAT comm's with a huge list of radios. It is not a separate app. Hamlib is used by Fldigi, WSJT-X and numerous other digi and logging app's.

Fldigi offers a choice of flrig, hamlib, and rigcat. Here's my setup in Fldigi.

Capture.JPG

Oh I see and understand. That being said I see in your previous captures the Thetis page for configuring the IP address. Where is the second capture from?

Sometimes I feel like that dumb duck to the left.

[w-u-2-o]

I posted screenshots from Thetis, WSJT-X, and Fldigi.

[rbduck]

I posted screenshots from Thetis, WSJT-X, and Fldigi.

I see. Thank you for everything you do for the ham community.