¿ªÔÆÌåÓý

try using windows snipping tool to capture the screen Dave Garber VE3WEJ / VE3IE [email protected]> wrote:

I was working on my FLDIGI with my ICOM 7300. Tx is working great but I am getting strange characters on the RX screen. Looks similar to Japanese. I must have something set wrong? Any help would be

Thank you Dave! The new delayed QSY macro tag works perfectly with my G106! 73! de HA3MGA Gabor

http://www.w1hkj.com/alpha/fllog/ Index of /alpha/fllog * Parent Directory <http://www.w1hkj.com/alpha/> * fllog-1.2.8.01.tar.gz <http://www.w1hkj.com/alpha/fllog/fllog-1.2.8.01.tar.gz> *

I want to thank all of you for input. All of your suggestions were very helpful. After my company leaves this weekend, I'm going to review all of your suggestions and play with my Fldigi settings.

Thank you for your input. Darryl

Thank you for your input. I'm going to revise my settings. Darryl

Thank you for your input. Darryl

Darryl, If you consider how digital decoding works, it's a logical consequence, that below a certain amount of SNR (Signal/Noise Ratio), things become completely unreadable - and thus gibberish. Since

I don't recall losing information this way, either. The decoding process is designed to extract real signals from the noise, and that process is pretty reliable. You could turn SQL up unless you are

Turn in the SQL and set the SQL level so it just stops the gibberish, i.e. the slider at the extreme right end of the waterfall. I've never lost text from modes with Forward Error Correction that way.

You can turn on SQL, but at the risk of losing text from modes with forward error correction. Most of us probably just tolerate the "gibberish". [email protected]> wrote: -- 73, AB1PH Don Rolph

Good Afternoon Follow FLdigi users, I have followed the FLdigi setup procedures and watched many videos. However, I can not find any information on how to stop the gibberish text on the screen. What

With all the connection errors I have seen on and off over the years with fl_suite, not one needed a clean install of Windows. But many...most? havna counted...resulted from the way Windows handles

Here's my feedback :-) After one week testing (in cold sweat) everything seems to work fine! But I have to "create" some macros, for QSOs as well as for contest. Next part is making CW with Fldigi. As

did you perhaps unplug from the pc and plug in later?? did you use the same usb port. check with device manager and see what ports are active, then check your fldigi Dave Garber VE3WEJ / VE3IE

I'm not familiar with the K4D and how it connects to the PC (I assume via a single USB cable?), or if it needs a manufacturer supplied driver, but the first thing I would try is i nstalling FLRIG for

Running v. 4.2.05 with a K4D. ?It worked perfectly yesterday but when I took down station and reset it up, I can¡¯t get Hamlib to initialize any of the ports in device manager. ?Help! I¡¯d like to

Bo, Just select CW like any of the other modes. It will transmit like the other modes at the cursor frequency on the waterfall. Please post a screen shot of the entire fldigi window and tell us what

Forgive my simple memory lapse, but I cannot get CW to work with fldigi (USB-D) mode, Other modes work fine, I tried 3 radios, 2 PCs, and the last 2 versions of fldigi. All is well with N1MM &