I'm sort of lost trying to set up my FTDX-3000  to run FT8 with Win4Yaesu and DXLab.  I have not been a big FT8 user and haven't used it since I had my old FTDX-1200 with a Rigblaster quite a while ago.  I've been trying to set it up but, as I say, I'm lost and scratching my 84 year old head.  I need someone to talk or help me through it. I can be reached at W5DT@...

Any help would really be appreciated.

73,
Marv, W5DT

I DID have that checked, but thank you, Joe!

Weird thing: I had some hang ups while stating DX Commander from the launcher.  After I shut everything down, and rebooted, its' all working.  I don't know why, I didn't change any settings.
GREMLINS!

Thanks all,
Dean W8ZF

Dave,
I'll go review the doc you linked.  If this is not something  I have already followed (I have already spent hours at this), then I'll just switch over to WSJT-X to see if I can get THAT working.
Thank you!
Dean

+ AA6YQ comments below

I upgraded my shack PC.  I followed the DXlab procedure and it seems to work fine (except, my new PC has different COM port numbers - fixed).  I installed fresh copies of JTDX (I *KNOW* Dave doesn't support JTDX, but it was working fine on the old PC and it is my preferred UI), and JTAlert.

+ I personally do not use of JTDX on ethical grounds, but that's irrelevant. JTDX does not support all of the programmatic interfaces that DXLab employs when directly connected to WSJT-X - but since you're using JTAlert, that's also irrelevant.

  Everything seems to be working with the following exception: QSOs on FT-8 are not being logged in DXkeeper.

I have compared settings on both computers, all the network servers seem to be working on the same ports, I can't find anything wrong, but even the "log now" on JTDX doesn't log the QSO or upload to LoTW and ClubLog.  There are MOUNDS of documentation to look through. 

+ There's only one DXLab document to review, but it assumes the use of WSJT-X:

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

      73,

            Dave, AA6YQ

 

I upgraded my shack PC.  I followed the DXlab procedure and it seems to work fine (except, my new PC has different COM port numbers - fixed).  I installed fresh copies of JTDX (I *KNOW* Dave doesn't support JTDX, but it was working fine on the old PC and it is my preferred UI), and JTAlert.  Everything seems to be working with the following exception: QSOs on FT-8 are not being logged in DXkeeper.

I have compared settings on both computers, all the network servers seem to be working on the same ports, I can't find anything wrong, but even the "log now" on JTDX doesn't log the QSO or upload to LoTW and ClubLog.  There are MOUNDS of documentation to look through.  I was hoping someone on the forum might be able to save me some time and give me the benefit of your experience.

Thanks and Happy New Year!
73,
Dean W8ZF

Oh, the new PC is Win 11 Pro, old was Win10 Pro, in case that could be a factor.

... via the Databases tab of DXView's Configuration window. Terminate DXKeeper and SpotCollector before directing DXView to update
these databases.

73,

Dave, AA6YQ

On 2022-12-27 8:45 PM, Anthony - N2KI wrote:

I spent the whole day trying to figure it out to no real solution other than a workaround. The only error that EXTFSK displays is "NO
GOOD" next to the com port. Even after it displays this error, WSJT
has no problem connecting to the com port.

First thing is you should probably not use the same port for WSJTX
and EXTFSK. You should certainly make sure that WSJTX is closed
(and hamlib has been unloaded from memory) before trying to start
EXTFSK/MMTTY.

Unplugging the USB cable causes Windows to delete the virtual port
- which would force hamlib to close if it was still in memory - and
reconnecting the USB cable will reinitialize the virtual port.

The only error that EXTFSK displays is "NO GOOD" next to the com port.

"No Good" means the port either does not exist or is in use by another
program (EXTFSK can not open the port).

73,

... Joe, W4TV

On 2022-12-27 8:45 PM, Anthony - N2KI wrote:

Dave,
It's the same reason I can't pick the numbers for the lottery, but I can sure get one off issues such as this.
I spent the whole day trying to figure it out to no real solution  other than a workaround.   The only error that EXTFSK displays is "NO GOOD" next to the com port.  Even after it displays this error, WSJT has no problem connecting to the com port.  The only way to resolve it is to unplug the 101 USB and plug it back it. Then EXTFSK can connect to the port.
I'm not familiar with USBView, but I will look that up.  I think ultimately I will build an FSK/PTT circuit in a db9 shell and eliminate the need for EXTFSK altogether, using the DATA/RTTY port instead.  So, yes, I agree it is a local issue.
--
Anthony - N2KI

+ AA6YQ comments below

It's the same reason I can't pick the numbers for the lottery, but I can sure get one off issues such as this.

I spent the whole day trying to figure it out to no real solution other than a workaround. The only error that EXTFSK displays is "NO GOOD" next to the com port. Even after it displays this error, WSJT has no problem connecting to the com port. The only way to resolve it is to unplug the 101 USB and plug it back it. Then EXTFSK can connect to the port.
I'm not familiar with USBView, but I will look that up. I think ultimately I will build an FSK/PTT circuit in a db9 shell and eliminate the need for EXTFSK altogether, using the DATA/RTTY port instead. So, yes, I agree it is a local issue.

+ If you want to pursue this a bit further, you could ask Oba-san JA7UDE what "NO GOOD" means; he is the developer of EXTFSK. You can contact him via

noboba (at) yahoo.com

+ If you have enough CPU horsepower to handle a sharp transmit filter in MMTTY, you could transmit with AFSK instead of FSK.

73,

Dave, AA6YQ

Dave,

It's the same reason I can't pick the numbers for the lottery, but I can sure get one off issues such as this.

I spent the whole day trying to figure it out to no real solution  other than a workaround.   The only error that EXTFSK displays is "NO GOOD" next to the com port.  Even after it displays this error, WSJT has no problem connecting to the com port.  The only way to resolve it is to unplug the 101 USB and plug it back it. Then EXTFSK can connect to the port.  
I'm not familiar with USBView, but I will look that up.  I think ultimately I will build an FSK/PTT circuit in a db9 shell and eliminate the need for EXTFSK altogether, using the DATA/RTTY port instead.  So, yes, I agree it is a local issue.
--

Anthony - N2KI

+ AA6YQ comments below

Joe. While we are on the subject of EXTFSK, is there any reason why EXTFSK does not seem to connect to the COM2 port (my ptt port for FTDX101mp) except if I disconnect the usb cable and then reconnect it.

+ I don't recall anyone else ever reporting that behavior over the past ~20 years, which implies a local issue.

+ Does EXTFSK issue an error message in that scenario?

+ Forced to guess, I'd say that Windows thinks that the port is still in use. You could download the free USBView application to see if it sheds any light on the situation:

https://www.nirsoft.net/utils/usb_devices_view.html

73,

Dave, AA6YQ

Thanks Joe.   While we are on the subject of EXTFSK, is there any reason why EXTFSK does not seem to connect to the COM2 port (my ptt port for FTDX101mp) except if I disconnect the usb cable and then reconnect it. I do not have an issue with WSJT connecting to it.  But always when using EXTFSK via Winwarbler.
--

Anthony - N2KI

+ AA6YQ comments below

Use:

(DXCCPrefix IN ('K','KH6','KL7')) and (Band ='40M') and (Mode = 'FT8')

When using a list of values *IN* is appropriate instead of *=*

+ The expression

(DXCCPrefix IN ('K','KH6','KL7'))

+ that Joe W4TV recommended above is "shorthand" for

((DXCCPrefix = 'K') or (DXCCPrefix = 'KH6') or (DXCCPrefix='KL7'))

+ The longer the list of items you are hunting, the more typing this shorthand will save you. It's helpful when selecting QSOs made on a particular set of bands, or in a particular set of modes, or from a particular set of myQTHs, etc.

73,

Dave, AA6YQ

 

 

+ AA6YQ comments below

Which report are you referring to, Julio? The Progress report? If so, I run the report, copy all the text, and paste into an Excel so I can manipulate, sort, filter by risk, confirmed status etc. to get it just the way I want it. 

+ You can do all that sorting and filtering in DXKeeper.

+ Note that DXKeeper's Marathon Submission generator automatically takes risk into account when selecting QSOs to submit; you can configure DXKeeper to automatically consider confirmed QSOs to be "low risk". See

https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#AP%20CQ%20DX%20Marathon

     73,

           Dave, AA6YQ

The Progress report is 155 columns (characters) wide. Configure your
printer for *LANDSCAPE MODE*, select a *MONOSPACED FONT* (in NotePad)
that will allow about 160 characters to print in 10 inches, set the
margins (top/bottom/left/right) to 1/2" and *unselect* word warp.

With Consolas 8 and 1/2" margins Top/Bottom/Left/Right, the Progress
Report prints in just over 7 pages.

73,

... Joe, W4TV

Is there anyway to get that to stick?

In WinWarbler, *while in RTTY*

Click Config
Select the RTTY tab
Make sure the Modulation and Transceiver Mode panel is set to:
LSB
XCVR Mode = RTTY
Mark Offset = your mark (typically -2125)
Optimal Offset = Mark+Space/2
FSK Control = EXTFSK (or EXTFSK64)

Always Start MMTTY with WinWrbler. *DO NOT* start a stand alone
copy of MMTTY separate from WinWarbler. WinWarber will set MMTTY
to the proper settings based on the settings in the "Modulation and
Transceiver Mode panel".

73,

... Joe, W4TV

On 2022-12-27 12:12 PM, Anthony - N2KI wrote:

Recently having an issue with running FSK on FTDX101MP, which I was able to resolve.  The one item that I have not been able to resolve is getting the EXTFSK to stick on the TX tab of MMTTY in the MMTTY setup.  I have started the instance of MMTTY directly, that is installed in the WinWarbler folder, selected EXTFSK in the TX tab, but when I start Winwarbler, I still have to go and do the MMTTY setup ad select EXTFSK again.
Is there anyway to get that to stick?
--
Anthony - N2KI

Which report are you referring to, Julio? The Progress report? If so, I run the report, copy all the text, and paste into an Excel so I can manipulate, sort, filter by risk, confirmed status etc. to get it just the way I want it. 
Jim K2JL

+ AA6YQ comments below

Any chance of moving the button for "Memory Banks-Filters and Devices" over to the left closer to the "Scan" button?

+ No, as the space between that button and the Scan button is occupied by the CIV warning indicator, which appears when the primary radio reports that is has detected a CI-V bus collision.

       73,

                Dave, AA6YQ