+ AA6YQ comments below

I have tried for days to print qsl labels. I think I have read everything several times. Problem is when I print, the characters
are on top of each other and I can not figure out how to adjust the space available for each piece of information.

+ Which variety of labels are you using? What font sizes have you specified?

73,

Dave, AA6YQ

开云体育

+ AA6YQ comments below

开云体育

On Thu, Mar 21, 2019 at 05:52 PM, Dave AA6YQ wrote:

+ AA6YQ comments below

+ Good. Interesting that the K3's TX soundcard was muted when used by WinWarbler, but not muted when used by MMTTY running standalone.
+ What actions did you take to unmute the K3's TX soundcard? I'd like to add this to the documentation.

To be clear, I'm not sure what caused the TX sound card to mute, whether it was messing with N1MM or not; I wasn't writing things down as I went along.

To unmute the soundcard (well, one of several, but this is how I did it under Windows 10:?

Strike the Windows key, type "sound". The first item was "Sound: Control Panel" which I selected.
This brings up the interface where you see all the audio devices present in the system.
Select the first tab (Playback).
Select the audio device corresponding to the K3s's USB audio codec and double-click it.
On the General tab, you have the option to rename it. I did so, and called it "K3s Transmit". Do this if you wish to make future configuration changes a little easier, since often in computers there are multiple USB audio codecs or other sound devices. Doing this helps with other radio-related software setups down the line.
On the LEVELS tab. You can then select the audio output level used for transmit. I set it to 60, your mileage may vary, but somewhere around mid-point is fine, and you will fine-tune your levels elsewhere.
Beside that is a speaker icon (to the left of the "Balance" button). If there's a red circle/line then the TX line is muted. Click to unmute. You should have TX audio at this point.
In the "Enhancements" tab ensure that none of the boxes are checked.?
In the Advanced" tab select 16 bit, 4800 Hz (DVD quality). By default the two check boxes in "Excludive Mode" were checked and I did not touch them. I don't know what they do.
In the Spacial Sound tab (if your PC is so equipped), make sure it's off.
Press OK, then OK to exit.

To prove the point, I went back in to the "bad" workspace and sure enough, things were still messed up. I changed back to the New and Improved workspace and everything was good to go.

+ There is no DXLab setting that can mute a soundcard. Your "proof" does not hold water,

I am not claiming that a DX Lab setting muted the soundcard. That could have happened any number of ways. It just was muted, and that was only a small part of the problem; the last step, which I discovered after changing to a different profile.

as your "bad workspace" could have contained other configuration errors that prevent RTTY AFSK operation -- like not correctly specifying the transceiver mode.

Right. The "bad workspace" was absolutely the problem. No matter which setting I would use, it would not place the radio in AFSK-A mode, as discovered over the 40-odd messages in the thread. Modifying a previously saved workspace to the new settings got the correct mode change. With those IDENTICAL settings used in the "bad" workspace it never worked. So whatever the cause of that behaviour I'm not sure, but the cure was absolutely to use a different WinWarbler workspace. It was only when I had that?aspect working that I discovered the sound card issue as a subsequent (parallel) problem.?

+ AA6YQ comments below

My backup system caused more problems than it solved.

I was having the original database file backed up online by Carbonite and to an external hard drive by Acronis. They both worked automatically, even when the file was being used by DXKeeper. The database was often corrupted with old data. Specifically, the LotW status had problems.

+ Clearly, one of those two apps is defective; perhaps the combination of the two manifests a defect in one of them.

+ Mozy, which I've used for cloud backup for years, was acquired by Carbonite, so I'm just starting to use it for cloud backup. I'll keep an eye out for problems.

73,

Dave, AA6YQ

+ AA6YQ comments below

I worked AL7TC yesterday on 160m FT8. The log entry was passed from WSJT-X automatically to DXKeeper as usual. DXKeeper uploaded the QSO to LOTW.

+ Did you invoke DXKeeper's "Sync LoTW QSOs" function after the AL7TC QSO was uploaded?

When AL7TC uploaded there was no match. After confirming via email that his WSJT ADIF file entry matched mine I decided to upload the WSJT entry to LOTW using TQSL. The upload was not rejected as a dupe and it was confirmed on LOTW. I imported the ADIF that I uploaded via TQSL to LOTW into DXKeeper.

+ If the original AL7TC QSO in DXKeeper was logged with a mode of FT8, that would have created a duplicate QSO.

+ If the original AL7TC QSO in DXKeeper was logged with a mode of SSB, that would not have created a duplicate.

When I did a sync on LOTW the new log entry was updated as confirmed but the old one was not.

+ That implies that the original AL7TC QSO in DXKeeper was logged with a mode of SSB.

When I compared the two entries on LOTW the problem there was obvious. The first upload was listed as SSB band and not FT8. I am at a loss how the same ADIF entry when passed from WSJT-X to DXKeeper could be uploaded as a different mode. DXKeeper shows both entries in my log as FT8.

+ I cannot explain how a QSO logged with a mode of FT8 would be interpreted by TQSL as SSB, but that's evidently what happened, because you say that

1. the original QSO is logged with a mode of FT8

2. when you uploaded an ADIF file specifying your AL7TC QSOs with a mode of FT8, TQSL did not rejected it as "already uploaded".

+ The most recent ADIF record(s) sent by DXKeeper to TQSL can be found in the file

LoTWUpload.ADI

+ in your DXKeeper folder. What is contained in this file?

73,

Dave, AA6YQ



Best<<John


<> Virus-free. www.avg.com <>

My backup system caused more problems than it solved.

I was having the original database file backed up online by Carbonite and to an external hard drive by Acronis.? They both worked automatically, even when the file was being used by DXKeeper.? The database was often corrupted with old data.? Specifically, the LotW status had problems.

My solution was to move the database file being used by DXKeeper to a USB flash drive, don't have that file backed up by either Carbonite or Acronis, set DXKeepr to save a backup on each exit to my hard drive, and have that backup file backed up by both Carbonite and Acronis.? That has eliminated the problem.

My solution may be overkill and I cannot tell you what caused the problem, but the solution works so I pass it along.? YMMV.

73 de K1ESE
John

I worked AL7TC yesterday on 160m FT8. The log entry was passed from WSJT-X automatically to DXKeeper as usual. DXKeeper uploaded the QSO to LOTW. When AL7TC uploaded there was no match. After confirming via email that his WSJT ADIF file entry matched mine I decided to upload the WSJT entry to LOTW using TQSL. The upload was not rejected as a dupe and it was confirmed on LOTW. I imported the ADIF that I uploaded via TQSL to LOTW into DXKeeper. When I did a sync on LOTW the new log entry was updated as confirmed but the old one was not. When I compared the two entries on LOTW the problem there was obvious. The first upload was listed as SSB band and not FT8. I am at a loss how the same ADIF entry when passed from WSJT-X to DXKeeper could be uploaded as a different mode. DXKeeper shows both entries in my log as FT8.?

Best<<John

* more AA6YQ comments below

On 2019-03-21 9:16 PM, Dave AA6YQ wrote:

+ If N1MM has muted a soundcard, what are the steps in Windows to unmute it?

1) Open Windows Volume Mixer,
2) click on the "Device" dropdown to select the output device that
has been muted,
3) click on the speaker icon to unmute the device
4) reset the master volume control (for that device) if needed.

+ Note that the K3 includes the ability to decode RTTY,

However, that decoder only works on the MAIN RECEIVER AUDIO.

73,

... Joe, W4TV


On 2019-03-21 9:16 PM, Dave AA6YQ wrote:

+ AA6YQ comments below
On 2019-03-21 12:30 PM, Peter Dougherty wrote:

> The issue of no SSB or RTTY tones was related to the TX soundcard > having somehow been muted by Windows (I have no idea how that > happened).
Probably because you were also playing with N1MM+ while trying to configure WinWarbler. If one selects "Config -> Use Logger+ Audio"
N1MM controls the *MASTER LEVEL* and *MUTE* switch of the selected sound card rather than controlling the *application specific* level for the sound card inputs and outputs. Among other things, N1MM+ will set the master level to zero and mute the sound card output when it is not using the specific sound card.
THIS IS BAD PROGRAMMING AS IT VIOLATES MICROSOFT STANDARDS BUT HAS EXISTED FOR MANY YEARS IN N1MM LOGGER+.
+ I will raise this with Tom N1MM the next time I see him.
+ If N1MM has muted a soundcard, what are the steps in Windows to unmute it?
+ As noted in
<>
"WinWarbler incorporates two independent RTTY decoders: the MMTTY engine and the 2-Tone engine. If your transceiver includes a Subreceiver, you can connect the Main receiver's audio output to your soundcard's left input channel, and the Subreceiver's audio output to your soundcard's right input channel. If you then configure one engine to decode your soundcard's left channel, and the other engine to decode your soundcard's right channel, you can simultaneously copy a RTTY station operating split while tuning the pileup to determine where best to call. The 2-Tone engine is only used for reception, so the MMTTY engine's AFSK or FSK output alone will handle RTTY transmission. The instructions below assume that you've already configured WinWarbler for RTTY operation."
+ The above article provides step-by-step configuration and operating instructions, and then goes on to explain how to further automate the procedure when using an Icom transceiver that supports main-sub audio switching via CI-V command.
+ Note that the K3 includes the ability to decode RTTY, complementing the MMTTY and 2Tone decoders with a 3rd display.
73,
Dave, AA6YQ

+ AA6YQ comments below

On 2019-03-21 12:30 PM, Peter Dougherty wrote:

> The issue of no SSB or RTTY tones was related to the TX soundcard > having somehow been muted by Windows (I have no idea how that > happened).

Probably because you were also playing with N1MM+ while trying to configure WinWarbler. If one selects "Config -> Use Logger+ Audio"
N1MM controls the *MASTER LEVEL* and *MUTE* switch of the selected sound card rather than controlling the *application specific* level for the sound card inputs and outputs. Among other things, N1MM+ will set the master level to zero and mute the sound card output when it is not using the specific sound card.

THIS IS BAD PROGRAMMING AS IT VIOLATES MICROSOFT STANDARDS BUT HAS EXISTED FOR MANY YEARS IN N1MM LOGGER+.

+ I will raise this with Tom N1MM the next time I see him.

+ If N1MM has muted a soundcard, what are the steps in Windows to unmute it?

+ As noted in

<>

"WinWarbler incorporates two independent RTTY decoders: the MMTTY engine and the 2-Tone engine. If your transceiver includes a Subreceiver, you can connect the Main receiver's audio output to your soundcard's left input channel, and the Subreceiver's audio output to your soundcard's right input channel. If you then configure one engine to decode your soundcard's left channel, and the other engine to decode your soundcard's right channel, you can simultaneously copy a RTTY station operating split while tuning the pileup to determine where best to call. The 2-Tone engine is only used for reception, so the MMTTY engine's AFSK or FSK output alone will handle RTTY transmission. The instructions below assume that you've already configured WinWarbler for RTTY operation."

+ The above article provides step-by-step configuration and operating instructions, and then goes on to explain how to further automate the procedure when using an Icom transceiver that supports main-sub audio switching via CI-V command.

+ Note that the K3 includes the ability to decode RTTY, complementing the MMTTY and 2Tone decoders with a 3rd display.

73,

Dave, AA6YQ

+ AA6YQ comments below

I uninstalled and installed several times, and then found the dll file on my old computer and placed it in the C:/DXLAB/Launcher folder, now I do not get that message anymore

+ The missing .dll is used by TQSL, not by any DXLab application. I'd defer to TQSL developer Rick K1MU (copied on this message) as to where tqsllib2.dll should be placed. He'll want to know what version of Windows you are using, and whether it's 32-bit or 64-bit.


but have a new one that I have no clue what it means or what to do, "Attempting to upload 19 QSOs
C:\DXLab\DXKeeper\LotWUpload.ADI: Couldn't upload the file: CURL returned "Peer certificate cannot be authenticated with given CA certificates" (SSL certificate problem: unable to get local issuer certificate) Final Status: TQSL Error (4)"
As always any help would be appreciated, thanks.

+ That's TQSL reporting that it cannot securely upload your encrypted QSOs to LoTW. What version of Windows are you using?

73,

Dave, AA6YQ

+ AA6YQ comments below

After three very long and grueling days, the problem has now been completely resolved.
The issue of no SSB or RTTY tones was related to the TX soundcard having somehow been muted by Windows (I have no idea how that happened). Once I unmuted the card I got diddle, and in SSB mode, all voice keying .wav files played normally.

+ Good. Interesting that the K3's TX soundcard was muted when used by WinWarbler, but not muted when used by MMTTY running standalone.

+ What actions did you take to unmute the K3's TX soundcard? I'd like to add this to the documentation.



Now it's a matter of setting audio levels and fine-tuning everything.

To prove the point, I went back in to the "bad" workspace and sure enough, things were still messed up. I changed back to the New and Improved workspace and everything was good to go.

+ There is no DXLab setting that can mute a soundcard. Your "proof" does not hold water, as your "bad workspace" could have contained other configuration errors that prevent RTTY AFSK operation -- like not correctly specifying the transceiver mode.

73,

Dave, AA6YQ

Thanks for the heads-up about N1MM+. I had no idea this was the case. I agree, not ideal. Also thanks for the info on the USB audio breakout. Yes, I use and love A-Ab, but I wasn't sure if the audio out was the same on USB as it was via the 3.5mm jack. That is good new indeed, but as I said, something I hope I never have to use for RTTY again. Those were some mighty frustrating pileups.

On 2019-03-21 12:30 PM, Peter Dougherty wrote:

The issue of no SSB or RTTY tones was related to the TX soundcard
having somehow been muted by Windows (I have no idea how that
happened).

Probably because you were also playing with N1MM+ while trying to
configure WinWarbler. If one selects "Config -> Use Logger+ Audio"
N1MM controls the *MASTER LEVEL* and *MUTE* switch of the selected
sound card rather than controlling the *application specific* level
for the sound card inputs and outputs. Among other things, N1MM+
will set the master level to zero and mute the sound card output
when it is not using the specific sound card.

THIS IS BAD PROGRAMMING AS IT VIOLATES MICROSOFT STANDARDS BUT HAS
EXISTED FOR MANY YEARS IN N1MM LOGGER+.

You will probably end up with no output/muted conditions in your
sound card (USB Audio CODEC) every time you run then close N1MM+.

One of the things the old MK-II did was break out RX audio into
left/VFO-A, and right/VFO-B. I still need to find a way using just the
USB connection to use only VFO-A audio for main receive, and open a
second instance of MMTTY for VFO-B receive on the right channel

The K3, K3/KIO3B and K3S all provide Main Rx audio on the Left channel
and Sub RX Audio on the Right channel if you have the optional Sub RX
installed. The only time mixed Main/Sub should appear on the Left (or
Right) channel of Line Out/USB Audio CODEC is if you have changed the
K3/K3S CONFIG:L-MIX-R setting from its default "A b" setting.

If you have selected "Ab b", "Ab Ab", or "A Ab" you will get
mixed Main/Sub audio in Left, Both, or Right channels respectively.

Again, refer to the Elecraft K3 or K3S Owners Manual for more details.

73,

... Joe, W4TV


On 2019-03-21 12:30 PM, Peter Dougherty wrote:

After three very long and grueling days, the problem has now been completely resolved.
The issue of no SSB or RTTY tones was related to the TX soundcard having somehow been muted by Windows (I have no idea how?that happened). Once I unmuted the card I got diddle, and in SSB mode, all voice keying .wav files played normally. Now it's a matter of setting audio levels and fine-tuning everything.
To prove the point, I went back in to the "bad" workspace and sure enough, things were still messed up. I changed back to the New and Improved workspace and everything was good to go.
One of the things the old MK-II did was break out RX audio into left/VFO-A, and right/VFO-B. I still need to find a way using just the USB connection to use only VFO-A audio for main receive, and open a second instance of MMTTY for VFO-B receive on the right channel in case (ghods-and-the-universe forbid) there's a major split RTTY DXpedition in the future. I've said it before, split RTTY pileups were the most painful part of any DXpedition!
Anyways, thanks to Dave and Joe for continuing to point me in the right direction and narrow down the settings to what they needed to be. It remains to be seen how and?why the registry settings got messed up, perhaps, but regardless, we're all good for now, workspace saved, K3s config saved (to several cloud services and removable media), and a working MK-II with several cables is now available for sale <grin>.

I backup to 3 locations from DXKeeper, 2 not in the computer. I recommend more than one backup location and at least 1 not part of the computer.

I delete several old copies of the backup files but always keep a few in each location should something go amiss with the most recent.

Jack AK7O

Sent from XFINITY Connect App

I uninstalled and installed several times, and then found the dll file on my old computer and placed it in the C:/DXLAB/Launcher folder, now I do not get that message anymore but have a new one that I have no clue what it means or what to do, "Attempting to upload 19 QSOs