Date   

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

Dave AA6YQ
 

+ AA6YQ comments below
Ok. I finally deleted the drivers (enhanced and standard) and re-installed and I have comms now.
+ Good! Does Windows now inform you when you connect your radio to your computer?

     73,

            Dave,. AA6YQ


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

Dave AA6YQ
 

+ AA6YQ comments below:
menu 32 CAT is 1000msec
menu 33 is RTS ENABLED
+ Thanks, Ed! I assume with those settings that you have RTS set to "Flow" in Commander's "Primary CAT Port" panel.

       73,

             Dave. AA6YQ


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

Lance HP
 

Ok. I finally deleted the drivers (enhanced and standard) and re-installed and I have comms now.
Thanks for your help. I wasn't sure what was happening before, but all good now.

Lance KK4DX


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

Ed
 

Hi Dave

menu 32 CAT is 1000msec
menu 33 is RTS ENABLED

Ed


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

Dave AA6YQ
 

+ AA6YQ comments below

I must be missing something. Baud rate matches up but still nothing.
Changed the settings in the radio as well to match (although parity is NOT defined anywhere that I can see).

I guess I will have to come back to this later and spend more time. There must be that 'magic checkbox easter egg' somewhere that I an not seeing.

+ The "Model-specific notes" section of

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

+ states that the FT-991 contains an internal SCU-17. The article to which it links

https://www.dxlabsuite.com/dxlabwiki/YaesuSCU-17

+ includes an "FT-991 Setup" section and a "Transceiver Control (CAT)" section.

73,

Dave, AA6YQ


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

Dave AA6YQ
 

+ AA6YQ comments below

I must be missing something. Baud rate matches up but still nothing.
Changed the settings in the radio as well to match (although parity is NOT defined anywhere that I can see).

I guess I will have to come back to this later and spend more time. There must be that 'magic checkbox easter egg' somewhere that I an not seeing.

+ There is no "magic easter egg checkbox. All configuration items are documented.

+ Things to check:

1. that you've configured Commander's "Primary CAT Port" panel to control the correct virtual COM port created by your FT-991 device driver

2. that the USB cable you're using to connect the radio to your computer is "good", and properly seated at both ends.

3. try increasing the "CAT TOT" menu setting (32) to 1000.

4. the "CAT RTS" menu item (33) defaults to ENABLE. In typical Yaesu style, the meaning of this setting is not documented; try setting it to DISABLE.

+ Your earlier report that connecting your radio to your computer did not produce the expected notification from Windows is not a good sign. When you connect your radio to your computer, the Window Device Manager should show two new COM ports appearing. Trouble in this area requires engaging with Yaesu support.

+ Ed WA6WGS, how are menu items 32 and 33 configured on your FT-991?

73,

Dave, AA6YQ


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

Joe Subich, W4TV
 

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.
Are you connected to the transceiver using the USB connection or
using the RS-232 connection? Mentioning an external cable would
tend to indicate a third party cable connected to the GPS/CAT jack
and not a generic USB cable connected to the USB jack.

If you are using a third party cable connected to the GPS/CAT jack,
make sure that:
Menu item 028 "GPS/232C Select" is set to RS232C.
Menu item 029 "232C Rate" is set to 38.400 bps
Menu item 030 "232 TOT" is set to 1000 or higher

If you are using a USB A-B cable connected to the USB jack, make
sure that:
Menu item 031 "CAT Rate" is set to 38,400 bps
Menu item 032 "CAT TOT" is set to 1000 or higher
Menu item 033 "CAT RTS" is set to DISABLE
In addition, make sure that Commander is configured for the correct
virtual port created by the Yaesu USB driver (it creates two ports
one "Enhanced" port for CAT, one "Standard" port for FSK, PTT, CW,
etc.). See "FT-991A SCU-17 USB Driver Installation Manual" in the
Files area of the FT-991A listing at www.Yaesu.com.


73,

... Joe, W4TV


On 2021-02-04 10:54 AM, Lance HP wrote:
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: trying to interface my Yaesu FT991A with DxLab - no joy

Lance HP
 

I must be missing something. Baud rate matches up but still nothing.
Changed the settings in the radio as well to match (although parity is NOT defined anywhere that I can see).

I guess I will have to come back to this later and spend more time. There must be that 'magic checkbox easter egg' somewhere that I an not seeing.

Lance KK4DX


Re: SpotCollector 8.8.3 is available

Dave AA6YQ
 

+ AA6YQ comments below


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

+ Corrected in the next version. Thanks!

73,

Dave, AA6YQ


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
 

3261 - 3280 of 202756