Date   

Re: Error Logging

Dave AA6YQ
 

+ AA6YQ comments below

At the completion of a WSJT-x QSO, instead of logging the QSO to DXKeeper this error message pops up. It is possible to manually log contacts.

+ Attachments are not conveyed here. What is the text of the error message?

+ Are you using the direct interoperation between WSJT-X and DXLab, or are you using JT-Alert?

+ Have these error messages always appeared, or is this a recent phenomenon? If the latter, what changes to your software or hardware did you make around the time they first began appearing?

73,

Dave, AA6YQ


Re: Error Logging

Joe Subich, W4TV
 

this error message pops up.
Screen captures are not supported here. Enter the text of the
error message.

It is possible to manually log contacts.
Have you studied the appropriate section of "Getting Started with DXLab
Suite"?

For WSJTX without JTAlert:
<http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect>

For WSJTX *with* JTAlert:
<http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert>

Also see:
<http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes>


73,

... Joe, W4TV


On 2021-07-07 9:25 PM, n7bv@hotmail.com wrote:
At the completion of a WSJT-x QSO, instead of logging the QSO to DXKeeper this error message pops up.  It is possible to manually log contacts.
=============
Tks.  73, Chuck N7BV


Re: FT-857D / FM Satellites

pinoleronica
 

Thanks, Dave....Maybe someone has figured it out.   Meanwhile I can still use it though cumbersome.   Tomorrow I will play with memories for the FM satellites just like I will do it with a HT and without connection to any software and only use LotW login.

73s

--
Rafael / NN3RP


Re: Need help with saving workspace

Scott Stembaugh
 

Have you selected 'Use multiple monitors' in each application's Config panel, General tab?

73,
--scott


On Wed, Jul 7, 2021 at 9:00 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
I just set up a new pc and transferred DXLabs to the new machine using the online instructions. Everything went well with one issue. My problem is i have two monitors on the new pc and I'm trying to save a workspace on monitor 2. I've gone through all the instructions on how to save a new workspace several times but can't get it to open on monitor 2.
I'm sure I'm missing the obvious but can't figure it out. Anyone using 2 monitors and setting DXLabs on monitor 2?

+ Unless the two monitors on the new machine are configured identically to those of the old machine, windows on the new machine's secondary monitor will not appear in the correct place.

+ To correct this,

1. start the Launcher and one DXLab application whose windows are not appearing where you want them

2, at the bottom of the Launcher's Configuration window, click the Reset button; this will direct that DXLab application to display all of its windows on the primary monitor. 

3. drag the DXLab application's windows to where you want them on the primary and second monitors

4. terminate the DXLab application whose windows placements you configured in step 3

5. start another DXLab application whose windows are not appearing where you want them

6. goto step 2

       73,

            Dave, AA6YQ


Re: Error Logging

n7bv@...
 

At the completion of a WSJT-x QSO, instead of logging the QSO to DXKeeper this error message pops up.  It is possible to manually log contacts.

=============
Tks.  73, Chuck N7BV


Re: FT-857D / FM Satellites

Dave AA6YQ
 

+ AA6YQ comments below
Gentlemen, good evening...I hope you're enjoying the summer days.

I have setup FT-857D for my soon trip to YN.   Commander is working fine together with SatPC32.   I have work a few of the "birds" (FM) already but with some difficulty.  Frequencies are automatically displayed on Command (Down and Uplink), split, mode, sat name, etc..  The radio, however, on RX flickers between the two VFOs almost too fast for me to correctly hear the call signs.  TX is no problem as I get replies back.

If I disable CAT ( - / + )  on SatPC32 then no flickering and can make smooth QSOs.  Then I activate again to catch up with doppler.  So I go in this way through the pass of the FM Sat.   I could make use of memories on the radio and avoid Commander but defeats the logging purpose.

Is there a way to make the flickering less active sort of a few seconds more?  Or is there a better way to do FM sat using FT-857D?

Satellite exhuberant, 

+ When you're using SatPC32, it controls your transceiver, not Commander. While a fellow satellite aficionado here may be able to help you, contacting the developer of SatPC32 may provide a faster resolution.

+ Safe travels to -- and good DX from -- YN!

         73,

                Dave, AA6YQ

 


Re: DXKeeper 16.1.5 upgrade then failure to open database

George KC1V
 

Hello,

Installing DXKeeper 16.1.9 has corrected the earlier problem.  Initially, DXKeeper would not open the kc1v.mdb I had placed in the databases folder or the config.txt file I placed in the Configurations folder.  After re-selecting the config.txt file, both files opened.  I'm not sure of the exact sequence of actions that caused the file to open, but at that point everything appeared to function correctly.

Thanks and 73,

George, KC1V
FN31 


FT-857D / FM Satellites

pinoleronica
 

Gentlemen, good evening...I hope you're enjoying the summer days.

I have setup FT-857D for my soon trip to YN.   Commander is working fine together with SatPC32.   I have work a few of the "birds" (FM) already but with some difficulty.  Frequencies are automatically displayed on Command (Down and Uplink), split, mode, sat name, etc..  The radio, however, on RX flickers between the two VFOs almost too fast for me to correctly hear the call signs.  TX is no problem as I get replies back.

If I disable CAT ( - / + )  on SatPC32 then no flickering and can make smooth QSOs.  Then I activate again to catch up with doppler.  So I go in this way through the pass of the FM Sat.   I could make use of memories on the radio and avoid Commander but defeats the logging purpose.

Is there a way to make the flickering less active sort of a few seconds more?  Or is there a better way to do FM sat using FT-857D?

Satellite exhuberant, 

Rafael / NN3RP


Re: Need help with saving workspace

Dave AA6YQ
 

+ AA6YQ comments below
I just set up a new pc and transferred DXLabs to the new machine using the online instructions. Everything went well with one issue. My problem is i have two monitors on the new pc and I'm trying to save a workspace on monitor 2. I've gone through all the instructions on how to save a new workspace several times but can't get it to open on monitor 2.
I'm sure I'm missing the obvious but can't figure it out. Anyone using 2 monitors and setting DXLabs on monitor 2?

+ Unless the two monitors on the new machine are configured identically to those of the old machine, windows on the new machine's secondary monitor will not appear in the correct place.

+ To correct this,

1. start the Launcher and one DXLab application whose windows are not appearing where you want them

2, at the bottom of the Launcher's Configuration window, click the Reset button; this will direct that DXLab application to display all of its windows on the primary monitor. 

3. drag the DXLab application's windows to where you want them on the primary and second monitors

4. terminate the DXLab application whose windows placements you configured in step 3

5. start another DXLab application whose windows are not appearing where you want them

6. goto step 2

       73,

            Dave, AA6YQ


Need help with saving workspace

Tim
 

I just set up a new pc and transferred DXLabs to the new machine using the online instructions. Everything went well with one issue. My problem is i have two monitors on the new pc and I'm trying to save a workspace on monitor 2. I've gone through all the instructions on how to save a new workspace several times but can't get it to open on monitor 2.
I'm sure I'm missing the obvious but can't figure it out. Anyone using 2 monitors and setting DXLabs on monitor 2? Thanks Tim NZ8J


Re: broken DXLAB

Dave AA6YQ
 

+ AA6YQ comments below

My friend's dxlab launcher is screwed up and won't work. I have tried to fix it but no luck.

+ Had you stopped this point and posted a message here explaining exactly what "screwed up and won't work" means, I'd likely have been able to correct whatever was wrong.

I want to do a full clean install so I renamed the dxlab folder downloaded dxlauncher and installed it in a new dxlab folder.
opened dxlauncher and upgraded it to v2.1.4 all of the buttons above every module are red. if i click one it reads that that module cannot be found

+ You are way outside the Windows envelope.

+ Renaming the DXLab folder that contains DXLab applications breaks each of those applications. Installing the Launcher in a new DXLab folder does not result in a "clean install"; it results in a mess.

I read that when launcher was installed that all the other modules are also installed but i am not seeing this

+ You didn't read that here or in any DXLab documentation. The Launcher installs DXLab applications one at a time, each at your direction.

I think it is cockpit trouble so can anybody throw this old dog a bone?

+ All bets are off at this point. You could try directing Windows to uninstall the Launcher, un-rename the DXLab folder to its original name, and then install the Launcher in that DXLab folder. The odds of this producing a reliable system are maybe 50%.

+ Windows is a brittle and unforgiving system. If you get to a point where you aren't absolutely certain that you know what to do, do nothing, and seek help here. Otherwise, backing up everything, wiping your C: drive, and re-installing Windows will become an all-too-familiar task.

73,

Dave, AA6YQ


Re: Filtering log by MONTH

Dave AA6YQ
 

+ AA6YQ comments below

I am looking to filter my log to see QSOs made during contests. Most of the QSOs have been imported to another logger prior to DXLab, and don't have any comment flagging them as contest QSOs. I can filter by a date range, but then I would have to go back and filter for each of the last 25 years or so, to look at a particular contest (since the date filter is a complete day/month/year, begin and end).

Is there a way to filter my log to pull out all QSOs made in the last 2 weeks of October, or last 2 weeks of November for ALL years at once? I don't think the dates are stored as strings, so looking for '11/' or '10/' doesn't work with an SQL query. Any ideas?

+ The QSO_Begin and QSO_End items are stored as dates, not strings.

+ The SQL expression

MONTH(QSO_BEGIN)=11

+ will find all QSOs made during any November.

+ Check out the SQL functions described here:

https://www.techonthenet.com/access/functions/

+ Perhaps they provide a way to home in more tightly on the date ranges you seek.

73,

Dave, AA6YQ


Filtering log by MONTH

dwfred@bellsouth.net
 

I am looking to filter my log to see QSOs made during contests.  Most of the QSOs have been imported to another logger prior to  DXLab, and don't have any comment flagging them as contest QSOs.  I can filter by a date range, but then I would have to go back and filter for each of the last 25 years or so, to look at a particular contest (since the date filter is a complete day/month/year, begin and end).

Is there a way to filter my log to pull out all QSOs made in the last 2 weeks of October, or last 2 weeks of November for ALL years at once?  I don't think the dates are stored as strings, so looking for '11/' or '10/' doesn't work with an SQL query.  Any ideas?

Thanks,
Dean W8ZF


Re: DXKeeper 16.1.9 is available

Dick Grote
 

Feature. 

Thanks.
--
Dick
K6PBF


Re: Error Logging

Dave AA6YQ
 

+ AA6YQ comments below
Why does this happen??  Every so often DXKeeper throws this curve ball.  Can get around it by manually logging the info, but curios if there is a way around this situation.
+ Please describe the situation to which you are referring in as much detail as you can.

       73,

             Dave, AA6YQ


Error Logging

n7bv@...
 

Why does this happen??  Every so often DXKeeper throws this curve ball.  Can get around it by manually logging the info, but curios if there is a way around this situation.

=============
Thanks.   73, Chuck N7BV


Re: DXKeeper 16.1.9 is available

Dave AA6YQ
 

+ AA6YQ comments below
I don't know if this is a bug or a feature but when the capture window is resized (shrunk vertically) and then returned to its original size, all of the rows are all selected again.

+ That's intentional, Dick; I sought to preserve the previous functionality for those users who found it sufficient and convenient:

- When you expand the Capture window's height, each newly-exposed row is automatically enabled on the new "Capture Layout" window. 

- When you reduce the Capture window's height, each newly-hidden row is automatically disabled on the new "Capture Layout" window.
 
           73,

                   Dave, AA6YQ



       73,

           Dave, AA6YQ

 


Re: DXKeeper 16.1.9 is available

Dave AA6YQ
 

+ AA6YQ comments below

Agreed! One question, though. When I start up I now have the QSL Msg dropdown selected instead of the Comment. I have to re-set the choice to Comment each time I start DXKeeper. Anyone else seeing this?

+ Thanks, Chuck, that's a regression defect. It is corrected in the next version of DXKeeper.

73,

Dave, AA6YQ


Re: DXKeeper 16.1.9 is available

Joe Subich, W4TV
 

Resizing vertically (expanding) always selected all rows.
You are triggering that standard response by expanding the
window.

73,

... Joe, W4TV

On 2021-07-07 10:03 AM, Dick Grote via groups.io wrote:
I like this.
I don't know if this is a bug or a feature but when the capture window is resized (shrunk vertically) and then returned to its original size, all of the rows are all selected again.
--
Dick
K6PBF


Re: DXKeeper 16.1.9 is available

Andy - K0AF
 

Agreed!  One question, though.  When I start up I now have the QSL Msg dropdown selected instead of the Comment.  I have to re-set the choice to Comment each time I start DXKeeper.  Anyone else seeing this?
 
 
73 de Chuck, WS1L  
I see the same thing Chuck; the default for row 10 is "QSL msg". I can change it to "comment" by clicking the "~" on the left side of the entry box but it reverts to "QSL msg" when DXKeeper is restarted. The Cfg window allows you to save and recall the Capture Window layout but it also reverts to "QSL msg" for row 10 regardless of the state when the view was saved.

The new Capture Window layout option is a nice enhancement. Thanks Dave!

Andy - K0AF

2361 - 2380 of 204646