Date   

Re: updated eQSL AG and LoTW databases are available ...

Frank Kirschner <frank.kirschner@...>
 


Just Commander. I don't know if other programs call on those databases.


On Tue, Aug 28, 2018, 17:27 Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I only use JTAlert and WSJT-X. Do I need these updates?

+ Which DXLab applications are you using, Frank?

       73,

              Dave, AA6YQ






Re: updated eQSL AG and LoTW databases are available ...

Frank Kirschner <frank.kirschner@...>
 

Just Commander. I don't know if oth


On Tue, Aug 28, 2018, 17:27 Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I only use JTAlert and WSJT-X. Do I need these updates?

+ Which DXLab applications are you using, Frank?

       73,

              Dave, AA6YQ






Re: Commander and IC-7610 ports changing

Joe Subich, W4TV
 

This is simply because Icom (and other manufacturers) are *LAZY*.
If they would use serial port hardware that had a unique serial
number in the port chip EPROM, Windows would load the hardware at
the same port number every time.

Simply put, the amateur manufacturers do not want to take the extra
step to program a serial number into the port hardware after the
rig is complete.

73,

... Joe, W4TV

On 2018-08-28 5:21 PM, dvpoplewski wrote:
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: Commander and IC-7610 ports changing

Dave AA6YQ
 

Thanks, David!

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of dvpoplewski
Sent: Tuesday, August 28, 2018 5:22 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Commander and IC-7610 ports changing

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


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


Re: updated eQSL AG and LoTW databases are available ...

Dave AA6YQ
 

+ AA6YQ comments below

I only use JTAlert and WSJT-X. Do I need these updates?

+ Which DXLab applications are you using, Frank?

73,

Dave, AA6YQ


Re: Commander and IC-7610 ports changing

George KF7NN
 

thats normal operation, the system was talking to the com port and you killed it by turning off the power ,so the system is stuck and dont know where the port went. when you re attached the port it is not the instance that the PC was originally talking to but another and you need to reset the driver to go fetch the correct instance of the port. I assume the port gets its own free block of memory address each time it is attached.


I am no expert but thats my opinion.

On 8/26/2018 10:10 PM, Dave AA6YQ wrote:
When connected to my PC (running Windows 7) via USB, my IC-7300 creates COM6; this appears in the Windows Device Manager's Ports section as "Silicon Labs CP210x USB to UART Bridge".

If I turn off the IC-7300 via its front panel Power button, the entry for COM6 remains present in the Windows Device Manager's Ports section. If I turn on the IC-7300 via its front panel Power button, Commander immediately tracks and controls the IC-7300.

If I turn off the IC-7300 via its front panel Power button, and then turn off the DC power supply connected to the IC-7300, the entry for COM6 is removed from the Windows Device Manager's Ports section. If I turn on the DC power supply connected to the IC-7300, the entry for COM6 re-appears in the Windows Device Manager's Ports section. If I then turn on the IC-7300 via its front panel Power button, Commander cannot control or track the radio; however, if I click the Reset button in the Radio tab on the General tab of Commander's Configuration window, Commander regains the ability to control and track the radio.

73,

Dave, AA6YQ





Re: Commander and IC-7610 ports changing

dvpoplewski
 

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


Winwarbler Change Wish

Curt Bowles
 

Hello

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...!

Just saying : - )
--
Curt Bowles
VE3ZN


Re: updated eQSL AG and LoTW databases are available ...

Frank Kirschner <frank.kirschner@...>
 

I only use JTAlert and WSJT-X. Do I need these updates? Do I need to install DXKeeper to get them?

Thanks. 

73,
Frank 
KF6E

On Tue, Aug 28, 2018, 00:27 Dave AA6YQ <aa6yq@...> wrote:
...via the Databases tab of DXView's Configuration window.

        73,

               Dave, AA6YQ





Re: Problems with WinWarbler and WIN10

Wolf E. Rose
 

Problems solved!

Good morning Dave,

mni tnx for your assistance. Now everything works asexpected. Just like my good friend Gisela DK9GG used to say: ‚As soon as you do it right, it works!‘

My comments in the text.

Am 28.08.2018 um 08:55 schrieb Dave AA6YQ <aa6yq@...>:

1. you sent your message to

aa5yq (at) ambersoft instead of

aa6yq (at) ambersoft, so I just now received it
Sorry my typo, glad that you picked it up anyhow.

2. if your WinWarbler macros are in the file

rtty_dx_hunt.txt

then the command to load them should be

<loadmacrobank: rtty_dx_hunt.txt>

not

<loadmacrobank: rtty_dx_hunt>
Just corrected it and no wonder it works!

3. the current version of WinWarbler is 9.0.6; why are you running version 8.1.1 - which is more than 4 years old?
Had the 9.0.6 version running before with the hassle I wrote about. Tried the old 8.1.1 from my friend Volker DL9HO just to verify it’s not the latest version making the crazy things.

By the way: I’m running DXLab suite since end of 2002. At that time Volker DL9HO introduced me into it and I'm a VERY happy camper from that time until today. I encouraged several other OM from our local DARC-chapter to wet their feet with DXLab and no wonder, they are as happy as me.

Tnx for your work!

73
Wolf * DK1IP * DQ1P


Re: Problems with WinWarbler and WIN10

Dave AA6YQ
 

1. you sent your message to

aa5yq (at) ambersoft instead of

aa6yq (at) ambersoft, so I just now received it


2. if your WinWarbler macros are in the file

rtty_dx_hunt.txt

then the command to load them should be

<loadmacrobank: rtty_dx_hunt.txt>

not

<loadmacrobank: rtty_dx_hunt>


3. the current version of WinWarbler is 9.0.6; why are you running version 8.1.1 - which is more than 4 years old?

73,

Dave, AA6YQ


updated eQSL AG and LoTW databases are available ...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


Re: <stop> macro ??

Dave AA6YQ
 

+ AA6YQ comments below

I wouldn't hold my breath waiting for a successful fix for this. It has been around since the beginning with the K3, over 10 years ago now. Elecraft did make firmware changes several years ago to address the situation, but perhaps their efforts may have been only partially successful. It looks as if there may be some kind of race condition in the radio's firmware that causes it to get confused about the TX/RX status of the radio if a PTT command via the rear panel PTT jack arrives while a CAT command to switch PTT is already being processed, and/or vice versa.

There is a simple workaround that applies regardless of which radio control software you are using: don't use two methods of PTT control in parallel. If you are using PTT via CAT command, don't connect anything to the transceiver's PTT input. Conversely, if you are using a hardware PTT signal, e.g. from a SignaLink, don't enable PTT via CAT command in your software.

Incidentally, instead of disabling PTT via CAT in Commander, could you not also achieve the same result by configuring WinWarbler's Configuration window, PTT tab, PTT Mode pane to select None instead of Xcvr Ctrl App? This may be a distinction without a difference...

+ The approach you suggest as the benefit of preventing requests from WinWarbler that Commander will ignore. However, the approach you suggest prevents only WinWarbler from directing Commander to issue RX/TX CAT commands. One could implement both approaches and have the best of both worlds...

73,

Dave, AA6YQ


Re: <stop> macro ??

neil_zampella
 

FWIW ... I'd just use the signalink as a sound card, and use the KXUSB cable to provide CAT control if possible.   I have no problems when just using a simple external USB sound card, the audio cables that came in the KX3-PCKT, and the KXUSB cable.

Neil, KN3ILZ

On 8/27/2018 5:35 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Dave - thanks. That does solve the problem with WinWabler. And not to belabor the point, But I guess what I don't understand with regard to the Elecraft transceivers getting confused. Is why does the KX3 work fine using WSJT_X program and FLDIGI in terms of going to Tx and Rx, and the <start> cmd in WinWabler works fine. So why is only one macro cmd in WW that the PTT isn't working and we have to make the change to suppress the CAT.

+ The difference in behavior among applications is likely the result of differences in timing between CAT instructions being issued and your Signalink's VOX responding to soundcard output. This is unquestionably a defect in the KX3, one that I suspect several Elecraft owners reported years ago when it was first encountered in the K3. The workaround is easy enough; in my opinion, however, holes should be filled the instant they are discovered, lest more users fall into them.

+ As a KX3 and K3 owner, perhaps you can persuade Elecraft to correct this defect.

73,

Dave, AA6YQ






-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.8048 / Virus Database: 4793/15883 - Release Date: 08/14/18




Re: <stop> macro ??

w2eck
 

Dave & Rich- thanks for the explanation and the review of what has transpired in the past. I wasn’t aware of the history on this issue.

73
Paul


Re: <stop> macro ??

ve3ki
 

I wouldn't hold my breath waiting for a successful fix for this. It has been around since the beginning with the K3, over 10 years ago now. Elecraft did make firmware changes several years ago to address the situation, but perhaps their efforts may have been only partially successful. It looks as if there may be some kind of race condition in the radio's firmware that causes it to get confused about the TX/RX status of the radio if a PTT command via the rear panel PTT jack arrives while a CAT command to switch PTT is already being processed, and/or vice versa.

There is a simple workaround that applies regardless of which radio control software you are using: don't use two methods of PTT control in parallel. If you are using PTT via CAT command, don't connect anything to the transceiver's PTT input. Conversely, if you are using a hardware PTT signal, e.g. from a SignaLink, don't enable PTT via CAT command in your software.

Incidentally, instead of disabling PTT via CAT in Commander, could you not also achieve the same result by configuring WinWarbler's Configuration window, PTT tab, PTT Mode pane to select None instead of Xcvr Ctrl App? This may be a distinction without a difference...

73,
Rich VE3KI


On Mon, Aug 27, 2018 at 05:35 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Dave - thanks. That does solve the problem with WinWabler. And not to belabor the point, But I guess what I don't understand with regard to the Elecraft transceivers getting confused. Is why does the KX3 work fine using WSJT_X program and FLDIGI in terms of going to Tx and Rx, and the <start> cmd in WinWabler works fine. So why is only one macro cmd in WW that the PTT isn't working and we have to make the change to suppress the CAT.

+ The difference in behavior among applications is likely the result of differences in timing between CAT instructions being issued and your Signalink's VOX responding to soundcard output. This is unquestionably a defect in the KX3, one that I suspect several Elecraft owners reported years ago when it was first encountered in the K3. The workaround is easy enough; in my opinion, however, holes should be filled the instant they are discovered, lest more users fall into them.

+ As a KX3 and K3 owner, perhaps you can persuade Elecraft to correct this defect.

73,

Dave, AA6YQ


Re: <stop> macro ??

Dave AA6YQ
 

+ AA6YQ comments below

Dave - thanks. That does solve the problem with WinWabler. And not to belabor the point, But I guess what I don't understand with regard to the Elecraft transceivers getting confused. Is why does the KX3 work fine using WSJT_X program and FLDIGI in terms of going to Tx and Rx, and the <start> cmd in WinWabler works fine. So why is only one macro cmd in WW that the PTT isn't working and we have to make the change to suppress the CAT.

+ The difference in behavior among applications is likely the result of differences in timing between CAT instructions being issued and your Signalink's VOX responding to soundcard output. This is unquestionably a defect in the KX3, one that I suspect several Elecraft owners reported years ago when it was first encountered in the K3. The workaround is easy enough; in my opinion, however, holes should be filled the instant they are discovered, lest more users fall into them.

+ As a KX3 and K3 owner, perhaps you can persuade Elecraft to correct this defect.

73,

Dave, AA6YQ


Re: <stop> macro ??

w2eck
 

Dave - thanks. That does solve the problem with WinWabler. And not to belabor the point,  But I guess what I don't understand with regard to the Elecraft transceivers getting confused. Is why does the KX3 work fine using WSJT_X program and FLDIGI in terms of going to Tx and Rx,  and the <start> cmd  in WinWabler works fine. So why is only one macro cmd in WW that the PTT isn't working  and we have to make the change to suppress the CAT.

Tnx & 73
Paul
w2eck


Re: Geochron 4K

Dave AA6YQ
 

+ AA6YQ comments below

For anybody who may be interested I sent an email to Geochron asking about the possibility of displaying ham radio related data from
logging programs on their screen. Here is the reply I received.

It is possible to manually place up to 16 location pins with custom names and local time in the Geochron Digital now, with the
remote. We have plans to add Ham-radio specific options within the next six months, as we update the clock every month. These
updates will be made available to all units already sold, although the update frequency may governed if provided without charge.

Sounds promising.

+ After every entry on every DXLab application's Enhancement list has been implemented, I'll consider it. See the "Enhancement Logs"
column in

<https://www.dxlabsuite.com/download.htm#AvailableReleases>

+ Hint: "conversation piece", "decorative item", and "eye candy" are the kiss of death for development priority. It's not that I
don't appreciate good art, there's just too much useful functionality yet to be implemented.

73,

Dave, AA6YQ


Geochron 4K

Julio Peralta
 

For anybody who may be interested I sent an email to Geochron asking about the possibility of displaying ham radio related data from logging programs on their screen. Here is the reply I received.

 

It is possible to manually place up to 16 location pins with custom names and local time in the Geochron Digital now, with the remote.   We have plans to add Ham-radio specific options within the next six months, as we update the clock every month.   These updates will be made available to all units already sold, although the update frequency may governed if provided without charge.

 

Sounds promising.

 

Julio, W4HY

 

29821 - 29840 of 209531