Date   
Re: Log on Dropbox

Phil Cooper
 

Dave and the group,

I have an external HDD, on which I keep my log backup and workspace. At present, I do this backup manually (ie transfer both files from my PC to the HDD), but wonder if I could implement a BAT file to do this. I just need ot work out the syntax of the COPY (or XCOPY?) C:\DXLab| text to accomplish this.
However, in your advice, you mention both these files AND the LoTW backup file. What is the LoTW backup file? Is it the p12 file? If so, I have that covered, but if not, what is it, and where is it?

73 de Phil GU0SUP

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: 26 April 2019 19:15
To: DXLab@groups.io
Subject: Re: [DXLab] Log on Dropbox

Hello folks. I decided to keep my logbook.mdb database in a Dropbox folder to protect it from computer crashes. Sometimes at startup DXKeeper complains that it cannot open it. I go to config and open it manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder.

+ The only thing I can add to this excellent discussion is the advice to maintain both local and cloud backups of critical data, like your log, Workspaces, and LoTW backup file.

+ The advantage of a local backup - on a thumb drive, external hard drive, or another computer - is the ease and speed of recovery.

+ The advance of a cloud backup is that your critical data will survive a local disaster that might damage your backups.

+ Ideally, one should backup critical data both locally and in the cloud: "belt *and* suspenders". If you're only willing to implement one backup mechanism, my recommendation is "in the cloud".

+ One more thing: periodically test your backup mechanism to confirm that you can recover a file and use its contents. For example, you might occasionally download a backed-up log file from the cloud to your computer, direct DXKeeper to open it, and confirm that the expected QSOs are present. Don't forget to direct DXKeeper to open your current log file after completing this test, and then delete the copy of the back-up log file from your computer (to prevent future confusion).

73,

Dave, AA6YQ

Re: Update: Commander and SmartSDR v3

K4PX K4PX
 

Thanks Dave and Eric!
Joe
K4PX

On Fri, Apr 26, 2019, 2:34 PM Dave AA6YQ <aa6yq@...> wrote:
The first problem encountered was that the current version of Commander does not correctly handle new items added in SmartSDR v3 to
the RX-TX interlock status message, causing Commander and the radio to disconnect. This is what prevented the TX-to-RX transition
from working correctly.  For the record, the new interlock status items were added to v3 in an upward-compatible manner, so this
should be considered a defect in Commander.

Correcting this Commander defect has exposed unexpected behavior in SmartSDR v3, specifically the presence of clients and
panadaptors that Commander did not request be created. Flex engineers are working to track down the root cause of this behavior.

Reminder: the objective is to enable Commander to control a Flex Signature transceiver running SmartSDR v3, but without the use of
multiFlex.

The addition of multiFlex support will be considered after we achieve the first objective.

         73,

              Dave, AA6YQ




Re: Log on Dropbox

Giovanni Carboni <iz5pqt@...>
 

Wow:  super fast response from the Group. That's  real support !
Thanks to everybody, I won't  worry anymore

73 Giovanni IZ5PQT

Update: Commander and SmartSDR v3

Dave AA6YQ
 

The first problem encountered was that the current version of Commander does not correctly handle new items added in SmartSDR v3 to
the RX-TX interlock status message, causing Commander and the radio to disconnect. This is what prevented the TX-to-RX transition
from working correctly. For the record, the new interlock status items were added to v3 in an upward-compatible manner, so this
should be considered a defect in Commander.

Correcting this Commander defect has exposed unexpected behavior in SmartSDR v3, specifically the presence of clients and
panadaptors that Commander did not request be created. Flex engineers are working to track down the root cause of this behavior.

Reminder: the objective is to enable Commander to control a Flex Signature transceiver running SmartSDR v3, but without the use of
multiFlex.

The addition of multiFlex support will be considered after we achieve the first objective.

73,

Dave, AA6YQ

Re: Log on Dropbox

Dave AA6YQ
 

Hello folks. I decided to keep my logbook.mdb database in a Dropbox folder to protect it from computer crashes. Sometimes at startup DXKeeper complains that it cannot open it. I go to config and open it manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder.

+ The only thing I can add to this excellent discussion is the advice to maintain both local and cloud backups of critical data, like your log, Workspaces, and LoTW backup file.

+ The advantage of a local backup - on a thumb drive, external hard drive, or another computer - is the ease and speed of recovery.

+ The advance of a cloud backup is that your critical data will survive a local disaster that might damage your backups.

+ Ideally, one should backup critical data both locally and in the cloud: "belt *and* suspenders". If you're only willing to implement one backup mechanism, my recommendation is "in the cloud".

+ One more thing: periodically test your backup mechanism to confirm that you can recover a file and use its contents. For example, you might occasionally download a backed-up log file from the cloud to your computer, direct DXKeeper to open it, and confirm that the expected QSOs are present. Don't forget to direct DXKeeper to open your current log file after completing this test, and then delete the copy of the back-up log file from your computer (to prevent future confusion).

73,

Dave, AA6YQ

Re: Log on Dropbox

neil_zampella
 

I keep my log on Dropbox, and this does happen occasionally, its not a bug, but as pointed out a delay in accessing the file.

What I do is before firing up anything, I go to the dropbox 'folder' and click on it to make sure its 'awake' .. then have no issues.

Neil, KN3ILZ

On 4/26/2019 10:43 AM, Giovanni Carboni wrote:
Hello folks. I decided to keep my logbook.mdb database in a Dropbox folder to protect it from computer crashes. Sometimes at startup DXKeeper complains that it cannot open it. I go to config and open it manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder. 

73 Giovanni IZ5PQT

Virus-free. www.avg.com

Re: Log on Dropbox

Darrell Drake
 

Hi All....
 
Anything wrong with backing up DXKeeper on a thumb drive? That’s what I do along with my Workspaces.
I have DXKeeper’s config set to auto back up to the thumb drive upon exiting the program.
 
Just asking.
 
Darrell,
VA3DG/VE3DDG
 
 

Sent: Friday, April 26, 2019 10:43 AM
Subject: [DXLab] Log on Dropbox
 
Hello folks. I decided to keep my logbook.mdb database in a Dropbox folder to protect it from computer crashes. Sometimes at startup DXKeeper complains that it cannot open it. I go to config and open it manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder.

73 Giovanni IZ5PQT

Re: Log on Dropbox

Norm - KC1BMD
 

Apparently, DropBox is known to cause some problems, although your problem might not necessarily be related:
https://www.dxlabsuite.com/dxlabwiki/ApplicationInteference

Re: Log on Dropbox

Gilbert Baron W0MN
 

If you are a user of office then consider subscription to office365. You get ALL of office and always up to date and a terabyte of onedisk cloud. O365 can be installed on 5 systems, no limit on mobile such as ipads.

Outlook Laptop Gil W0MN
Hierro Candente Batir de Repente
44.08226N 92.51265 W en34rb

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of g4wjs
Sent: Friday, April 26, 2019 10:02
To: DXLab@groups.io
Subject: Re: [DXLab] Log on Dropbox

On 26/04/2019 15:43, Giovanni Carboni wrote:
Hello folks. I decided to keep my logbook.mdb database in a Dropbox
folder to protect it from computer crashes. Sometimes at startup
DXKeeper complains that it cannot open it. I go to config and open it
manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder.

73 Giovanni IZ5PQT
Hi Giovanni,

I do the same and often get this message, I believe it is because Dropbox locks the file every now and again while it synchronizes to the Cloud and this interferes with the MS Jet database engine initially opening the database. I also go straight to the DXKeeper configuration and click the Open button to try again and it always works first time. I have never had a problem once the log is opened, despite using this for many Years. It is a small disadvantage which I accept for the greater benefit of being able to switch DXKeeper operation to another computer and to have near instant backups.

Having aid that, Dropbox have recently severely restricted their free of charge option to two devices only per account, so I will be considering using a different Cloud file sharing service if I can find a less restricted one that works for me.



--
73

Bill

G4WJS.






--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

Re: Log on Dropbox

Peter Laws
 

Not being paranoid about "system crashes", my log is on my local storage.

But Dave (being Dave) has included a way to make it far, far too
simple to make a copy of my DXKeeper database on remote storage. For
that, I use Dropbox and it works fine. I also send a TQSL tbk file to
the same place occasionally. If there was one-click or automated way
to send my workspaces (I manage logs for several club calls), I'd send
those offsite as well. As it is, it's something I need to remind
myself to do ... which I think I just did (remind myself, I mean).

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

On Fri, Apr 26, 2019 at 9:59 AM d_ziolkowski <dan.ziolkowski@...> wrote:

Giovanni
Same happened to me. So I keep it on the c drive and save the backup to the Dropbox.

Then I also backup entire Dxlabs folder to Google drive.

Dan KC2STA

On Fri, Apr 26, 2019, 10:43 Giovanni Carboni <@IZ5PQT> wrote:

Hello folks. I decided to keep my logbook.mdb database in a Dropbox folder to protect it from computer crashes. Sometimes at startup DXKeeper complains that it cannot open it. I go to config and open it manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder.

73 Giovanni IZ5PQT
--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!

Re: Log on Dropbox

g4wjs
 

On 26/04/2019 15:43, Giovanni Carboni wrote:
Hello folks. I decided to keep my logbook.mdb database in a Dropbox folder to protect it from computer crashes. Sometimes at startup DXKeeper complains that it cannot open it. I go to config and open it manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder.

73 Giovanni IZ5PQT
Hi Giovanni,

I do the same and often get this message, I believe it is because Dropbox locks the file every now and again while it synchronizes to the Cloud and this interferes with the MS Jet database engine initially opening the database. I also go straight to the DXKeeper configuration and click the Open button to try again and it always works first time. I have never had a problem once the log is opened, despite using this for many Years. It is a small disadvantage which I accept for the greater benefit of being able to switch DXKeeper operation to another computer and to have near instant backups.

Having aid that, Dropbox have recently severely restricted their free of charge option to two devices only per account, so I will be considering using a different Cloud file sharing service if I can find a less restricted one that works for me.



--
73

Bill

G4WJS.

Re: Log on Dropbox

Jon Baker
 

Hi Giovanni,
there may be other ways to do this but one work around  is to pause syncing in dropbox before starting  Launcher 
at the end of DXLab operation  restart syncing 

73
Stan  N1ZX

Re: Log on Dropbox

d_ziolkowski
 

Giovanni 
Same happened to me. So I keep it on the c drive and save the backup to the Dropbox.

Then I also backup entire Dxlabs folder to Google drive. 

Dan KC2STA 

On Fri, Apr 26, 2019, 10:43 Giovanni Carboni <iz5pqt@...> wrote:
Hello folks. I decided to keep my logbook.mdb database in a Dropbox folder to protect it from computer crashes. Sometimes at startup DXKeeper complains that it cannot open it. I go to config and open it manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder. 

73 Giovanni IZ5PQT

Log on Dropbox

Giovanni Carboni <iz5pqt@...>
 

Hello folks. I decided to keep my logbook.mdb database in a Dropbox folder to protect it from computer crashes. Sometimes at startup DXKeeper complains that it cannot open it. I go to config and open it manually. It only occurs occasionally. Is it a bug?
I keep all the other databases in the C:\DXLab folder. 

73 Giovanni IZ5PQT

Re: Exporting ADIF by Range of Dates

KK7YC
 

Thank you so much Andy!! I knew that there had to be a way!!! appreciate your time and response. 

73 Ronnie de KK7YC

On Thursday, April 25, 2019, 8:04:21 AM MST, KK7YC via Groups.Io <kk7yc@...> wrote:


Good morning, I have QSO's in my log from various locations, I wish to export to an ADIF by a range of dates so that I can upload to EQSL without having to upload all QSO's. Is this possible, and if so what is the process? Thanks KK7YC Ronnie

Re: DXK QSO distance

Andy k3wyc <a.durbin@...>
 

On Thu, Apr 25, 2019 at 11:01 AM, Dave AA6YQ wrote:
+ Which application was used to log this new QSO?
JTAlertX, and now I see what is happening.    I loaded the backup dxk log I had created before the distance computation and find that distance is populated, presumably by JTAlertX, for WSJT-X QSO for which a grid was logged.  I had not noticed this before as I didn't have distance displayed in the log page display.  The DXK distance computation would have refined the distance for confirmations that included a 6 character grid and hopefully would have come up with the same answer for 4 character grids.

Thanks and 73,
Andy, k3wyc

Re: What Computer Speed/Memory needed to fully and rapidly decode over 40 stations on a crowded band????

Hugh Valentine
 

Thanks for the helpful advice and information.  Have a new 480GB SSD and more memory coming.

Val
N4RJ

Re: Exporting ADIF by Range of Dates

Dave AA6YQ
 

+ AA6YQ comments below

"I wish to export to an ADIF by a range of dates so that I can upload to EQSL without having to upload all QSO's"

You can apply any filter to your DXK log to produce a sub-set of QSO that will be used for any following action. You will be told the log is filtered and you choose to continue with that filter active. To set a date range use advanced and set the UTC filter to your date range then select filter. Confirm the QSO date range is as required then select export QSO. Don't remove the filter when prompted. Now select the ADIF export you want and start it.

+ Information about filtering the Log Page Display is available via

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

+ and

<https://www.dxlabsuite.com/dxkeeper/Help/FilterLog.htm>

+ DXKeeper provides automation for submitting QSOs to eQSL (as well as to Clug Log and LoTW). See

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

+ and

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

73,

Dave, AA6YQ

Re: DXK QSO distance

Dave AA6YQ
 

+ AA6YQ comments below

I wanted to know if my recent QSO with Mauritius Island was the longest distance QSO with my 40 m attic dipole. I followed the instructions <http://www.dxlabsuite.com/dxlabwiki/QSODistance> to populate path with "S" and then computed the distances. It turned out that a previous QSO with Reunion was reported as being a couple of miles longer. Everything worked as I had expected.

Today I noticed that new QSO which include a grid show a path distance even though propagation/antenna/path is blank. How is path distance being computed for these QSO without needing me to set the path and force a distance compute? In other words - if the distance can be computed now then why wasn't it for all the previous QSO? Just curious, it's not a problem.

+ Which application was used to log this new QSO?

73,

Dave, AA6YQ

Re: QSO Import

Carl - WC4H
 

FB Giovanni.

Then all you have to do is save the filtered file and import into DXKeeper.

73.
Carl - WC4H