![]() ![]() But having troubles with the DDElibrary as its no longer being supported and trying to figure out some issues isn’t panning out well. This information is taken from the CREATED-BY field in the Cabrillo log. That works fine, both working stations and logging them in DXkeeper. I have started re-writting the gateway in vb.net as windows 10 on my computer will no longer let me use the dll file that communicates with Fldigi. CQ WW Committee member Doug Zwiebel, KR2Q, has dived into the logs to analyze which logging software packages were used by entrants in the CQ WW SSB Contest 2019. The Gateway minimizes once FLDigi has started, however, some functions of FLDigi. Hopefully someday I can re-write things so it uses TCP messages but its not yet. SO there could be a little delay depending on when the timer went off and when the gateway detects Fldigi has sent the TX’ing signal. ![]() the timer for keeping track of the tx/rx setting is set to 400ms there are 5 timers in all. But the gateway uses timers to keep tabs on changes made in Fldigi. I’m not sure what is causing the trasmit delay. ACLog Airlink Express DigiPan DX4WIN DXBase DXLab FLdigi Hamscope HRD-DM780 Logger32 Logic MixW MMTTY MMVARI N1MM TrueTTY TRX-Manager Win-Test Win-Test RTTY. I had tried it with Linux in the past, but could never manage to interface properly with the rig. SO there is a delay set to see if the frequency is the same as commander or if it didn’t come from commander is the frequency still being updated in Fldigi. Working FLDIGI is pretty simple and straightforward, like Skip Teller's wonderfully simple DigiPan, but it is loaded with the versatility of a multiplicity of modes only a mouse-click away - very like MixW. ![]() Because of the techniqe used in Fldigi I have no way of knowing if Fldigi changed frequency because A you actually changed the frequency or B you changed the frequency via commander. There is a delay built in when changing the radio in Fldigi. ![]()
0 Comments
Leave a Reply. |