Date   

Re: DXlabs Commander and icom7610....slow response to test CAT and TX commands

g4wjs
 

On 15/03/2021 22:09, w6de wrote:

Fred, the recommended approach by the WSJTX developers is to use “Fake it.”  Otherwise, you will eventually find that using split on Icom rigs does not work well on WSJTX.

 

73,

Dave, w6de

Dave,

that's news to me.

73
Bill
G4WJS.


--
73

Bill

G4WJS.


Re: DXlabs Commander and icom7610....slow response to test CAT and TX commands

w6de
 

Fred, the recommended approach by the WSJTX developers is to use “Fake it.”  Otherwise, you will eventually find that using split on Icom rigs does not work well on WSJTX.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Fred Roberts
Sent: Monday, March 15, 2021 00:45
To: DXLab@groups.io
Subject: [DXLab] DXlabs Commander and icom7610....slow response to test CAT and TX commands

 

Hello to the group again. New to DXlabs, I've been learning about DXkeeper most of the day from my Elmer, who has a lot of experience with the programs. When operating ft8, I use WSJT-x - the Radio tab on it is now set to DXlabs - and I noticed that the TestCat button took 4 or 5 seconds to turn green. I had a test QSO with my Elmer and there were no problems, but I noticed that the rig did not immediately go into xmit at the start of the 15 second cycle, but instead started about 3 seconds into the cycle. Also, when I activate the Tune button in WSJT-x, it takes the rig about 3 seconds to go into XMIT. Looking closely at the rig, when I press Tune on WSJT-x, it appears that VFO B is selected and then queried. Then the mode is set to USB-D1 (even if it is already there), then VFO A is selected, and then the XMIT command is sent to VFO B. The rig is in Split mode. Is there a way to speed the process up? Should I use 'Fake it' instead of split mode?

Thanks for the great support on the questions I had earlier.

73,

Fred

WB4QOC

 

 

 

Sent from my phone.....Fred

 

On Sun, Mar 14, 2021, 8:13 PM Fred Roberts via groups.io <fred5352=gmail.com@groups.io> wrote:

Dave....

      Thank you for your quick reply....again....I apologize for not getting back to you sooner.....sometimes my 10 year old grandson can get a bit demanding. He is going back to 'Real School' starting tomorrow.

      Thank you for the my QTH fix. No problems now.

Fred

WB4QOC

 

 

Sent from my phone.....Fred

 

On Sat, Mar 13, 2021, 7:41 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

Yes. All of them made from the same call, but some of them were made from a different grid square.

+  You should define a myQTH for each physical location from which you made QSOs -- independent of the callsign you employed over the air. I suggest using a town name or county name as the myQTH ID. Let me know when you have your two myQTHs defined, and we'll proceed to the next step, which is updating your logged QSOs to reflect the correct myQTH ID

Is that where the problem lies?

+ The flashing myQTH ID label is DXKeeper pointing out that you had not specified a myQTH ID in that QSO. We'll be taking care of that.

        73,

              Dave, AA6YQ


Re: Unable to Complete DXLabs Installation

Dave AA6YQ
 

+ AA6YQ comments below

When trying to install the DXLab suite of software on one of my computers, I encountered an install abort message on some of the modules during the process. I was able to install "Launcher","Commander" and "DXKeeper" just fine, but when I tried to install "DXView" I got the following message: "unable to install in specified folder because Pathfinder is already installed in that folder". When I tried to install Pathfinder the message changed to: "unable to install Pathfinder in specified folder because DXView is already installed in that folder"
and so on with each of the other modules that I tried to install. I checked my DXLab folder where the programs reside and do not see any other folders in there, except the ones that had been installed, Launcher, DXKeeper and DXView. I'm baffled as to why the install program thinks the modules have already been installed and will not allow me to proceed with the installation. I did start the Commander and DXKeeper modules and they seem to be working correctly.

+ By default, the Launcher installs each DXLab application in a separate sub-folder of the "root folder"

C:\DXLab

+ e.g. C:\DXLab\DXView, C:\DXLab\DXKeeper, C:\DXLab\WinWarbler

+ You can change the "root folder" to another location, but if you attempt to install more than one DXLab application into the same sub-folder, the Launcher will refuse. On the Launcher's Configuration window's "DXLab Apps" tab, each application's "Program Path" shows where the Launcher thinks you want each uninstalled application installed, and where each installed application has been installed. If this information doesn't enable you to proceed, then please make a screen shot showing the Launcher's Configuration window's "DXLab Apps" tab, attach the screenshot to an email message, and send the email message to me via

aa6yq (at) ambersoft.com


Is there a possible issue with my "Registry" getting trashed?

+ No.

73,

Dave, AA6YQ


Re: Asterisk on IOTA Progress Report

Dave AA6YQ
 

+ AA6YQ comments below

Under LotW Cfm there are asterisks next to some of the Y entries. What does that mean? I can't find a reference in the
documentation.

+ *Y in the report's LoTW Cfm column means that the QSO's IOTA item exactly matches the IOTA designator submitted by your QSO
partner to LoTW.

+ I have updated the reference documentation to reflect this:

https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#AP%20IOTA

+ Thanks, Bob!

73,

Dave, AA6YQ


Unable to Complete DXLabs Installation

Henry Boze
 

When trying to install the DXLab suite of software on one of my computers, I encountered an
install abort message on some of the modules during the process.  I was able to install
"Launcher","Commander" and "DXKeeper" just fine, but when I tried to install "DXView" I got
the following message: "unable to install in specified folder because Pathfinder is already
installed in that folder". When I tried to install Pathfinder the message changed to: "unable
to install Pathfinder in specified folder because DXView is already installed in that folder"
and so on with each of the other modules that I tried to install. I checked my DXLab folder
where the programs reside and do not see any other folders in there, except the ones that had
been installed, Launcher, DXKeeper and DXView. I'm baffled as to why the install program
thinks the modules have already been installed and will not allow me to proceed with
the installation. I did start the Commander and DXKeeper modules and they seem to be working
correctly. Is there a possible issue with my "Registry" getting trashed? 

Thanks for any help with this issue!

Henry Boze, N4HB



Re: Audio Recording problem

Panagiotis Klimis
 

I think Joe is right,but I wonder why don't you use the internal sound card which your FTDX3000 is equipped with. Just plug the USB cable and there it is, no level matching, no worries.

Panos, SV8PMM 


Re: DXlabs Commander and icom7610....slow response to test CAT and TX commands

Fred Roberts
 

Excellent!!!!

Sent from my phone.....Fred

On Mon, Mar 15, 2021, 1:52 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Now, can we PLEASE get some sunspots.....

+ Working on it:

http://www.dxlabsuite.com/propview/SolControl.jpg

       73,

               Dave, AA6YQ








Asterisk on IOTA Progress Report

 

Under LotW Cfm there are asterisks next to some of the Y entries.  What does that mean?  I can’t find a reference in the documentation. 

 

Bob AF9W

 


Re: Marking a QSO as made on a net

Mike Wasserburger - WF0M
 

This worked perfectly!  Thanks for the suggestion.  I went with the "list" style type and have options for all kinds of nets to record in a QSO now.

THANKS!

Mike / WF0M

Virus-free. www.avg.com


On Sun, Mar 14, 2021 at 8:12 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

  I was wondering what the best DXKeeper practice is for marking a QSO as having occurred on a particular net.  For example, to get WAS for the OMISS net, the QSO have to have taken place on one if their nets.  What is the best way to indicate that such that I could filter on it when exporting a ADIF file for WAS verification?

+ I suggest setting up a user-defined item to capture the Net on which the QSO was made, as described in

https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#User%20Items%20tab

+ You could, for example, configure the first user-defined item with a Caption of Net and Alphanumeric style. If you type OMISS into the Net item of each QSO you log when participating in the OMISS net, then you can later filter the Log Page Display with the SQL expression

APP_DXKEEPER_USER_DEFINED_0 = 'OMISS'

+ to see all logged QSOs made while participating in that Net. Directing DXKeeper to generate a WAS progress report would show you're doing on "WAS for the OMISS net".

+ However, if you type OLEMISS instead of OMISS into a QSO's Net item, it won't appear when you filter the Log Page Display as described above. Thus would be better to configure the Net user-defined item to employ a "list" style. This enables you to populate a text file with legal values; when logging a QSO, you can select a legal Net value from a selector (rather than typing it in).

+ Note that you can specify a default value for the Net item. Just before the OMISS net convenes, set this to OMISS; when the net terminates, clear it. All QSOs made while the Omiss net is in progress will thus be logged with the correct Net item.

          73,

                Dave, AA6YQ








Re: Using Commander with SatPC32

Dave AA6YQ
 

+ AA6YQ comments below

Try as I may, I can't get SatPC32 to talk to Commander ... see screenshot.

+ Attachments are not conveyed by this group.

I re-started both Commander then SatPC32 ... no error ... just that Pressing "Connect" has no effect.

I searched for an address setting for the DDE to SatPC32 but never found one.

+ Have you stepped through the instructions in " Interoperating with the SatPC32 Satellite Tracking Application"?

https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking

73,

Dave, AA6YQ


Re: Unable to launch DXK 16.0.7

Dave AA6YQ
 

DXK worked yesterday 3-14-2021 (a bit slow). Today 3-15-2021 "unable to launch after 180 seconds).
I have not tried anything to to "fix" the situation. All other DXLabs components launch fine.

+ If you're running Windows Defender Antivirus, did implement the recommendation given in the first sentence of the release note:

https://www.dxlabsuite.com/dxkeeper/ReleaseNotes/1607.txt

?

73,

Dave, AA6YQ


Re: DXlabs Commander and icom7610....slow response to test CAT and TX commands

Dave AA6YQ
 

+ AA6YQ comments below

Now, can we PLEASE get some sunspots.....

+ Working on it:

http://www.dxlabsuite.com/propview/SolControl.jpg

73,

Dave, AA6YQ


Unable to launch DXK 16.0.7

WH
 

DXK worked yesterday 3-14-2021 (a bit slow). Today 3-15-2021 "unable to launch after 180 seconds).
I have not tried anything to to "fix" the situation. All other DXLabs components launch fine.
Bill, N9CDX 


Re: Audio Recording problem

Joe Subich, W4TV
 

The "Line" jack on the FTdx3000 is non-standard ... it is *MONO* out
and in - not a stereo input or output as would be expected based on
the three conductor jack. It is also rated for 300 mV p-p at 10K
Ohms.

1) you need a three conductor jack on each end of the cable with
*only* tip to tip and sleeve to sleeve connections.

2) the audio level is *much too high* for a mic input. Put a 10K
resistor in series with the tip to tip connection and a 1K from
tip to sleeve on the computer end of the cable.

3) If your computer places 3.3V - 5V on the mic or line jack (bias
for a microphone), put a 1uF to 10uF capacitor in series with
the tip to prevent the bias voltage from upsetting the audio
output circuit in the FTdx3000.

73,

... Joe, W4TV

On 2021-03-14 11:01 PM, Marv Stasak wrote:
DXKeeper has what I think is an elegant recording feature with its ability to record a QSO automatically and store it using the contact's call sign in the file name.  Unfortunately, for some reason, I can't get a decent recording. The audio is distorted and the volume is always too low. *I know this is not a problem caused by DXLab but something I'm doing or not doing*.  The rig is an FTDX3000. I'm running from the line out on the radio to the computer using a  shielded cable with 3.5mm stereo jacks.I have 2 inputs in the computer, 1 a mono plug, the other a stereo.L & R input.  Whichever I use doesn't make any difference, I get the same low volume, distorted playback results. I am using Audacity for playback but the Windows playback feature gives me the same results.  If I hook up a digital recorder to the shielded cable, the results are fine so it's something in how I've set up the sound card settings on the computer but I can't imagine what it could be. It should be simple but it is not proving to be so. Yaesu does not supply anything more than the line-out feature; No volume controls or anything.  I am looking for suggestions.
Marv, W5DT
the .


Re: Audio Recording problem

Fred Roberts
 

I may be way off base, but I ran into a similar problem occaisonly in my broadcast career....the level coming from your rig is line level (+/- 0db) and your computer input is looking for microphone level. The attenuator on your computer will not be able to compensate for that much difference in levels. You will need a pad, or find some way to feed a line level signal into your computer. BTW, this would dovetail into Dave's suggestion of connecting powered speakers to the line output of your rig and seeing how that sounded....hope this helps.
Fred
WB4QOC



Sent from my phone.....Fred


On Mon, Mar 15, 2021, 1:51 AM Dave AA6YQ <aa6yq@...> wrote:
DXKeeper has what I think is an elegant recording feature with its ability to record a QSO automatically and store it using the contact's call sign in the file name.  Unfortunately, for some reason, I can't get a decent recording. The audio is distorted and the volume is always too low.  I know this is not a problem caused by DXLab but something I'm doing or not doing.  The rig is an FTDX3000. I'm running from the line out on the radio to the computer using a  shielded cable with 3.5mm stereo jacks.I have 2 inputs in the computer, 1 a mono plug, the other a stereo.L & R input.  Whichever I use doesn't make any difference, I get the same low volume, distorted playback results. I am using Audacity for playback but the Windows playback feature gives me the same results.  If I hook up a digital recorder to the shielded cable, the results are fine so it's something in how I've set up the sound card settings on the computer but I can't imagine what it could be. It should be simple but it is not proving to be so. Yaesu does not supply anything more than the line-out feature; No volume controls or anything.  I am looking for suggestions.

+ Connect a pair of powered speakers to the FTDX3000's line output. How does it sound?

     73,

              Dave, AA6YQ








Re: DXlabs Commander and icom7610....slow response to test CAT and TX commands

Fred Roberts
 

Dave....
       That did it! Thank you. Now, can we PLEASE get some sunspots.....
73,
Fred
WB4QOC



Sent from my phone.....Fred


On Sun, Mar 14, 2021, 9:07 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Hello to the group again. New to DXlabs, I've been learning about DXkeeper most of the day from my Elmer, who has a lot of experience with the programs. When operating ft8, I use WSJT-x - the Radio tab on it is now set to DXlabs - and I noticed that the TestCat button took 4 or 5 seconds to turn green. I had a test QSO with my Elmer and there were no problems, but I noticed that the rig did not immediately go into xmit at the start of the 15 second cycle, but instead started about 3 seconds into the cycle. Also, when I activate the Tune button in WSJT-x, it takes the rig about 3 seconds to go into XMIT. Looking closely at the rig, when I press Tune on WSJT-x, it appears that VFO B is selected and then queried. Then the mode is set to USB-D1 (even if it is already there), then VFO A is selected, and then the XMIT command is sent to VFO B. The rig is in Split mode. Is there a way to speed the process up? Should I use 'Fake it' instead of split mode?

+ As a first step, in the Radio panel on the General tab of Commander's Configuration window, set the "Command interval" to 25.

+ Any change in behavior?

      73,

              Dave, AA6YQ








Using Commander with SatPC32

KD7YZ Bob
 

Try as I may, I can't get SatPC32 to talk to Commander ... see screenshot.

I re-started both Commander then SatPC32 ... no error ... just that
Pressing "Connect" has no effect.

I searched for an address setting for the DDE to SatPC32 but never found
one.

--
--
73
Bob KD7YZ


Re: N1MM ,DXLab, Gateway.

Dave AA6YQ
 

# more AA6YQ comments below

Thanks a lot for the clarification.
I found a bug where QSO was not logged in DXKeeper - wrong port number.

# Nice work, Yuri!

73,

Dave, AA6YQ


@ more AA6YQ comments below

Linkage N1MM-DXKeeper Gateway.
When registering QSOs in the N1MM journal, the registration in the DXKeeper journal does not occur.
Configured the ports (added the IPv4 address of the computer) in the N1MM Broadcast panel, added N1MM Logger ini to the configuration. changes according to the manual N1MM-DXKeeper Gateway Online Help.
Gateway: DXKeeper, DXView, Pathfinder - the status is "connected", at the bottom there is a red inscription "see Errorl log". The file with errors is attached.
Please help me find the reason in the setting.

@ Thanks for sending me your errorlog.txt file. The gateway is generating an errorlog.txt file because you have its "Log debugging info" box checked - not because any program errors are occurring. You should uncheck this box.

@ The errorlog shows that you have been successfully logging QSOs from N1MM to DXKeeper, for example on 2021-03-10 starting at 1524Z when you logged 5 QSOs within 30 minutes, and most recently today at 0617Z with RK3ZI on 20m SSB.


Re: ADIF import for Rovers

Dave AA6YQ
 

@ AA6YQ comments below

+ At present, DXKeeper ignores the MY_GRIDSQUARE, MY_CNTY, MY_STATE, and MY_COUNTRY ADIF fields.

When I switched to DXLab earlier this year I imported thousands of state QSO party QSOs from hundreds of different counties creating a myQTH ID for each county. I used a bulk search and replace program where I searched for the MY_CNTY tag that had the county abbreviation and replaced it with a string of ADIF tags. Here's an example from the Texas QSO Party:

Search for <MY_CNTY:4>ANDR
Replace with <NOTES:16>TQP from Andrews<MY_STATE:2>TX<MY_CNTY:10>TX,Andrews<App_DXKeeper_My_QTHID:11>TQP-Andrews

So, DXKeeper DOES read the MY_CNTY and MY_STATE ADIF tags.

After importing my QSO party logs using the above method I ended up with close to 300 myQTH IDs.


@ Here's what the current version of DXKeeper does with MY_fields in imported ADIF files:

"When an imported ADIF record contains an APP_DXKEEPER_MY_QTHID tag, the associated myQTH ID is placed in the imported QSO's myQTH ID item. If the log contains no QTH definition that specifies the imported myQTH ID, then a new QTH definition is created, and assigned this myQTH ID. If the imported ADIF record contains any of the following ADIF 2.0 tags, their associated data is used to populated the newly-created QTH definition: MY_CITY, MY_CNTY, MY_COUNTRY, MY_CQZONE, MY_GRIDSQUARE, MY_IOTA, MY_ITUZONE, MY_LAT, MY_LON, MY_POSTAL_CODE, MY_STATE, and MY_STREET."

https://www.dxlabsuite.com/dxkeeper/Help/Import.htm


@ Thus most of what I proposed implementing in

https://groups.io/g/DXLab/message/200409

@ is in fact already implemented. All that's needed is to provide the option to handle an ADIF record with no APP_DXKEEPER_MY_QTHID tag by optionally fabricating a "my QTH ID" from the content of MY_GRIDSQUARE.



+ 1. look for an already-defined "my QTH" consistent with the contents of the record's MY_GRIDSQUARE, MY_CNTY, MY_STATE, and MY_COUNTRY ADIF fields

I think for a VHF rover the county is probably not going to be logged. For a state QSO party the grid square is not going to be logged. So requiring MY_GRIDSQUARE AND MY_CNTY may not be a good solution.

@ I'll have to work through call of the permutations, but I suspect there's a reasonable way to handle every scenario with either MY_GRIDSQUARE specified, or MY_COUNTRY and one of MY_STATE or MY_CNTY specified.

@ Thanks, Alan!

73,

Dave, AA6YQ


Re: Audio Recording problem

Dave AA6YQ
 

DXKeeper has what I think is an elegant recording feature with its ability to record a QSO automatically and store it using the contact's call sign in the file name. Unfortunately, for some reason, I can't get a decent recording. The audio is distorted and the volume is always too low. I know this is not a problem caused by DXLab but something I'm doing or not doing. The rig is an FTDX3000. I'm running from the line out on the radio to the computer using a shielded cable with 3.5mm stereo jacks.I have 2 inputs in the computer, 1 a mono plug, the other a stereo.L & R input. Whichever I use doesn't make any difference, I get the same low volume, distorted playback results. I am using Audacity for playback but the Windows playback feature gives me the same results. If I hook up a digital recorder to the shielded cable, the results are fine so it's something in how I've set up the sound card settings on the computer but I can't imagine what it could be. It should be simple but it is not proving to be so. Yaesu does not supply anything more than the line-out feature; No volume controls or anything. I am looking for suggestions.

+ Connect a pair of powered speakers to the FTDX3000's line output. How does it sound?

73,

Dave, AA6YQ

3121 - 3140 of 203497