Date   

Re: Winwarbler Change Wish

Björn SM7IUN
 

Even even better with even less chance of misclick.

73,

Björn SM7IUN

Den ons 29 aug. 2018 kl 20:34 skrev Dave AA6YQ <aa6yq@...>:

+ AA6YQ comments below

That would be an improvement, but I would suggest swapping the Spot button and the Log button, then enlarge the Log button.

+ Here's a second iteration, with Dale AA1QD's proposed improvement (above) and the width of the Spot button slightly reduced to
provide more separation from the dreaded X button:

<http://www.dxlabsuite.com/winwarbler/WW914.jpg>

+ Any objections?

        73,

             Dave, AA6YQ





Re: DXKeeper Carson City, NV County Pull Down Menu

Joe Subich, W4TV
 

On 2018-08-29 2:14 PM, Dave AA6YQ wrote:
+ CQ Magazine's "Worked All US Counties" award -- abbreviated USA-CA -- mandates special treatment of the independent cities of Nevada (like Carson City) and Virginia: you must record them as an adjacent
county of your choice.
Note: Once you have chosen to map an independent city to an adjacent
county, you must map all instances of that independent city to the
same adjacent country. For example, Alexandria (City) Virginia sets
between Arlington and Fairfax counties. You may not make contact with two stations in Alexandria (City) and treat one as Arlington County
and the other as Fairfax County.

73,

... Joe, W4TV


On 2018-08-29 2:14 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
I just added QRZ XML lookup to my log and updated my complete log. I have a few broken QSO's showing.
One of these is K7WLX. He shows his county as Carson City, NV
and this explains how the original county was abolished and all brought under the city
https://en.wikipedia.org/wiki/Carson_City,_Nevada
Carson City was the county seat <https://en.wikipedia.org/wiki/County_seat> of Ormsby County <https://en.wikipedia.org/wiki/Ormsby_County,_Nevada> . In 1969, the county was abolished, and its territory merged with Carson City to form the Consolidated Municipality of Carson City.[ <https://en.wikipedia.org/wiki/Carson_City,_Nevada#cite_note-consolidatedmunicipality-3>
DXKeeper does not have a county pull down option for NV, Carson City which is what I think it should have.
+ CQ Magazine's "Worked All US Counties" award -- abbreviated USA-CA -- mandates special treatment of the independent cities of Nevada (like Carson City) and Virginia: you must record them as an adjacent county of your choice. DXKeeper's reference documentation cites a URL that describes this rule, but the URL is no longer functional. I am including CQ USA-CA award manager Ted K1BV in hopes that he will provide me with an updated URL with which I will update the reference documentation.
73,
Dave, AA6YQ


Re: Winwarbler Change Wish

Dave AA6YQ
 

+ AA6YQ comments below

That would be an improvement, but I would suggest swapping the Spot button and the Log button, then enlarge the Log button.

+ Here's a second iteration, with Dale AA1QD's proposed improvement (above) and the width of the Spot button slightly reduced to
provide more separation from the dreaded X button:

<http://www.dxlabsuite.com/winwarbler/WW914.jpg>

+ Any objections?

73,

Dave, AA6YQ


Re: DXKeeper Carson City, NV County Pull Down Menu

Dave AA6YQ
 

+ AA6YQ comments below

I just added QRZ XML lookup to my log and updated my complete log. I have a few broken QSO's showing.

One of these is K7WLX. He shows his county as Carson City, NV

and this explains how the original county was abolished and all brought under the city

https://en.wikipedia.org/wiki/Carson_City,_Nevada

Carson City was the county seat <https://en.wikipedia.org/wiki/County_seat> of Ormsby County <https://en.wikipedia.org/wiki/Ormsby_County,_Nevada> . In 1969, the county was abolished, and its territory merged with Carson City to form the Consolidated Municipality of Carson City.[ <https://en.wikipedia.org/wiki/Carson_City,_Nevada#cite_note-consolidatedmunicipality-3>

DXKeeper does not have a county pull down option for NV, Carson City which is what I think it should have.

+ CQ Magazine's "Worked All US Counties" award -- abbreviated USA-CA -- mandates special treatment of the independent cities of Nevada (like Carson City) and Virginia: you must record them as an adjacent county of your choice. DXKeeper's reference documentation cites a URL that describes this rule, but the URL is no longer functional. I am including CQ USA-CA award manager Ted K1BV in hopes that he will provide me with an updated URL with which I will update the reference documentation.

73,

Dave, AA6YQ


Re: DXKeeper: "LotW sent" not setting to "Y"

Dave AA6YQ
 

+ AA6YQ comments below

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Mike Dower
Sent: Wednesday, August 29, 2018 8:56 AM
To: DXLab@groups.io
Subject: Re: [DXLab] DXKeeper: "LotW sent" not setting to "Y"

Thanks Iain,

I checked through each of the 10 items in the page you referenced, and I couldn't find anything wrong.

DXKeeper shows 380 (!!!) QSOs which are still (stubbornly) set to "U". I have looked at the list of QSOs on my XYL's LotW account, and comparing a few between LotW and DXKeeper didn't show any errors, etc, so I think it's safe to assume that there is a high likelihood that the 380 QSOs in DXKeeper and LotW all match? Some of them even show QSLs received in both LotW and DXKeeper.

I'm wondering if the best way to fix this is to do a bulk change of "U" to "Y" using the "DXKeeper Advanced Sorts, Filters & Modifiers" page in order to convince the software that what the humans are seeing is actually correct?

+ It's not necessary to make assumptions; DXKeeper can update those 380 QSOs with their LoTW acceptance "en masse". However, before doing that, let's try updating one QSO and see what happens. Please do the following:

1. on the Main window's "Log QSOs" tab, click the Filter panel's LoTW button; the Log Page Display should be filtered to contain those 380 QSOs whose "LoTW QSL Sent" items are set to 'U'.

2. Pick one of these QSOs, right-click its entry in the Log Page Display, and select "Update from LoTW" in the popup menu. What is the result of this operation?

73,

Dave, AA6YQ


Re: DX View

Dave AA6YQ
 

+ AA6YQ comments below

Pretty sure there is a way to "Port" the DXlabs data to a separate computer that has dxlabs on it with DX Atlas so that I could use a separate monitor (third Monitor)

+ I'm not aware of a way to do that, Steve; for DXView to interoperate with DX Atlas, the two applications must be running on the same PC. You can of course attach a 3rd monitor to that PC.

73,

Dave, AA6YQ


Re: DX View

WA8Y Steven
 

DXAtlas


On Tue, Aug 28, 2018, 8:16 PM Jim - KR9U <kr9u@...> wrote:

Recently there has been talk of using DXView as an alternative to Geochron.

However, the map is pretty small and I see no way to enlarge it to fill a screen.  Is it possible to do this or can it be implemented?

 

Jim - KR9U

 


Re: Winwarbler Change Wish

Dale Drake
 

That would be an improvement, but I would suggest swapping the Spot button and the Log button, then enlarge the Log button.

 

My 2 cents worth.

 

Dale AA1QD

 

 


Re: DXKeeper Carson City, NV County Pull Down Menu

KA9JAC
 

Carson City is an Independent City, you will find them other places also. There is a bunch of them in VA.
For the purpose of county hunting and the USA-CA award, you can count it for one of the adjoining counties.

73
Bob, KA9JAC

On 8/29/2018 9:02 AM, Mark Robinson wrote:
I just added QRZ XML lookup to my log and updated my complete log.  I have a few broken QSO's showing.

One of these is K7WLX.  He shows his county as Carson City, NV

and this explains how the original county was abolished and all brought under the city

https://en.wikipedia.org/wiki/Carson_City,_Nevada

Carson City was the county seat of Ormsby County.  In 1969, the county was abolished, and its territory merged with Carson City to form the Consolidated Municipality of Carson City.[


DXKeeper does not have a county pull down option for NV, Carson City which is what I think it should have.

73 Mark N1UK



Virus-free. www.avg.com


Re: Winwarbler Change Wish

Björn SM7IUN
 

Very sensible proposal. 

After having made this mistake myself a prefer to use Ctrl-L.

Björn SM7IUN


Den ons 29 aug. 2018 kl 04:23 skrev Dave AA6YQ <aa6yq@...>:

+ AA6YQ comments below

If I had one wish to make a change to Winwabler... I would move the X (click to clear all QSO info textboxes) underneath the Red Button (Audio record) and widen the Log button to occupy the space the X was in...

I don't know how many times I have cleared a QSO rather than logging it...especially... when in the heat of the battle or not get my mouse arrow directly over the Log button...!

+ I am not comfortable with moving the X button, as its position helps document its function. Moving it elsewhere would require changing its name to "Clear", as is done in DXKeeper's Capture window; this would consume significantly more space.

+ However, the Log button can be enlarged by dropping the Audio Recording button to the second row, as shown in the upper-right corner of the "QSO Info" panel of this screen shot:

<http://www.dxlabsuite.com/winwarbler/WW914.jpg>

+ Would this be a worthwhile improvement? Does anyone object to this change?

         73,

                Dave, AA6YQ





Re: Winwarbler Change Wish

 

I agree with this proposed change

Steve
KG5VK


http://www.KG5VK.com
My Ham Radio Friends


On Wed, Aug 29, 2018 at 8:05 AM, Greg <vk3vt@...> wrote:
Dave

I think this is a good idea.

73, Greg VK3VT


On 29/08/2018 12:23 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

If I had one wish to make a change to Winwabler... I would move the X (click to clear all QSO info textboxes) underneath the Red Button (Audio record) and widen the Log button to occupy the space the X was in...

I don't know how many times I have cleared a QSO rather than logging it...especially... when in the heat of the battle or not get my mouse arrow directly over the Log button...!

+ I am not comfortable with moving the X button, as its position helps document its function. Moving it elsewhere would require changing its name to "Clear", as is done in DXKeeper's Capture window; this would consume significantly more space.

+ However, the Log button can be enlarged by dropping the Audio Recording button to the second row, as shown in the upper-right corner of the "QSO Info" panel of this screen shot:

<http://www.dxlabsuite.com/winwarbler/WW914.jpg>

+ Would this be a worthwhile improvement? Does anyone object to this change?

          73,

                 Dave, AA6YQ











DXKeeper Carson City, NV County Pull Down Menu

Mark Robinson
 

I just added QRZ XML lookup to my log and updated my complete log.  I have a few broken QSO's showing.

One of these is K7WLX.  He shows his county as Carson City, NV

and this explains how the original county was abolished and all brought under the city

https://en.wikipedia.org/wiki/Carson_City,_Nevada

Carson City was the county seat of Ormsby County.  In 1969, the county was abolished, and its territory merged with Carson City to form the Consolidated Municipality of Carson City.[


DXKeeper does not have a county pull down option for NV, Carson City which is what I think it should have.

73 Mark N1UK


Re: Winwarbler Change Wish

Greg
 

Dave

I think this is a good idea.

73, Greg VK3VT

On 29/08/2018 12:23 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

If I had one wish to make a change to Winwabler... I would move the X (click to clear all QSO info textboxes) underneath the Red Button (Audio record) and widen the Log button to occupy the space the X was in...

I don't know how many times I have cleared a QSO rather than logging it...especially... when in the heat of the battle or not get my mouse arrow directly over the Log button...!

+ I am not comfortable with moving the X button, as its position helps document its function. Moving it elsewhere would require changing its name to "Clear", as is done in DXKeeper's Capture window; this would consume significantly more space.

+ However, the Log button can be enlarged by dropping the Audio Recording button to the second row, as shown in the upper-right corner of the "QSO Info" panel of this screen shot:

<http://www.dxlabsuite.com/winwarbler/WW914.jpg>

+ Would this be a worthwhile improvement? Does anyone object to this change?

73,

Dave, AA6YQ




Re: DXKeeper: "LotW sent" not setting to "Y"

Mike Dower
 

Thanks Iain,

I checked through each of the 10 items in the page you referenced, and I couldn't find anything wrong.

DXKeeper shows 380 (!!!) QSOs which are still (stubbornly) set to "U".  I have looked at the list of QSOs on my XYL's LotW account, and comparing a few between LotW and DXKeeper didn't show any errors, etc, so I think it's safe to assume that there is a high likelihood that the 380 QSOs in DXKeeper and LotW all match?  Some of them even show QSLs received in both LotW and DXKeeper.

I'm wondering if the best way to fix this is to do a bulk change of "U" to "Y" using the "DXKeeper Advanced Sorts, Filters & Modifiers" page in order to convince the software that what the humans are seeing is actually correct?

Regards,

Mike VK2IG 


Re: DX View

 

Pretty sure there is a way to "Port" the DXlabs data to a separate computer that has dxlabs on it with DX Atlas so that
I could use a separate monitor (third Monitor)

with the server tool

But not sure ???

Dave can you point me to the right direction

I know I should be able to find it in the Manual but it alludes me

Thanks in adavance

Steve
KG5VK


Re: Winwarbler Change Wish

Curt Bowles
 

Hello dave...

Yes that certainly would be a big improvement from my perspective.

thanks for taking a look at his : - )

73
--
Curt Bowles
VE3ZN


Re: Winwarbler Change Wish

Gordon LaPoint
 

Dave,
    Moving the Audio Recording Button to the second row sounds like a Great! idea.  I have also clicked the X when I wanted "Log".
Thanks,
Gordon - N1MGO

On 08/28/2018 10:23 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

If I had one wish to make a change to Winwabler... I would move the X (click to clear all QSO info textboxes) underneath the Red Button (Audio record) and widen the Log button to occupy the space the X was in...

I don't know how many times I have cleared a QSO rather than logging it...especially... when in the heat of the battle or not get my mouse arrow directly over the Log button...!

+ I am not comfortable with moving the X button, as its position helps document its function. Moving it elsewhere would require changing its name to "Clear", as is done in DXKeeper's Capture window; this would consume significantly more space.

+ However, the Log button can be enlarged by dropping the Audio Recording button to the second row, as shown in the upper-right corner of the "QSO Info" panel of this screen shot:

<http://www.dxlabsuite.com/winwarbler/WW914.jpg>

+ Would this be a worthwhile improvement? Does anyone object to this change?

73,

Dave, AA6YQ


--
Gordon - N1MGO


Re: Winwarbler Change Wish

Salvatore Besso
 

no objection to this change. I also have cleared some QSO's instead of logging them... The X side by side with Log button is somewhat dangerous...

73 de
Salvatore (I4FYV)


Re: Commander and IC-7610 ports changing

Björn SM7IUN
 

I would suggest you to not follow the ICOM guys advice and instead 
manually set the COM port of your radio in the advanced settings. 
Windows will tell you which ports are in use and not.

Björn SM7IUN 

28 aug. 2018 kl. 23:21 skrev dvpoplewski <dpopski@...>:

Here is the question and answer I got back from Icom.

Question
Loaded Silicon Labs drivers into windows 7 computer. Turning on IC-7610 shows comm ports 4 and 5. I assign com port 4 to my DX Suites commander logging and radio control program and the radio and software communicate fine. 
If I turn off the radio and power supply the com ports disappear from device manager. 
Turning the radio and power supply back on, the com ports change to different numbers and DX commander no longer works. If I leave the power supply on all the time, then the com ports remain, but it is not practical to leave the power supply running all the time. 
If I leave the software program running and turn back on the power supply and radio, the DX Command program no longer responds to port 4. I have to toggle command to port 5 and then back to port 4, then all works again. 
What is the solution to this comm port issue?

Answer:
Greetings David, 

Thank you for contacting Icom America. 

Unfortunately this is a quirk of Windows. Windows assigns resources on a "as needed" basis. What I can suggest is with the radio connected and powered up then shutdown down Windows and then restart. In some cases doing this will allow the Operating System to use the same resources each time the radio is connected/disconnected. Though adding/removing other USB devices could force another remapping of resources. Unfortunately this is all within Windows and beyond the users control. You could go into device manager and force the CP210x device(s) to use a specific COM Port (in the Advanced tab for the device) but this is for advanced users of Windows so I would not suggest you doing that unless you have extensive knowledge of Windows since you have to insure that no other devices are using the COM Port you want to use. 

Click here for information regarding Warranty Registration, Service/Repair Authorization form, Knowledge Base & Technical Support: http://www.icomamerica.com/en/support/default.aspx 

Note: Mention of third party products or services is provided for customer convenience and does not imply an endorsement or quality assurance by ICOM America. 

Sincerely, 
Greg Popovich / KF2M 
Technical Support Representative 
Icom America Inc. 
East Coast Office 
14000 Commerce Parkway Suite H 
Mount Laurel, NJ 08054

David KC8IV


Re: Winwarbler Change Wish

Dave AA6YQ
 

+ AA6YQ comments below

If I had one wish to make a change to Winwabler... I would move the X (click to clear all QSO info textboxes) underneath the Red Button (Audio record) and widen the Log button to occupy the space the X was in...

I don't know how many times I have cleared a QSO rather than logging it...especially... when in the heat of the battle or not get my mouse arrow directly over the Log button...!

+ I am not comfortable with moving the X button, as its position helps document its function. Moving it elsewhere would require changing its name to "Clear", as is done in DXKeeper's Capture window; this would consume significantly more space.

+ However, the Log button can be enlarged by dropping the Audio Recording button to the second row, as shown in the upper-right corner of the "QSO Info" panel of this screen shot:

<http://www.dxlabsuite.com/winwarbler/WW914.jpg>

+ Would this be a worthwhile improvement? Does anyone object to this change?

73,

Dave, AA6YQ

31481 - 31500 of 211215