Date   

updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


Enhancement requests

Dave AA6YQ
 

I will continue to accept enhancement requests in whatever form they are
posted.

That said, the process runs more smoothly when an enhancement describes a
scenario that illustrates how one or more DXLab applications currently do
not provided needed functionality, or provide functionality that is
difficult or awkward to use.

When an enhancement request is conveyed by proposing a change to an
application, I must first reverse engineer the "need" from the proposed
change. Sometimes I get that right, and sometimes I don't. Fortunately, many
of you notice these situations, and are willing to jump in to get the
discussion headed in the right direction. Please continue to do so!

73,

Dave, AA6YQ


Re: WSJT-X log pop up to log to DX Keeper

w6de
 

What you describe also happens to me on occasion.  I now wait to click on the Log It button until I receive his 73 or he goes away.  On crowded bands—like 20 meters—this happens regularly when I’m working Europe.

There is a way to possibly predict the distant station will not copy your RR73 or 73.  Look at what he sent you for a signal report if it is lower than roughly -10 start thinking he may not receive your end of QSO message.  For me I click the transmit button/bar to enable transmit and select the 73 message to send from the sequence list.  Then if I get the 73 from the distant station I un-select transmit and click OK to log the QSO. Repeat as necessary—which is usual for really weak distant stations.

 

73,

Dave, w6de

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of N0CWR via groups.io
Sent: Sunday, September 20, 2020 17:01
To: DXLab@groups.io
Subject: [DXLab] WSJT-X log pop up to log to DX Keeper

 

T6AA is on 20m FT8

 

I double click T1 WSJT FT-8 program.

So my FT-8 program sends a report to T6AA

I see he responds with report to me

A log pop up box comes up to log to DXbase so I click it and my FT-8 sends him a single RR 73
 All right that was easy . 

So now my FT8 program is all done sending.

As far as it’s concerned the contact is completed.

I see T6AA still sends me a report 

Clublog later shows NIL

What do I do to get a good QSO acknowledgement using  FT 8 when at my end the software is all done?

Is there something wrong with this software sequencing or is there something I should or shouldn’t be clicking?

It was all just so easy when the ‘clicking’ was done on my CW paddles! Ha!
73
Kevin





Re: WSJT-X log pop up to log to DX Keeper

g4wjs
 

On 20/09/2020 18:00, N0CWR via groups.io wrote:
T6AA is on 20m FT8

I double click T1 WSJT FT-8 program.

So my FT-8 program sends a report to T6AA

I see he responds with report to me

A log pop up box comes up to log to DXbase so I click it and my FT-8 sends him a single RR 73
 All right that was easy . 

So now my FT8 program is all done sending.

As far as it’s concerned the contact is completed.

I see T6AA still sends me a report 

Clublog later shows NIL

What do I do to get a good QSO acknowledgement using  FT 8 when at my end the software is all done?

Is there something wrong with this software sequencing or is there something I should or shouldn’t be clicking?

It was all just so easy when the ‘clicking’ was done on my CW paddles! Ha!
73
Kevin

Kevin,

WSJT-X is not a replacement for the operator, it has aids that help with the quick turnaround of QSOs where there is very little thinking time between decoding a signal and transmitting your reply. If your QSO partner does not copy your last acknowledgment then you must send it again - just like you would in a CW QSO. The mode might be different but the rules and conventions are the same.


--
73

Bill

G4WJS.


WSJT-X log pop up to log to DX Keeper

N0CWR
 
Edited

T6AA is on 20m FT8

I double click T1 WSJT FT-8 program.

So my FT-8 program sends a report to T6AA

I see he responds with report to me

A log pop up box comes up to log to DXkeeper so I click it and my FT-8 sends him a single RR 73
 All right that was easy . 

So now my FT8 program is all done sending.

As far as it’s concerned the contact is completed.

I see T6AA still sends me a report 

Clublog later shows NIL

What do I do to get a good QSO acknowledgement using  FT 8 when at my end the software is all done?

Is there something wrong with this software sequencing or is there something I should or shouldn’t be clicking?

It was all just so easy when the ‘clicking’ was done on my CW paddles! Ha!
73
Kevin






Re: SQL filter help

Dave AA6YQ
 

+ AA6YQ comments below

I agree Ian, bizarre.....have no idea where Dave is coming from

+ Jamie, the description of DXKeeper's Operator item is "the callsign of your station's operator".

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm#op_call>

+ It is designed to record a single callsign, not a list of callsigns.

my only suggestion was to expand this field longer than 13......nothing to do with illegal use, fabricated callsigns, etc.....I'll crawl back under my rock now.....

+ I misunderstood your request.

+ I cannot expand the meaning of the Operator item from its current "the callsign of your station's operator" to "a comma-separated list of station operators" because there is no ADIF field with the latter definition. If implemented, the requested expansion would prevent DXKeeper from exporting an ADIF OPERATOR field from a logged QSO's Operator item; that would be a regression in DXKeeper's functionality.

+ As Joe W4TV suggested, if you want each of your contest QSOs to record all of the participating operators, setup a user-defined item for that purpose; the capacity of a user-defined field is 1024 characters. See

<https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#User%20Items%20tab>

73,

Dave, AA6YQ


Re: SQL filter help

Joe Subich, W4TV
 

On 2020-09-19 10:21 PM, Jamie WW3S wrote:
since many different ops use the club callsign, I've been using the op
field to denote which group was there for that contest,
Jamie, your misuse of the Operator field is bizarre ... The "Operator
CALL" field is defined by ADIF as the *single* callsign of the operator
who logged (made) the QSO. If you want to record *all* the operators
involved in a multi-op effort, put their calls in the "Comments" field
or in one of the user defined fields.

73,

... Joe, W4TV


On 2020-09-19 10:21 PM, Jamie WW3S wrote:
I agree Ian, bizarre.....have no idea where Dave is coming from....here is a snip from one that worked....
since many different ops use the club callsign, I've been using the op field to denote which group was there for that contest, may not be the way it was intended, but it works, as long as the total string is less than 13 characters.....otherwise it returns this error:
my only suggestion was to expand this field longer than 13......nothing to do with illegal use, fabricated callsigns, etc.....I'll crawl back under my rock now.....
------ Original Message ------
From: "iain macdonnell - N6ML" <@N6ML>
To: DXLab@groups.io
Sent: 9/19/2020 10:10:37 PM
Subject: Re: [DXLab] SQL filter help

On Sat, Sep 19, 2020 at 6:44 PM Dave AA6YQ <@AA6YQ> wrote:

 + AA6YQ comments below

 It's for a club callsign, in a multi op contest....it took ND8L, WW3S but won't take longer....

 + It would be illegal to use that callsign over the air. Callsigns cannot contain spaces or punctuation. Also, US callsigns are issued by the FCC; you can't just fabricate one.
This conversation is getting a bit bizarre :)

Are we talking about the Operator Callsign field? If so, that's
intended to be the callsign of *the operator who made that QSO*, not
the list of all of the operators who jointly participated in a
multi-op contest entry. Contest logging software usually allows each
operator to "log in" (so subsequent QSOs will be logged with them as
the operator).

73,

    ~iain / N6ML


Re: SQL filter help

iain macdonnell - N6ML
 

On Sat, Sep 19, 2020 at 7:21 PM Jamie WW3S <ww3s@...> wrote:
since many different ops use the club callsign, I've been using the op field to denote which group was there for that contest, may not be the way it was intended, but it works, as long as the total string is less than 13 characters.....otherwise it returns this error:
The ADIF spec (https://www.adif.org/311/ADIF_311.htm#QSO_Field_OPERATOR)
defines it as:

"the logging operator's callsign"

So yeah, thatt's not how the field is intended to be used - it's
intended to store one (and only one) callsign.

73,

~iain / N6ML


Re: SQL filter help

Jamie WW3S
 

I agree Ian, bizarre.....have no idea where Dave is coming from....here is a snip from one that worked....



since many different ops use the club callsign, I've been using the op field to denote which group was there for that contest, may not be the way it was intended, but it works, as long as the total string is less than 13 characters.....otherwise it returns this error:



my only suggestion was to expand this field longer than 13......nothing to do with illegal use, fabricated callsigns, etc.....I'll crawl back under my rock now.....


------ Original Message ------
From: "iain macdonnell - N6ML" <ar@...>
Sent: 9/19/2020 10:10:37 PM
Subject: Re: [DXLab] SQL filter help

On Sat, Sep 19, 2020 at 6:44 PM Dave AA6YQ <aa6yq@...> wrote:
 
+ AA6YQ comments below
 
It's for a club callsign, in a multi op contest....it took ND8L, WW3S but won't take longer....
 
+ It would be illegal to use that callsign over the air. Callsigns cannot contain spaces or punctuation. Also, US callsigns are issued by the FCC; you can't just fabricate one.
 
This conversation is getting a bit bizarre :)
 
Are we talking about the Operator Callsign field? If so, that's
intended to be the callsign of *the operator who made that QSO*, not
the list of all of the operators who jointly participated in a
multi-op contest entry. Contest logging software usually allows each
operator to "log in" (so subsequent QSOs will be logged with them as
the operator).
 
73,
 
~iain / N6ML
 
 
 
 


Re: SQL filter help

iain macdonnell - N6ML
 

On Sat, Sep 19, 2020 at 6:44 PM Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

It's for a club callsign, in a multi op contest....it took ND8L, WW3S but won't take longer....

+ It would be illegal to use that callsign over the air. Callsigns cannot contain spaces or punctuation. Also, US callsigns are issued by the FCC; you can't just fabricate one.
This conversation is getting a bit bizarre :)

Are we talking about the Operator Callsign field? If so, that's
intended to be the callsign of *the operator who made that QSO*, not
the list of all of the operators who jointly participated in a
multi-op contest entry. Contest logging software usually allows each
operator to "log in" (so subsequent QSOs will be logged with them as
the operator).

73,

~iain / N6ML


Re: SQL filter help

Dave AA6YQ
 

+ AA6YQ comments below

It's for a club callsign, in a multi op contest....it took ND8L, WW3S but won't take longer....

+ It would be illegal to use that callsign over the air. Callsigns cannot contain spaces or punctuation. Also, US callsigns are issued by the FCC; you can't just fabricate one.

73,

Dave, AA6YQ


Re: SQL filter help

Jamie WW3S
 

It’s for a club callsign, in a multi op contest....it took ND8L, WW3S but won’t take longer....

On Sep 19, 2020, at 9:29 PM, Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

K3GP, ND8L, WW3S returns a string about exceeding the 13 character length....with or without the spaces....

+ That's not a valid US callsign, with or without the spaces

73,

Dave, AA6YQ

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 9/19/2020 9:18:03 PM
Subject: Re: [DXLab] SQL filter help

+ AA6YQ comments below

any chance of a future enhancement to the operator ID field.....13 characters is too small for some multi op operations.

+ Please provide some examples.

73,

Dave, AA6YQ





Re: SQL filter help

Dave AA6YQ
 

+ AA6YQ comments below

K3GP, ND8L, WW3S returns a string about exceeding the 13 character length....with or without the spaces....

+ That's not a valid US callsign, with or without the spaces

73,

Dave, AA6YQ

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 9/19/2020 9:18:03 PM
Subject: Re: [DXLab] SQL filter help

+ AA6YQ comments below

any chance of a future enhancement to the operator ID field.....13 characters is too small for some multi op operations.

+ Please provide some examples.

73,

Dave, AA6YQ


Re: problems integrating IC -746 as second radio into commander

Dave AA6YQ
 

+ AA6YQ comments below

Dave I have an aftermarket USB to cat cable. it is about 12 years old and so could be bad... I am going to try the CT17 tomorrow ... but I have no idea how to test for a good com port other than shutting down DXLab and setting up something like mixw to see if that works. Let me see if any of my USB utilities will work on this..

+ Since Commander correctly controls your IC-7300, you can use IC-7300 to test your USB-to-CIV cable with the same COM port you're using with the IC-746.

+ There is a small risk that your USB-to-CIV cable is damaged in a way that damages the connected transceiver's internal CI-V port. I've not seen this happen with Icom transceiver and interfaces, but have seen it in other debugging scenarios.

73,

Dave, AA6YQ


Re: SQL filter help

Jamie WW3S
 

K3GP, ND8L, WW3S returns a string about exceeding the 13 character length....with or without the spaces....

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 9/19/2020 9:18:03 PM
Subject: Re: [DXLab] SQL filter help

+ AA6YQ comments below

any chance of a future enhancement to the operator ID field.....13 characters is too small for some multi op operations.

+ Please provide some examples.

73,

Dave, AA6YQ







Re: SQL filter help

Dave AA6YQ
 

+ AA6YQ comments below

any chance of a future enhancement to the operator ID field.....13 characters is too small for some multi op operations.

+ Please provide some examples.

73,

Dave, AA6YQ


Re: problems integrating IC -746 as second radio into commander

Adrian Fewster
 

Dave, Ok on , that. Well it seems in either case Device manager is a useful tool to see ;

 

 

Real DB9 serial ports if known directly connected, such as above, of which there are usually few, numbered low, and ;

 

usb-ser ports which are well identified, with properties showing the type, ftdi etc which the user may know regarding the adapter ;

 

 

 

So only these would be considered , and the either type of connection of the two groups above, further defining the selectable range to try,

rather than guessing.

 

 

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Sunday, 20 September 2020 10:06 AM
To: DXLab@groups.io
Subject: Re: [DXLab] problems integrating IC -746 as second radio into commander

 

+ AA6YQ comments below

 

I was wondering if Jim has used device manager to identify the CAT comports ?

 

+ Unlike his IC-7300, the IC-746 does not have a built-in USB CI-V port; thus one can't use the technique of connecting the radio to the PC with a USB cable while watching the Ports section of the Windows Device Manager to see which serial port is created when the connection is made.

 

+ The IC-746 requires an external CI-V interface that must be connect to a PC serial port, or must be connected to a USB-to-serial-port adaptor. If a USB-to-serial-port adaptor is being used, making the USB connection while monitoring the Device Manager will reveal the serial port. Connecting the CI-V interface directly to a serial port requires knowing that serial port's COM #.

 

+ Correctly configured, Commander continuously directs the radio to report its frequency, mode, RX/TX status, etc. You can monitor the outgoing and incoming traffic in Commander's Messages window:

 

<https://www.dxlabsuite.com/commander/Help/MonitoringMessages.htm>

 

+ If the radio is not responding to the directives Commander is sending, one can use an oscilloscope to check the CI-V bus for radio responses. If they are present, you can then trace the signals through the CI-V interface to the serial port.

 

+ The CI-V interfaces inside Icom transceivers are vulnerable to failure from static discharge damage, but prosaic failures like "wrong baud rate" and "wrong CI-V address" are more common.

 

         73,

 

                 Dave, AA6YQ

 

 

 

 

 


Re: problems integrating IC -746 as second radio into commander

Jim
 

Dave I have an aftermarket USB to cat cable. it is about 12 years old and so could be bad... I am going to try the CT17 tomorrow ... but I have no idea how to test for a good com port other than shutting down DXLab and setting up something like mixw to see if that works.  Let me see if any of my USB utilities will work on this.. 

Dave I saw that string of reports indicating the 746 was not responding to the commands and nothing I sent it seemed to work. Thats why I started wondering about baud rate and data bits etc..  

Lets see what happens tomorrow 

 thanks guy


Re: problems integrating IC -746 as second radio into commander

Jim
 

Yes thats where I got them to plug into Commander  and thanks for asking..  sometimes you miss things like that.. 

Jim


Re: SQL filter help

Jamie WW3S
 

thanks Dave.....

any chance of a future enhancement to the operator ID field.....13 characters is too small for some multi op operations.

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 9/19/2020 8:15:10 PM
Subject: Re: [DXLab] SQL filter help

+ AA6YQ comments below

Need help filtering by contest ID and year, like CQWW cw in 2015, I thought I had it, but must have a bracket in the wrong place....

+ Try this:

(CONTEST_ID = 'CQWW') and (YEAR(QSO_BEGIN)=2015)

+ If your CQWW contest QSOs specify something other than CQWW in their CONTEST_ID items (like CQ-WW-CW), adjust the above expression
accordingly.

73,

Dave, AA6YQ