I have run fldigi many times using the API with ACL and have had no problems. I do not use radio control though so I don’t have to worry about COM conflicts. Dan Morris KZ3T dbmorris315@... I

Mark, Go to the Configure tab in Fldigi and select the log option. Select N3FJP logs and enable the data stream and that should take care of it. Turn off the com port in ACL. You can also set

Mark, Only one program can use a COM port at the same time. If you have ACLog setup and connected to your radio correctly simply start it first. In FLDigi “Don’t” select a rig control

I googled R6H-212 and got a few hits. Looks like it is a club call with Victor as the operator. Give it a try and see if you can find enough info to make LOTW happy. Kevin/NB7O

Hi Bob, Thanks for your e-mail. If you put an L in the Sent Confirmed By field, AC Log will no longer hand the QSO record to TQSL for upload. Enjoy! 73, Scott N3FJP http://www.n3fjp.com Serving the

My rule of thumb is: If I can’t find a particular call in QRZ.COM, then as far as I’m concerned, it is an invalid call. My two cents worth. 73 and be safe! Lou WA5LOU -- Lou WA5LOU

Another solution is Win4IcomSuite and com0com. The combination of these two programs allow me to share the COM port of my IC-7300 with Win4IcomSuite and up to 6 other programs.

Steve, I decided the smart thing to do was search the archive of messages re:merging and found the instructions as you indicated on how to do this. Went flawlessly (not a cough in a carload as

I worked a guy in European Russia 3 times on FT8 with the callsign R6H-212. His real callsign must be different, but I have not been able to find it. He is listed with this callsign on the Russian

Before I dig into the fldigi manual, hoping I can get some help here. I start the logger, then fldigi In fldigi I set the logger to generic contest and check the API logging connected item Generic

Also your antivirus , particularly Windows Defender is not allowing you to open the software as it thinks it’s unsafe Frank NG1I

n3fjp.com works just fine for me. -- 73, Dave KC3AM

Wes, Export them as and ADIF file and then import them the correct file. Steve, AI3KS

I messed up and logged a dozen QSOs to an auxiliary log file by mistake and need to merge/add these to my main station log. I’m sure someone else out there has incurred this pilot error. Please

Mark, You cannot share the COM Port. Probably the easiest way would be to disable rig control in AClog (Ctrl-Shift+R) prior to starting FLDigi. Then, after you close FLDigi

At this point it sounds like an ISP issue, Dale. Let us all know what you find out. Lou WA5LOU -- Lou WA5LOU

Thanks for the suggestion Gary. Keep in mind that even if I added them to the code my software generates, Winkeyer would need to recognize them for anyone using Winkeyer to send CW. Thanks again for

Thanks Lou Yes all is fine here ! Thanks for asking... New install on computer with windows 10. I have tried 5 computers to log on to N3FJP's web site I can't. Dale KJ6IX

My goal is to have N3FJP Amateur Contact Log V6.6 work with FLdigi. The problem is that when I try to start the Contact logger while FLdigi is running I get a message that access to port COM 3

Scott, In future versions of your logging programs would you please add the following CW keyboard characters? AA (double-A), which is used by CW traffic handlers to separate address line