Date   

Re: Likely leaving DXLab Suite After Changing Computers

Björn SM7IUN
 

I have moved DXLab several times due to hard drive crashes and motherboard failures. 

I mirrored all my DXLab files on a cloud drive, made sure my workspace 
was properly saved, and was up and running within a few minutes on a 
freshly installed Windows or even a completely new PC.

Björn SM7IUN



Den ons 19 maj 2021 kl 16:23 skrev Peter Laws / N5UWY <plaws0@...>:

On Wed, May 19, 2021 at 9:12 AM Richard Lawn <rjlawn@...> wrote:

> Seems like it would be easier to just start fresh with a new copy, configure your radio(s) setup and move your log over. I'll likely do that or just abandon using DXLab suite of software. Other loggers and multi-purpose applications seem to be much easier in this regard.


Good summary of the "5 pages". I don't recall it being that long, but
it's been a while since the last new PC (3+ years).  I think I'm on my
3rd PC with DXLab ... or is it 4?  XP SP2 for a long time, then W7 for
quite a while and now W10 since I bought this NUC back in '17.
Multiple logs for multiple calls and AFAIK, I have never lost a thing.

Peter




--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!






Re: Likely leaving DXLab Suite After Changing Computers

Peter Laws / N5UWY
 

On Wed, May 19, 2021 at 9:12 AM Richard Lawn <rjlawn@gmail.com> wrote:

Seems like it would be easier to just start fresh with a new copy, configure your radio(s) setup and move your log over. I'll likely do that or just abandon using DXLab suite of software. Other loggers and multi-purpose applications seem to be much easier in this regard.

Good summary of the "5 pages". I don't recall it being that long, but
it's been a while since the last new PC (3+ years). I think I'm on my
3rd PC with DXLab ... or is it 4? XP SP2 for a long time, then W7 for
quite a while and now W10 since I bought this NUC back in '17.
Multiple logs for multiple calls and AFAIK, I have never lost a thing.

Peter




--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Likely leaving DXLab Suite After Changing Computers

Richard Lawn <rjlawn@...>
 

I've been working on transitioning to a new ham shack computer. Not fun but everything now seems to be working, except DXLab Suite which still sits on the old (source) computer. 
I read through the 5 page explanation of relocating DXLab explanations from one PC to another and my eyes glazed over! It's probably me and my aging brain, but this process appears to be very very involved, especially if it takes 5 pages to explain it! I couldn't get past the first section about Commander. 
Seems like it would be easier to just start fresh with a new copy, configure your radio(s) setup and move your log over. I'll likely do that or just abandon using DXLab suite of software. Other loggers and multi-purpose applications seem to be much easier in this regard.

73s 
--
Rick, W2JAZ


Re: Question about QSL queue

Salvatore Besso
 

ok Joe, that's what I wanted to know to report back to my friend.

Thank you.

73 de
Salvatore (I4FYV)


Re: Question about QSL queue

Joe Subich, W4TV
 

So I repeat the question: is it a normal behaviour or is there
something wrong, in the program or in the operator?
*Unchecking* entries in the QSL queue after printing *clears* the
internal "has been printed" flag. The behavior you see is "normal".

The expected workflow is to only print QSLs when one is going to
send them and/or update the log immediately after printing QSLs.

73,

... Joe, W4TV


On 2021-05-19 2:37 AM, Salvatore Besso wrote:
hello,

> The "Update Log" function only operates on QSL Queue entries that
> were printed or saved to a file
of course, I know that it operates so, what I meant to say is:
One month ago:
1. New QSOs added in queue and QSLs printed
2. The log has not been updated
3. All QSLs entries are unchecked and stay in queue
20 days ago:
Repeat 1, 2 and 3
10 days ago:
Repeat 1, 2 and 3
Yesterday:
1. New QSOs added in queue and QSLs printed
2. All old QSLs entries are checked again
3. Update the log for ALL entries, also old ones
4. Update log doesn't do anything
Maybe I was not clear in my previous message.
So I repeat the question: is it a normal behaviour or is there something wrong, in the program or in the operator?
Thank you
73 de
Salvatore (I4FYV)


Re: Question about QSL queue

Salvatore Besso
 

hello,

The "Update Log" function only operates on QSL Queue entries that
were printed or saved to a file
of course, I know that it operates so, what I meant to say is:

One month ago:
1. New QSOs added in queue and QSLs printed
2. The log has not been updated
3. All QSLs entries are unchecked and stay in queue

20 days ago:
Repeat 1, 2 and 3

10 days ago:
Repeat 1, 2 and 3

Yesterday:
1. New QSOs added in queue and QSLs printed
2. All old QSLs entries are checked again
3. Update the log for ALL entries, also old ones
4. Update log doesn't do anything

Maybe I was not clear in my previous message.

So I repeat the question: is it a normal behaviour or is there something wrong, in the program or in the operator?

Thank you

73 de
Salvatore (I4FYV)


Re: QSL Print - Printer Size: User-Defined

Dave AA6YQ
 

+ AA6YQ comments below
My new QSLs arrived today.  In the meantime, my old Epson Photo printer, which I used to use for QSL printing, bit the dust.  I am trying to use my Brother MFC-L2750 laser printer center feed but the needed card stock size is not in the list under Printer | QSL Cards and Reply...  If I select, User-Defined, where can I define the 5.5 X 3.5" size?  

+ Typically, in the printer management software provided by your printer's manufacturer. I've never used a Brother printer, and so can't be more specific than that.

+ Keep in mind that DXKeeper QSL card printing capabilities are utilitarian. If you need more flexibility, DXKeeper can generate and ADIF or tab-delimited file from the QSL Queue that can be used to drive more flexible QSL-printing applications. See

https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing%20via%20ADIF

            73,

                   Dave, AA6YQ

 


QSL Print - Printer Size: User-Defined

John Samuels K2CIB
 

My new QSLs arrived today.  In the meantime, my old Epson Photo printer, which I used to use for QSL printing, bit the dust.  I am trying to use my Brother MFC-L2750 laser printer center feed but the needed card stock size is not in the list under Printer | QSL Cards and Reply...  If I select, User-Defined, where can I define the 5.5 X 3.5" size?  Of course, it is already defined in Cards | Card Dimensions. The print preview shows that it is set for 8.5 X 11.


Re: WSJT-X & Commander

Dave AA6YQ
 

+ AA6YQ comments below

Read Wiki on running both WSJT and Commander. Question is what does running Commander bring to the FT8 party? I can open any DXL Suite, log to DXK via JTAlert, watch Spot Collector, DXView etc without Commander. Does Commander integrate everything pertaining to a logged contact?

Obviously, I run all Suites including Commander running CW, SSB etc.

+ There are two ways that WSJT-X can interoperate with DXLab:

1. using JT-Alert

2. interoperating with DXLab directly

+ See " Getting Started with K1JT modes and DXLab"

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

+ for a summary of each approach, and pointers to step-by-step instructions

+ Commander plays the same role in both approaches: it enables WSJT-X to control your transceiver while allowing the other DXLab applications to retain access to your transceiver.

+ In the "direct interoperation" approach, SpotCollector directly communicates with WSJT-X, and directs DXKeeper, DXView, Pathfinder, and PropView as appropriate.

73,

Dave AA6YQ


Re: WSJT-X & Commander

g4wjs
 

On 18/05/2021 23:17, Jim Denneny wrote:
Read Wiki on running both WSJT and Commander.  Question is what does running Commander bring to the FT8 party?  I can open any DXL Suite, log to DXK via JTAlert, watch Spot Collector, DXView etc without Commander. Does Commander integrate everything pertaining to a logged contact?

Obviously, I run all Suites including Commander running CW, SSB etc.

Jim K7EG
Jim,

Commander controls you rig, WSJT-X can use Commander as a proxy rig control server to set the frequency, mode etc. of your rig.

You have things the wrong way, normally Commander integrates your rig with the reset of DX Lab Suite, making sure you log contacts on the right band, allowing to efficiently and quick pounce on spots of stations you need to work, and so on. Once Commander is controlling your rig it has exclusive access to the rig, by offering a proxy rig control mechanism Commander can allow WSJT-X to also control your rig when it needs to.



--
73

Bill

G4WJS.


WSJT-X & Commander

Jim Denneny
 

Read Wiki on running both WSJT and Commander.  Question is what does running Commander bring to the FT8 party?  I can open any DXL Suite, log to DXK via JTAlert, watch Spot Collector, DXView etc without Commander. Does Commander integrate everything pertaining to a logged contact?

Obviously, I run all Suites including Commander running CW, SSB etc.

Jim K7EG


Re: question about DXView

K3QH Start
 

Thank you very much for such a quick response....Got it! thanx 73


Re: question about DXView

Dave AA6YQ
 

+ AA6YQ comments below
Hi, I have a question about the dxview window. when I have spot collector active, dxview is constantly putting callsigns in its window. Seems to coincide with spot collectors motions however they only sometimes are the same ones that appear at the bottom of SC screen where a new spot appears. Most of the time I can't tell where they are coming from. When i click on a line in SC , I do get dxview to display the window for a short time before it continues to display many spots. My friends dxview only displays when you select a line in SC, it doesn't constantly keep populating the callsigns. I'm new to dxlab and would like to know if there is a selection in the configurations or is this an anomaly. 

+ In the General panel on the General tab of SpotCollector's Configuration window, uncheck the "Automatic DXView lookup" box.

+ See 

https://www.dxlabsuite.com/spotcollector/Help/ConfigurationGeneral.htm#Automatic%20DXView%20Update

    73,

           Dave, AA6YQ

 


question about DXView

K3QH Start
 

Hi, I have a question about the dxview window. when I have spot collector active, dxview is constantly putting callsigns in its window. Seems to coincide with spot collectors motions however they only sometimes are the same ones that appear at the bottom of SC screen where a new spot appears. Most of the time I can't tell where they are coming from. When i click on a line in SC , I do get dxview to display the window for a short time before it continues to display many spots. My friends dxview only displays when you select a line in SC, it doesn't constantly keep populating the callsigns. I'm new to dxlab and would like to know if there is a selection in the configurations or is this an anomaly.  73 and thanks.


Re: Question about QSL queue

Dave AA6YQ
 

+ AA6YQ comments below
I hope that you are all well and healty. Here all is well.

I ask a question on behalf of a friend of mine, DXLab user as me.

Franco has the habit to periodically print his QSL labels that he doesn't send immediately, so he doesn't update the log immediately after the print, but only when he really send the cards out. For this reason the QSL queue remains populated and already printed labels are simply unchecked. If the next days or weeks he has other labels to print, he adds them to the queue as usual and he repeat the print/uncheck process.

When it's time to really send out the cards (this afternoon for example) he checks again all the QSOs in the queue and clicks "Update log". The hourglass briefly appears, but DXKeeper does nothing and the log is not updated.

I say that I don't know if this problem already occurred to him in the past; anyway, I have found a way to resolve his problem by reprinting all the QSOs in the queue to a pdf file. After this, the log updated successfully and the queue has been emptied as usual.

The question is: is this a normal behaviour or there is something wrong?

I cannot verify my installation because I usually send out cards the same day when I print them, so I immediately update the log and this problem has never occurred to me

+ The "Update Log" function only operates on QSL Queue entries that were printed or saved to a file.

       73,

                Dave, AA6YQ

 


Question about QSL queue

Salvatore Besso
 

hello all,

I hope that you are all well and healty. Here all is well.

I ask a question on behalf of a friend of mine, DXLab user as me.

Franco has the habit to periodically print his QSL labels that he doesn't send immediately, so he doesn't update the log immediately after the print, but only when he really send the cards out. For this reason the QSL queue remains populated and already printed labels are simply unchecked. If the next days or weeks he has other labels to print, he adds them to the queue as usual and he repeat the print/uncheck process.

When it's time to really send out the cards (this afternoon for example) he checks again all the QSOs in the queue and clicks "Update log". The hourglass briefly appears, but DXKeeper does nothing and the log is not updated.

I say that I don't know if this problem already occurred to him in the past; anyway, I have found a way to resolve his problem by reprinting all the QSOs in the queue to a pdf file. After this, the log updated successfully and the queue has been emptied as usual.

The question is: is this a normal behaviour or there is something wrong?

I cannot verify my installation because I usually send out cards the same day when I print them, so I immediately update the log and this problem has never occurred to me.

Thank you.

73 de
Salvatore (I4FYV)


Re: SC linked to DXView

Dave AA6YQ
 

+ AA6YQ comments below
A fellow user of DXLab has asked me a "why does this happen" question regarding his DXLab setup.  The question was related to what is the linkage between SC reporting and DXView display.  In his case, DXView is reporting (sometimes) the latest new Spot in SC but he also says sometimes it is not the last one shown.  He can also get a DXV report of a SC station highlited with the Cursor which is the way DXView changes in my set up.
We have checked the "Configurations" for both DXV and SC looking for a function choice that would produce this continuous update of DXView - nothing found, so now asking the group for a solution which I am sure is out there.  

+ In the General panel on the General tab of SpotCollector's Configuration window, uncheck the "Automatic DXView lookup" box.

       73,

             Dave, AA6YQ


SC linked to DXView

Norm_W4QN
 

A fellow user of DXLab has asked me a "why does this happen" question regarding his DXLab setup.  The question was related to what is the linkage between SC reporting and DXView display.  In his case, DXView is reporting (sometimes) the latest new Spot in SC but he also says sometimes it is not the last one shown.  He can also get a DXV report of a SC station highlited with the Cursor which is the way DXView changes in my set up.
We have checked the "Configurations" for both DXV and SC looking for a function choice that would produce this continuous update of DXView - nothing found, so now asking the group for a solution which I am sure is out there.  
--
Norm_W4QN


Re: "DXing with DXLab" presentation to the International DX Convention

Craig Fastenow
 

I have been using an LG 43 inch 4k monitor for a couple of years and absolutely love it. It is the equivalent of 4- 24 inch 1080p monitors stacked in a 2 x 2 array.  Cost was very reasonable at about $600.

73, Craig K0CF


Re: Tracking down an my anomaly with Spot Collector

Mike Flowers
 

Thanks, Dave.   I will let you know what I find. 

-- 73 de Mike Flowers, K6MKF, NCDXC - "It's about DX!"

On May 17, 2021, at 4:53 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I have a small anomaly with Spot Collector that I’m trying to track down.

 

It appears that after Spot Collector has been running awhile (perhaps an hour or so), the spots that I submit through the ‘Outgoing spot’ panel no longer appear in my Spot database display although they had done so previously.

 

I use the VE7CC cluster for my spots.   I have filters at that cluster that keep the spots received by Spot Collector relevant and at a manageable level.

 

When this anomaly is occurring, my outgoing spots are shown on the VE7CC cluster when I look at it through the VE7CC client.

 

My outgoing spots also are shown on DXsummit.fi. 

 

Also, if I run this query in Spot Collector - ( Source = 'K6MKF' ) – all my outgoing spots are shown.   This tells me that my outgoing spots are stored in the Spot database, but just not displayed in the Spot database display.

 

Restarting Spot Collector restores the display of my outgoing spots, and all will be working OK until Spot Collector loses interest in my outgoing spots again.

 

I’d appreciate some guidance about how to proceed in my investigations.

+ If changing the Spot Database filter to

Source = 'K6MKF' 

+ makes Spot Database Entries for the stations you spotted visible, that implies that the Spot Database Filtering you were previously using is what's been hiding them. 

+ The next time a Spot Database Entry for a station you spotted fails to appear,

1. open the Band Filter window, and click the All button; does the Entry appear?

2. if not, open the Mode Filter window, and click the All button; does the Entry appear?

3. if not, open the Cont Filter window, and click the All button; does the Entry appear?

4. if not, open the Origin Filter window, and click the All button; does the Entry appear?

       73,

              Dave, AA6YQ

 

 

 

 

 

3261 - 3280 of 204684