开云体育

Hello Al,

Please consider the attached explanation.


73s Tobias
.-.-.

Hello Al,

In any issue description, it would generally be helpful to be very specific about the FLdigi version, DigiMode and settings used, either in the text description, and/or please join a screenshot of the entire FLdigi window, to see the respective settings there, and also show, which FLdigi version you are using.


Not sure what exactly you refer to here. But I assume you tried clicking a line in the Signal Browser Window (some modes allow this multi-signal decoding, but you didn't mention which one you were using - MFSK16, which you wrote about earlier, is not even supported) and it didn't select the frequency to show the result in the (main) Rx Pane ...?

Regarding your info 'I have to read the tiny text on the left', you should always be able to click the respective frequency in the waterfall and then the main Rx Pane should instantly display what's received on the selected QRG. This also is a good check, whether the mouse command (clicking) as such is working OK. At least in Windows, sometimes modifier keys (e.g. Shift, Ctrl, Alt on the keyboard) 'get stuck' and continue to be logically active while physically, they are no longer pressed. In such a case, unexpected things (or nothing) may happen, instead of the expected function. But I don't think this was the case here.


To verify what's possible (FLdigi V4.2.06, running Windows 7), I have tried all potential frequency 'locking' settings I could find, but in no case or combination, this effect could be reproduced. So bottom line I'm really puzzled...


Looking at your earlier e-mail about the RSID, you have mentioned that you tried 'Passband' already without success. That's yet another puzzle, because the RSID has always worked very reliably here, and I have not been able to reproduce what you have described. So here are just 2 more remarks based on experience:

If the received signals are not strong or noisy, you may wish to open the Config RsID dialog and set the 'Allow errors' setting to 'High' (my usual setting), which increases the chances of decoding an RSID tag.

On a related note, I would generally *discourage* activating the settings 'Mark previous mode' (which normally won't be of much use anyway, since it's the NEW, that really matters) and also the Rx/Tx RsID EOT, which is very rarely used and, if so, often inadvertendly: It's not at all helpful in QSOs, since this EOT TxID appears after the end of the digimode signal, when as answering station may already send its normal TxID, leading to overlapping signals possibly failing to decode. We've had such a case on the air, quite confusing! The OM had no idea, that he had activated this option an gladly got rid of it, once notified.


Well, if any 'odd behavior' is *permanent* in your otherwise functional FLdigi installation, please send your FLdigi configfuration files over. Comparing these with a 'functional' configuration here might provide a clue, which setting(s) may be off. Both files usually are located in 'C:\Users\<USER_NAME>\fldigi.files': 'fldigi.prefs' and 'fldigi_def.xml'.


Sorry, that's all I can come up with at this point.


Good Luck!


73s Tobias
.-.-.