Date   

Re: Mulitmonitor not recovering positions after lockking laptop and closing lid or when monitor is repositioned

Björn (SM0SBL)
 

Of course!
My fault!
I had that setting on all other windows but realized I could have the SC UI up behind the other windows to be able to se the first columns of spots from all bands while working the radio and had forgot I had to set it in SC as well...

I consider my request from this post as closed now. 
I'll probably post a reply here later on for those who might be interested when I have a working registry-file for window-settings only as a workaround.

And once again; BIG thank you for an incredible program suite for hams! It is by far the best interface for my radio, on site or remote, of all the others I have tried, including those that cost quite a lot of money...

Now I will focus on 17m which seam to be wide open at the moment :)
--
Björn, SM0SBL


Re: Mulitmonitor not recovering positions after lockking laptop and closing lid or when monitor is repositioned

Dave AA6YQ
 

+ AA6YQ comments below

Ok, fair enough.
I guess though that if you don't have enough with important stuff to work on you should be on the radio instead :o)

I do have an issue with window position of the SpotCollector.
It seams that SC don't accept negative number on registry key SpotDatabaseUILeft and SpotDatabaseUITop.
If I put SC on my external monitor and close the program the negative numbers are stored in the registry but when starting SC again it ends up on my main screen and when closing again the registry keys are set to zero.
The behavior is as if you by mistake used an unsigned int or by some other reason accidently limit the value to positive numbers.

+ Check the "Use multiple monitors" box in the General panel on the General tab of SpotCollector's Configuration window, and then SpotCollector won't coerce window X and Y coordinates to positive values; see

<https://www.dxlabsuite.com/spotcollector/Help/ConfigurationGeneral.htm#Use%20dual%20monitors>

73,

Dave, AA6YQ


Re: Mulitmonitor not recovering positions after lockking laptop and closing lid or when monitor is repositioned

Björn (SM0SBL)
 

I have emailed you the ErrorLog and registry entries before and after opening 0f SC when positioned on the secondary monitor.
--
Björn, SM0SBL


Re: Mulitmonitor not recovering positions after lockking laptop and closing lid or when monitor is repositioned

Björn (SM0SBL)
 

Ok, fair enough.
I guess though that if you don't have enough with important stuff to work on you should be on the radio instead :o)

I do have an issue with window position of the SpotCollector.
It seams that SC don't accept negative number on registry key SpotDatabaseUILeft and SpotDatabaseUITop.
If I put SC on my external monitor and close the program the negative numbers are stored in the registry but when starting SC again it ends up on my main screen and when closing again the registry keys are set to zero.
The behavior is as if you by mistake used an unsigned int or by some other reason accidently limit the value to positive numbers.

--
Björn, SM0SBL


Re: Logging WSJTX Q's into DXKeeper

Hasan Schiers N0AN
 

Can you wrap more than  one device cable on to that 2" toroidal forrf choking, or do you need a separate choir for each cable?

Also, a url for the specific choke being recommended would be very helpful.

TIA, 73 N0AN 

Hasan


On Fri, Nov 27, 2020, 5:28 PM BILL KENNAMER <k5fuv@...> wrote:
Further to that, wrap all cables coming into your computer around a two inch type 31 toroid  form. That will probably eliminate your rfi problem, which needs to be done first. 

K5FUV 


Sent from AT&T Yahoo Mail for iPad

On Friday, November 27, 2020, 4:04 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I sometimes am unable to log WSJT Q's thru JTAlert due to RFI issue. I must log manually.

Today, for first time, I copied WSJT-X log and pasted it into DXKeeper k7eg.adi file.  There is also a k7eg.mdb folder.  I only used adi file.  Is that correct?

+ No. DXKeeper does not reference your K7EG.ADI file, thus your action had no operational impact.

+ If your objective is to import all QSOs logged by WSJT-X that were not logged to DXKeeper, then you must import the ADIF file generated by WSJT-X into your DXKeeper log file with duplicate checking enabled and set for a range of 1 minute. This requires DXKeeper to check each QSO being imported against every other logged QSO; depending on the number of QSOs in your log and the number of QSOs being imported, this import operation can take a very long time. See

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

There maybe several dupes but that did not cause a problem. The JTAlert to DXKeeper works most of the time but once RFI hits it - game over.

+ DXLab applications require a reliable computer running Windows. A situation in which RFI is interfering with your computer's operation does not meet this requirement.

+ The adverse impact on your computer each time you transmit could be doing damage that isn't as visible as a QSO not being logged from JT-Alert to DXKeeper. I strongly suggest that you

1. backup your log, all critical files, and all settings, as described in steps 1, 2, and 3 in

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

+ The SafeStorage folder referred to in those instructions should be somewhere other than on your computer; a thumb drive, for example.

2. Backup all other critical files and application installers

3. Eliminate the RFI problem

4. Wipe your hard drive, re-install Windows, and re-install your applications (Complete the rest of the steps in the article cited above)


+ Step 4 prevents a latent problem or set of problems caused by RFI from popping up unexpectedly at some inconvenient point in the future.

    73,

              Dave, AA6YQ







WinWarbler 9.3.3 is available

Dave AA6YQ
 

If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in

<https://www.microsoft.com/en-us/wdsi/definitions>

before installing or upgrading to WinWarbler 9.3.3.



This release

- in a macro containing the <cwspeed> command, properly sends characters preceding the command

- with the Keying panel on the Configuration window's CW tab set to "serial port RTS", "serial port DTR", "PTT port RTS", "PTT port
DTR" or "parallel port", transmits CW for "international" characters Ä, ä, Æ, æ, Á, á, Å, å, É, é, Ñ, ñ, Ö, ö, Ø, ø, Ü, and ü (tnx
to Knut LA9RY and Björn SM7IUN)

- updates the CW.htm and CWKeystrokes.htm documentation files


Notes:


1. Update your firewall and anti-malware applications to consider this new version of WinWarbler to be "safe"

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 1 of 71 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable



2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


3. After upgrading, to revert to the previous version of WinWarbler, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


WinWarbler 9.3.3 is available via the DXLab Launcher or via

<http://www.dxlabsuite.com/download.htm>

73,

Dave, AA6YQ


Re: Using VE7CC with Spot Collector

Dave AA6YQ
 

+ AA6YQ comments below

Thanks ~iain, I did have that checked, but I was under impression that that had to be checked if you wanted to post a spot.

+ The "Ann/Talk" option has no impact on being able to generate an outgoing spot.

+ Retaining all information received from each spot source can consume significant amounts of memory over time. Enabling each spot source's "Ann/Talk" option limits this retention to announcements and "talk" messages to significantly reduce memory consumption. See the second item in

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

73,

Dave. AA6YQ


Re: Mulitmonitor not recovering positions after lockking laptop and closing lid or when monitor is repositioned

Dave AA6YQ
 

+ AA6YQ comments below

I'll post my script here when finished Carlo.
I think it will be a simple registry-changefile with only the window related lines in it. You will then have to manually change to your needs by comparing with the workspace saved settings for the corresponding lines.

@Dave: I still think it would be a good idea for you to consider the option to separate the window setups from the other settings.
When working on a 'script' I have realized it would be really great with the option to be able to save and load only the windows layout specific registry settings separate from other program behaviour settings if one want to.
A checkbox to save and load only windows layout specific information such as position, size, 'always on top', 'user defined controls expanded or not' and so on.

If I had that checkbox I could easily first load workspace for SM0SBL or SB0G which are my two callsigns depending on physical location. When at home, i.e. SM0SBL, I could also load only the window related information for either my 1920x1080 or 2560x1440 external monitor or if working with only the laptop a settings for a single 1920x1080 without changing other working condition related (call sign, QTH, IOTA etc..) When loading the workspace information regarding window layout the name in Launcher of the current workspace need not be changed as nothing behavioral has actually changed, only where and how the windows are visible or not.

It would not be a drastically change for the software I guess but a huge improvement for the few of us who have different setups from time to time.

The problem I would like to avoid is to not have separate workspaces for the same callsign and all working related information just to have separate window related settings. When I change something working condition related I must remember to change it in all workspaces regarding that working condition.
I am a developer myself, but for chip design, and my experience that any redundancy when the same information is stored in more than one place is doomed to diverge over time with confusion and potential problems...

It might be a some work to find all window related information to separate from the other settings but I'm willing to help you find that out by first make a registry file with enough settings to setup the window environment. Of course the position and size for all windows, and weather or not they shall be visible, is to be incorporated, but there are other settings such as 'always on top', 'expanded user control panel' and such that are candidates as well.

+ Thanks Björn. The time that I would spend implementing your enhancement request is time that I could not spend implementing other enhancement requests that provide greater value to a significantly larger fraction of the user community.

+ Using the Workspace mechanism for maintaining operational consistency among multiple DXLab installations works best when those installations share a common file structure (example: DXLab applications are installed in C:\DXLab in each installation) and a common monitor arrangement.

+ Someday, when I've run out of high-value enhancements to implement, I'll be able to address the more idiosyncratic requests.

73,

Dave, AA6YQ


Re: A shot in the dark question

Dave AA6YQ
 

+ AA6YQ comments below

It is done in the Barrett supplied programming software, then uploaded to the 2050. Programming can also be accomplished thru the front panel keys.

+ Thanks, Tom. My initial assessment stands.

73,

Dave, AA6YQ


Re: Spot Collector to N1MM

Dave AA6YQ
 

+ AA6YQ comments below

I think this is in the MM ballpark (last time I looked) but is there any movement on implementing this option

+ Correct, Stan. I have no progress to report.

73,

Dave. AA6YQ


Re: Mulitmonitor not recovering positions after lockking laptop and closing lid or when monitor is repositioned

Björn (SM0SBL)
 

I'll post my script here when finished Carlo.
I think it will be a simple registry-changefile with only the window related lines in it. You will then have to manually change to your needs by comparing with the workspace saved settings for the corresponding lines.

@Dave: I still think it would be a good idea for you to consider the option to separate the window setups from the other settings.
When working on a 'script' I have realized it would be really great with the option to be able to save and load only the windows layout specific registry settings separate from other program behaviour settings if one want to.
A checkbox to save and load only windows layout specific information such as position, size, 'always on top', 'user defined controls expanded or not' and so on.

If I had that checkbox I could easily first load workspace for SM0SBL or SB0G which are my two callsigns depending on physical location. When at home, i.e. SM0SBL, I could also load only the window related information for either my 1920x1080 or 2560x1440 external monitor or if working with only the laptop a settings for a single 1920x1080 without changing other working condition related (call sign, QTH, IOTA etc..)
When loading the workspace information regarding window layout the name in Launcher of the current workspace need not be changed as nothing behavioral has actually changed, only where and how the windows are visible or not.

It would not be a drastically change for the software I guess but a huge improvement for the few of us who have different setups from time to time.

The problem I would like to avoid is to not have separate workspaces for the same callsign and all working related information just to have separate window related settings. When I change something working condition related I must remember to change it in all workspaces regarding that working condition.
I am a developer myself, but for chip design, and my experience that any redundancy when the same information is stored in more than one place is doomed to diverge over time with confusion and potential problems... 

It might be a some work to find all window related information to separate from the other settings but I'm willing to help you find that out by first make a registry file with enough settings to setup the window environment. Of course the position and size for all windows, and weather or not they shall be visible, is to be incorporated, but there are other settings such as 'always on top', 'expanded user control panel' and such that are candidates as well.

--
Björn, SM0SBL


Added Folder /Compute Distance/Compute Distance #file-notice

DXLab@groups.io Notification <noreply@...>
 

mike s added folder /Compute Distance/Compute Distance


Re: Compute Distance with for each QSO?

 

Dave,

As you had indicated, when I populated all QSO's with the attribute Antenna_Path = S, the log immediately populated the distance field.  

The batch processing capability of dxkeeper is truly spectacular.  


Re: Compute Distance with for each QSO?

 

Dave,

Many, many thanks for your rapid and able investigation!   I will modify my log with noted addition of the short path.

I had, in fact, imported all of the qso's before I set the default value of the Antenna Path to S.  

Then, I set that in defaults and assumed (or did almost no thinking at all if the truth be known) that would propagate to previously imported qso's.

I appreciate your time and will be more thorough going forward.

Thank you again.

Mike (KM2B)


Re: A shot in the dark question

Tom Martin
 

It is done in the Barrett supplied programming software, then uploaded to the 2050. Programming can also be accomplished thru the front panel keys.


Re: Using VE7CC with Spot Collector

Mike Flowers
 

VE7CC just came back here - must have been a localized problem.

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Mike Flowers via
groups.io
Sent: Saturday, November 28, 2020 10:46
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

VE7CC is down. Been down all day.

I tried to connect with the VE7CC app and confirmed no connection.

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

On Nov 28, 2020, at 10:39 AM, Bob Main <bobmain1@windstream.net>
wrote:

Did that Dave and restarted SC, but I see no spots showing on the
spot source window for VE7CC, but I do on the others. Any idea why?

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave
AA6YQ
Sent: Saturday, November 28, 2020 1:32 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

+ AA6YQ comments below

I might be just missing something, but thought I would ask. I have
tried the following:

Using SC cluster box with Host of VE7CC.NET and port 23 and

CCUser with Host of 127.0.0.1 and port 7300. Now with this one I
don't remember which boxes in Spot Sources I need to have checked, I
am thinking only Enable and Ann/Talk. I would have Auto and Hide
unchecked since that would open the SC cluster box and not sure what
good that would do since the spots are on CCUser.

I used to see spots get posted on SC shortly after they appeared on
VE7CC, either connection above, but today with "Need" turned off I am
seeing a lot of spots going through the cluster but almost none are
appearing in SC. I also have 3 other clusters running and it appears
any spots that I am seeing appear to be coming from one of those.
Normally during a contest such as the one we have going on right now I
have "Need" turned on because I am hoping for some new CW countries to
add to my CW list.

Any ideas or suggestions?

+ Remove CCUser. It's only contribution is increased CPU and memory
+ loading,
which is a bad idea during a contest (with the SFI at
106!) that is generating high spot volume.

73,

Dave, AA6YQ













Re: Using VE7CC with Spot Collector

Bob Main
 

Thanks ~iain, I did have that checked, but I was under impression that that had to be checked if you wanted to post a spot.

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of iain macdonnell - N6ML
Sent: Saturday, November 28, 2020 2:08 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

Do you have Ann/Talk enabled for that spot source? If you do, you will
not see spots in the spot source window (that's the whole point of
that option).

73,

~iain / N6ML


On Sat, Nov 28, 2020 at 10:59 AM Bob Main <bobmain1@windstream.net> wrote:

Hmmm when I had CC User running I saw spots scrolling so it appears to be up to me, just not seeing spots on the source window. I am seeing spots on Spot Collector coming from Network VE7CC though.

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Mike Flowers
Sent: Saturday, November 28, 2020 1:46 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

VE7CC is down. Been down all day.

I tried to connect with the VE7CC app and confirmed no connection.

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

On Nov 28, 2020, at 10:39 AM, Bob Main <bobmain1@windstream.net> wrote:

Did that Dave and restarted SC, but I see no spots showing on the spot
source window for VE7CC, but I do on the others. Any idea why?

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Saturday, November 28, 2020 1:32 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

+ AA6YQ comments below

I might be just missing something, but thought I would ask. I have tried
the following:

Using SC cluster box with Host of VE7CC.NET and port 23 and

CCUser with Host of 127.0.0.1 and port 7300. Now with this one I don't
remember which boxes in Spot Sources I need to have checked,
I am thinking only Enable and Ann/Talk. I would have Auto and Hide
unchecked since that would open the SC cluster box and not sure
what good that would do since the spots are on CCUser.

I used to see spots get posted on SC shortly after they appeared on VE7CC,
either connection above, but today with "Need" turned off
I am seeing a lot of spots going through the cluster but almost none are
appearing in SC. I also have 3 other clusters running and
it appears any spots that I am seeing appear to be coming from one of those.
Normally during a contest such as the one we have
going on right now I have "Need" turned on because I am hoping for some new
CW countries to add to my CW list.

Any ideas or suggestions?

+ Remove CCUser. It's only contribution is increased CPU and memory loading,
which is a bad idea during a contest (with the SFI at
106!) that is generating high spot volume.

73,

Dave, AA6YQ



















Re: Using VE7CC with Spot Collector

iain macdonnell - N6ML
 

Do you have Ann/Talk enabled for that spot source? If you do, you will
not see spots in the spot source window (that's the whole point of
that option).

73,

~iain / N6ML

On Sat, Nov 28, 2020 at 10:59 AM Bob Main <bobmain1@windstream.net> wrote:

Hmmm when I had CC User running I saw spots scrolling so it appears to be up to me, just not seeing spots on the source window. I am seeing spots on Spot Collector coming from Network VE7CC though.

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Mike Flowers
Sent: Saturday, November 28, 2020 1:46 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

VE7CC is down. Been down all day.

I tried to connect with the VE7CC app and confirmed no connection.

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

On Nov 28, 2020, at 10:39 AM, Bob Main <bobmain1@windstream.net> wrote:

Did that Dave and restarted SC, but I see no spots showing on the spot
source window for VE7CC, but I do on the others. Any idea why?

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Saturday, November 28, 2020 1:32 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

+ AA6YQ comments below

I might be just missing something, but thought I would ask. I have tried
the following:

Using SC cluster box with Host of VE7CC.NET and port 23 and

CCUser with Host of 127.0.0.1 and port 7300. Now with this one I don't
remember which boxes in Spot Sources I need to have checked,
I am thinking only Enable and Ann/Talk. I would have Auto and Hide
unchecked since that would open the SC cluster box and not sure
what good that would do since the spots are on CCUser.

I used to see spots get posted on SC shortly after they appeared on VE7CC,
either connection above, but today with "Need" turned off
I am seeing a lot of spots going through the cluster but almost none are
appearing in SC. I also have 3 other clusters running and
it appears any spots that I am seeing appear to be coming from one of those.
Normally during a contest such as the one we have
going on right now I have "Need" turned on because I am hoping for some new
CW countries to add to my CW list.

Any ideas or suggestions?

+ Remove CCUser. It's only contribution is increased CPU and memory loading,
which is a bad idea during a contest (with the SFI at
106!) that is generating high spot volume.

73,

Dave, AA6YQ



















Spot Collector to N1MM

Jon Baker
 

I think this is in the MM ballpark (last time I looked)
but is there any movement on implementing this option

73
Stan N1ZX


Re: Using VE7CC with Spot Collector

Bob Main
 

Hmmm when I had CC User running I saw spots scrolling so it appears to be up to me, just not seeing spots on the source window. I am seeing spots on Spot Collector coming from Network VE7CC though.

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Mike Flowers
Sent: Saturday, November 28, 2020 1:46 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

VE7CC is down. Been down all day.

I tried to connect with the VE7CC app and confirmed no connection.

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

On Nov 28, 2020, at 10:39 AM, Bob Main <bobmain1@windstream.net> wrote:

Did that Dave and restarted SC, but I see no spots showing on the spot
source window for VE7CC, but I do on the others. Any idea why?

73, Bob KB4CL

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Saturday, November 28, 2020 1:32 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Using VE7CC with Spot Collector

+ AA6YQ comments below

I might be just missing something, but thought I would ask. I have tried
the following:

Using SC cluster box with Host of VE7CC.NET and port 23 and

CCUser with Host of 127.0.0.1 and port 7300. Now with this one I don't
remember which boxes in Spot Sources I need to have checked,
I am thinking only Enable and Ann/Talk. I would have Auto and Hide
unchecked since that would open the SC cluster box and not sure
what good that would do since the spots are on CCUser.

I used to see spots get posted on SC shortly after they appeared on VE7CC,
either connection above, but today with "Need" turned off
I am seeing a lot of spots going through the cluster but almost none are
appearing in SC. I also have 3 other clusters running and
it appears any spots that I am seeing appear to be coming from one of those.
Normally during a contest such as the one we have
going on right now I have "Need" turned on because I am hoping for some new
CW countries to add to my CW list.

Any ideas or suggestions?

+ Remove CCUser. It's only contribution is increased CPU and memory loading,
which is a bad idea during a contest (with the SFI at
106!) that is generating high spot volume.

73,

Dave, AA6YQ










3561 - 3580 of 201280