Date   

Re: WW ISSUE - RTTY

Jim Denneny <57JNDenneny@...>
 

Whoa.  WW is not working in CW either.  Looks like a total WW reinstall.  Can someone point me to reinstall wiki? This happened overnight

Jim


Re: WW ISSUE - RTTY

Jim Denneny <57JNDenneny@...>
 

Also, MMTTY Profiles are now blank

Jim


WW ISSUE - RTTY

Jim Denneny <57JNDenneny@...>
 

Issue just developed doing WW RTTY Setup. WW worked yesterday in RTTY.

In WW RTTY Configuration MMTTY Setup button does not respond.

RTTY works in MMTTY standalone and N1MM.I use low tones with FSK.

Jim K7EG


Re: Eqsl and LoTW panels missing from Log page display

Dave AA6YQ
 

+ AA6YQ comments below

If you look at <https://www.dxlabsuite.com/dxlabwiki/LogPageDisplayConfiguration> and the image that shows the 2 panels under On Line QSL that show the contacts status for EQSL and LoTW are what I'm missing. 

+ See the third paragraph and first screen shot in

<https://www.dxlabsuite.com/dxlabwiki/QSLingLotW>

       73,

              Dave, AA6YQ


Re: Eqsl and LoTW panels missing from Log page display

ve3ki
 

On that same image there is a set of check boxes at the upper right. Check the one called "Online QSL".

73,
Rich VE3KI


On Sun, Sep 6, 2020 at 04:22 PM, Marv Stasak wrote:
Dave,
If you look at <https://www.dxlabsuite.com/dxlabwiki/LogPageDisplayConfiguration> and the image that shows the 2 panels under On Line QSL that show the contacts status for EQSL and LoTW are what I'm missing. 


Re: Eqsl and LoTW panels missing from Log page display

Marv Stasak
 

Dave,
If you look at <https://www.dxlabsuite.com/dxlabwiki/LogPageDisplayConfiguration> and the image that shows the 2 panels under On Line QSL that show the contacts status for EQSL and LoTW are what I'm missing. 


DXKeeper configured for SWL/MWDX/etc?

Peter Laws / N5UWY
 

Has anyone every played with a configuration -- stored in a separate
workspace because as another poster recently mentioned, workspaces are
the bomb -- that is optimized for non-amateur station logging? I've
looked at what's out there for SWL logging and it's OK, I guess, but
most of the authors would like some money, please, and the programs
look like a chore to use, or at least learn.

Since I'm already a long-time DXLab user and not really willing to
learn a new package, let alone pay some for the privilege, I thought
I'd start here in case someone had experience with this. It's only
the log part that interests me because 90% of the rest of the suite --
which I use all the time on the amateur bands -- is not really useful
for SWL (or MWDX or FMDX ...).

Anyone done this?

Please don't suggest other packages - I have no interest. I use
spreadsheets now and will continue to do that *unless* I can bend
DXKeeper to the task (it's an amateur log, I get it, I use it that
way, don't post and say "you know it's an *amateur* log, right?").

Peter

--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: IC-7610 Operation. Dual Watch/HDSDR Search and Pounce (Help!)

Dave AA6YQ
 

+ AA6YQ comments below

Well, the IC-7610 is fantastic. SDR opens up some very interesting doors and the visualization of the spectrum gives a depth of perspective I have long desired. It's like reading a book, and seeing the movie. In this case, both are outstanding, but together they're marvelous.

So, anyway. I have always wanted a second receiver as well, but here is where I'm somewhat flummoxed. What I'd like to do (I think), is to use the second receiver to center the frequency of the I/Q output, then on HDSDR (for the porpoises of this example, and other than the bewildering lack of documentation seems rather capable) I'd like to scan/view the bands for signals. When I find one that I'd like to reply (transmit) to, I'd like to (right?) click something to transfer the 'Tune' frequency to VFO-A, Thus allowing me to 'pounce' (reply) and conduct a QSO with that station, while continuing to use HDSDR to independently continue the 'search'. "Search and pounce" right?

+ Do you have a second antenna that allows you to receive on the second receiver while are in QSO?

Here's the 'rub'. While this seems straight forward, I've simply been unable to configure my station for this method of operation. I've got all the pieces and parts in place. I've configured through omnirig and virtual audio cables to use cwskimmer (what a thrill), just so i could say I did.

I've found that setting WSJT-X to 'fake it' for split mode operation is part of the solution, so that it doesn't take over the second receiver.

Currently I've got HDSDR configured to control the radio through the I/Q USB-B connection, and Commander through the first serial port CIV on USB-A. PTT is setup on RTS on the second serial port. Omnirig and virtual serial ports are not in play. I'm not at all opposed to using omnirig as a secondary CAT interface for my porpoises, just doing it this way for now because I can. ;)

Whenever I select and double click in Spot Collector, Commander QSY's the 1st receiver (VFO-A) and unsets dual watch! Where do I disable this behavior?

+ In the General panel on the General tab of Commander's Configuration window, uncheck the "Accept Dual Rcv Off directives" box.

And how do I transfer the 'TUNE' VFO in HDSDR to VFO-A on the radio?

+ Configure Commander's Secondary CAT to interoperate with HDSDR using "Lead primary" or "Follow & lead primary". This article shows the general approach to interoperation with SDR Consoles like HDSDR:

<https://www.dxlabsuite.com/dxlabwiki/SDRTopics>

+ This article specific to HDSDR may describe close to what you're seeking

<https://www.dxlabsuite.com/dxlabwiki/HDSDRCWSkimmerConfiguration>

+ In your case, the block labeled "SDR Hardware" would be your iC-7610's second receiver, and the block labeled "CW Skimmer" would be absent.

73,

Dave, AA6YQ


Re: Workspaces - use them!

Jon Gefaell
 

I couldn't agree more. This methodology of using available backup facilities and storing in (multiple locations/services) on the cloud and locally. I run MacOS on everything but the shack computer, and the continuity options are flabbergasting. In Windows, I use Macrium to create bootable backup images and so forth. Not as facile and rapid as MacOS, but definitely functional and allows for rapid RTO (Recovery Time Objective) with a fantastic RPO (Recovery Point Objective) of 100%


IC-7610 Operation. Dual Watch/HDSDR Search and Pounce (Help!)

Jon Gefaell
 

Well, the IC-7610 is fantastic. SDR opens up some very interesting doors and the visualization of the spectrum gives a depth of perspective I have long desired. It's like reading a book, and seeing the movie. In this case, both are outstanding, but together they're marvelous.

So, anyway. I have always wanted a second receiver as well, but here is where I'm somewhat flummoxed. What I'd like to do (I think), is to use the second receiver to center the frequency of the I/Q output, then on HDSDR (for the porpoises of this example, and other than the bewildering lack of documentation seems rather capable) I'd like to scan/view the bands for signals. When I find one that I'd like to reply (transmit) to, I'd like to (right?) click something to transfer the 'Tune' frequency to VFO-A, Thus allowing me to 'pounce' (reply) and conduct a QSO with that station, while continuing to use HDSDR to independently continue the 'search'. "Search and pounce" right?

Here's the 'rub'. While this seems straight forward, I've simply been unable to configure my station for this method of operation. I've got all the pieces and parts in place. I've configured through omnirig and virtual audio cables to use cwskimmer (what a thrill), just so i could say I did. 

I've found that setting WSJT-X to 'fake it' for split mode operation is part of the solution, so that it doesn't take over the second receiver. 

Currently I've got HDSDR configured to control the radio through the I/Q USB-B connection, and Commander through the first serial port CIV on USB-A. PTT is setup on RTS on the second serial port. Omnirig and virtual serial ports are not in play. I'm not at all opposed to using omnirig as a secondary CAT interface for my porpoises, just doing it this way for now because I can. ;) 

Whenever I select and double click in Spot Collector, Commander QSY's the 1st receiver (VFO-A) and unsets dual watch! Where do I disable this behavior? And how do I transfer the 'TUNE' VFO in HDSDR to VFO-A on the radio?

  • THANK YOU IN ADVANCE! 


Re: Eqsl and LoTW panels missing from Log page display

Dave AA6YQ
 

+ AA6YQ comments below

I have been reinstalling DXLab after having to replace an old computer.

+ Did you save all of your settings on the old computer to a Workspace and move that Workspace to your new computer, as described in step 3.h of this procedure?

<https://www.dxlabsuite.com/dxlabwiki/MovingBetweenPCs>


The Eqsl and LoTW panels are missing from the Log page display. I looked through the setup info and don't see want I missed but it must be something.

+ If you're seeking to add eQSL and LoTW columns to the Log Page Display, see these step-by-step instructions:

<https://www.dxlabsuite.com/dxlabwiki/LogPageDisplayConfiguration>

73,

Dave, AA6YQ


Eqsl and LoTW panels missing from Log page display

Marv Stasak
 

I have been reinstalling DXLab after having to replace an old computer.  The Eqsl and LoTW panels are missing from the Log page display.  I looked through the setup info and don't see want I missed but it must be something.


Re: CBA Look-ups in the Log QSOs tab not 'color-coding' for LoTW, eQSL or both

Carl - WC4H
 

Hi Howard.

Try this: 
Go to the QSL tab and click on "Sync LoTW QSOs" button.   Once that's done, click on the "Sync LoTW QSLs" button.  You should see the lines with the appropirate colors in the Log Display grid.

73.
Carl - WC4H


Re: CBA Look-ups in the Log QSOs tab not 'color-coding' for LoTW, eQSL or both

Dave AA6YQ
 

+ AA6YQ comments below
I previously was using JTAlert-X to log QSOs from WSJT-X in DXKeeper and CBA Look-up worked. The log updated to reflect the colors in the QSL Sent Key for LoTW, eQSL or Both. Also, when using JTAlert, DXKeeper would perform a look-up for previous QSOs - this does not occur with Gridtracker. what needs to occur in GridTracker for the lookup to happen?

Now I'm using Gridtracker to log to DXKeeper and the CBA Lookup is not pulling the color coding - but appears to be performing a look-up for relevant data. I also tried to see if SpotCollecter may be an issue - nothing evident. I've looked to see if I've changed a setting that might affect this but didn't see anything relevant. Help and advice is appreciated.

+ If there is interoperation between GridTracker and DXLab, I'm not aware of it. When operating K1JT modes, there are two forms of interoperation: direct, and with JT-Alert. See

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes>

+ Also note that DXLab can displaye worked/confirmed grid squares on the DX Atlas world map:

<https://www.dxlabsuite.com/dxlabwiki/GridPlottingDXAtlas>

          73,

               Dave, AA6YQ


CBA Look-ups in the Log QSOs tab not 'color-coding' for LoTW, eQSL or both

Howard Waxman, WZ4K
 

I previously was using JTAlert-X to log QSOs from WSJT-X in DXKeeper and CBA Look-up worked. The log updated to reflect the colors in the QSL Sent Key for LoTW, eQSL or Both. Also, when using JTAlert, DXKeeper would perform a look-up for previous QSOs - this does not occur with Gridtracker. what needs to occur in GridTracker for the lookup to happen?

Now I'm using Gridtracker to log to DXKeeper and the CBA Lookup is not pulling the color coding - but appears to be performing a look-up for relevant data. I also tried to see if SpotCollecter may be an issue - nothing evident. I've looked to see if I've changed a setting that might affect this but didn't see anything relevant. Help and advice is appreciated.

73, Howard, WZ4K


Re: Auxiliary 'station call' flashing

Dave AA6YQ
 

In Dx keeper the blue station call is flashing, no matter what I do I cannot enter my callsign into the auxiliary boxes.

+ On the Configuration window's General tab, do you have the "Main Log QSOs options" panels' "Require Edit to modify logged QSOs"
box checked? If so, then on the Main window's "Log QSOs" tab, you must click the Edit button above the Log Page Display (on the
left) before you can enter your callsign into the auxiliary boxes.

+ As Tim N3XX suggested, setting your "Station Callsign" on the Configuration window's Defaults tab will eliminate the need to do
this each time you log a new QSO.

+ If you have many logged QSOs that are missing a "Station Callsign" item, you can fill them in "en masse", as described here:

<https://www.dxlabsuite.com/dxlabwiki/QSOModifying>

+ Don't skip step 1 !

73,

Dave, AA6YQ


Re: Auxiliary 'station call' flashing

Tim N3XX
 

Go to DXKeeper Config, Defaults tab. You can enter the station callsign there.

73,
Tim - N3XX

On 2020-09-05 2:45 PM, Max Cotton wrote:
In Dx keeper the blue station call is flashing, no matter what I do I cannot enter my callsign into the auxiliary boxes. TZ4AM was the call entered.
Help,
73 Max M0GHQ


Auxiliary 'station call' flashing

Max Cotton
 

In Dx keeper the blue station call is flashing, no matter what I do I cannot enter my callsign into the auxiliary boxes. TZ4AM was the call entered. 
Help,
73 Max M0GHQ


Re: WW and MMTTY RX Issue

Joe Subich, W4TV
 

Without knowing which setting had been changed, it is hard to say
what caused the problem. However, The MMTTY MARK frequency is
stored in MMTTY.INI - you have at least three copies (in N1MM+,
in the stand alone MMTTY directory, and in your WinWarbler directory) -
*and* in the Windows Registry entries for WinWarbler (plus your
"workspace" if you use that feature as recommended). If the issue
existed for all three applications, I would say the K3 pitch had
been changed.

The K3/K3S DATA/PITCH setting is not changed in the CONFIG menu -
it is changed using the "Pitch" key (SPOT/Hold) and VFO A while
the K3 is in DATA/DATA_A or DATA/FSK_D mode.

73,

... Joe, W4TV

On 2020-09-05 12:14 PM, Jim Denneny wrote:
Appreciate the analysis Joe.  I guess tone mismatch remains a mystery if root cause is not Win 10 upgrade. I have used these apps for years and never experienced high-low tone mismatch.  Also, it has been over a year since I was in the K3S CONFIG menu. You can be sure I will remain vigilant to this event. Thanks again to all who responded.
73, Jim K7EG


Re: WW and MMTTY RX Issue

Jim Denneny <57JNDenneny@...>
 

Appreciate the analysis Joe.  I guess tone mismatch remains a mystery if root cause is not Win 10 upgrade. I have used these apps for years and never experienced high-low tone mismatch.  Also, it has been over a year since I was in the K3S CONFIG menu. You can be sure I will remain vigilant to this event. Thanks again to all who responded.

73, Jim K7EG

15061 - 15080 of 211152