Date   

Re: Commander PTT Sluggish with JT65-HF

Stephen Rabinowitz
 

Well, Rich, I recall the good old days, when DDE was the President.
73 Steve WA2DFP


Sent via the Samsung Galaxy Note® II, an AT&T 4G LTE smartphone



-------- Original message --------
From: Rich - W3ZJ <rich@...>
Date: 01/20/2014 6:04 PM (GMT-05:00)
To: dxlab@...
Subject: Re: [dxlab] RE: Commander PTT Sluggish with JT65-HF


 

Unfortunately, it has to do with DDE which is an outdated technology
that still works (if you use it right) but is no longer supported by the
folks in Washington.

73, Rich - W3ZJ

Stephen Rabinowitz MD wrote:
> You were right on the money. My DXLab Launcher was running as
> administrator and WSJT-X was not. Once all programs were running at a
> humbler status the communications began to to flow. Seems like the
> folks in Washington should be introduced to this concept. Many thanks.
> 73 Steve WA2DFPby the


Re: Commander PTT Sluggish with JT65-HF

Richard B Drake
 

Unfortunately, it has to do with DDE which is an outdated technology that still works (if you use it right) but is no longer supported by the folks in Washington.

73, Rich - W3ZJ

Stephen Rabinowitz MD wrote:

You were right on the money. My DXLab Launcher was running as administrator and WSJT-X was not. Once all programs were running at a humbler status the communications began to to flow. Seems like the folks in Washington should be introduced to this concept. Many thanks.
73 Steve WA2DFPby the


Re: Commander PTT Sluggish with JT65-HF

Stephen Rabinowitz
 

You were right on the money.  My DXLab Launcher was running as administrator and WSJT-X was not. Once all programs were running at a humbler status the communications began to to flow.  Seems like the folks in Washington should be introduced to this concept.  Many thanks.
73 Steve WA2DFP


Sent via the Samsung Galaxy Note® II, an AT&T 4G LTE smartphone



-------- Original message --------
From: Dave AA6YQ <aa6yq@...>
Date: 01/20/2014 4:04 PM (GMT-05:00)
To: dxlab@...
Subject: RE: [dxlab] RE: Commander PTT Sluggish with JT65-HF


 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On Behalf Of Joe Subich, W4TV
Sent: Monday, January 20, 2014 2:55 PM
To: dxlab@...
Subject: Re: [dxlab] RE: Commander PTT Sluggish with JT65-HF

The connection to other members of the DXLab Suite is handled by JT-Alert. No application - either DXLab Suite or JT-Alert may be
run with elevated privileges ("run as administrator"). DDE works only between "peers".

>>>Explanation: either all communicating applications must be started with "Run as Administrator", or none them can be started with
"Run as Administrator".

>>>So long as you didn't install your applications in a folder that Windows considers "protected" -- like c:/program files or
c:/program files (x86) -- there is no need to initiate your applications with "Run as Administrator".

>>>By default, the Launcher installs all DXLab applications in the non-protected folder c:/dxlab

73,

Dave, AA6YQ


FW: logging in to your LoTW account

Dave AA6YQ
 

-----Original Message-----
From: Dave AA6YQ [mailto:aa6yq@...]
Sent: Monday, January 20, 2014 5:08 PM
To: ARRL-LOTW@...
Cc: lotw-devel@...; Dave AA6YQ
Subject: logging in to your LoTW account

Executive Summary
===============

For more reliable access to your LoTW account, log in via this URL:

<https://lotw.arrl.org/lotwuser/default>


Technical Details
=============

The LoTW Server, which processes incoming QSOs and generates the web pages you see when you log in to your LotW account, is
accessible via lotw.arrl.org .

p1k.arrl.org provides a proxy connection to lotw.arrl.org . The server that hosts p1k.arrl.org employs older hardware that hosts
multiple infrastructure functions, and is thus more likely to be impacted by congestion on the ARRL's headquarters network. This
p1k.arrl.org proxy connection is being maintained because several logging applications still use it.

It's been noted that clicking the "Go Now" or "Login Now" links in

<http://www.arrl.org/logbook-of-the-world>

reference the less reliable p1k.arrl.org instead of lotw.arrl.org. Until this is corrected, avoid these links, and log in to your
LoTW account via

<https://lotw.arrl.org/lotwuser/default>

73,

Dave, AA6YQ


Re: Commander PTT Sluggish with JT65-HF

Dave AA6YQ
 

Parker, the errorlog.txt file you sent me does not show any instance where you

1. enabled Commander's "log debugging info" option

2. performed an action in JT65-HF that cause JT65-HF do direct Commander to switch the transceiver from RX to TX

3. disabled "log debugging info"

Thus the errorlog.txt file does not provide the trace of activities I need to see to determine what's going on.

However, one of the screen shots you sent shows that you have Commander's "verify CI-V acceptance" option enabled. This option is
intended for use in environments where multiple devices are connected to the CI-V bus in a way that permits collisions to occur.
When sending a CI-V command to a transceiver, Commander waits for a positive acknowledgement from the transceiver before proceeding
-- which if the transceiver's microprocessor is not responsive can cause things to slow down. If you have your PC connected to your
IC-7600 via the USB interface with nothing else connected to the IC-7600's backpanel CI-V port, then no collisions are possible, and
you should disable the "verify CI-V acceptance" option.

Disabling "verify CI-V acceptance" may not eliminate the delay you've been reporting, but it will reduce the number of variables
in the equation. If the delays remain, please perform the 3 steps above and send me the resulting errorlog.txt file from your
Commander folder.

Thanks.

73,

Dave, AA6YQ

-----Original Message-----
From: Parker Dinkins [mailto:parker@...]
Sent: Monday, January 20, 2014 9:28 AM
To: Dave AA6YQ
Subject: Re: [dxlab] Commander PTT Sluggish with JT65-HF

Dave -

I am attaching ErrorLog.Txt and various screen grabs, which should be self-explanatory. The ErrorLog.txt shows no activity in
connection with this issue.

Apparently HRD uses TCP/IP, just FWIW.

Correction: this issue does not appear with the current version of WSJT-X.

--
73 Parker W5ADD

PS - If this is a software issue in JT65-HF, then I'll just raise the priority in Windows Task Manager so I can continue using
DXLab. Many thanks for your help.


Re: R: Card Aging Report Question

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On Behalf Of Larry Bryan
Sent: Monday, January 20, 2014 12:09 PM
To: dxlab@...
Subject: Re: R: [dxlab] Card Aging Report Question

Hi Dave,

So if I understand your response, the information I provided in my email is just summery info for all the cards on the report. For
example I have 16 cards for DXCC entities that have not been worked before. I have 96 cards that have bands that have not been
worked before in a given DXCC entity and so on. If I'm correct, it was the word "missing" that was throwing me, thinking some
information was missing on the contact. I understood the "Need" column, it was the summery stuff that was confusing me as stated
above.

The word "missing" refers to QSLs that have been requested but not received. It does not refer to information "left out" of a
logged QSO.

It would be easy to substitute a different word or phrase that would improve the Card Aging Report's clarity. "Unrequited" comes
to mind...

73,

Dave, AA6YQ


Re: Commander PTT Sluggish with JT65-HF

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On Behalf Of Joe Subich, W4TV
Sent: Monday, January 20, 2014 2:55 PM
To: dxlab@...
Subject: Re: [dxlab] RE: Commander PTT Sluggish with JT65-HF


The connection to other members of the DXLab Suite is handled by JT-Alert. No application - either DXLab Suite or JT-Alert may be
run with elevated privileges ("run as administrator"). DDE works only between "peers".

Explanation: either all communicating applications must be started with "Run as Administrator", or none them can be started with
"Run as Administrator".

So long as you didn't install your applications in a folder that Windows considers "protected" -- like c:/program files or
c:/program files (x86) -- there is no need to initiate your applications with "Run as Administrator".

By default, the Launcher installs all DXLab applications in the non-protected folder c:/dxlab
73,

Dave, AA6YQ


Re: Commander PTT Sluggish with JT65-HF

Joe Subich, W4TV
 

The connection to other members of the DXLab Suite is handled by
JT-Alert. No application - either DXLab Suite or JT-Alert may be
run with elevated privileges ("run as administrator"). DDE works
only between "peers".

If you have questions about JT-Alert, contact Laurie VK3AMA (via
the support page in JT-ALert - send him the session files from
JT-Alert so he can diagnose your problems).

73,

... Joe, W4TV

On 1/20/2014 12:10 PM, Stephen Rabinowitz wrote:
Joe,

I am using WSJT-X v1.1, r3496 with JTAlert-X 2.4.13 and the DXLab Suite.
The TCP connection to Commander works well, but the connection to the other
members of the suite, which I think is supposed to be by DDE, does not work.
I tested this with DXLabTest 1.3.2 and got the same result. Can you please
tell me what I am missing here? There are too many moving parts for this
old head to track.

73, Steve WA2DFP





From: dxlab@... [mailto:dxlab@...] On Behalf Of Joe
Subich, W4TV
Sent: Sunday, January 19, 2014 2:26 PM
To: dxlab@...
Subject: Re: [dxlab] RE: Commander PTT Sluggish with JT65-HF






I have had no problem using Commander for CAT/PTT with WSJT-X
or for PTT only with Joe Large's no longer supported JT65HF.
However, since I prefer hardware PTT ever since I lost a rig
due to a hung software PTT several years ago, I generally used
a separate serial port for JT65-HF (and use hardware PTT from
Commander).

73,

... Joe, W4TV

On 1/19/2014 1:21 PM, parker@... wrote:
-- Have you tried WSJT-X?

Yes, no difference.

And I am not a fan of WSJT-X yet.

--
Parker W5ADD



Re: Needed not updating in Spotcollector Need column

Dave AA6YQ
 

OK. Please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "log debugging info" box

2. the next time you log a QSO but the relevant Spot Database Entry is not updated

2a. on the General tab of DXKeeper's Configuration window, uncheck the "log debugging info" box

2b. create an email message that describes the QSO you logged (call, band, mode), and the change you expected in the Spot Database Display that did not occur

2c. attach the errorlog.txt file from your DXKeeper folder to that email message

2d. send the email message to me via aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On Behalf Of k6xt@...
Sent: Monday, January 20, 2014 11:00 AM
To: dxlab@...
Subject: [dxlab] RE: Needed not updating in Spotcollector Need column

Tnx Dave - its been thru several reboots in the past few weeks.

73 Art


Re: Spotcollector QSY not working

Dave AA6YQ
 

Not having its power supply enabled could also cause a CI-V interface to receive but not send signals.


       73,


          Dave, AA6YQ


R: R: Card Aging Report Question

Carlo Bonomi <ik2rpe@...>
 

Hi Larry,

 

Sorry, I misunderstood.

I thought, erroneously, that the issue was referred to “Add NEEDED” Cards in the pane “QSL”.

In “Card Aging” report of the pane “Check Progress” everything is fine.

 

Forgive me, please

 

‘73 de  Carlo  IK2RPE

 


Da: dxlab@... [mailto:dxlab@...] Per conto di Larry Bryan
Inviato: lunedì 20 gennaio 2014 16:44
A: dxlab@...
Oggetto: Re: R: [dxlab] Card Aging Report Question

 

 

Carlo,

 

The "Need" column should be the last column to the right on your card aging report you don't need to add it. On mine before I added the QSL_sent_via column, the Expired and Need headings were very close together and looked like one heading but they are two separate headings.

73

Larry - W8LIG

Nessun virus nel messaggio.
Controllato da AVG - www.avg.com
Versione: 2014.0.4259 / Database dei virus: 3681/7017 - Data di rilascio: 20/01/2014


Re: Commander PTT Sluggish with JT65-HF

Stephen Rabinowitz
 

Joe,

I am using WSJT-X v1.1, r3496 with JTAlert-X 2.4.13 and the DXLab Suite.  The TCP connection to Commander works well, but the connection to the other members of the suite, which I think is supposed to be by DDE, does not work.  I tested this with DXLabTest 1.3.2 and got the same result.  Can you please tell me what I am missing here?  There are too many moving parts for this old head to track.

73, Steve  WA2DFP

 

 

From: dxlab@... [mailto:dxlab@...] On Behalf Of Joe Subich, W4TV
Sent: Sunday, January 19, 2014 2:26 PM
To: dxlab@...
Subject: Re: [dxlab] RE: Commander PTT Sluggish with JT65-HF

 

 


I have had no problem using Commander for CAT/PTT with WSJT-X
or for PTT only with Joe Large's no longer supported JT65HF.
However, since I prefer hardware PTT ever since I lost a rig
due to a hung software PTT several years ago, I generally used
a separate serial port for JT65-HF (and use hardware PTT from
Commander).

73,

... Joe, W4TV

On 1/19/2014 1:21 PM, parker@... wrote:
> -- Have you tried WSJT-X?
>
> Yes, no difference.
>
> And I am not a fan of WSJT-X yet.
>
> --
> Parker W5ADD
>


Re: R: Card Aging Report Question

Larry Bryan
 

Hi Dave,

So if I understand your response, the information I provided in my email is just summery info for all the cards on the report. For example I have 16 cards for DXCC entities that have not been worked before. I have 96 cards that have bands that have not been worked before in a given DXCC entity and so on. If I'm correct, it was the word "missing" that was throwing me, thinking some information was missing on the contact. I understood the "Need" column, it was the summery stuff that was confusing me as stated above.


73
Larry - W8LIG


Re: Another question about WinWarbler and RTTY

Duncan Campbell
 

DAVE:


>>>If you have Commander running, then the "Xcvr Freq" panel in the upper-right corner of WinWarbler's Main window should match the frequency displayed in the VFO panel of DXKeeper's Main window. Is this the case?

>>>In what panel of what window do you see the frequency "off by a factor of 10"


+++ It is the Xcvr panel that the frequencies do not match the radio, But ONLY when I am using RTTY (transmitting)..  Before I start, the frequencies are correct, and if I wait a min or so after the QSO then they stable out to the correct freqs.  However when I am sending,  They are off by 10%.  Looks like an RF issue now.   



>>>In the "Operating Mode Selection" panel on the General tab of WinWarbler's Configuration window, clear all of the "Operating Mode" selectors.

+++ Done: thank you!  The CW is now staying put.


Again Thank you for a great program and great support.


73 

Duncan, KF6ILA


Re: Spotcollector QSY not working

David <k4zzr@...>
 

Dave.....I think you’re right.   I’ve been using a K1NU CI-V interface for years, but didn’t replace it after the lightning strike because I thought it was still good because both DXLab Commander and the Steppir controller were receiving signals.   I’m guessing now that the interface was actually damaged too, and not sending signals to back to the radio.   I’ll replace it. 
 
73,
David, K4ZZR


Re: Needed not updating in Spotcollector Need column

k6xt@...
 

Tnx Dave - its been thru several reboots in the past few weeks.


73 Art


Re: R: Card Aging Report Question

Larry Bryan
 

Carlo,

The "Need" column should be the last column to the right on your card aging report you don't need to add it. On mine before I added the QSL_sent_via column, the Expired and Need headings were very close together and looked like one heading but they are two separate headings.
73
Larry - W8LIG


R: Card Aging Report Question

Carlo Bonomi <ik2rpe@...>
 

I do not see the “Need” column at the right-most of the screen.

What I missed? Where to command to have such a column as well?

 

Thanks

 

Carlo  IK2RPE

 


Da: dxlab@... [mailto:dxlab@...] Per conto di Dave AA6YQ
Inviato: lunedì 20 gennaio 2014 06:32
A: dxlab@...
Oggetto: RE: [dxlab] Card Aging Report Question

 

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...] On Behalf Of Larry Bryan
Sent: Sunday, January 19, 2014 2:06 PM
To: dxlab@...
Subject: [dxlab] Card Aging Report Question

I was going to ask about adding a column to this report, when I discovered while reading the help files that there is a way to do
that. I wanted to know what method was used to send the QSL card at a glance. So I was able to add that to my report. Wonderful
feature.

I have looked for the answer to this question without success. Below is the beginning of my recent card aging report. I would like
to know what each of these items mean or their intended purpose. I don't see any indication on the report that would tell me which
entry is missing what.

Then I thought maybe I could add that field to the report and that would show me, but these fields do not exist that I can see. So
if this information is important enough to be on the report, I would like to understand what it is and what I need to do about it if
anything.

missing DXCC entities: 16
missing DXCC entity-bands: 96
missing DXCC entity-modes: 45
missing IOTA groups: 34
missing WAZ zones: 0
missing WAZ zone-bands: 5
missing WAZ zone-modes: 3

>>>The right-most column of the report is "Need"; for each QSO listed, the "Need" column indicates whether the missing confirmation
is needed for (in your case) DXCC, IOTA, and/or WAZ.

73,

Dave, AA6YQ

Nessun virus nel messaggio.
Controllato da AVG - www.avg.com
Versione: 2014.0.4259 / Database dei virus: 3681/7016 - Data di rilascio: 19/01/2014


updated eQSL AG and LotW databases are available...

Dave AA6YQ
 

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

73,

Dave, AA6YQ


DXCC Database version 2.4.8 is available...

Dave AA6YQ
 

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

Joe W4TV has included the following updates in this version:

* update the prefixes and callsigns recognized as being in the Shetland Islands

* recognize Olympic callsigns with known locations

* apply minor fixes and changes to prefixes recognized as being in European Russia

* correct the time zone for Canada's province of Alberta


To upgrade to DXCC Database 2.4.8

1. if you have DXKeeper, SpotCollector, and/or WinWarbler running, terminate them

2. start DXView, open its Configuration window, and select its Databases tab

2a. click the New? button

2b. click the DXCC Database's Upgrade button

2c. terminate and restart DXView

Thanks, Joe!

73,

Dave, AA6YQ

81261 - 81280 of 211137