http://writelog.com/digirite Update history 1.1.30 * CQ and Messages to Me panels hold presented decodes in place, once presented. * Add font selection dialog. * Add Apply QnP button (move QSOs in Pr
For various reasons, MSK144 ain't gonna happen DigiRite. One is that there are no contests that use it (or none that WriteLog currently supports.) As for the manual entry issue, I suggest we take th
oops. That sentence was NOT intended to sound dismissive nor confrontational. Its not you that's the problem with MSK144, its me. Or, maybe more accurately, its me and some others I won't name. Wayne
Try WriteLog's Yaesu FT-991 setting. That looks like its compatible with the FTdx101D (and 101MP) command set. _______________________________________________ WriteLog mailing list WriteLog@contesti
This problem apparently only appears in WriteLog's "CW keyer type" set to "WinKey+OTRSP pipes". The symptom is that any f-key message longer than 7 characters will only send the first 7 characters an
Hi AL HUTCHESON, Did anything change on the radio side? The problem you describe sounds like an intermittent communication error. What's the hardware you use to connect the radio to the computer f
If you are running an IC-7600 and recent versions of WriteLog are not working correctly, you can help us diagnose the problem. You mission, should you choose to accept it, is as follows: 1. Take note
If you're going to run... RTTY Round Up in FT4/FT8 with DigiRite ...then you need to get DigiRite version 1.34. To download, see the discussion at https://groups.io/g/digirite Wayne _____
You probably missed the final control site setup instructions way down at the bottom of this page: https://writelog.com/remote-control-setup-step-3-rig-control Wayne ________________________________
There is not such an entry in the WriteLog gui. (There will be a future release.) However, if you use WriteLog Setup/Options/Ports to set it to some other rate, then Setup/Save-Cnnfiguration, Exit a
The latest version of WriteLog does NOT repeat the log's DGTL column across networked PCs. This will be fixed in a future version. For those of you that ran WriteLog and either DigiRite or the UDP li
This very likely means you have not yet installed OmniRig. Try this: http://www.dxatlas.com/OmniRig/Files/OmniRig.zip _______________________________________________ WriteLog mailing list WriteLog@c
The download at http://writelog.com/Contest-Super-Simulator is updated to version 1.15.02. There are several small feature updates, but also a fix to a bug in the previously published kit, 1.14.0
A couple of comments: 1. "station keeps coming back" might be the simulated station answering your CQ expects you to send either "QSL" or "TU" after you receive theirs. Specifically, it doesn't reco
You are looking in the correct place for the kit: https://github.com/w5xd/WriteLogRunMode/tree/master/DownloadInstaller And you see there that V.2.8 is the latest build. The readme does show comment
It has come to our attention that the recently-released WriteLog version 12.51J introduced an error in its ADIF export. Specifically it fails to write the specified "RTTY" tag for RTTY QSOs. (It writ
You can change this behavior using WriteLog's menu item Contest/Exchange-Format-Setup. In the left most column (labeled "Exchange Fields") click on the "SECT" entry. The "Required" check box by defa
Hi, Currently i use N1MM++ for contesting and DXLabs for daily use. My station is band switching automated by listening <RadioInfo> UDP packets send by N1MM++ and DXLabs. https://n1mmwp.hamdocs.com/a
I have never played much with Writelog's exchange fields except for eliminating unnecessary fields so I found Wayne's post on its other settings interesting. For the ARRL 160m contest you could set t
I happen to have access to a Flex-6500, have tested with SmartSDR 3.2.39 and "it works for me". Confirm you have the most recent version of the Flex driver: http://writelog.com/Downloads/WlFlexDriver