开云体育

Romas, My information is that the Xiegu radios ignore the CI-V address and respond to messages sent to any address. A4 is the default CI-V address for the IC-705. It would be great if you could

Dave i'm glad you noticed the error in 5b in the screenshot that i prepared to send. In that screenshot destinated to sent to You, i made a typo. Forgot writing the underscore. Indeed, in step 5b i

Dave - Right clicking on each, and selecting "Update from LotW" yields report: LotW Sync QSLs: 1 QSL processed, 1 log entry updated, 0 errors LotW Sync QSLs: no new confirmations of anything Needed

+ AA6YQ comments below + Thanks! I added your information to https://www.dxlabsuite.com/dxlabwiki/TranceiverControlXiegu + Please check the X6200 entry there for accuracy. + You may be able to speed

+ AA6YQ comments below They are each set to "Y". Neither is confirmed. + If their "LoTW QSL Sent" items are set to 'Y', that means LoTW reported that it has accepted them. + If you want to check for

After hours of digging found best configuration as IC-705 with address A4 and delay 200 ms. Everything seems to work (only slower), sometimes WSJT tune function after turning off still sends signal.

Dave - They are each set to "Y". Neither is confirmed. Dave - K9FN [email protected]> wrote:

+ AA6YQ comments below + I didn't give you an answer. I gave you some information, and asked a question. 73, Dave, AA6YQ

Thanks for the quick answer. 73 Hauke

... via the Databases tab of DXView's Configuration window. Terminate DXKeeper and SpotCollector before directing DXView to update these databases. 73, Dave, AA6YQ

+ AA6YQ comments below Dave... File sent! + The errorlog you sent me shows your transceiver rejecting valid commands from Commander: 2025-01-27 00:39:41.194 > CIVModule.DisplayLine: Port = P, Asc = ?;

Dave... File sent! Hank

Everyone installing Pathfinder downloads the same file. Yours is the only report of a problem. I suggest that you 1. delete the files in DXLab/Pathfinder/Install 2. reboot windows 3. direct the

My entry in DXKeeper automatically showed Mt Athos and uploaded to LoTW and Club Log as Mt Athos with no help from me. Jack AK7O (no slash A entered) [email protected]> wrote:

+ AA6YQ comments below + Nothing was wrong with your log, other than you recorded WAB squares in user-defined item #6 instead of the REGION item + I followed the step-by-step instructions I send you

Hi Rich, Thanks for the detailed explanation. I logged from JTAlert which showed the call without the /A and logged it in DXKeeper without the /A. I need to update the contact in DXKeeper to reflect

I wasn't using Hound mode either. You do not need to use Hound mode to make contacts with a Fox. They were clearly in Fox (or multi-stream) mode; they were sending as many as 5 parallel streams when I

I was not using fox/hound mode. When I worked them this is what I received. 250126_021100 7.056 Rx FT8 -14 1.6 510 KQ5S RR73; AB1J <...> -02 Tom-KQ5S

When I worked them, their Tx6 (CQ) message was CQ SV1GA/A, and their compound Tx4/Tx2 message contained a hash for SV1GA/A, as in VE3KI RR73; K9RE <SV1GA/A> -02. Their separate Tx2 and Tx4 messages