Date   
Re: Database recovery after a few year absents

Dave AA6YQ
 

Thanks for the responses. Here's my advice.

1. With DXKeeper running on your current computer,

1a. On the main window's "Log QSOs" tab, click the Filter panel's X button so that all QSOs are present in the Log Page Display

1b. on the Main window's "Export QSOs" panel,

1b-i set the "Options" panel's to "Export standard ADIF"

1b-ii check the "Export QTH definitions" box

1b-iii check the "Export callsigns with leading !" box

1b-iv click the Start button, and save the export ADIF to a file named W0RO-recent.ADI

2. Terminate DXKeeper

3. In your new computer's C:\DXLab\DXKeeper\Databases folder, rename the file

W0RO.mdb

to

W0R0-recent.mdb

4. Copy the file W0R0.mdb from

D:\Old-DXKeeper-Log\W0RO.mdb

into your new computer's C:\DXLab\DXKeeper\Databases folder

5. start DXKeeper, and confirm that it contains the QSOs made on your old computer

6. on the "Import QSO's" tab

6a. clear all boxes in the "options" panel except "Recor import errors in error file"

6b. set the "ADIF style options" panel to "standard ADIF"

6c. clear the boxes in the "Duplicate checking", "Substitution options", and "Replacement options" panels.

6d. click the Start button, and select the ADIF file your imported in step 1.b-iv above

7. On the Main window's "Log QSO" tab, confirm that both your old and recent QSOs are present

8. On the Main window's "my QTHs" panel, confirm that the "myQTH" from your recent log file is present.

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dan Scott
Sent: Sunday, March 24, 2019 4:19 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Database recovery after a few year absents

Sorry for the delay in response. Out of town meetings/travel.



1. Assumptions are correct

a. Fresh install.
b. All apps configured in that fresh install
c. No need to bring configuration files across

2. No log file overlap – Also the location (MyQTH) of the new installation is unique
3.







From: Dave AA6YQ <mailto:@AA6YQ>
Sent: Monday, March 18, 2019 5:37 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Database recovery after a few year absents



+ AA6YQ comments below



After moving from a house then through a series of apartments, I have gotten on the air via in-apartment antenna.



* I did a fresh install of the DX Suite about 4 months back and started using DXkeeper. At the same time, my old “radio” computer was in storage.



+ I assume that you created a new log file on your current computer, and began logging QSOs in that new log file. I also assume that you've already configured each of your DXLab apps on your current computer, and thus have no need of settings from your "old radio computer".

<W0RO> Correct



* My old “radio” computer did not survive all the moves, but the drive is recoverable. Based on the timestamps the last update with my old computer was June 2016.



+ You have two log files that don't overlap in time. Before I describe the procedure for combining their contents into a single log file, some questions:

1. what is the name of the log file on your "old radio computer"?

DB old computer:

D:\Old-DXKeeper-Log\W0RO.mdb

Size: 4,904 KB

Approx contacts: 1000 to 1500



2. what is the name of the log file on your current computer?

Current DB:

C:\DXLab\DXKeeper\Databases\W0RO.mdb

Size: 992 KB

Approx contacts: 50



3. how many "my QTHs" are defined in the log on your "old radio computer"?

I do not know. My guess is no more that 20



4. how many "my QTHs" are defined in the log on your new computer?

a. 1 – The myQTH in the new install is Unique when compared to the old install



73,

Dan














<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: question regarding com port baud rate

Dave AA6YQ
 

+ AA6YQ comments below

This sounds complicated to me.
Can i change any card or slot in a new card to shunt the problem around?

+ The procedure described below will reliable determine whether the computer or radio is at fault.

+ You could take a wild guess that the USB interface in your computer is at fault, purchase a device like this one

<https://www.amazon.com/StarTech-com-Port-PCI-Express-Card/dp/B00WJOVQB2/ref=asc_df_B00WJOVQB2/?tag=hyprod-20&linkCode=df0&hvadid=319185484784&hvpos=1o2&hvnetw=g&hvrand=4242802553258170515&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9001879&hvtargid=pla-441200318528&psc=1&tag=&ref=&adgrpid=63609080556&hvpone=&hvptwo=&hvadid=319185484784&hvpos=1o2&hvnetw=g&hvrand=4242802553258170515&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9001879&hvtargid=pla-441200318528>

+ and plug the IC-7300 cable into it, but if Commander still can't control the radio at 115,200 baud, you will have only ruled out one of several potential causes of the problem.

73,

Dave, AA6YQ

Re: Database recovery after a few year absents

Dan Scott
 

Sorry for the delay in response.  Out of town meetings/travel.

 

  1. Assumptions are correct
    1. Fresh install.
    2. All apps configured in that fresh install
    3. No need to bring configuration files across
  2. No log file overlap – Also the location (MyQTH) of the new installation is unique
  3.  

 

 

 

From: Dave AA6YQ
Sent: Monday, March 18, 2019 5:37 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Database recovery after a few year absents

 

+ AA6YQ comments below

 

After moving from a house then through a series of apartments,  I have gotten on the air via in-apartment antenna.

 

*             I did a fresh install of the DX Suite about 4 months back and started using DXkeeper.   At the same time, my old “radio” computer was in storage. 

 

+ I assume that you created a new log file on your current computer, and began logging QSOs in that new log file. I also assume that you've already configured each of your DXLab apps on your current computer, and thus have no need of settings from your "old radio computer".

<W0RO> Correct

 

*             My old “radio” computer did not survive all the moves, but the drive is recoverable.  Based on the timestamps the last update with my old computer was June 2016. 

 

+ You have two log files that don't overlap in time. Before I describe the procedure for combining their contents into a single log file, some questions:

  1. what is the name of the log file on your "old radio computer"?

DB old computer:

D:\Old-DXKeeper-Log\W0RO.mdb

Size:  4,904 KB

Approx contacts: 1000 to 1500

 

  1. what is the name of the log file on your current computer?

Current DB:

C:\DXLab\DXKeeper\Databases\W0RO.mdb

Size:  992 KB

Approx contacts: 50

 

  1. how many "my QTHs" are defined in the log on your "old radio computer"?

I do not know.  My guess is no more that 20

 

  1. how many "my QTHs" are defined in the log on your new computer?
    1. 1 – The myQTH in the new install is Unique when compared to the old install

 

73,

Dan

 

 

 

 

 

 

Re: question regarding com port baud rate

ghassan chammas
 

This sounds complicated to me.
Can i change any card or slot in a new card to shunt the problem around?

Od5ya



Sent from Samsung tablet.

-------- Original message --------
From: Dave AA6YQ <aa6yq@...>
Date: 24/03/2019 19:52 (GMT+02:00)
To: DXLab@groups.io
Subject: Re: [DXLab] question regarding com port baud rate

+ AA6YQ comments below

I meant commander - radio handshake is lost. I.e beyond 9600 bauds commander loses control over the radio.

Please note that the ic 7300 is connected to pc via a usb cable.
Pc is a i3 with 8gb ram
No antivirus is intalled yet and firewall is disabled.

+ You don't specify the i3's clock frequency or cache organization, but I'd be surprised if any i3 would be unable to keep up with 115,200 baud.

+ Assuming that Commander and the radio are both correctly configured, debugging this would require using a serial port analyzer to monitor the signal received from the USB interface internal to the IC-7300 when operated at 9600 baud and when operated at 115,200 baud. This would reveal whether the information being received from the PC is correctly formatted, and whether the radio is correctly responding.

           73,

                Dave, AA6YQ




Re: question regarding com port baud rate

Dave AA6YQ
 

+ AA6YQ comments below

I meant commander - radio handshake is lost. I.e beyond 9600 bauds commander loses control over the radio.

Please note that the ic 7300 is connected to pc via a usb cable.
Pc is a i3 with 8gb ram
No antivirus is intalled yet and firewall is disabled.

+ You don't specify the i3's clock frequency or cache organization, but I'd be surprised if any i3 would be unable to keep up with 115,200 baud.

+ Assuming that Commander and the radio are both correctly configured, debugging this would require using a serial port analyzer to monitor the signal received from the USB interface internal to the IC-7300 when operated at 9600 baud and when operated at 115,200 baud. This would reveal whether the information being received from the PC is correctly formatted, and whether the radio is correctly responding.

73,

Dave, AA6YQ

Re: question regarding com port baud rate

Greg Engle
 

Do you have the radio  CI-V Baud rate set correctly on the radio. (Page 12-8 in the manual). If it’s set to AUTO try one of the fixed settings.

 

Set Function/CI-V Baud Rate.

 

Just a guess…

 

Greg

NZ6E

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of ghassan chammas via Groups.Io
Sent: Saturday, March 23, 2019 10:13 PM
To: DXLab@groups.io
Subject: Re: [DXLab] question regarding com port baud rate

 

Hello Dave

 

I meant commander - radio handshake is lost. I.e beyond 9600 bauds commander loses control over the radio.

 

Please note that the ic 7300 is connected to pc via a usb cable.

Pc is a i3 with 8gb ram

No antivirus is intalled yet and firewall is disabled. 

 

Regards

Ghassan

 

 

 

Sent from Samsung tablet.

 

-------- Original message --------

From: Dave AA6YQ <aa6yq@...>

Date: 24/03/2019 02:29 (GMT+02:00)

To: DXLab@groups.io

Subject: Re: [DXLab] question regarding com port baud rate

 

+ AA6YQ comments below

I have 2 qth and 2 similar setups with 2 icom 7300 and 2 (Almost) similar win 7 pc.
In my qth1 i have dxlab installed and running perfectly, with the commander waterfall  running smoothly at the baud rate of 115000.

In qth2, same setup with same workspace and same ic7300 setup, however i cannot run the fom port but at 9600 bauds. If i go one notch higher i loose the commander-pc handshake.

+ What do you mean by "lose the Commander-PC handshake"? Exactly what happens?

So in qth2 i am unable to run the waterfall.

My question is :

In a pc, what determines the capability to run a com port at a high baud rate?

+ 115,200 baud is approximately 10K characters per second, which from a computing perspective is slow, and should not be problematic. There are many possible factors. Pending your answer to my question above, I suggest starting by temporarily disabling your firewall and anti-malware apps.

        73,

                Dave, AA6YQ



Re: question regarding com port baud rate

ghassan chammas
 

Hello Dave

I meant commander - radio handshake is lost. I.e beyond 9600 bauds commander loses control over the radio.

Please note that the ic 7300 is connected to pc via a usb cable.
Pc is a i3 with 8gb ram
No antivirus is intalled yet and firewall is disabled. 

Regards
Ghassan



Sent from Samsung tablet.

-------- Original message --------
From: Dave AA6YQ <aa6yq@...>
Date: 24/03/2019 02:29 (GMT+02:00)
To: DXLab@groups.io
Subject: Re: [DXLab] question regarding com port baud rate

+ AA6YQ comments below

I have 2 qth and 2 similar setups with 2 icom 7300 and 2 (Almost) similar win 7 pc.
In my qth1 i have dxlab installed and running perfectly, with the commander waterfall  running smoothly at the baud rate of 115000.

In qth2, same setup with same workspace and same ic7300 setup, however i cannot run the fom port but at 9600 bauds. If i go one notch higher i loose the commander-pc handshake.

+ What do you mean by "lose the Commander-PC handshake"? Exactly what happens?

So in qth2 i am unable to run the waterfall.

My question is :

In a pc, what determines the capability to run a com port at a high baud rate?

+ 115,200 baud is approximately 10K characters per second, which from a computing perspective is slow, and should not be problematic. There are many possible factors. Pending your answer to my question above, I suggest starting by temporarily disabling your firewall and anti-malware apps.

        73,

                Dave, AA6YQ




Re: question regarding com port baud rate

Dave AA6YQ
 

+ AA6YQ comments below

I have 2 qth and 2 similar setups with 2 icom 7300 and 2 (Almost) similar win 7 pc.
In my qth1 i have dxlab installed and running perfectly, with the commander waterfall running smoothly at the baud rate of 115000.

In qth2, same setup with same workspace and same ic7300 setup, however i cannot run the fom port but at 9600 bauds. If i go one notch higher i loose the commander-pc handshake.

+ What do you mean by "lose the Commander-PC handshake"? Exactly what happens?

So in qth2 i am unable to run the waterfall.

My question is :

In a pc, what determines the capability to run a com port at a high baud rate?

+ 115,200 baud is approximately 10K characters per second, which from a computing perspective is slow, and should not be problematic. There are many possible factors. Pending your answer to my question above, I suggest starting by temporarily disabling your firewall and anti-malware apps.

73,

Dave, AA6YQ

Re: question regarding com port baud rate

Carl - WC4H
 
Edited

What are your other CAT parameters set at?

Normally a quad core processor (or better) and at least 8GB RAM.

I run it on an older Quad Core (AMD A8-3850 APU 2.90 GHz) with 12 GB RAM & 2 TB H/D with no problems.

73.
Carl - WC4H

question regarding com port baud rate

ghassan chammas
 


Hi Dave
I have 2 qth and 2 similar setups with 2 icom 7300 and 2 (Almost) similar win 7 pc.
In my qth1 i have dxlab installed and running perfectly, with the commander waterfall  running smoothly at the baud rate of 115000.

In qth2, same setup with same workspace and same ic7300 setup, however i cannot run the fom port but at 9600 bauds. If i go one notch higher i loose the commander-pc handshake. So in qth2 i am unable to run the waterfall.

My question is :

In a pc, what determines the capability to run a com port at a high baud rate? It should be the pc because radio and radio setups are the same and dxlab setup is exactly the same. In other words what should be done to my set up in qth2 to run the waterfall?

Thank you very much

Yours
Ghassan
Od5ya
Beirut






Sent from Samsung tablet.

Re: Something went amiss

n4qwf .
 

If this proves to be a reoccurring problem I will reach out to ARRL LOTW group. If it has happened before it would have been some QSO that was of no consequence to my DXCC totals. I likely would not have noticed it in that case. I will monitor my uploads closely to see if it happens again. Thanks you for your continued great help and support.

Best<<John

Re: Spotcollector Window

ve6sh@...
 

Dave

That fixed it. thank you.

73

Tim VE6SH

Re: Spotcollector Window

Dave AA6YQ
 

+ AA6YQ comments below

Just today, the SC window remains minimized in the system tray (running Win 10). Usually the three windows for the spot sources run minimized but the main display opens on the screen.

I have tried right clicking in the start up tray and trying to restore the window or even clicking on “move” with no luck. I have also tried the restore button on the DxLab start up window with the same result.

Any ideas?

+ Take a look at

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

+ If that doesn't get you going, please let me know.

73,

Dave, AA6YQ

Re: Band Edge Warnings: Commander

Dave AA6YQ
 

+ AA6YQ comments below

I might have missed it in my searching but does Commander have configurable band edge warnings?

+ Yes. See

<https://www.dxlabsuite.com/commander/Help/Configuration.htm#Defining%20sub-bands>

73,

Dave, AA6YQ

Re: labels

Dave AA6YQ
 

+ AA6YQ comments below

It is Avery 94202 1"x4". Also tried blank and also the default # (can not recall it right now). The results seem identical no
matter what settings I use. the colums are too small and the info overlaps into the next cell. You may have it ... the font may be
too big. I have not seen a setting for that.

+ There are four Font panels in the lower have of the "QSL Labels" tab of DXKeeper's "QSL Configuration" window. Set them all to 7,
check and print preview, and then increase the font size for the elements as desired.

73,

Dave, AA6YQ

Re: Something went amiss

Dave AA6YQ
 

+ AA6YQ comments below

Yes I did invoke the sync after the contact was uploaded and it was not marked as confirmed in DXKeeper log.

+ If the first QSO was logged in DXKeeper with a mode of FT8 and uploaded to LoTW by DXKeeper, then if you invoked "Sync LoTW QSOs", DXKeeper would have informed you if LoTW had reported the QSO's mode to be SSB instead of FT8.

After I uploaded the ADIF from WSJT log using TQSL and did the sync that QSO was mark confirmed in DXKeeper but not the one that indicated SSB on LOTW of course. That QSO still shows FT8 in my log but SSB on LOTW.

I assume from this content that the ADIF file keeps only the last contact uploaded. This is the QSO from the next day when I worked him again. This uploaded as it should have. I can't open the MDB file in my backup folder that would contain the QSO in question. Anyway here is the content of the file you ask for.


ADIF QSL record generated by DXKeeper 14.8.5 on 22-Mar-2019 09:28:04 UTC <ProgramID:8>DXKeeper
<ADIF_VER:4>1.00
<EOH>
<CALL:5>AL7TC <TIME_ON:6>092700 <QSO_DATE:8>20190322 <MODE:3>FT8 <BAND:4>160M <FREQ:8>1.841599 <BAND_RX:4>160M <FREQ_RX:8>1.841599 <EOR>

+ That's that QSO as uploaded by DXKeeper. It's not the ADIF that you subsequently uploaded using TQSL.

+ As you can see, DXKeeper specified the mode as FT8.

+ How LoTW received a QSO whose mode was SSB, I can't explain. If you want to pursue this further, engage the ARRL's LoTW Help Desk, and present them with the ADIF record above.

73,

Dave, AA6YQ







<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: Waterfall for Yeasu FT-991A

Dave AA6YQ
 

+ AA6YQ comments below

I have SDR waterfalls working for my cheap $7 SDR and for another guy who as the more expensive SDR 2. What I liked about the one waterfall I saw for DXLab was there were callsigns showing. I have not see that on any other waterfall.

+ The Spectrum-Waterfall that Commander displays when controlling an IC-7300, IC-7610, or IC-785X displays the callsigns of active DX stations as reported by SpotCollector. See

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

snip<
Seems to me that I would want to in real time to see callsigns and the freq that the station is using.

+ DXLab can also display the callsigns of active DX stations as reported by SpotCollector on FlexRadio panafall windows:

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

+ DXLab interoperates with many panadaptors, but none of them (yet) enable the display of callsigns:

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

Then a propagation indicator as to if I could reach the station.

+ SpotCollector has long provided that capability; see

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

73,

Dave, AA6YQ

Re: labels

John Battin
 

Dave … tnx … Font size was problem.

 

john

 

Sent from Mail for Windows 10

 


From: DXLab@groups.io <DXLab@groups.io> on behalf of John Battin <jbattin@...>
Sent: Saturday, March 23, 2019 12:21:40 PM
To: DXLab@groups.io
Subject: Re: [DXLab] labels
 

It is Avery 94202 1”x4”.  Also tried blank and also the default # (can not recall it right now).  The results seem identical no matter what settings I use… the colums are too small and the info overlaps into the next cell.  You may have it ….. the font may be too big… I have not seen a setting for that.

Tnx john

 

Sent from Mail for Windows 10

 


From: DXLab@groups.io <DXLab@groups.io> on behalf of Dave AA6YQ <aa6yq@...>
Sent: Friday, March 22, 2019 9:58:58 PM
To: DXLab@groups.io
Subject: Re: [DXLab] labels
 
+ AA6YQ comments below

I have tried for days to print qsl labels.  I think I have read everything several times. Problem is when I print, the characters
are on top of each other and I can not figure out how to adjust the space available for each piece of information.

+ Which variety of labels are you using? What font sizes have you specified?

        73,

            Dave, AA6YQ




Spotcollector Window

ve6sh@...
 

Just today, the SC window remains minimized in the system tray (running Win 10). Usually the three windows for the spot sources run minimized but the main display opens on the screen.

 

I have tried right clicking in the start up tray and trying to restore the window or even clicking on “move” with no luck. I have also tried the restore button on the DxLab start up window with the same result.

 

Any ideas?

 

73

 

Tim VE6SH

Band Edge Warnings: Commander

Norm - KC1BMD
 

I might have missed it in my searching but does Commander have configurable band edge warnings?