I have been doing digital on this rig and PC a long time.

To ensure the USB settings aren't confused with the PC mic and speaker, I renamed them to From_Rig and To_Rig.

I am fairly familiar since I run the same setup with my 7300 in Texas, the only difference here is the Digirig and the FT-891.

At this point I will try using a different rig control vs Flrig..

I am still confused by RTTY-L & U as RTTY is lower based on my experience..

The manual does not even address RTTY-L&U.

This is from the manual?

"You must operate your transceiver in the USB mode for the fldigi RTTY signal to be the correct polarity. If your transceiver is set to LSB then use the fldigi "Rev" button to reverse the sense of the mark and space signals."

Hello David,

Thank you, and what you describe is what I had (or rather would have) assumed, too! And it's the reason why I could not answer Kim's e-mail right away, when he stated, that he was entirely unable to switch this 'veering AFC' off, because the AFC button just is not active.


But for his recent SW Radiogram programs, Kim only used MFSK32 and MFSK64. So the chosen mode just cannot be the culprit anyways.


- - - - - -


I wondered, without knowing whether this might offer a clue, whether at some point (no idea, when) in the fldigi update history, when the per-mode-AFC-settings were introduced (Menu - Config - Misc - Save Parameters: AFC control), the AFC setting(s) storage may have been re-defined (to allow this individualized mode) in the config file, and that a later update may have gone astray between a (former) global and the (then) per-mode settings, possibly when the user updated fldigi skipping several revisions. Well, just an assumption, but even so, I cannot tell, what exactly may have gone wrong in Kim's case.


- - - - - -


On the other hand, I just tested fldigi ver4.2.06.24 (a separate 'thumb drive' style install), switching modes and even to the ones you have mentioned (DominoEX, Thor, FSQ, IFKP, MT63), the AFC Button NEVER greys out! In fact, it readily allows AFC ON/OFF clicking and toggles the 'light' state accordingly. This is not what I would have expected.


- - - - - -


Experiment (fldigi ver4.2.06.24):


I know quite well (and have experienced this listening to QSOs) what you mean regarding VFO chasing, but this is not what we had observed. Please take a moment and follow this example sequence, following a fresh fldigi launch:

0. Set the MFSK AFC LPF to 200, which should be the default anyway (Menu - Config - Modem - MFSK: 200).

1. Switch SQL OFF and pull the SQL slider all the way UP (top position!). I know this doesn't really make any sense, but I'll explain it below.

2. Do not feed any valid MFSK64 audio into fldigi, at least not within the catch range of the AFC, e.g. by keeping the level input audio low or off, any noise floor will do.

3. Switch to MFSK64 (visualizing the effect may be faster for such a fast mode).

4. Set the center frequency to 1500 Hz exactly.

5. Wait a minute. Some gibberish shows up in the Rx screen, nothing unusual.

6. Check the center frequency: it's unchanged at 1500 Hz, spot-on. Great!

7. Switch AFC ON.

8. Wait a minute. More gibberish shows up in the Rx screen, nothing unusual.

9. Check the center frequency: see what I mean? No? Right, it's still unchanged at 1500 Hz, spot-on, and doesn't move an inch. Still great, just as expected!

10. Now pull the SQL slider all the way DOWN (bottom limit position!).

11. Wait a minute. More gibberish shows up in the Rx screen. And - the center frequency (I also call it 'offset') suddenly starts moving about!

12. After about 1 minute, it had already drifted off by -50 Hz (to the left, this time). After 2 minutes, it was in the 1200 Hz range, still veering further off...

13. Try to toggle SQL ON / OFF and try to pull the SQL slider up to the green bar threshold: as expected, if 'ON' it affects the gibberish showing (or not, if 'OFF', as expected), but regardless of the SQL toggle state, it also impacts the AFC induced frequency offset drifting.

14. Now pull the SQL slider all the way UP again (top position!), SQL ON or OFF doesn't matter here, as it's well above the green signal bar now.

15. Wait a minute. More gibberish shows up in the Rx screen, nothing unusual. And the frequency offset, with AFC ON, stays put where it last stopped!

16. I repeated the above from step 10 and now the AFC started veering off to higher frequencies, while switched ON.
I would rather expect AFC to stay on the spot unless it senses a valid signal within its catch range of a few Hz.

17. If you care, try setting the MFSK LPF to 2 (the minimum) and watch the rapid AFC oscillations, rather 'out of control', and the resulting drift off the previous offset!


Conclusion:

Quite unexpectedly, the SQL slider setting (not the SQL toggle state!) directly affects the AFC behavior, allowing or inhibiting the unintentional AFC drift.
In Kim's screenshot, the slider is somewhere in the middle, so if he played back some audio while compiling his program, the AFC may well have started waking up and do the 'drift thing', as he has experienced and reported, calling the experience of the new version 'frustrating'.


As a quick fix, I will ask him to pull the SQL slider all the way up and check, whether the unwanted AFC veering stops.


Now all this does not explain why Kim's fldigi has the AFC button grayed out (thus non-reacting), and why mine, quite the opposite, doesn't grey out the AFC Button in any mode: I have tried all I could access via the mouse wheel or from the Op Mode Menu, it always remains active and allows to toggle its state. Something appears to be a bit off or at least non-intuitive, I would say.


- - - - - -


But now get this: I didn't really think this might explain it, but, of course, at some point, I had transferred part of my 'personal' config files into the (otherwise independent) thumb drive installation. So I thought, I'd better double-check, whether I really told 'nothing but the truth' up there. So I renamed (disabled) my previous thumb drive installation and made an all-new one, fresh from the 'fldigi-4.2.06.24_setup.exe'. Followed the few instructions, done, all only merely using the setup-included default config settings etc.

I started fldigi - and the AFC Button was, in fact, greyed out, not reacting to input, just like on Kim's screenshot!

And, with the SQL slider in a lower position, enough to get activated, the AFC started drifting again, just like what I'd seen and described above.

I attach 4 annotated screenshots, there's a time reference in the upper right corner, showing the respective (Central European) time and the fldigi screen.


- - - - - -


David, please let me know what you think and whether you are able to reproduce this behavior. And if so, is this considered a topic to be fixed, or just some operator error, which can be overcome by proper control of the software...?


Thank you very much in advance!


Best regards
Tobias
.-.-.

sent by ve3wej on samsung s21+

Jack,?

?

I found that the Microphone Array? Reltek Audio volume was set to around 25%. I brought it up to 100% and lowered the Signal range and upper signal level values.? And now (which I don't like) is the 7300 speaker volume also effects the water fall signal level.?

So the radio volume is too loud. When I transit, the sound comes out the laptop speakers. The laptop microphone picks up back ground sound and I see it on the water fall.

?

I believe the only way to remedy all these problems is to install windows 10.

?

The windows Input volume for 2-USB Audio CODEC is at 100%.

?

?

?

?

Hello, a bit frustrated here..I thought I would try this weekend with my FT-891. I am in Belize and have never used my 891 on RTTY.

The current equipment is a Windows 11 PC, FT891, and a digirig. I have used JS8call, WSJT-x, VARAC, digital modes, no problem.

Flrig 2.0.0.4 is my rig control and love it.

FLdigi 4.2.06 I use for keyboard CW, Wefax and so on.

However I am stumped, the online manual for RTTY is for an older version of Fldigi.

Here is what happens in different modes with FLrig and Fldigi

RTTY-45 - op mode

FLdigi set on USB - "per the manual" - nothing happens., no audio

FLdigi set on RTTY-L , solid tone?

FLdigi set on RTTY-U, solid tone

Fldigi set on Data-U no tones

NOW,

If I have Flrig off, then FLdigi only shows RTTY as option but again no tone nothing goes.

Anyone out there got a working configuration?

73's

V31XE

Ed

?

The AFC button is grayed out ONLY if the modem in use does not employ AFC.? This will be true for all DominoEX, Thor, FSQ, IFKP, MT63, etc.? The kind of drift reported is usually caused by VFO offset chasing.? The easiest way to resolve this is to have one or more of the stations "lock" the transmit audio frequency.? This is a common user originated problem.

Hello Drew,

You are right, but this screenshot was taken while compiling 'TX generate' a radiogram, thus it was normal to not see an input signal.

The problem rather is the 'impossibility' to De-Activate AFC, which, if active, causes a slow up-drift of the audio frequency, nominally 1500 Hz. Drift is most unfavorable while compiling a program for a broad audience who expect the offset to be precise at all times.

My question thus is twofold:

How to switch off a greyed out (but activated) AFC.

How to avoid the AFC drift while idling without a 'guiding' received signal being present.


I'm lost, not knowing the answers...


73s Tobias
.-.-.

The diamond shaped indicator - to the left of the afc button - being black tells me there is something wrong with your incoming audio to the computer. The audio volume is too low. I don't know if that is related to the afc being grayed out, but it will also prevent you from decoding anything properly.?

Run that -47? value to around -10 and the right number to 60

My laptop is an ASUS VivoBook intel Core i7.

?

Jack, With your last instructions, things got better.

?

I had to increase these values higher than I have to in windows 10 in order to see a signal in the water fall.

But being able to use the program is much better now.

?

Phil,

That is the way the instructions said to do when I first started using Fldigi on windows 10.?

Jack,?

?This is what I have in the sound settings.

The water fall doesn't have any noise or signal displayed unless I bring up the signal levels in the bottom left panes. Then I can see an in coming signal to?

pick on. Then the signal in the right side of the water fall will show up in green.? I just discovered this.

In windows 10 I usually have those signal levels at 20 and 40.? In windows 11, I have to raise them really high for even noise to show up in the WF.

?

?

?

?

?

Jack, thank you for trying to help.

Since I have run Fldigi in windows 10 for along time, I am very familiar with the sound settings and all.

It just doesn't work with windows 11.