Date   

Re: trying to interface my Yaesu FT991A with DxLab - no joy

Ed
 
Edited

Make sure you are using the correct port .  Your 991A should have made 2 com ports.  Not sure which one you are using.  You might test the port you are not using?


I don’t have my 991A hooked up right now, but works perfect with commander, with the right settings.

like Dave just indicated, make sure all your settings match the radio.

Ed WA6WGS


Re: trying to interface my Yaesu FT991A with DxLab - no joy

Dave AA6YQ
 

+ AA6YQ comments below
I followed the step by step instructions. Still not talking to commander.
When I have the radio plugged in, looking at the com port in device manager indicates that the port is working properly. When unplugged it recognizes that the port is not connected. The strange thing is that windows doesn't 'cue' me when I plug the radio into my computer.
I did modify the baud rate to 38,400, but where would I find the radio interface info? My FT991A operating manual does not contain that information.

+ If you configured Commander to use 38400 baud but didn't configure the radio to use 38,400 baud, that's one reason the two can't communicate.

+ Menu item 31 controls the CAT baud rate; see page 121 of your FT-991 "Operating Manual".

        73,

               Dave, AA6YQ


Re: Odd problem with DXKeeper!

Dave AA6YQ
 

+ AA6YQ comments below
I finally got around to applying to the League so that they would move my 800+ "New LotW QSLs" to the "DXCC Credits Awarded" column.  Then using DXKeeper, everything seemed to go smoothly during the Download, Analyze and Autolink processes, or so I thought since now there is a strange problem as described below.

In the last 2+ years I've made 25,000 (+/-) FT8 QSO's.  Because of this, I normally "Sync LotW QSOs" followed by "Sync LotW QSLs" a couple of times a day, usually finding that I have up to 50 new confirmations every 24 hours.  Since updating the database as shown above, now each time I "Sync LotW QSOs" followed by "Sync LotW QSLs", I am told that I have only 1 new QSL, but this QSL is not shown at the top of the log list.  Somewhere in my log file there is 1 or more QSOs that are causing the problem (I think), but I have no idea how to identify these problem log entries.

I realize I could restore my backup database file, but this would be a BIG process and I'm sure the same error would occur again.  Also this would mean that I need to import the newest QSOs from my WSJT file to DXKeeper.  All-in-all, I'd much rather find the problem in the database and fix it.  Can anyone help?

+There is no problem.

+ When you invoke "Sync LoTW QSOs" or "Sync LoTW QSLs", DXKeeper sends the date-and-time shown beneath the button, directing LoTW to report all QSOs accepted or confirmed (respectively) since the that date-and-time. LoTW ignores the time, reporting all QSOs accepted or confirmed since 0Z on the specified date. Thus QSOs accepted or confirmed on the last date a QSO was accepted or confirmed are reported each time you invoked "Sync LoTW QSOs" or "Sync LoTW QSLs". I consider this a defect in LoTW; not everyone agrees.

      73,

            Dave, AA6YQ

 

 

 


Re: trying to interface my Yaesu FT991A with DxLab - no joy

Lance HP
 

I followed the step by step instructions. Still not talking to commander.
When I have the radio plugged in, looking at the com port in device manager indicates that the port is working properly. When unplugged it recognizes that the port is not connected. The strange thing is that windows doesn't 'cue' me when I plug the radio into my computer.
I did modify the baud rate to 38,400, but where would I find the radio interface info? My FT991A operating manual does not contain that information.


Odd problem with DXKeeper!

Bill - AA4M
 

I finally got around to applying to the League so that they would move my 800+ "New LotW QSLs" to the "DXCC Credits Awarded" column.  Then using DXKeeper, everything seemed to go smoothly during the Download, Analyze and Autolink processes, or so I thought since now there is a strange problem as described below.

In the last 2+ years I've made 25,000 (+/-) FT8 QSO's.  Because of this, I normally "Sync LotW QSOs" followed by "Sync LotW QSLs" a couple of times a day, usually finding that I have up to 50 new confirmations every 24 hours.  Since updating the database as shown above, now each time I "Sync LotW QSOs" followed by "Sync LotW QSLs", I am told that I have only 1 new QSL, but this QSL is not shown at the top of the log list.  Somewhere in my log file there is 1 or more QSOs that are causing the problem (I think), but I have no idea how to identify these problem log entries.

I realize I could restore my backup database file, but this would be a BIG process and I'm sure the same error would occur again.  Also this would mean that I need to import the newest QSOs from my WSJT file to DXKeeper.  All-in-all, I'd much rather find the problem in the database and fix it.  Can anyone help?

Thanks, Bill  AA4M


Re: trying to interface my Yaesu FT991A with DxLab - no joy

Dave AA6YQ
 

+ AA6YQ comments below
Hi. Trying to get the DXlab commander to communicate to the subject radio. I haven't had any luck so far. I don't really know what the communications setting should be for the radio (com port, baud rate, etc). I can communication with the radio using the programming software that I bought so I confirmed my cable is good and apparently that software is using a driver that works with the radio. I am not sure about DXLab though. I downloaded the driver from Yaesu and that didn't really change anything. I didn't change the default comm settings in commander and at a loss of what to change them to.
Any suggestions?
By the way, it occurred to me that I might have to upgrade my radio firmware, but I shied away from that 'rabbit hole' for now

+ Step-by-step instructions are here:

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

+ If those don't get you going, let me know.

      73,

            Dave, AA6YQ

 


trying to interface my Yaesu FT991A with DxLab - no joy

Lance HP
 

Hi. Trying to get the DXlab commander to communicate to the subject radio. I haven't had any luck so far. I don't really know what the communications setting should be for the radio (com port, baud rate, etc). I can communication with the radio using the programming software that I bought so I confirmed my cable is good and apparently that software is using a driver that works with the radio. I am not sure about DXLab though. I downloaded the driver from Yaesu and that didn't really change anything. I didn't change the default comm settings in commander and at a loss of what to change them to.
Any suggestions?
By the way, it occurred to me that I might have to upgrade my radio firmware, but I shied away from that 'rabbit hole' for now.


Re: SpotCollector 8.8.3 is available

Steve W5GP
 

On Wed, Feb 3, 2021 at 07:18 PM, Dave AA6YQ wrote:
- displays the WSJT-X version number on the SC_WSJTX main window
FYI,  this is displayed as WSJ-X n.n.n  rather than WSJT-X n.n.n.

73, Steve W5GP


Re: Ionoprobe demise.

Dave AA6YQ
 

+ AA6YQ comments bewlo

I see that ionoprobe, the solar indices part of DXAtlas has been withdrawn.

Is it possible that Propview could send over the data required to DXatlas? Or,,, maybe, could it be added to the Wishlist?

+ Without documentation describing DXAtlas' requirements, it's not possible to answer your question.

73,

Dave, AA6YQ


Ionoprobe demise.

Brian Bowers G0VAX
 

I see that ionoprobe, the solar indices part of DXAtlas has been withdrawn.
Is it possible that Propview could send over the data required to DXatlas? Or,,, maybe, could it be added to the Wishlist?

Best Wishes

Brian G0VAX


LoTW has stopped processing submitted QSOs; I have alerted ARRL staff <EOM

Dave AA6YQ
 


another new K1JT mode: Q65

Dave AA6YQ
 

The latest release candidate for WSJT-X, v2.4.0-rc1, introduces a new mode called Q65. Quoting from their quick-start guide:

"Q65 uses 65-tone frequency-shift keying and builds on the demonstrated weak-signal strengths of QRA64, a mode introduced to WSJT-X
in 2016"

After Q65 has been accepted by ADIF, I will update DXKeeper's DefaultModes.txt file to include Q65, and update SpotCollector to
recognize Q65 in spot notes.

If you'd like to immediately add Q65 to SpotCollector's mode selectors, see "Adding Support for a New Mode" in

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

Tnx to Rick K1MU for the information on Q65!

73,

Dave, AA6YQ


SpotCollector 8.8.3 is available

Dave AA6YQ
 

If you are using Windows Defender anti-malware, direct it to update its definitions from

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

before you install SpotCollector 8.8.3.


This release

- with an expanded spot database display row height, selects the correct spot database display entry when right-clicking (tnx to
Mark N1UK)

- correctly handles changes to the Spot Database Display layout made via keystrokes in the Layout panel on the Configuration
window's "Spot Database Display" tab

- prevents the loss of SQL filters (tnx to Dale AA1QD, Tom W1TJL, Jim KR9U, Parker W5ADD, Björn SM7IUN, Iain N6ML, and Nyles KS4S)

- adds the computed age (in minutes) to the tooltips for the LastTime and SpotTime fields (tnx to Jon KM8V)

- handles additional message fields sent by WSJT-X 2.3.0 (tnx to Bill G4WJS)

- responds to CTRL-C typed in the "Spots of" window's display of a Spot Database Entry's spots by copying those spots to the Windows
clipboard

- displays the WSJT-X version number on the SC_WSJTX main window

- replaces 24 audio announcement files voiced by AA6YQ with new versions voiced by Joe DX (tnx to Peter K0PLT and Chuck NA6BR)

- updates the SpotDatabase.htm documentation file


Notes:

1. Update your firewall and anti-malware applications to consider the new versions of SpotCollector.exe and SC_WSJTX.exe to be
"safe"

a. 0/15 Jotti scanners detected malware in SpotCollector.exe

b. 0/70 VirusTotal scanners detected malware in SpotCollector.exe

c. 0/15 Jotti scanners detected malware in SC_WSJTX.exe

d. 2/70 VirusTotal scanners detected malware in SC_WSJTX.exe

c. SpotCollector.exe and SC_WSJTX.exe have been submitted to "Microsoft Security Intelligence" and found free of malware.

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 SpotCollector, see

http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion



SpotCollector 8.8.3 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ


Re: Spot Collector error log

Dave AA6YQ
 

+ AA6YQ comments below

Here is the log.

+ Thanks for the errorlog, Jim. It shows that SpotCollector has lost access to your log file.

+ There was one occurrence of this back on 2019-06-23.

+ There have been many occurrences starting on 2021-01-21.

+ I suggest that you check your Windows event logs for reports of hardware or software failures on 2021-01-21.

73,

Dave, AA6YQ


Re: Spot Can't open Log File for award progress checking

Jim Cary
 

Will do


Re: Unusual Log QSO's Row Sizing ?

w2eck
 

Dave - that fixed it, thanks very much for the quick assist.

73 & Be Safe
Paul
w2eck


Re: rst and tx reversed

Dave AA6YQ
 

Thanks for the screen shots, Robert. The QSO shown as selected in your "Lot QSOs" tab screen shot -- KM6SO -- is not present in your
label screen shot.

Your Log Page Display shows several logged QSOs whose "RST Sent" items are set to "1H GTA" These appear in the RST sections of your
printed QSL labels as "1H G" because with the font metrics you're using, the labels only print the first 4 characters of each QSO's
" RST Sent item. You could try reducing the font size to get more characters printed, or you could use DXKeeper to drive a more
flexible label generation application, as described here:

https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing%20via%20ADIF

73,

Dave, AA6YQ


Re: Unusual Log QSO's Row Sizing ?

Dave AA6YQ
 

+ AA6YQ comments below

I have inadvertently done something that has caused each row in the Log QSO's tab to have a huge amount of white space between each contact and the entire DxKeeper window to be very large top to bottom and I am having trouble shrinking it. Looked around in the Config page but have found how to revert to normal display. Any suggestions on a fix?

+ You evidently dragged a "row separation line" downward. The fastest way to correct that is to click the Reset button on the right side of the "Log Page Display" panel near the bottom of the Configuration window's Log tab.

73,

Dave, AA6YQ


Unusual Log QSO's Row Sizing ?

w2eck
 

I have inadvertently done something that has caused each row in the Log QSO's tab to have a huge amount of white space between each contact and the entire DxKeeper window to be very large top to bottom and I am having trouble shrinking it. Looked around in the Config page but have found how to revert to normal display. Any suggestions on a fix?

73 Paul w2eck


Re: Spot Can't open Log File for award progress checking

Dave AA6YQ
 

+ AA6YQ comments below
The error log says "program error 91 in module LOgDataBaseModule..........
+ Please place the errorlog.txt file from your SpotCollector folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

     73,

              Dave, AA6YQ

3181 - 3200 of 202667