Date   

Re: QRZ look up in DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

Not at all , but than I saw in the pathfinder an option Internet Explorer Emulation, clicked update and now it works.

+ I'm glad you found and corrected the configuration problem, Alex. Nice work!

73,

Dave, AA6YQ


Re: DXKeeper: Filtering/Exporting QSO data of QSOs made with members of a club to an ADIF-file

Dave AA6YQ
 

* More AA6YQ comments below

There is no way to do that with SQL or DXKeeper.

* Tom DF7TV, please attach an example of a "callsign file" to an email message, and send it to me via

aa6yq (at) ambersoft.com

* I'll add a new "Set Select from Callsign File" function to DXKeeper that will set the "Select" item to 'Y' for each QSO in the Log Page Display whose callsign appears in the selected file.

* To export an ADIF file containing these QSOs, the workflow would be

1. click the "Clear Select" item on the Main window's "Check Progress" tab (clears the Select items of every QSO in your log)

2. click the X button in the Filter panel at the bottom of the Main window's "Log QSOs" tab (removes all filtering from the Log Page Display)

3. click the new "Set Select from Callsign File" function (as described above)

4. click the Sel button in the Filter panel at the bottom of the Main window's "Log QSOs" tab (filters the Log Page Display to contain all QSOs whose Select items are set to 'Y')

5. select the Main window's "Export QSOs" tab, and click the Start button to export the selected QSOs (exports an ADIF file containing all QSOs in the Log Page Display)

73,

Dave, AA6YQ


Re: Creating a List of QSO's with DXCC Entities for which Confirmation is Needed

dwfred@bellsouth.net
 

Hi Dave,
This query is good for finding all QSOs that haven't been confirmed.  What I'm looking for is a step further.  I am trying to find a way to find all QSOs only for COUNTRIES that have not been confirmed.  I'm not looking for every unconfirmed QSO -- I want to know which QSOs would confirm a new country.  I have a pile of cards and I want to know which ones I need to submit to boost my LOTW already verified with LOTW.
It seems a SELECT FOR NOT COUNTRY_CONFIRMED would be needed in an SQL query, before applying your query.  The problem is, the "COUNTRY_CONFIRMED" would have to be the result of checking each QSO in the database to generate this confirmed list.  Using an SQL database, I think I could figure it out, but I don't know how to do it within the context of DxLab.  

Any ideas?

Thanks & 73!
Dean


Re: QRZ look up in DXKeeper

Alex OE3JTB
 

Not at all , but than I saw in the pathfinder an option Internet Explorer Emulation, clicked update and now it works.
Tnx Dave
73 Alex, OE3JTB


Re: DXKeeper: Filtering/Exporting QSO data of QSOs made with members of a club to an ADIF-file

Dave AA6YQ
 

There is no way to do that with SQL or DXKeeper.

    73 de AA6YQ


DXKeeper: Filtering/Exporting QSO data of QSOs made with members of a club to an ADIF-file

Tom DF7TV
 

Hello,
Assume there is a list (a one column txt-file) listing all callsigns of members of a club (member list).

Now to apply for an award of that club I want to transfer an ADIF-file to the award manager
only showing the QSO data of all QSOs with members of this club shown in the member list.

May you give me some information of an effective way (SQL ?) to do this within DXKeeper ?

TNX in advance
73, Stay well!

Tom


Re: NEED HELP IN GETTING COMMANDER WORKING

Andrew OBrien
 

My experience with FSK RTTY using Winwarbler and Commander with a 7610, 7300, and 705 is that most hiccups are with the radio's "keying" menu settings .  Occasionally with MMTTY Engine settings but usually the steps missed are the radio settings.
Andy K3UK

On Sun, Mar 7, 2021 at 9:20 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Dave: Last night I had WW working in AFSK. I could receive and decode I could press the transmit button (in WW) and it would key the
radio, send diddles, with RF out. I could type in RY's TEST then my call in the transmit window and it would transmit that. Today, I
could not duplicate WW working on AFSK.

OK, so today (starting over) I started Launcher,  and Commander. Pressing the TX button in commander keyed the radio, produced a
single tone and I did get RF out. I then started WW, which changed the radio to LSB, and I press the TX button in WW. It did not key
the radio and did not produce a tone or any RF even though the software thought it was transmitting. When I checked port five, the
port used to control the radio, WW said it was not available. I'm guessing that is because it was being used by commander. ??

You sent me a link to "Configuring WinWarbler for RTTY Operation" which I followed religiously (both AFSK and FSK) but, it did not
work. I also tried the radio in D1, D2 & D3 but that made no difference. Throughout all of these tests, I could receive and decode
RTTY in WW. I even tried the K0PIR video for N1MM with MMTTY with same lack of results.

+ The article "Configuring WinWarbler for RTTY Operation" does not cover configuring WinWarbler for RX-TX switching (aka "PTT");
that's described in "Switching a Transceiver between Reception and Transmission" in

https://www.dxlabsuite.com/dxlabwiki/PTTMechanism

+ My assumption was that anyone wishing to use WinWarbler would first review "Setting up CW, Phone, PSK, and RTTY Operation in
WinWarbler" in

https://www.dxlabsuite.com/dxlabwiki/Multimode_Setup

+ which introduces configuration topics common to all modes: RX-TX switching, audio connections, and setting audio levels. See the
RTTY subsection in the "General Setup Instructions" section of this article.

+ To prevent this from happening again, I have added a "Configuration Steps You May Have Already Taken" section to the beginning of

"Configuring WinWarbler for RTTY Operation" in

https://www.dxlabsuite.com/dxlabwiki/ConfigureRTTY

+ and added  steps for making the required audio settings and level adjustments.

+ Since you're using Commander to control your IC-7610, and since Commander can switch your IC-7610 between RX and TX, on the
Configuration window's PTT tab, set the Mode panel to "Xcvr Ctrl App" and set the Port panel to None. If that doesn't enable
WinWarbler to switch your transceiver between RX and TX, please let me know.

        73,

              Dave, AA6YQ











updated eQSL AG and LoTW databases are available ...

Dave AA6YQ
 

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

73,

Dave, AA6YQ


Re: DXKeeper auto populate

Dave AA6YQ
 

+ AA6YQ comments below

Well that would be better than what's happening now.
 
Your suggestion sounds like a reasonable solution.

+ I've sent a you a version of DXKeeper. In this version, when double-clicking a Spot Database Entry in SpotCollector sends a NewEntry directive to DXKeeper with SpotCollector's "Log Filter" option set to "Call" and DXKeeper's "Display previous QSOs on Lookup" option  disabled, DXKeeper's Filter panel textbox is set to the Spot Database Entry's callsign - making it possible to quickly display previous QSOs with that callsign by clicking the Filter panel's Call button - which won't extract information from those previous QSOs and use it to populate the Capture window.

+ Please let me know how it goes...

       73,
 
              Dave, AA6YQ

 


Re: CQ 160 SSB contest submit problem

Dave AA6YQ
 

+ AA6YQ comments below

Tnx Dave and I used the Capture window in DXKeeper. Did not see anything in the window that said "RX#". From memory it would show the state in the area that said "pri sub". I think in the contest mode it that area said "state or prov".

+ The Capture window's rx# box is the right-most box in the 11th row of boxes in the Capture window. Take a look at this screenshot:

http://www.dxlabsuite.com/dxkeeper/FullCapture.jpg

+ You may have to drag the Capture window's lower border downward to make the 11th row of boxes visible; see the 2nd and 3rd screen shots in "Getting Started with Logging" in

https://www.dxlabsuite.com/dxlabwiki/Logging

+ The rx# box is always present, whether "Contest Mode" is enabled or not.


When I imported my ADIF file into N1MM after the test, I did a Cabrillo generation but the state never showed up. Sounds like there should be a header called "Exch" or something like that in the ADIF file. My ADIF file shows the state in header called "state"

+ QSOs imported from N1MM do not comply with the rules specified in the large table in

https://www.dxlabsuite.com/dxkeeper/Help/Contesting.htm

+ If you use N1MM in a contest and want to submit a Cabrillo file for the QSOs logged in that contest, generate that Cabrillo file from N1MM.

73,

Dave, AA6YQ


Re: CQ 160 SSB contest submit problem

Phil W9IXX
 

Hi,

Tnx Dave and I used the Capture window in DXKeeper. Did not see anything in
the window that said "RX#". From memory it would show the state in the area
that said "pri sub". I think in the contest mode it that area said "state or prov".

When I imported my ADIF file into N1MM after the test, I did a Cabrillo generation
but the state never showed up. Sounds like there should be a header called "Exch" or
something like that in the ADIF file. My ADIF file shows the state in header called "state"

Sorry for such a minor item.
Tnx agn.
Phil W9IXX


Re: sorting out Log to LotW discrepancies

David Reed
 

Thank you sir; will get right on it!

73 de W5SV - David F. Reed

On Mar 7, 2021, at 20:47, Dave AA6YQ <aa6yq@...> wrote:

Assuming that the table in your post below was generated when you clicked the Compare button in the "DXCC, Challenge, TopList" panel on the "Check Progress" tab of DXKeeper's Configuration window, that's not and indication of how well your log and LoTW match. As described in

http://dxlabsuite.com/dxkeeper/Help/Progress.htm#Verification%20discrepancies

the Compare function displays discrepancies between DXCC award credit shown as granted in your logged QSOs, and DXCC award credit shown as granted in your DXCC record - as maintained by the ARRL.

19 of the 20 discrepancies listed are cases in which your DXCC record contains no credit granted, but a logged QSO shows DXCC credit granted: either its "QSL Rcvd" or "LoTW QSL Rcvd" item is set to 'V'. For each of these 19 discrepancies, determine why each is marked "DXCC credit granted" when there is no such credit shown in your DXCC record: either its "QSL Rcvd" or "LoTW QSL Rcvd" item was erroneously set to 'V', or your DXCC record is in error. If the former, change the erroneous status item from 'V' to 'Y'; if the latter, engage with the ARRL's DXCC desk (dxccadmin {at} arrl.org) and request a correction.

In the case of "Guadeloupe on 20m", your DXCC record shows that DXCC credit has been granted, but no logged 20m QSO with Guadeloupe has its "QSL Rcvd" or "LoTW QSL Rcvd" item set to 'V'. Determine which 20m QSO with Guadeloupe you submitted in a DXCC award application, and change its "QSL Rcvd" or "LoTW QSL Rcvd" item from 'Y' to 'V', depending upon whether you submitted a QSL card or LoTW confirmation, respectively.

       73,

              Dave, AA6YQ

 

On Sun, Mar 7, 2021 at 03:11 PM, David Reed wrote:

Hi folks; taking a break from the contest for a few moments; I thought "I wonder how well my log and LotW match?" so I ran the report to identify any.

No surprise that I have some; my problem is to figure out what to do about them so both are correct and no discrepancies are reported...

Here is what it looks like:

   Entity Prefix     Band or Mode     Log Status    ARRL Status    Entity Code   Entity


               5R              20m              V -            438   Madagascar
               DA            Phone V             81   Germany (deleted)
               DA            Mixed V             81   Germany (deleted)
               FG              20m              W V             79   Guadeloupe
               FG              15m              V -             79   Guadeloupe
              FO0               CW              V -             36   Clipperton Island
               FW              15m              V -            298   Wallis & Futuna Islands
               GD              17m              V -            114   Isle Of Man
             HK0S            Phone V            228   Serrana Bank & Roncador Cay (deleted)
             HK0S            Mixed V            228   Serrana Bank & Roncador Cay (deleted)
              KH6              12m              V -            110   Hawaii
              KH6          Digital              V -            110   Hawaii
              KZ5            Phone V             28   Canal Zone (deleted)
              KZ5            Mixed V             28   Canal Zone (deleted)
               OK            Phone V            218   Czechoslovakia (deleted)
               OK            Mixed V            218   Czechoslovakia (deleted)
               P4               CW              V -             91   Aruba
              YV0            Phone V             17   Aves Island
              YV0            Mixed V             17   Aves Island
               ZS              80m              V -            462   Republic of South Africa


Re: sorting out Log to LotW discrepancies

Dave AA6YQ
 

Assuming that the table in your post below was generated when you clicked the Compare button in the "DXCC, Challenge, TopList" panel on the "Check Progress" tab of DXKeeper's Configuration window, that's not and indication of how well your log and LoTW match. As described in

http://dxlabsuite.com/dxkeeper/Help/Progress.htm#Verification%20discrepancies

the Compare function displays discrepancies between DXCC award credit shown as granted in your logged QSOs, and DXCC award credit shown as granted in your DXCC record - as maintained by the ARRL.

19 of the 20 discrepancies listed are cases in which your DXCC record contains no credit granted, but a logged QSO shows DXCC credit granted: either its "QSL Rcvd" or "LoTW QSL Rcvd" item is set to 'V'. For each of these 19 discrepancies, determine why each is marked "DXCC credit granted" when there is no such credit shown in your DXCC record: either its "QSL Rcvd" or "LoTW QSL Rcvd" item was erroneously set to 'V', or your DXCC record is in error. If the former, change the erroneous status item from 'V' to 'Y'; if the latter, engage with the ARRL's DXCC desk (dxccadmin {at} arrl.org) and request a correction.

In the case of "Guadeloupe on 20m", your DXCC record shows that DXCC credit has been granted, but no logged 20m QSO with Guadeloupe has its "QSL Rcvd" or "LoTW QSL Rcvd" item set to 'V'. Determine which 20m QSO with Guadeloupe you submitted in a DXCC award application, and change its "QSL Rcvd" or "LoTW QSL Rcvd" item from 'Y' to 'V', depending upon whether you submitted a QSL card or LoTW confirmation, respectively.

       73,

              Dave, AA6YQ

 

On Sun, Mar 7, 2021 at 03:11 PM, David Reed wrote:

Hi folks; taking a break from the contest for a few moments; I thought "I wonder how well my log and LotW match?" so I ran the report to identify any.

No surprise that I have some; my problem is to figure out what to do about them so both are correct and no discrepancies are reported...

Here is what it looks like:

   Entity Prefix     Band or Mode     Log Status    ARRL Status    Entity Code   Entity


               5R              20m              V -            438   Madagascar
               DA            Phone V             81   Germany (deleted)
               DA            Mixed V             81   Germany (deleted)
               FG              20m              W V             79   Guadeloupe
               FG              15m              V -             79   Guadeloupe
              FO0               CW              V -             36   Clipperton Island
               FW              15m              V -            298   Wallis & Futuna Islands
               GD              17m              V -            114   Isle Of Man
             HK0S            Phone V            228   Serrana Bank & Roncador Cay (deleted)
             HK0S            Mixed V            228   Serrana Bank & Roncador Cay (deleted)
              KH6              12m              V -            110   Hawaii
              KH6          Digital              V -            110   Hawaii
              KZ5            Phone V             28   Canal Zone (deleted)
              KZ5            Mixed V             28   Canal Zone (deleted)
               OK            Phone V            218   Czechoslovakia (deleted)
               OK            Mixed V            218   Czechoslovakia (deleted)
               P4               CW              V -             91   Aruba
              YV0            Phone V             17   Aves Island
              YV0            Mixed V             17   Aves Island
               ZS              80m              V -            462   Republic of South Africa


Re: NEED HELP IN GETTING COMMANDER WORKING

Dave AA6YQ
 

+ AA6YQ comments below

Dave: Last night I had WW working in AFSK. I could receive and decode I could press the transmit button (in WW) and it would key the
radio, send diddles, with RF out. I could type in RY's TEST then my call in the transmit window and it would transmit that. Today, I
could not duplicate WW working on AFSK.

OK, so today (starting over) I started Launcher, and Commander. Pressing the TX button in commander keyed the radio, produced a
single tone and I did get RF out. I then started WW, which changed the radio to LSB, and I press the TX button in WW. It did not key
the radio and did not produce a tone or any RF even though the software thought it was transmitting. When I checked port five, the
port used to control the radio, WW said it was not available. I'm guessing that is because it was being used by commander. ??

You sent me a link to "Configuring WinWarbler for RTTY Operation" which I followed religiously (both AFSK and FSK) but, it did not
work. I also tried the radio in D1, D2 & D3 but that made no difference. Throughout all of these tests, I could receive and decode
RTTY in WW. I even tried the K0PIR video for N1MM with MMTTY with same lack of results.

+ The article "Configuring WinWarbler for RTTY Operation" does not cover configuring WinWarbler for RX-TX switching (aka "PTT");
that's described in "Switching a Transceiver between Reception and Transmission" in

https://www.dxlabsuite.com/dxlabwiki/PTTMechanism

+ My assumption was that anyone wishing to use WinWarbler would first review "Setting up CW, Phone, PSK, and RTTY Operation in
WinWarbler" in

https://www.dxlabsuite.com/dxlabwiki/Multimode_Setup

+ which introduces configuration topics common to all modes: RX-TX switching, audio connections, and setting audio levels. See the
RTTY subsection in the "General Setup Instructions" section of this article.

+ To prevent this from happening again, I have added a "Configuration Steps You May Have Already Taken" section to the beginning of

"Configuring WinWarbler for RTTY Operation" in

https://www.dxlabsuite.com/dxlabwiki/ConfigureRTTY

+ and added steps for making the required audio settings and level adjustments.

+ Since you're using Commander to control your IC-7610, and since Commander can switch your IC-7610 between RX and TX, on the
Configuration window's PTT tab, set the Mode panel to "Xcvr Ctrl App" and set the Port panel to None. If that doesn't enable
WinWarbler to switch your transceiver between RX and TX, please let me know.

73,

Dave, AA6YQ


FW: [DXLab] DXKeeper auto populate

Dave AA6YQ
 

Re-sending due to a Groups.io malfunction...

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@ambersoft.com]
Sent: Sunday, March 07, 2021 6:34 PM
To: 'DXLab@groups.io'
Subject: RE: [DXLab] DXKeeper auto populate

+ AA6YQ comments below


Well that would be better than what's happening now.

Your suggestion sounds like a reasonable solution.


I thought there was a setting that allowed DXKeeper to be populated with previous qso info or not to be populated but still show previous qso info.

+ There is no such setting. As usual, I'm reluctant to add new settings because they increase user-perceived complexity - especially for a "once in 20 years" request.


Since I do not subscribe to any callbooks and have primary call book set to none is that why it is auto populating?

+ Unless an override is specified, DXKeeper harvests information from previously-logged QSOs if its "Display previous QSOs on Lookup" option is enabled:

https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Display%20Previous%20QSOs%20on%20Lookup%20checkbox


Would subscribing to one of the callbooks and clicking the "automatically use callbook data to initialize new QSO's" eliminate my problem?

+ No, because information extracted from previous QSOs has priority over information provided by a callbook lookup.

73,

Dave, AA6YQ


sorting out Log to LotW discrepancies

David Reed
 

Hi folks; taking a break from the contest for a few moments; I thought "I wonder how well my log and LotW match?" so I ran the report to identify any.

No surprise that I have some; my problem is to figure out what to do about them so both are correct and no discrepancies are reported...

Here is what it looks like:

   Entity Prefix     Band or Mode     Log Status    ARRL Status    Entity Code   Entity


               5R              20m              V -            438   Madagascar
               DA            Phone V             81   Germany (deleted)
               DA            Mixed V             81   Germany (deleted)
               FG              20m              W V             79   Guadeloupe
               FG              15m              V -             79   Guadeloupe
              FO0               CW              V -             36   Clipperton Island
               FW              15m              V -            298   Wallis & Futuna Islands
               GD              17m              V -            114   Isle Of Man
             HK0S            Phone V            228   Serrana Bank & Roncador Cay (deleted)
             HK0S            Mixed V            228   Serrana Bank & Roncador Cay (deleted)
              KH6              12m              V -            110   Hawaii
              KH6          Digital              V -            110   Hawaii
              KZ5            Phone V             28   Canal Zone (deleted)
              KZ5            Mixed V             28   Canal Zone (deleted)
               OK            Phone V            218   Czechoslovakia (deleted)
               OK            Mixed V            218   Czechoslovakia (deleted)
               P4               CW              V -             91   Aruba
              YV0            Phone V             17   Aves Island
              YV0            Mixed V             17   Aves Island
               ZS              80m              V -            462   Republic of South Africa
All suggestions are very much appreciated!

Thanks & 73 de Dave, W5SV


Re: NEED HELP IN GETTING COMMANDER WORKING

Dan Coleman <w8kmx@...>
 

Dave: Last night I had WW working in AFSK. I could receive and decode I could press the transmit button (in WW) and it would key the radio, send diddles, with RF out. I could type in RY’s TEST then my call in the transmit window and it would transmit that. Today, I could not duplicate WW working on AFSK.
 OK, so today (starting over) I started Launcher,  and Commander. Pressing the TX button in commander keyed the radio, produced a single tone and I did get RF out. I then started WW, which changed the radio to LSB, and I press the TX button in WW. It did not key the radio and did not produce a tone or any RF even though the software thought it was transmitting. When I checked port five, the port used to control the radio, WW said it was not available. I’m guessing that is because it was being used by commander. ??
You sent me a link to “Configuring WinWarbler for RTTY Operation“ which I followed religiously (both AFSK and FSK) but, it did not work. I also tried the radio in D1, D2 & D3 but that made no difference. Throughout all of these tests, I could receive and decode RTTY in WW. I even tried the K0PIR video for N1MM with MMTTY with same lack of results. I am getting embarrassed that I can’t figure this out. Dan, W8KMX




On Mar 6, 2021 at 9:23 PM, <Dave AA6YQ> wrote:

Hello Dave and thanks for the information. It worked fine

+ Does that mean that you have Commander correctly controlling your IC-7610?

and in fact I now have WinWarbler working. Or at least I think it’s working I can hear the tones and I’m producing RF and it sounds good at this end through the monitor. I still don’t have MMTTY working and I fully don’t understand because they’re almost the same thing.

+ Your first post in this thread said

"when I press the "TX" icon, it does key the radio (ICOM 7610) but it only sends one steady tone (Mark, I think)."

+ To transmit RTTY with WinWarbler, type some text in its transmit pane, and then click the "Start" button in WinWarbler's "RTTY transmit" panel. See this annotated screen shot:

http://www.dxlabsuite.com/Wiki/Graphics/WinWarbler/RTTY.jpg

+ Later, you can configure WinWarbler to "auto start".

+ A constant mark tone when transmitting RTTY is a classic symptom of having the transceiver configured for RTTY FSK transmission (for an IC-7610, mode set to "RTTY") but not supplying a FSK signal to the transceiver; for an IC-7610, that can be done via the second virtual COM port created by the transceiver, as described in this Icom manual:

http://www.icom.co.jp/world/support/download/manual/pdf/USB_Port_Setting_Ver.1.0_Eng.pdf

+ The alternative is to transmit RTTY AFSK, in which case you'd configure WinWarbler to put your IC-7610 in DATA-L mode when operating RTTY.

+ Step-by-step instructions for configuring WinWarbler for RTTY operation are here:

https://www.dxlabsuite.com/dxlabwiki/ConfigureRTTY


       73,

              Dave, AA6YQ









Re: DXKeeper auto populate

Joe - W9RF
 

Hi Dave,


Well that would be better than what's happening now.

Your suggestion sounds like a reasonable solution.


I thought there was a setting that allowed DXKeeper to be populated with previous qso info or not to be populated but still show previous qso info.

Since I do not subscribe to any callbooks and have primary call book set to none is that why it is auto populating?

Would subscribing to one of the callbooks and clicking the "automatically use callbook data to initialize new QSO's" eliminate my problem?


ie. NOT use old qso info but instead use data found as a new lookup?




73,

W9RF - Joe









On Saturday, March 6, 2021, 11:48:03 PM CST, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

When clicking on a call from Spotcollector or entering a callsign on the main DXKeeper page (new call) the previous qso info is automatically populated in DXKeeper.

This is very problematic when the previous call may have been worked several years in the past.

Even more problematic is entering a special event call, 1X1 calls are very often populated with the incorrect info.


The only way I have found to stop this is the general tab of DXKeeper config, (display previous QSO's on lookup)  but if I uncheck this it will not show any previous qso's.

I need to show the previous qso but NOT to populate the new qso with old info.

+ I can extend DXKeeper so that when you double-click a Spot Database Entry with DXKeeper's "Display previous QSOs on Lookup" option disabled, the callsign will still be placed in DXKeeper's  Filter panel; you can then review previous QSOs with the Entry's Callsign by clicking DXKeeper's  Filter panel's Call button - without information from previous QSOs being used to populate the Capture window.

+ Acceptable?

      73,

                Dave, AA6YQ








Re: Commander with multiple radios

Jim W1RET
 

Thanks Dave.  All good answers.  And binary encoded is no problem.  As long as I know there is something available.

73,

Jim W1RET


2Tone 21.03a

Dave AA6YQ
 

David G3YYD announced 2Tone version 21.03a today. I asked him what changed relative to the 2Tone version 21.02a included with
WinWarbler, here is his response:

-----------------
The Writelog fix and minor changes to the source code - removing old code that is no longer used. I also added the N1MM
documentation that I had left out last time but had intended to add in to make it easier for guys who prefer pictures over words. I
trialled the picture system with some UK amateurs and they found it helpful. However there are words just not as many!

In terms of decode performance no difference.
-----------------

Thus I am not planning to include 2Tone 21.03a in a future version of WinWarbler. If anyone would like access to David's improved
N1MM documentation, it's included in the 21.03a zip archive available here:

https://www.rttycontesting.com/downloads/2tone/

73,

Dave, AA6YQ

5661 - 5680 of 205881