Date   

Re: LOTW download?

Dave AA6YQ
 

+ AA6YQ comments below

Computer crash.. Windows 10 Pro reset. Can't find DXKeeper log files for last seven months.

+ Did you restore the Workspace you created before the crash? If so, the "Log file" panel at the top of the Configuration window's
Log tab will specify the location of your log file


Everything was uploaded to LoTW. Seems like there was formerly a download button, but I have not found it.

+ There was never a "Download from LoTW" button. There is this procedure for recovering lost QSOs from LoTW:

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

+ As noted in this article, only a small subset of your QSO information can be recovered in this way. Signal reports, QSL status,
award credits (except those granted to LoTW confirmations), names, addresses -- none of this information will be recovered.

+ Did you not make log backups?

73,

Dave, AA6YQ


Re: Broken link in DXLabwiki

Dave AA6YQ
 

+ AA6YQ comments below

While reading the wiki on using DXLab with RemoteHams.com software (http://www.dxlabsuite.com/dxlabwiki/RemoteControlRemoteHams) I found a broken link for the K3 emulatgion setup when using an Orb device. (If using an Online Remote Base (Orb), see Configuring Digital Mode or Logging Software for Elecraft K3 Emulation) The link is pointing to a file.

+ Corrected. Thanks, Gordon!

73,

Dave, AA6YQ


Re: Upload failed

W9MR Mike
 

Dave forwarded the message from ClubLog yesterday. Some maintenance work is being done on the ClubLog side.



73,
Mike ND9G


On Tue, Jul 30, 2019 at 8:28 AM Richard Clare <19idgaf52@...> wrote:
Keep getting message: Upload QSO to Club Log failed: OK.


LOTW download?

CSM&#92;(r&#92;) Gary Huber - AB9M
 

Computer crash.. Windows 10 Pro reset. Can't find DXKeeper log files for last seven months. Everything was uploaded to LoTW. Seems like there was formerly a download button, but I have not found it. What to do now?

Get Outlook for Android

73,
Gary ~ AB9M


Upload failed

Richard Clare
 

Keep getting message: Upload QSO to Club Log failed: OK.


Broken link in DXLabwiki

Gordon LaPoint
 

While reading the wiki on using DXLab with RemoteHams.com software (http://www.dxlabsuite.com/dxlabwiki/RemoteControlRemoteHams) I found a broken link for the K3 emulatgion setup when using an Orb device. (If using an Online Remote Base (Orb), see Configuring Digital Mode or Logging Software for Elecraft K3 Emulation)  The link is pointing to a file.

Thanks,

Gordon - N1MGO


Re: Recumpute Z6 to YU

Dave AA6YQ
 

+ AA6YQ comments below

On Mon, Jul 29, 2019 at 04:26 AM, Patrick ON6AT wrote:

I found that the "recompute" command is executed incorrectly.
Z6 suddenly becomes YU as DXCC.

DXKeeper changed all my Z6 DXCC's to YU DXCC's.
The report also shows this change.

I have qso's from before 2018 and they are indeed DXCC YU.
But my qso's after 2018 should still be DXCC Z6

Is something wrong or do I not have the latest update from the DXCC list?

However, I have updated everything within DXLab Suite.

+ The "Recompute Actions Report" that Patrick sent me shows that his log contained several QSOs whose "country code" was set to 296 ("Serbia") but whose "DXCC Prefix" was set to Z6 ("Kosovo"); the Recompute operation correctly changed the "DXCC Prefix" of each of these QSOs to match its "country code".

         73,

               Dave, AA6YQ


Re: Phantom QSOs

Mike Kasrich
 

That appears to have solved the problem

On 7/29/2019 2:57 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I've been going through my DXCC credit list and comparing it to entries in DXLab. Tedious for sure. I noticed something in DXView that is odd. I have band mode slots that show "W" or "C" that when you click on the slot to see who was worked and not confirmed or confirmed and haven't been submitted, nothing shows up in DXKeeper. I'm not sure what I've done to cause the phantom entries or if there is a fix to this.

+ Please let me know if clicking the Recompute button at the bottom of the Main window's "Check Progress" tab doesn't correct this.

+ In the upper-left corner of the Configuration window's Awards tab, checking the "Automatically recompute realtime award tracking" box will keep your realtime award progress up-to-date without your having to invoke Recompute after making changes to logged QSOs.

73,

Dave, AA6YQ




Re: User Define Button

David Burden
 

In the files section in this formum look at /command sequences and sliders / icom / 7300 - you can use the tune sequence to engage the 7610 Tune button.


73
David


Re: Flex 6400 as 2nd radio in Commander - no TX issue

Dave AA6YQ
 

+ AA6YQ comments below


For future reference when would that box need to be checked and if you
did that would it impact other radios if you are using the multiRadio
function?
That box *MUST BE CHECKED* when using a microHAM interface to force Commander to use hardware PTT rather than software command. With software commands any microHAM microKEYER, MK2R or micro2R can not switch between mic and sound card - for example when using audio macros - or (potentially) activate the PA PTT (if used).

Dave, it looks like "Suppress CAT" needs to be made radio specific as there are other interfaces (e.g. some "RigBlaster"models) that also use computer PTT for mic/Sound card switching.

+ The "Suppress CAT" setting only suppresses the issuance of CAT instructions to switch between RX and TX; it does not force the use of a modem control signal for RX/TX switching. To force the use of a modem control signal for RX/TX switching on a per-radio basis, set the DTR or RTS selector to X in the "CAT Serial port" panel on the Configuration window's MultiRadio tab.

+ Since Curt had "Suppress CAT" enabled, he must already have Commander configured to use DTR or RTS to switch his TS-990 between RX and TX. Disabling "Suppress CAT" so that Commander can switch his Flex 6400 between RX and TX will mean that CAT instructions will also be sent when he switches his TS-990 between RX and TX, but external hardware dependent on a PTT signal will still see one.

73,

Dave, AA6YQ


Re: Flex 6400 as 2nd radio in Commander - no TX issue

Joe Subich, W4TV
 

For future reference when would that box need to be checked and if you did that would it impact other radios if you are using the multiRadio function?
That box *MUST BE CHECKED* when using a microHAM interface to force
Commander to use hardware PTT rather than software command. With
software commands any microHAM microKEYER, MK2R or micro2R can not
switch between mic and sound card - for example when using audio
macros - or (potentially) activate the PA PTT (if used).

Dave, it looks like "Suppress CAT" needs to be made radio specific
as there are other interfaces (e.g. some "RigBlaster"models) that
also use computer PTT for mic/Sound card switching.

73,

... Joe, W4TV


On 2019-07-29 5:25 PM, Curt wrote:
Thanks Joe.  I had tried that earlier with no success but I think that was before I figured out the suppress carrier box was checked.
Just curious, I had that box checked from when I setup my microKeyer II as the TS-990.  Since that box does not appear to be radio specific and both the 990 and 6400 seem to work fine by un-checking it I guess I'm good.  For future reference when would that box need to be checked and if you did that would it impact other radios if you are using the multiRadio function?
Thanks again for all of your help.
Curt


Re: Query Special Callsign database button

Dave AA6YQ
 

+ AA6YQ comments below

Recently a failure of the boot drive on my main computer had me installing DXLab Suite on my backup computer. I've got almost everything working. In DXView, clicking the antenna preset buttons results in the rotator moving to the correct azimuth. However, as I wrote last year, only 13 preset buttons appear on each side. I followed the instructions you mentioned and have the 'Progress' box showing but in order to see the remaining presets I know that I need to enable the "Query Special Callsign database" checkbox. However, it is grayed out so it can't be checked. I couldn't find any mention in the documentation on how to activate the grayed out box.

What am I missing?

+ DXView checks a Windows Registry setting created by SpotCollector to determine the pathname of the Special Callsign database. The "Query Special Callsign database" checkbox is only enabled if a Special Callsign Database exists. Have you installed and run SpotCollector on your backup computer?

Also, is there a file containing the Antenna presets that I might be able to retrieve from my backup files and reinstall in the second computer without having to enter them all manually?

+ Those settings are stored in the Windows Registry, which died with your main computer's boot drive.

+ Had you directed the Launcher to create a Workspace before your main computer's boot drive died and then backed up that Workspace somewhere safe, you'd have been able to direct the Launcher on your backup computer to restore all DXLab settings from that Workspace, including the location of the Special Callsign database and your antenna presets.

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

73,

Dave, AA6YQ


Query Special Callsign database button

Rich - K1HTV
 

Recently a failure of the boot drive on my main computer had me installing DXLab Suite on my backup computer. I've got almost everything working. In DXView, clicking the antenna preset buttons results in the rotator moving to the correct azimuth. However, as I wrote last year, only 13 preset buttons appear on each side. I followed the instructions you mentioned and have the 'Progress'  box showing but in order to see the remaining presets I know that I need to enable the "Query Special Callsign database" checkbox. However, it is grayed out so it can't be checked. I couldn't find any mention in the documentation on how to activate the grayed out box.

What am I missing?

Also, is there a file containing the Antenna presets that I might be able to retrieve from my backup files and reinstall in the second computer without having to enter them all manually?

73,
Rich - K1HTV


Re: Flex 6400 as 2nd radio in Commander - no TX issue

Curtis WX4W
 

I took about 5 minutes to figure out how to display spots so no reply needed.  I wonder what else I don't know....Hi Hi.


Re: Flex 6400 as 2nd radio in Commander - no TX issue

Curtis WX4W
 

Yes Dave it seems to be working fine with both radios.  As I said before I'm new to Flex so there may be issues I'm unaware of and I don't want to waste everyone's time with things I should be figuring out on my own.  You did mention that spots from spot collector will show up on the spectrum display and that's not happening but I assume that's some menu setting I'll need to figure out.

Once again I can't thank you enough for such a wonderful suite of programs and all of your help!

73

Curt WX4W


Re: Flex 6400 as 2nd radio in Commander - no TX issue

Curtis WX4W
 

Thanks Joe.  I had tried that earlier with no success but I think that was before I figured out the suppress carrier box was checked. 

Just curious, I had that box checked from when I setup my microKeyer II as the TS-990.  Since that box does not appear to be radio specific and both the 990 and 6400 seem to work fine by un-checking it I guess I'm good.  For future reference when would that box need to be checked and if you did that would it impact other radios if you are using the multiRadio function?

Thanks again for all of your help.

Curt


FW: [Club Log] Re: Club Log maintenance window = Saturday 27th/Sunday 28th July

Dave AA6YQ
 

Club Log is undergoing changes, so don't be surprised if QSOs you upload aren't processed:

-----------------------------
From Michael G7VJR:

Right, here's a bit of an update.

Obviously today is a work day here in the UK, so I have not been able to get a note out - but those who are regulars will have noticed there is still a pause on uploads (which can be queued but won't get processed right now) and real-time uploads (which are blocked). If you are not too into technology, then I can tell you that I'm on top of this and it's all getting sorted out as fast as the computers will go. :-)


For technical sorts:

I am preventing writes and changes to the logs table with the record of users' QSOs, to allow a rearrangement of the underlying database table. Club Log uses MariaDB 10.4 and InnoDB tables. It was TokuDB, which had some very neat indexing and compression features, but I fell out of love with that because it crashed in a bad way recently, and I decided that was not a good sign. Given that TokuDB is a relatively exotic technology with probably a small user base, I've switched to InnoDB.

Everything I wanted to do was sorted out overnight on Saturday as planned. However, now it's Monday and I'm having to make two large table changes. One is to drop partitioning and one is to add a new index. I can make online changes to a table of this size (around 600 million records) but only select statements can run (not inserts, deletes, updates etc). Those queries get locked, and table changes take about 9 hours a piece so that's a huge backlog to accumulate over effectively 18 hours. For this reason I have added a global lock-out in the Club Log code to help keep the service up, just not accepting writes to the logs table. Doing that keeps cty, DXCC lookups, dxlite, skimmer, log search etc etc. running (actually the majority of Club Log is reads so it's not that bad).

The table changes needed are to drop a 2048-way partition on the logs table (first pass) and replace it with an index (second pass). As to why, well, that rather giant partition set was causing xtrabackup to fail on a subtle bug which I traced to some code that uses pthread and fails to maintain a lock across so many partitions. So, I've been right down into the bowels of the source code of MariaDB before I could figure it out. Rather annoying although in fairness quite interesting, too. Needless to say, if I can't backup the logs table and get it replicating properly on the MySQL slave, I can't leave Club Log online as it would be unsafe. So this *has* to be solved, even accepting the amount of disruption entailed, and the partitions have to go. I reckon it will complete overnight tonight UK time. As soon as it does, all the uploads will flush through.

Despite the downtime, I am actually happy with the changes. I know that might seem a bit mad, but even the ability to keep Club Log online for "read" access is a new advantage of the updates done over the weekend. It's a shame there is a bug that slightly took the shine off it, but I'll let the MariaDB team know about it and hopefully someone (somewhere!) will get the benefit in the end. So sit tight, don't worry, it's almost sorted now.
-----------------------------

73,

Dave, AA6YQ


Re: FT$ again

Dave AA6YQ
 

+ AA6YQ comments below

Apparently we all aren't on the same page when logging/uploading FT4 QSO's. So I need the definitive answer. are we logging/uploading as FT4, DATA, or MFSK with submode FT4.

+ On May 22, 2019, the ARRL released "TQSL Configuration Data" version 11.8, which enables TQSL to accept FT4 QSOs for submission to LoTW using this ADIF-approved representation:
+ Everyone on the planet should be uploading FT4 QSOs to LoTW with

<MODE:4>MFSK <SUBMODE:3>FT4

I uploaded 30 contacts to LoTW yesterday, got about 5 back saying other guy logged as DATA. Maybe I need to change my TQSL?

+ The only ARRL award for which those 5 LoTW confirmations don't "count" is a WAS FT4 endorsement.

+ There is no change you could make in LoTW that would alter this situation.

+ If any of those 5 QSO partners live in a US State, you can send them email asking that they resubmit your QSO with a mode of FT4. That may require them to reconfigure their TQSL (e.g. remove the FT4=>DATA mapping they may have added, upgrade to Configuration Data 11.8) or to use a logging application that correctly submits FT4 QSOs to LoTW.

73,

Dave, AA6YQ


Re: FT$ again

Joe Subich, W4TV
 

So I need the definitive answer. are we logging/uploading as
FT4, DATA, or MFSK with submode FT4.
DXKeeper uploads FT4 as <MODE:4> MFSK <SUBMODE:3> FT4

tQSL accepts *either* <MODE:3> FT4 or <MODE:4> MFSK <SUBMODE:3> FT4
and signs them identically using LotW's own internal mode ID.

*SOME* logging software is still not ADIF compliant and when configured
as that (commercial) logging software's customer support instructs will
force tQSL to "sign" an FT4 QSO as <MODE:4> DATA. There is nothing you
or the developers of tQSL/LotW can do about the noncomplaint logger.

The only recourse is to contact your QSO partner and request that they
upload the QSO *AGAIN* with the proper mode, using an ADIF compliant
application (WSJT-X, DXKeeper, manual entry into tQSL, etc.).

73,

... Joe, W4TV


On 2019-07-29 4:03 PM, F.R. Ashley wrote:
Apparently we all aren't on the same page when logging/uploading FT4
QSO's.   So I need the definitive answer. are we logging/uploading as
FT4, DATA, or MFSK with submode FT4.  I uploaded 30 contacts to LoTW
yesterday, got about 5 back saying other guy logged as DATA.  Maybe I
need to change my TQSL?
73 Buddy WB4M


Re: WSJT-X 2.1 drops connection with Commander

Jens Zander SM0HEV
 

Thanks, Dave.
Updating JTAlert to 2.14 and rebooting did the trick!
--
SM0HEV/Jens

24101 - 24120 of 211090