Date   
Re: Commander 14.4.0 - Yaesu FTdx101D - Startup filter width anomaly

C. Michael D'Alto
 

* Commander does not notice that its filter selection is probably in appropriate for the mode selected and change that filter selection on your behalf.

Yes, I agree that is what is happening.  I can hear when it happens because of the drastic difference in band noise when the rig goes 300 Hz.

* In the power-up scenario you describe above, what filter width is shown on the radio's front panel?

This is an excellent question and probably the crux of the matter.  The filter width is not on the display until you rotate the width knob.  They opted to put an LED indicator next to the concentric controls for Shift and Width.  If you deviate from the default of 3000 Hz on SSB either narrower or wider, the LED illuminates.  If you want to check what it is set to, it you have to move the knob, then the setting pops up on the screen for a moment.  It's like Schrodinger's Cat.  Can't tell if the cat is alive or dead until you open the box.  When you start Commander ahead of the radio powering on, Commander checks, and displays the settings correctly without changing the bandwidth to 300 Hz. 

* Perhaps Yaesu's engineers learned a few things from their FTDX-3000 experience.

I hope so.  I know they're using the exact same Silicone Labs drivers for the USB ports, so I'm not sure.  This is the next thing I have to tackle as I like using the builtin sound card for RTTY.

DXView antenna presets setup?

Gordon LaPoint
 

How do I set up the presets buttons?  I would like to change some of the preset bearings.

Thanks,

Gordon - N1MGO

Settings for WSJT-X and TS-590SG with USB Audio and CAT/PTT

Hasan Schiers N0AN
 

Since I just had to go thru this, I thought it might be useful to anyone using a TS-590sg with WSJT-X and perhaps, DXLabSuite who wanted to implement USB instead of using the Front Microphone and a Com Port RTS for PTT. I had this front mike input setup with a RigBlaster Plus interface for many, many years and was too timid to change. It was well worth the change, and now only one cable is required (USB) between the computer and the TS-590sg to do everything, and no more playing with audio levels and external interfaces.

Installing the required drivers in Windows 10:
2 Sets of drivers are required, one for Audio and one for CAT (Virtual Serial Port)
The Virtual Serial Port driver is from Kenwood: CP210x_Universal_Windows_Driver
The Audio Driver is native to Windows and will be installed as soon as you connect the USB cable between the computer and the TS-590sg


Do not connect the usb cable between the Kenwood and the computer before you install the virtual serial port driver. Install the CP210x driver package first.

Windows will install the TS-590sg USB Audio Driver automatically, AFTER you install the Virtual Com Port driver, at the moment you connect the USB cable from the back of the TS-590sg to the computer. Do not go to the Kenwood site and download their Audio Drivers. The native Windows 10 driver is what you need.

Kenwood: CP210x_Universal_Windows_Driver   for the Virtual Serial Port
Win10 Pro 64 bit  (Google TS-590sg USB and the Kenwood site will come up)

USING USB AUDIO IN and OUT on a TS-590SG:

On my TS-590sg,  I have the following settings:

Menu #: (in TS-590sg)
#76 Vox with Data OFF : If front panel SSB mike input fails, try ON
#72 Audio Out: 1 ; Yields 41 dB on the Rx Thermometer on 6 meters
#71 Audio In:    3 ; Shows small amount of Transmit ALC
#70 Source of PTT send PTT transmission: rEAr
#69 Audio Input Line Select for DATA Communication: USB
#68 USB Port Baudrate: 115200

WSJT-X
TS-590sg Vox OFF
File > Settings > Radio:
Radio = DXLab Suite Commander  (or your chosen Radio) : Poll Interval 1 s
PTT = CAT
Mode: USB
Split Operation = Fake It  (Reduces command delay between DXLab and WSJT-X)

File > Settings > Audio :
Input: Microphone (2-USB Audio CODEC)
Output: Speakers (2-USB Audio CODEC)
X Poll: 1 sec; X Advanced TX Delay 0.1 s
Windows Settings Microphone (USB CODEC) Slider 0 dB
Windows Settings Speaker (USB CODEC) Slider 0 dB

How to Set Windows Sliders: WIndows 10

Do the following for the Speaker CODEC
Right Click on Speaker Icon in Task Bar (far right side of desktop, bottom)
Select Open Sound Settings
Under Output : Choose USB Audio CODEC  from the drop down menu
Click on Device Properties (below in Blue)
On top Right of Window: Click on Additional Device Properties
5 TABS Appear in the new small Speaker Properties window
Click on Enhancements: Check the Box that says "Disable all enhancements"
Click on Levels: set slider to 0 dB if dB is not showing, Right Click on the slider,choose dB
Click on Advanced: select 16 bit, 48000Hz DVD Quality (ignore warning) Click OK
Close the Settings Main Window

Do the following for the Microphone CODEC
Right Click on Speaker Icon in Task Bar (far right side of desktop, bottom)
Select Open Sound Settings
Under Input: Choose Microphone USB Audio CODEC)
Click on Device Properties (below in Blue)
On top Right of Window: Click on Additional Device Properties
4 TABS Appear in a new small Microphone Properties window
Click on Advanced: Choose 1 Channel, 16 bit 48000 Hz, DVD Quality
Click on Levels: set to 0 dB, if % is showing, Right Click on level box and choose dB
Click OK, Close Settings Main Window

Stop WSJT-X then Restart WSJT-X, especially if you changed the audio sample rate from some other value to 48000 Hz.

(Note: in DXCommander:( Config > General Tab > Command Interval : Set to 50 ms from 200) This helps lag time in the radio accepting commands to set frequency etc)

Thanks to Dave, AA6YQ and Bill, G4WJS for helping me get this altogether.

Hopefully this will help someone as befuddled by the process as I was.

73, N0AN
Hasan

Re: Spotcollector pruning window granularity

Tim N3XX
 

I have my setting for pruning set to .021 days, which leaves about the last half hour of spots in the database after pruning. All works fine, but I can only prune automatically once an hour. In that time the database gets bigger than I want it to. It would be really helpful if I could set automatic pruning to happen every 1/2 hour, or even every 1/4 hour.

73,
Tim - N3XX

On 2020-02-02 5:57 AM, Björn Ekelund, SM7IUN wrote:
I use multiple spot sources including FT8 spots from RBN which means a quite large influx.
To make sure SpotCollector keeps up and not overflow, I set a very short pruning window.
I have found that anything below 0.05 days is treated as zero.
Is there a reason for this quantization?
I would value if it was possible to set even lower numbers.
Björn SM7IUN

Spotcollector pruning window granularity

Björn SM7IUN
 

I use multiple spot sources including FT8 spots from RBN which means a quite large influx. 

To make sure SpotCollector keeps up and not overflow, I set a very short pruning window. 

I have found that anything below 0.05 days is treated as zero. 
Is there a reason for this quantization? 
I would value if it was possible to set even lower numbers.

Björn SM7IUN


Re: Gritty Gateway not showing in WW

Dave AA6YQ
 

+ AA6YQ comments below

I just installed Gritty and the Gritty Gateway and am trying to get it to print in the "X" channel of WW.
I followed the instructions in the Wiki "displaying RTTY decoded by Gritty".

The Gateway says it is connected, and the Gritty program itself is working, but nothing is showing in the "X" channel of WW.
The "X" is not blinking, so its not suspended.

Any suggestions?

+ What version of the Gritty Gateway are you running?

+ Did you configure your anti-malware to consider Gritty, the Gateway, and WinWarbler to be "safe"?

+ I just tied Gritty, the Gritty Gateway (version 1.0.4), and WinWarbler here; they are interoperating correctly.

73,

Dave, AA6YQ

Gritty Gateway not showing in WW

Jim - KR9U
 

I just installed Gritty and the Gritty Gateway and am trying to get it to print in the "X" channel of WW.
I followed the instructions in the Wiki "displaying RTTY decoded by Gritty".

The Gateway says it is connected, and the Gritty program itself is working, but nothing is showing in the "X" channel of WW.
The "X" is not blinking, so its not suspended.

Any suggestions? 

Jim - KR9U

Re: JT Alert Logging to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

I am not sure if this question is better asked with the JTDX or JT alert folks or here.

I have the options checked the DXview/pathfinder info but I have noticed that no data such as county is not being populated in DXKeeper. Is that not what should be happening? Or does it just populate the calls into those windows? Maybe the data is coming directly from JTDX

If not is there an easy way to import data from QRZ or other places with county and other missing data?

+ Step-by-step instructions for configuring JTAlert to interoperate with DXLab are here:

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

73,

Dave, AA6YQ

Re: JT Alert Logging to DXKeeper

W0MU
 

I changed some settings in JT Alert.  It now looks like missing data is being filled in at least on a few contacts.  I will let you know if things should change.

W0MU

JT Alert Logging to DXKeeper

W0MU
 

I am not sure if this question is better asked with the JTDX  or JT alert folks or here.

I have the options checked the DXview/pathfinder info but I have noticed that no data such as county is not being populated in DXKeeper.  Is that not what should be happening?  Or does it just populate the calls into those windows?  Maybe the data is coming directly from JTDX

If not is there an easy way to import data from QRZ or other places with county and other missing data?

Thanks!

W0MU

Re: Commander 14.4.0 - Yaesu FTdx101D - Startup filter width anomaly

Dave AA6YQ
 

* more AA6YQ comments below

+ Since the radio isn't powered up, it's not "on SSB".

Correct, it is not. Until I press the power button on the radio. So before I power on the radio Commander is sitting there idle, as it should. I am seeing the Main frequency window reading 000,000.00 - Sub window is blank - Filters slider is all the way to the left showing "0" - Nar box is unticked - Shift slider is amidships showing "0 Hz" - Mode choices are blank.

Okay, so now I power on the radio on 14,222.00 on USB for argument sake. Now I am seeing 14,222.00 in the Main (TX): 20M - Sub is correctly reading the radio (7,161.00) - Filters reading "300 Hz" - Width slider is all the way to the left - Nar box is ticked - Shift slider is still amidships - Mode is correctly reading USB.

I just wonder why it decides to set the filter width to 300 Hz (which is not appropriate for SSB) seemingly on its own volition. It knows I am on SSB because it is showing that circle as ticked. So I set it back to 3000 Hz each time. That is, when I turn off the radio, I do not turn it off at 300 Hz., rather it's usually much wider than that. I'm sorry if I am making a mountain out of a molehill. I can live with it the way it is and just fix it each time it happens either by the slider or the width knob on the radio.

* Commander does not notice that its filter selection is probably in appropriate for the mode selected and change that filter selection on your behalf.

* In the power-up scenario you describe above, what filter width is shown on the radio's front panel?


+ There is nothing that Commander or WinWarbler can do to cause the "loss" of serial ports; with respect to those ports, their activities are limited to open, close, read, and write operations. If any of those operations cause the serial port to be "lost", the responsible defect likely lies in the serial port device driver.

I didn't phrase that quite right. I'm not trying to blame it on your software. What I meant was that if the radio was turned off and then back on while it was connected via the USB port, the computer would assign new com port numbers.

* That's the result of a defect in the Serial Port driver.

Usually I could go back in and change it in the configuration, but sometimes I'd have to do a reboot. This was with my FTdx3000. I assume it will be the same with the FTdx101D.

* Perhaps Yaesu's engineers learned a few things from their FTDX-3000 experience.

73,

Dave, AA6YQ

Re: Commander 14.4.0 - Yaesu FTdx101D - Startup filter width anomaly

C. Michael D'Alto
 

+ Since the radio isn't powered up, it's not "on SSB".

Correct, it is not. Until I press the power button on the radio.  So before I power on the radio Commander is sitting there idle, as it should. I am seeing the Main frequency window reading 000,000.00 - Sub window is blank - Filters slider is all the way to the left showing "0" - Nar box is unticked - Shift slider is amidships showing "0 Hz" - Mode choices are blank. 

Okay, so now I power on the radio on 14,222.00 on USB for argument sake.  Now I am seeing 14,222.00 in the Main (TX): 20M - Sub is correctly reading the radio (7,161.00) - Filters reading "300 Hz" - Width slider is all the way to the left - Nar box is ticked - Shift slider is still amidships - Mode is correctly reading USB. 

I just wonder why it decides to set the filter width to 300 Hz (which is not appropriate for SSB) seemingly on its own volition. It knows I am on SSB because it is showing that circle as ticked.  So I set it back to 3000 Hz each time.  That is, when I turn off the radio, I do not turn it off at 300 Hz., rather it's usually much wider than that.  I'm sorry if I am making a mountain out of a molehill.  I can live with it the way it is and just fix it each time it happens either by the slider or the width knob on the radio.

+ There is nothing that Commander or WinWarbler can do to cause the "loss" of serial ports; with respect to those ports, their activities are limited to open, close, read, and write operations. If any of those operations cause the serial port to be "lost", the responsible defect likely lies in the serial port device driver.

I didn't phrase that quite right.  I'm not trying to blame it on your software. What I meant was that if the radio was turned off and then back on while it was connected via the USB port, the computer would assign new com port numbers.  Usually I could go back in and change it in the configuration, but sometimes I'd have to do a reboot.  This was with my FTdx3000.  I assume it will be the same with the FTdx101D.  So I try to remember to exit the software before I turn off the radio, or to have the radio on when I start the software.  I'm just absentminded at times.  No worries.

73, Mike

Re: Commander 14.4.0 - Yaesu FTdx101D - Startup filter width anomaly

Dave AA6YQ
 

+ AA6YQ comments below

I have the rig connected via the 9 pin RS-232C connection. If I allow Launcher to start Commander before I power up the radio, Commander sets the filter width slider to 300 Hz and checks the Nar box (even if the rig is on SSB).

+ Since the radio isn't powered up, it's not "on SSB".

If I have the radio already powered up, then start Commander via Launcher, Commander correctly reads the current state of the rig's Filters Width setting. It's not a major annoyance, but slightly so. I was hoping that by using the old school serial port I could avoid having to worry about the order of what I started first. When I used the USB port for rig control and sound card it was a major hassle if I forgot and shut the radio off when either Commander or WinWarbler were running, as I'd lose the Com ports and have to reboot the computer.

+ There is nothing that Commander or WinWarbler can do to cause the "loss" of serial ports; with respect to those ports, their activities are limited to open, close, read, and write operations. If any of those operations cause the serial port to be "lost", the responsible defect likely lies in the serial port device driver.

73,

Dave, AA6YQ

Commander 14.4.0 - Yaesu FTdx101D - Startup filter width anomaly

C. Michael D'Alto
 

I have the rig connected via the 9 pin RS-232C connection.  If I allow Launcher to start Commander before I power up the radio, Commander sets the filter width slider to 300 Hz and checks the Nar box (even if the rig is on SSB).  If I have the radio already powered up, then start Commander via Launcher, Commander correctly reads the current state of the rig's Filters Width setting.   It's not a major annoyance, but slightly so.  I was hoping that by using the old school serial port I could avoid having to worry about the order of what I started first.  When I used the USB port for rig control and sound card it was a major hassle if I forgot and shut the radio off when either Commander or WinWarbler were running, as I'd lose the Com ports and have to reboot the computer. 

73, Mike, K2CD

Re: Filtering SpotCollector

Dave AA6YQ
 

+ AA6YQ comments below

Hello Dave and all

I have really never done much filtering of spots in SC. I have dabbled with filtering of the spot sources before the spots are received by SC.

I am looking at SC now and I see spots for SU1DL, which is a bad spot for HU1DL. The spots are being picked up incorrectly by the RBN and mistaking the H for an S. I need Egypt for the CQ DX Marathon so every time SU1DL comes up it sets off my alarm.

My question is what would be the best way to ignore spots for SU1DL?

+ Add SU1DL to SpotCollector's "Special Callsign" list with no tags:

<https://www.dxlabsuite.com/dxlabwiki/IdentifyBadCallsigns>

73,

Dave, AA6YQ

Filtering SpotCollector

Kent N6WT
 

Hello Dave and all

I have really never done much filtering of spots in SC. I have dabbled with filtering of the spot sources before the spots are received by SC.

I am looking at SC now and I see spots for SU1DL, which is a bad spot for HU1DL. The spots are being picked up incorrectly by the RBN and mistaking the H for an S. I need Egypt for the CQ DX Marathon so every time SU1DL comes up it sets off my alarm. 

My question is what would be the best way to ignore spots for SU1DL?

Thanks
73
Kent
N6WT

Re: Spot Collector Delete Spots

Dave AA6YQ
 

+ AA6YQ comments below

Is there also an easy way to like clear the whole field?
LIKE A CLEAR ALL?

+ If by "clear the whole field" you mean "remove all entries from the Spot Database", then

1. note the location of the Spot Database in the "Spot Database File" panel at the top of the Configuration window's "Spot Database"
tab

2. terminate SpotCollector

3. delete the Spot Database

4. start SpotCollector


73,

Dave, AA6YQ

Re: Spot Collector Delete Spots

Joe WB9SBD
 

Is there also an easy way to like clear the whole field?
LIKE A CLEAR ALL?
Joe WB9SBD

On 2/1/2020 1:46 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

If you click on a spot in Spot Collector, and delete it.

If/when the station is spotted again, will it re-appear?

+ If you delete the Spot Database Entry for callsign C operating in mode M near frequency F, and C is subsequently spotted in M near
F, then yes, a new Spot Database Entry for C in M near F will be created; subsequent spots of C in M near F will update that Entry.

        73,

               Dave, AA6YQ






Re: Spot Collector Delete Spots

Dave AA6YQ
 

+ AA6YQ comments below

If you click on a spot in Spot Collector, and delete it.

If/when the station is spotted again, will it re-appear?

+ If you delete the Spot Database Entry for callsign C operating in mode M near frequency F, and C is subsequently spotted in M near
F, then yes, a new Spot Database Entry for C in M near F will be created; subsequent spots of C in M near F will update that Entry.

73,

Dave, AA6YQ

Re: Can't Add Overrideto DXView

Dave AA6YQ
 

+ AA6YQ comments below

I do see that window but I didn't understand that it's telling that I can't make another override for the same call. I just changed the dates for the existing override and can live with that but I don't see how, if I import a log now that has a QSO that would be dependent on the older override dates, DXK would handle it properly. If it would assume the older entry entity was ambiguous and generate an error to fix manually that would work.

+ DXLab's initial override capability provided 16 unique overrides. These were only intended to support current operations. "fix scripts" developed and maintained by Joe W4TV were provided as a way to correct already-logged "incompliant" QSOs:

<https://www.dxlabsuite.com/dxlabwiki/CorrectDXCCEntity>

+ In the beginning, there was never a need for more than 16 overrides at any point in time, but that has changed over the years. Mounting requests from the user community for more overrides resulted in the release of DXKeeper 4.4.6 in November 2018; it supports an unlimited number of overrides, and can be populated with information published by Club Log and by Jim AD1C.

+ Yes, the same callsign can be re-used from a different location. Yes, you might import an ADIF record for a re-used non-compliant callsign that doesn't specify the correct DXCC entity or other location-based information. However, the rate at which this occurs is quite low, and correction can be accomplished with a "fix script". Yes, DXView, DXKeeper, and SpotCollector could all be extended to use the Override List as a cumulative repository for non-compliant callsigns, and handle the case where a callsign-based query of this list yields more than one result that must be further selected based on date-and-time. The priority of a candidate development task is based on the value it would deliver to a DXLab user, the fraction of the user community that would benefit from that value, and the effort required for development and testing. When there are no higher-priority tasks on the queue, I will consider further extending the override mechanism.

73,

Dave, AA6YQ