Dave … tnx … Font size was problem.
?
john
?
Sent from for Windows 10
?
toggle quoted message
Show quoted text
It is Avery 94202 1”x4”.? Also tried blank and also the default # (can not recall it right now).? The results seem identical no matter what settings I use… the colums are too small and the info overlaps into the next cell.? You may have
it ….. the font may be too big… I have not seen a setting for that.
Tnx john
?
Sent from for Windows 10
?
+ 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
|
Just today, the SC window remains minimized in the system tray (running Win 10). Usually the three windows for the spot sources run minimized but the main display opens on the screen.
?
I have tried right clicking in the start up tray and trying to restore the window or even clicking on “move” with no luck. I have also tried the restore button on the DxLab start up window with the same result.
?
Any ideas?
?
73
?
Tim VE6SH
|
Band Edge Warnings: Commander
I might have missed it in my searching but?does Commander have configurable band edge warnings?
|
It is Avery 94202 1”x4”.? Also tried blank and also the default # (can not recall it right now).? The results seem identical no matter what settings I use… the colums are too small and the info overlaps into the next cell.? You may have
it ….. the font may be too big… I have not seen a setting for that.
Tnx john
?
Sent from for Windows 10
?
toggle quoted message
Show quoted text
+ 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
|
Re: Waterfall for Yeasu FT-991A
Need to purchase Win4Yaesu Suite $60.00 USD to run N1MM for the FT-991A.Jerry N7YGE? ?
toggle quoted message
Show quoted text
From: [email protected] [mailto:[email protected]] On Behalf Of Larry K8UT
Sent: Saturday, March 23, 2019 3:57 AM
To: [email protected]
Subject: Re: [DXLab] Waterfall for Yeasu FT-991A? For contest operation, N1MM supports a spectrum display with superimposed callsigns from the packet spots. You can see and read about it here: ------ Original Message ------ Sent: 2019-03-23 04:26:33 Subject: Re: [DXLab] Waterfall for Yeasu FT-991A I have SDR waterfalls working for my cheap $7 SDR and for another guy who as the more expensive SDR 2.? What I liked about the one waterfall I saw for DXLab was there were callsigns showing.? I have not see that on any other waterfall.? Well there was one note I read where they stated Eazypal sends out the callsign and it shows on the waterfalls.? With both freq and callsign shown you can try to contact the station. ? I am not a DXer and just trying to help a guy get on some software like DXLab without going to HRD.? I have played with HRD version 5.xx and tried the com0com ? virtual drivers. ? Got the drivers to show on the Device Manager as Com 7 & 8 but could not relate them to CNCA0 and CNCB0. ? Seems to me that I would want to in real time to see callsigns and the freq that the station is using.? Then a propagation indicator as to if I could reach the station.? Just guessing. ? Jerry N7YGE ? ? + AA6YQ comments below On Fri, Mar 22, 2019 at 06:29 PM, Jerry wrote: DXLab Commander Waterfall menu/box only appears if you pick an Icom radio on the list.?
+ Only if you set the "Radio Model" selector to IC-7300, IC-7610, IC-7850, or IC-7851. What would it take to make DXLab so when choosing the FT-991A radio the waterfall box appears and the box can be checked so the waterfall screen can be used? + It would take a new version of FT-991A firmware from Yaesu that can convey spectrum data via the CAT interface, under the control of CAT instructions. That's how the above 4 Icom radios support Commander's Spectrum-Waterfall window. + I'm exploring ways of providing this capability using a low-cost SDR (like the RSP family) connected to an antenna or to your receiver's IF. ? ? ? ? 73,
? ? ? ? ? ? ? ? ? Dave, AA6YQ ? ? ?
|
Re: next step on the "waterfall-spectrum display" roadmap: request for input
This sounds great! I'm new to SDR (don't have one yet) but I'm thinking about purchasing the SDRPlay RSP1a and doing?the RXout?mod on my TT OMNI-VII. Then I'll?see about integrating Commander, HDSDR, VSPM?and whatever else I might need to set up a panadapter using information on this site and various other sites. Having a DXLab integrated solution with instructions sure would be nice but I'm sure the development effort is high and do not expect anything too soon (assuming the project get approval and funding :).
|
Yes I did invoke the sync after the contact was uploaded and it was not marked as confirmed in DXKeeper log. After I uploaded the ADIF from WSJT log using TQSL and did the sync that QSO was mark confirmed in DXKeeper but not the one that indicated SSB on LOTW of course. That QSO still shows FT8 in my log but SSB on LOTW. I assume from this content that the ADIF file keeps only the last contact uploaded. This is the QSO from the next day when I worked him again. This uploaded as it should have. I can't open the MDB file in my backup folder that would contain the QSO in question. Anyway here is the content of the file you ask for.
ADIF QSL record generated by DXKeeper 14.8.5 on 22-Mar-2019 09:28:04 UTC
<ProgramID:8>DXKeeper?
<ADIF_VER:4>1.00?
<EOH>?
<CALL:5>AL7TC <TIME_ON:6>092700 <QSO_DATE:8>20190322 <MODE:3>FT8 <BAND:4>160M <FREQ:8>1.841599 <BAND_RX:4>160M <FREQ_RX:8>1.841599 <EOR>
|
Re: Waterfall for Yeasu FT-991A
For contest operation, N1MM supports a spectrum display with superimposed callsigns from the packet spots. You can see and read about it here:
-larry (K8UT)
------ Original Message ------
Sent: 2019-03-23 04:26:33
Subject: Re: [DXLab] Waterfall for Yeasu FT-991A
I have SDR waterfalls working for my cheap $7 SDR and for another guy who as the more expensive SDR 2.? What I liked about the one waterfall I saw for DXLab was there were callsigns showing.? I have not see that on any other waterfall.? Well there was one note I read where they stated Eazypal sends out the callsign and it shows on the waterfalls.? With both freq and callsign shown you can try to contact the station. ? I am not a DXer and just trying to help a guy get on some software like DXLab without going to HRD.? I have played with HRD version 5.xx and tried the com0com ? virtual drivers. ? Got the drivers to show on the Device Manager as Com 7 & 8 but could not relate them to CNCA0 and CNCB0. ? Seems to me that I would want to in real time to see callsigns and the freq that the station is using.? Then a propagation indicator as to if I could reach the station.? Just guessing. ? Jerry N7YGE ? ? + AA6YQ comments below On Fri, Mar 22, 2019 at 06:29 PM, Jerry wrote: DXLab Commander Waterfall menu/box only appears if you pick an Icom radio on the list.?
+ Only if you set the "Radio Model" selector to IC-7300, IC-7610, IC-7850, or IC-7851. What would it take to make DXLab so when choosing the FT-991A radio the waterfall box appears and the box can be checked so the waterfall screen can be used? + It would take a new version of FT-991A firmware from Yaesu that can convey spectrum data via the CAT interface, under the control of CAT instructions. That's how the above 4 Icom radios support Commander's Spectrum-Waterfall window. + I'm exploring ways of providing this capability using a low-cost SDR (like the RSP family) connected to an antenna or to your receiver's IF. ? ? ? ? 73,
? ? ? ? ? ? ? ? ? Dave, AA6YQ ? ? ?
|
Re: Waterfall for Yeasu FT-991A
I have SDR waterfalls working for my cheap $7 SDR and for another guy who as the more expensive SDR 2.? What I liked about the one waterfall I saw for DXLab was there were callsigns showing.? I have not see that on any other waterfall.? Well there was one note I read where they stated Eazypal sends out the callsign and it shows on the waterfalls.? With both freq and callsign shown you can try to contact the station. ? I am not a DXer and just trying to help a guy get on some software like DXLab without going to HRD.? I have played with HRD version 5.xx and tried the com0com ? virtual drivers. ? Got the drivers to show on the Device Manager as Com 7 & 8 but could not relate them to CNCA0 and CNCB0. ? Seems to me that I would want to in real time to see callsigns and the freq that the station is using.? Then a propagation indicator as to if I could reach the station.? Just guessing. ? Jerry N7YGE ?
toggle quoted message
Show quoted text
From: [email protected] [mailto:[email protected]] On Behalf Of Dave AA6YQ
Sent: Friday, March 22, 2019 6:36 PM
To: [email protected]
Subject: Re: [DXLab] Waterfall for Yeasu FT-991A? + AA6YQ comments below On Fri, Mar 22, 2019 at 06:29 PM, Jerry wrote: DXLab Commander Waterfall menu/box only appears if you pick an Icom radio on the list.?
+ Only if you set the "Radio Model" selector to IC-7300, IC-7610, IC-7850, or IC-7851. What would it take to make DXLab so when choosing the FT-991A radio the waterfall box appears and the box can be checked so the waterfall screen can be used? + It would take a new version of FT-991A firmware from Yaesu that can convey spectrum data via the CAT interface, under the control of CAT instructions. That's how the above 4 Icom radios support Commander's Spectrum-Waterfall window. + I'm exploring ways of providing this capability using a low-cost SDR (like the RSP family) connected to an antenna or to your receiver's IF. ? ? ? ? 73,
? ? ? ? ? ? ? ? ? Dave, AA6YQ ? ? ?
|
Re: RTTY (AFSK) **FIXED**
* More AA6YQ comments below 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. * Testing the above on my Windows 10 system, one can mute or unmute an audio device either form the Properties window's Levels tab, as you did above, or from the "Volume Mixer" window as described in <> * Had you reviewed the above article, as I suggested 2 days ago < /g/DXLab/message/184767> * you likely would have noticed that the K3 audio codec was muted. I added step 3.c to make this more explicit. 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. * The settings in the two Workspaces are unlikely to be identical. Please do the following: 1. Using Windows Explorer, navigate to the DXLab Launcher's Workspaces folder. You should see subfolders corresponding to your "good workspace" and your "bad workspace". 2. Double-click on the entry or your "good workspace"; you'll see a file for each of your DXLab applications. Each file has an extension of .reg, but depending upon how you have Windows Explorer configured, the extension may not be visible. 3. Make a copy of the WinWarbler file, and name the copy GoodWinWarbler 4. Double-click on the entry for your "good workspace" 5. Make a copy of the WinWarbler file, and name the copy BadWinWarbler 6. place both GoodWinWarbler and BadWinWarbler in a zip archive, attach the zip archive to an email message, and send the message to me via aa6yq (at) ambersoft.com * I'll be able to tell you what's different between the "bad settings" and the "good settings". 73, Dave, AA6YQ
|
+ 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
|
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.
John k9dx
?
Sent from for Windows 10
?
|
Re: Waterfall for Yeasu FT-991A
toggle quoted message
Show quoted text
On Fri, Mar 22, 2019 at 06:29 PM, Jerry wrote:
DXLab Commander Waterfall menu/box only appears if you pick an Icom radio on the list.?
+ Only if you set the "Radio Model" selector to IC-7300, IC-7610, IC-7850, or IC-7851.
What would it take to make DXLab so when choosing the FT-991A radio the waterfall box appears and the box can be checked so the waterfall screen can be used?
+ It would take a new version of FT-991A firmware from Yaesu that can convey spectrum data via the CAT interface, under the control of CAT instructions. That's how the above 4 Icom radios support Commander's Spectrum-Waterfall window.
+ I'm exploring ways of providing this capability using a low-cost SDR (like the RSP family) connected to an antenna or to your receiver's IF.
? ? ? ? 73,
? ? ? ? ? ? ? ? ? Dave, AA6YQ
?
?
?
|
Waterfall for Yeasu FT-991A
DXLab Commander Waterfall menu/box only appears if you pick an Icom radio on the list.? What would it take to make DXLab so when choosing the FT-991A radio the waterfall box appears and the box can be checked so the waterfall screen can be used? ? Jerry N7YGE
|
Re: RTTY (AFSK) **FIXED**
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.?
|
Re: DXKeeper backups question
+ 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 <>
|
Re: DXKeeper backups question
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
|
Re: RTTY (AFSK) **FIXED**
* more AA6YQ comments below
toggle quoted message
Show quoted text
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.
* Thanks, Joe. I added step 3.c in
<>
* to illustrate a muted output device, and explain how to unmute it.
+ Note that the K3 includes the ability to decode RTTY,
However, that decoder only works on the MAIN RECEIVER AUDIO.
* Understood. That provides two RTTY decoders for the DX station (2Tone, K3 internal) and one for the pileup (MMTTY).
73,
Dave, AA6YQ
|
Norm - KC1BMD
n4qwf .
Larry K8UT