Date   
Re: WinWarbler Soundcard plugs on new PC

Dave AA6YQ
 

+ AA6YQ comments below

Dave - I would logically look at my previous PC - a WIN 7 machine that as a result of a 10/9 Net Framework Microsoft update wiped out all MS Office, Internet explorer and all DXLab Suite Apps . . . so I cannot look at the WW setup to see the setup OR move the settings! Wish I could.

+ Do you not have a Workspace backed up from that system?


Seems like using an external Soundcard to run WW should be simple, but since the transmit for RTTY works all OK, don't understand what is needed to make Receive work with my K3. It worked all OK w/ the WIN 7 machine and internal sound card, but not w/ WIN 10 and the external SC. Surely I am not the only one to have this problem w/ DXLab and WW!?

+ No one else has reported a problem with running digital modes on Windows 10 when properly configured (not counting Windows 10 updates wiping out settings).

Hopefully someone can provide some guidance.

+ Step 1 is to determine the name of the correct "receive soundcard" and configure WinWarbler to use it. If the soundcard documentation isn't explicit about the names of the soundcard devices it creates then

a. open the Windows Device Manager, expand the "Sound, video, and game controllers" section, and make a screen shot showing all soundcard devices

b. disconnect your soundcard's USB connection from your PC

c. open the Windows Device Manager, expand the "Sound, video, and game controllers" section, and make a screen shot showing all soundcard devices

d. reconnect your soundcard's USB connection from your PC

e. compare the screen shots taken in steps a and c; which soundcard devices disappeared when you disconnected your soundcard? If there's only one that disappeared, configure WinWarbler to use that soundcard for reception. If there's more than one, what are their names?


+ Step 2 is to configure Windows 10 to convey the audio from that receive soundcard at an appropriate volume level:

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

73,

Dave, AA6YQ

Re: WinWarbler Soundcard plugs on new PC

Alan Swinger
 

Dave - I would logically look at my previous PC - a WIN 7 machine that as a result of a 10/9 Net Framework Microsoft update wiped out all MS Office, Internet explorer and all DXLab Suite Apps . . . so I cannot look at the WW setup to see the setup OR move the settings! Wish I could. Seems like using an external Soundcard to run WW should be simple, but since the transmit for RTTY works all OK, don't understand what is needed to make Receive work with my K3. It worked all OK w/ the WIN 7 machine and internal sound card, but not w/ WIN 10 and the external SC. Surely I am not the only one to have this problem w/ DXLab and WW!?
Hopefully someone can provide some guidance.
Tks - Alan K9MBQ

On Wed, Oct 23, 2019 at 5:25 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Joe/all - As indicated in prior note, xmit work OK w/ soundcard Transmit set to SPDIF Interface (2-USB Advance). However, only intermittently does WW read text and am not seeing the clear Ovals. In Soundcard Reception have tried PSK & RTTY Reception in the Three settings available: Windows Default Soundcard; MIC (Realtech Audio); and MIC (2-USB Advance). In the Windows and 2-USB settings the visual presentation (where the ovals should be) is a highly concentrated blob in the middle. In the Realtech Audio setting I see a large noise blob w/o signal and deformation with signal approaching ovals.

Seems like this should not be this hard! Thoughts appreciated.

+ I suggest that you consult your transceiver's documentation to determine the name of the virtual soundcard it creates; if this information is not present in the documentation, then engage with the manufacturers Technical Support.

+ Alternatively, consult the instance of WinWarbler on your previous PC to see how you had it configured. Even better: move the settings from your previous PC to your new PC, as described in

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

        73,

               Dave, AA6YQ




Re: TS-480 Rig Control

Dave AA6YQ
 

+ AA6YQ comments below

Got it working. Main problem was the cable provided with the rig. It was a Null Modem cable and it requires a straight through cable. I used the same cable and USB-serial adaptor that works on the TS-2000. I had to restart Commander and the rig, but it finally worked.

Now to find a combination that will permit setting it up as a secondary rig.

+ Should be straightforward with a straight-through cable. See the "Setting up a Secondary Radio" via

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

+ Take care to protect the secondary transceiver's antenna input when your primary transceiver is transmitting...

73,

Dave, AA6YQ

Re: TS-480 Rig Control

Don Inbody AD0K
 

Got it working. Main problem was the cable provided with the rig. It was a Null Modem cable and it requires a straight through cable. I used the same cable and USB-serial adaptor that works on the TS-2000. I had to restart Commander and the rig, but it finally worked.

Now to find a combination that will permit setting it up as a secondary rig.

Re: WinWarbler Soundcard plugs on new PC

Dave AA6YQ
 

+ AA6YQ comments below

Joe/all - As indicated in prior note, xmit work OK w/ soundcard Transmit set to SPDIF Interface (2-USB Advance). However, only intermittently does WW read text and am not seeing the clear Ovals. In Soundcard Reception have tried PSK & RTTY Reception in the Three settings available: Windows Default Soundcard; MIC (Realtech Audio); and MIC (2-USB Advance). In the Windows and 2-USB settings the visual presentation (where the ovals should be) is a highly concentrated blob in the middle. In the Realtech Audio setting I see a large noise blob w/o signal and deformation with signal approaching ovals.

Seems like this should not be this hard! Thoughts appreciated.

+ I suggest that you consult your transceiver's documentation to determine the name of the virtual soundcard it creates; if this information is not present in the documentation, then engage with the manufacturers Technical Support.

+ Alternatively, consult the instance of WinWarbler on your previous PC to see how you had it configured. Even better: move the settings from your previous PC to your new PC, as described in

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

73,

Dave, AA6YQ

Re: WinWarbler Soundcard plugs on new PC

Alan Swinger
 

Joe/all - As indicated in prior note, xmit work OK w/ soundcard Transmit set to SPDIF Interface (2-USB Advance). However, only intermittently does WW read text and am not seeing the clear Ovals. In Soundcard Reception have tried PSK & RTTY Reception in the Three settings available: Windows Default Soundcard; MIC (Realtech Audio); and MIC (2-USB Advance). In the Windows and 2-USB settings the visual presentation (where the ovals should be) is a highly concentrated blob in the middle. In the Realtech Audio setting I see a large noise blob w/o signal and deformation with signal approaching ovals.

Seems like this should not be this hard! Thoughts appreciated.
Thanks - Alan K9MBQ

-----Original Message-----
From: Alan Swinger <awswinger@...>
Sent: Oct 21, 2019 6:29 AM
To: DXLab@groups.io, DXLab@groups.io
Subject: Re: [DXLab] WinWarbler Soundcard plugs on new PC

Tks, Joe. Transmit works OK, but need an RTTY sig to check Recv. Have Soundcard setting for Receive on MIC (Realtech audio) (vice Windows Default audio or MIC (2-usb adv audio)) - waiting to chk w/ a signal. - Alan K9MBQ


-----Original Message-----
From: "Joe Subich, W4TV" <lists@...>
Sent: Oct 20, 2019 9:31 PM
To: DXLab@groups.io
Subject: Re: [DXLab] WinWarbler Soundcard plugs on new PC


K3 Line Out and Line In are analog audio. They should be
connected to mic or analog Line IN an speaker or analog
line out on any sound card. The K3 can not connect to an
SPDIF (optical) connection.

If your Startech sound card is ICUSBAUDIO2D, connect the
K3 Line In to the jack marked with the headphones and
the K3 Line Out to the jack marked with the microphone.

73,

... Joe, W4TV


On 2019-10-20 8:13 PM, Alan Swinger wrote:
Despite prior help I am unable to work RTTY on my K3 using the startech external soundcard (connected to a USB port) with my Win 10 PC and Winwarbler. K3 is set to Line In. K3 Line in connected to soundcard SPDF Line out; K3 Line out connected to MIC on Soundcard. I can key the transmitter from Winwarbler, but I cannot read any signals heard.
Soundcard settings in WW:
- PSK & RTTY Reception - Windows Default
- PSK & RTTY Transmit - SPDIF Interface (2-USB Advance)
- Mixer Adjust - MIC-2USB Adv
- RTTY Demod Audio Channel - Mono

K3 is in Data mode w/ AFSK selected.

Don't know what I am missing or doing wrong. Help appreciated.
Thanks - Alan K9MBQ




Re: Heading info in Capture Window?

Rod Greene
 

Thanks for the clarification Dave.

I do have directional antennas. Haven't tried the rotor interface yet. Guess I need to set that up.

Okay on the screen shots - I won't bother with them again.

73, and thanks again - Rod/w7zrc

On Wednesday, October 23, 2019, 2:19:04 PM MDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

Still learning my way around this amazing bundle of software --

I'm trying to learn to use the Capture Window for DXKeeper. When I enter a call and tab it fills some information but does not show the az heading. I understand from the help that it will fill the heading from previous QSOs but is that the only way it looks up this info? In my example , using 5K0K, I have worked them a couple of times already but it does not fill the az heading in Capture. It does fill the az heading in Spot Collector and DXView okay. I've looked in the documentation for Capture, but not finding an answer.

I'll try pasting a screen shot - hope it works.

+ Screen shots aren't conveyed here.

+ If you click on the Log Page Display entry for any logged QSO, DXView's Main window will display the short-path and long-path headings for the great-circle path between your QTH and that of your QSO partner.

+ What the Capture window logs in its "Az" item is the last short-path or long-path heading that DXView sent to your antenna rotator; this information is displayed immediately above the SP and LP buttons on DXView's Main window. This enables you to accurately record skew paths and other unusual propagation events.

+ If you don't have a directional antenna, then you don't know what path your signals have taken, so there is no "Az" item to record.


        73,


              Dave, AA6YQ



Re: Heading info in Capture Window?

Dave AA6YQ
 

+ AA6YQ comments below

Still learning my way around this amazing bundle of software --

I'm trying to learn to use the Capture Window for DXKeeper. When I enter a call and tab it fills some information but does not show the az heading. I understand from the help that it will fill the heading from previous QSOs but is that the only way it looks up this info? In my example , using 5K0K, I have worked them a couple of times already but it does not fill the az heading in Capture. It does fill the az heading in Spot Collector and DXView okay. I've looked in the documentation for Capture, but not finding an answer.

I'll try pasting a screen shot - hope it works.

+ Screen shots aren't conveyed here.

+ If you click on the Log Page Display entry for any logged QSO, DXView's Main window will display the short-path and long-path headings for the great-circle path between your QTH and that of your QSO partner.

+ What the Capture window logs in its "Az" item is the last short-path or long-path heading that DXView sent to your antenna rotator; this information is displayed immediately above the SP and LP buttons on DXView's Main window. This enables you to accurately record skew paths and other unusual propagation events.

+ If you don't have a directional antenna, then you don't know what path your signals have taken, so there is no "Az" item to record.

73,

Dave, AA6YQ

Re: [eQSLLoggers] Change to the location of DownloadInbox.cfm generated files

Dave AA6YQ
 

+ AA6YQ comments below

If your logger started failing to find the ADIF file generated by DownloadInbox.cfm here is the reason:

We moved the DownloadedFiles folder to be above the QSLCard folder on October 22, 2019.

Any external programs that had hardcoded the folder structure might not find the files!

To prevent any folder structure changes from breaking your program, the hyperlinks on the results page should be followed to the location of the file.


+ Dave, here is your response to my request for a synchronization mechanism back in 2003:

________________________________
From: Dave Morris [mailto:dave@...]
Sent: Wednesday, October 22, 2003 10:36 PM
To: @AA6YQ
Subject: ADIF download of incoming eQSLs

Try this:

After logging into eQSL.cc, go here
http://www.eqsl.cc/qslcard/DownloadInbox.cfm and it will generate an ADIF formatted file of incoming eQSLs. Will that work?

73,
Dave N5UP

At 10:01 PM 10/22/2003 -0400, you wrote:

The mechanism I requested is to download QSOs from the database in ADIF
form -- no signing is required. This would permit a logging application
to automatically synchronize with eQSL.cc with respect to confirmations.
________________________________

+ Some comments

1. it is traditional to inform clients of potentially breaking changes *before* you make them, not afterwards

2. there is nothing in your message above about following hyperlinks, nor do I see any documentation on eQSL.cc describing exactly what is required

3. "the hyperlinks on the results page should be followed to the location of the file" is ambiguous. By "the results page", do you mean the page delivered by http://www.eqsl.cc/qslcard/DownloadInbox.cfm ?

4. One DXLab user has reported a synchronization failure, but my test a few minutes ago succeeded. Downloading http://www.eqsl.cc/qslcard/DownloadInbox.cfm yielded a page containing

http://www.eqsl.cc/qslcard/../downloadedfiles/AAPBJ9750.txt

which resolves to

http://www.eqsl.cc/downloadedfiles/AAPBJ9750.txt

which contains my inbox.


73,

Dave, AA6YQ

Re: Kenwood TS-890S with DX Lab

K4PX K4PX
 

Thanks Dave!


On Wed, Oct 23, 2019, 3:38 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Just received my Kenwood TS-890S.  Can you point me to instructions is getting DX Lab setup with the 890S.

+ See

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

      73,

            Dave, AA6YQ





Re: Kenwood TS-890S with DX Lab

Dave AA6YQ
 

+ AA6YQ comments below

Just received my Kenwood TS-890S. Can you point me to instructions is getting DX Lab setup with the 890S.

+ See

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

73,

Dave, AA6YQ

Kenwood TS-890S with DX Lab

K4PX K4PX
 

Just received my Kenwood TS-890S.  Can you point me to instructions is getting DX Lab setup with the 890S.  Thanks!
73,
Joe
K4PX

Re: Heading info in Capture Window?

Brian K <kb3wfv@...>
 

Rod,

If you click on SP (short path) or LP (long path) in DX View, the AZ box in the capture window will fill in and the rotor (if set up) will turn to that heading.

Brian
KB3WFV


On Oct 23, 2019, at 1:08 PM, Rod Greene via Groups.Io <w7zrc@...> wrote:

Still learning my way around this amazing bundle of software --

I'm trying to learn to use the Capture Window for DXKeeper. When I enter a call and tab it fills some information but does not show the az heading. I understand from the help that it will fill the heading from previous QSOs but is that the only way it looks up this info? In my example , using 5K0K, I have worked them a couple of times already but it does not fill the az heading in Capture. It does fill the az heading in Spot Collector and DXView okay. I've looked in the documentation for Capture, but not finding an answer.

I'll try pasting a screen shot - hope it works.

Thanks again, and 73, Rod/w7zrc



Heading info in Capture Window?

Rod Greene
 

Still learning my way around this amazing bundle of software --

I'm trying to learn to use the Capture Window for DXKeeper. When I enter a call and tab it fills some information but does not show the az heading. I understand from the help that it will fill the heading from previous QSOs but is that the only way it looks up this info? In my example , using 5K0K, I have worked them a couple of times already but it does not fill the az heading in Capture. It does fill the az heading in Spot Collector and DXView okay. I've looked in the documentation for Capture, but not finding an answer.

I'll try pasting a screen shot - hope it works.

Thanks again, and 73, Rod/w7zrc



Re: Save Settings To Workspace

Dave AA6YQ
 

I set up a workspace for backup-recovery. After invoking "Save Settings to Workspace" how do I know the process occurred?

+ No error message appeared informing you of a failure.

I don't recall seeing a message. Is there a way to easily inspect the file so I can tell the action happened?

+ Using Windows Explorer, navigate to the Launcher's Workspaces folder; it will contain a folder for each Workspace you've created. Each such folder contains a file for each of your applications containing its settings. Don't attempt to open these files, as by default Windows will load the settings they contain into the Windows Registry.

Is there an easy way to automate the save-to-workspace process, for example, an option screen comes up every time apps are terminated through Launcher (but see my other question about apps that don't start and stop through Launcher)? Or maybe I should figure out how to write a batch file to do this? (I have a friend who can write batch files and maybe I can get him to teach me.) I'm trying to make the backup/recovery process as painless as possible. I've been reading your help files on the subject and hope I didn't miss anything that answers my question.

+ It is only appropriate to update a Workspace after making permanent changes to an application's settings. The low frequency of this action does not merit automation.

73,

Dave, AA6YQ

Re: Launcher Operation and Configuration

Dave AA6YQ
 

+ AA6YQ comments below

In the help file talking about using workspaces as a way to build and switch between several configuration this line occurs:
"terminate all DXLab applications except the Launcher; the Launcher's Terminate button is a convenient way to do this"
At the suggestion of a more experienced DXLab user, I do not run View or SpotCollector through the Launcher, rather, I leave them on all the time. When I get ready for a radio session, I turn them off, invoke Launcher and after the other applications are loaded I load View and SC again individually so they communicate with Commander.

1. The Terminate button obviously doesn't work in the case such as mine. Perhaps there should be a master terminate button that would turn off all DXLab apps even if they weren't loaded through Launcher?

+ You can use the Terminate button to terminate most of your DXLab applications, and manually terminate SpotCollector and DXView by clicking the X buttons in the upper-right corner of their Main windows.

2. Do you have any observations on the pros and cons of running DXLab suites which don't start and terminate through Launcher - am I engage in a bad practice?

+ You can start/terminate DXLab applications using whatever mechanism you find most convenient.

73,

Dave, AA6YQ

Re: 3 Column Labels

Dave AA6YQ
 

+ AA6YQ comments below

I use 3 column labels and am finding that some have “Pse QSL” printed but some do not. I thought I had set up everything correctly as outlined in the documentation but clearly I was wrong.

Having read and reread the documentation I have not found the solution.

+ In the Options panel on the "QSL Configuration window's General tab, check the "Outgoing QSLs request confirmation unless already confirmed" box.

+ Then each outgoing QSLs will include "Pse QSL!" unless you've already received a QSL.

73,

Dave, AA6YQ

Re: Launcher Operation and Configuration

Don Inbody AD0K
 

Why not start SC and DV from the launcher to leave them running. Then, when you begin operation, just click start to get the others going. When you subsequently click Terminate, it will shut down all applications.

Do not check "Shutdown after Terminate"

Re: 3 Column Labels

ND9G Mike
 

You may need to check the box for Include QSL Mgr & Pse/Tnx QSL box on the QSL Labels tab of the QSL config window.


You may also choose to enable the Outgoing QSLs request confirmation unless already confirmed box on the General tab of QSL config

The overarching topic of paper QSLing is described here with links to the above two specific areas.

73,
Mike ND9G


On Wed, Oct 23, 2019 at 7:19 AM Ivor Lee <mm02m0iel@...> wrote:


I use 3 column labels and am finding that some have “Pse QSL” printed but some do not.  I thought I had set up everything correctly as outlined in the documentation  but clearly I was wrong.  

Having read and reread the documentation I have not found the solution.


Advice please on what I need to do to ensure all labels include Pse QSL?


Thanks

Ivor
MM0IEL

Save Settings To Workspace

 

I set up a workspace for backup-recovery.  After invoking "Save Settings to Workspace" how do I know the process occurred? I don't recall seeing a message.  Is there a way to easily inspect the file so I can tell the action happened?
Is there an easy way to automate the save-to-workspace process, for example, an option screen comes up every time apps are terminated through Launcher (but see my other question about apps that don't start and stop through Launcher)?  Or maybe I should figure out how to write a batch file to do this?  (I have a friend who can write batch files and maybe I can get him to teach me.)
I'm trying to make the backup/recovery process as painless as possible.  I've been reading your help files on the subject and hope I didn't miss anything that answers my question.
--
Jim NO0B