Date   

locked Re: #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

neil_zampella
 

Um ... just a quick note:

The KX3 does not have a 'built-in' USB/Serial adapter.  It and the KX2 uses the KXUSB serial cable which DOES have the UART in question.

Neil, KN3ILZ

On 6/25/2021 5:53 AM, W4JBB wrote:
Fred,

Did it work before Catalina?

Also, from https://www.dogparksoftware.com/MacLoggerDX%20Help/mldxfc_computer.html

Which Driver do I need ?

If you don't see the USB/Serial adapter port connected to your radio in the Port popup (or all you see is a Bluetooth port) then it could be one of the following:

  • The right driver (kernel extension) is not installed.
  • A bad or loose cable from the adapter/radio to your computer.
  • A radio with an internal USB/Serial adapter (UART) and the radio is powered down.

You can tell which chip set is being used in your adapter/radio by selecting "About This Mac / Overview / System Report / Hardware / USB. If the UART shows up in the Hardware/USB report It means that it is plugged in and powered up - not that a driver is necessarily loaded. Once you have identified the UART Chip set (FTDISilicon LabsProlificKeyspan/TrippliteRT Systems etc.) you can download and install the Mac driver from the manufacturers web site. 

Where can I get a Mac driver for my ICOM IC-705, IC-7100, IC-7200, IC-7300, IC-7600, IC-7610, IC-7850, IC-9100, IC-9700, PCR2500, Kenwood TS-890S, TS-990S, TS-590S, Elecraft KX3, K3S, Yaesu FTdx101, FTdx3000, FT-891, FT-991 or Ten-Tec Eagle USB direct connect built in USB/Serial adapter ?

The USB/UART Bridge chip inside the Icom, Yaesu and Kenwood radios is a Silicon Labs USB to UART Bridge Controller and the Mac drivers are available here.

The USB/UART Bridge chip inside the Eagle, K3S and KX3 is an FTDI USB to UART Bridge Controller and the Mac drivers are available here.

Note: macOS built in FTDI driver: Supports FTDI based devices with standard VID/PID combinations.

"Since 10.9 (Mavericks), OS X has included built-in partial support for some FTDI devices in VCP mode. Starting with 10.11 (El Capitan), Apple’s own driver seems to be sufficiently comprehensive that many customers will not need to install FTDI’s own VCP unless they wish to use its advanced features such as baud-rate aliasing and configurable latency times" .

Note the part I italicized and underlined (because I cannot figure out how to highlight in this format)...

If you *never* see the UART identifier, I'm going back to a bad cable regardless of whether or not that cable works with something else. Yes, I have seen cables go bad just "lying there" (that was a lesson in humility for me).

If you never see anything resembling "/dev/tty.usbserial-1444410", even after unplugging, running "ls /dev/tty*" and re-plugging and re-running "ls /dev/tty*,"my thought is you have a USB cable that does not have all the pins needed.

Thanks,
Joel, W4JBB



locked Re: #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

W4JBB
 

Fred,

Did it work before Catalina?

Also, from https://www.dogparksoftware.com/MacLoggerDX%20Help/mldxfc_computer.html

Which Driver do I need ?

If you don't see the USB/Serial adapter port connected to your radio in the Port popup (or all you see is a Bluetooth port) then it could be one of the following:

  • The right driver (kernel extension) is not installed.
  • A bad or loose cable from the adapter/radio to your computer.
  • A radio with an internal USB/Serial adapter (UART) and the radio is powered down.

You can tell which chip set is being used in your adapter/radio by selecting "About This Mac / Overview / System Report / Hardware / USB. If the UART shows up in the Hardware/USB report It means that it is plugged in and powered up - not that a driver is necessarily loaded. Once you have identified the UART Chip set (FTDISilicon LabsProlificKeyspan/TrippliteRT Systems etc.) you can download and install the Mac driver from the manufacturers web site. 

Where can I get a Mac driver for my ICOM IC-705, IC-7100, IC-7200, IC-7300, IC-7600, IC-7610, IC-7850, IC-9100, IC-9700, PCR2500, Kenwood TS-890S, TS-990S, TS-590S, Elecraft KX3, K3S, Yaesu FTdx101, FTdx3000, FT-891, FT-991 or Ten-Tec Eagle USB direct connect built in USB/Serial adapter ?

The USB/UART Bridge chip inside the Icom, Yaesu and Kenwood radios is a Silicon Labs USB to UART Bridge Controller and the Mac drivers are available here.

The USB/UART Bridge chip inside the Eagle, K3S and KX3 is an FTDI USB to UART Bridge Controller and the Mac drivers are available here.

Note: macOS built in FTDI driver: Supports FTDI based devices with standard VID/PID combinations.

"Since 10.9 (Mavericks), OS X has included built-in partial support for some FTDI devices in VCP mode. Starting with 10.11 (El Capitan), Apple’s own driver seems to be sufficiently comprehensive that many customers will not need to install FTDI’s own VCP unless they wish to use its advanced features such as baud-rate aliasing and configurable latency times" .

Note the part I italicized and underlined (because I cannot figure out how to highlight in this format)...

If you *never* see the UART identifier, I'm going back to a bad cable regardless of whether or not that cable works with something else. Yes, I have seen cables go bad just "lying there" (that was a lesson in humility for me).

If you never see anything resembling "/dev/tty.usbserial-1444410", even after unplugging, running "ls /dev/tty*" and re-plugging and re-running "ls /dev/tty*,"my thought is you have a USB cable that does not have all the pins needed.

Thanks,
Joel, W4JBB


locked Re: Where I can download WSJT-X 2.9.x? #wsjt-x #IssueReport

Pietro Molina
 

Thanks! 
2.9.x means any of the 2.9 releases...

I2OIM Pietro


locked Re: #WSJTX_config -- USB vs DATA-USB Modes #WSJTX_config

Dave KD2SGM
 

Hi Charles,

I have a Yaesu FTDX 3000 so I’m not sure if these settings will help. I spent a long time searching the internet and it took a while to get it right as everyone seems to have that one little change that makes it all work for them. I use Win4YaesuSuite to control everything so again, this may or may not fix your situation.

FTDX 3000 Menu Settings
#40 CAT RTS - Disable
#65 PC KEYING - Off
#67 DATA MODE - OTHERS
#69 OTHER DSP - 0
#75 DATA IN - USB
#76 DATA MIC GAIN - MCVR
#77 DATA OUT LEVEL - 50
MIC GAIN -20

WSJT-X Settings
Radio - FTDX 3000
Serial Port - COM 10 (COM0COM virtual port)
Baud Rate - 38400 (same as radio)
Data Bits - Default
Stop Bits - Default
Handshake - Default
PTT Method - CAT
Mode - Data/ Pkt
Split - Fake It

Good Luck,
Dave, KD2SGM


locked Re: New Q65 mode report #Q65

Tom Melvin
 

Tell me more about q65 , what program offers it ?

What program offers it: WSJT-X

Quick Start Guide : See WSJT-X web page

WSJT-X page Q65 is mentioned at least 6 times

Google Q65 takes you to quick start guide

Suggest scan those references and come back if any specific questions - your post a little too generic at present.

Tom
GM8MJV




On 24 Jun 2021, at 13:45, Ray Armstrong via groups.io <sallisawfireman@...> wrote:

Tell me more about q65 , what program offers it ?
On Jun 23, 2021, at 5:23 PM, Rory Bowers <k6cks01@...> wrote:

I have been working the new Q65 mode on 6M this week. This new mode is both exciting and works great. We did discover that it doesn't like a /R Rover callsign. It will refuse to send a 73 when it sees that callsign. I am sure that Joe will take care of this in the final release. Great new mode for weak signal!!
73,
Rory, K5CKS




locked Re: Can't open RPM on RHEL 8.4 #IssueReport #linux

Karza
 

OM,

On 24.6.2021 17.42, kempint@... wrote:
[shkemp@unknown00155d000c17 ~]$ sudo dnf install /Downloads/wsjtx-2.4.0.x86_64.rpm
Updating Subscription Management repositories.
Last metadata expiration check: 0:00:56 ago on Thu 24 Jun 2021 10:37:32 AM EDT.
Can not load RPM file: /Downloads/wsjtx-2.4.0.x86_64.rpm.
Could not open: /Downloads/wsjtx-2.4.0.x86_64.rpm

Any suggestions?

It looks like the system can not find your rpm.

Do you really have "Downloads" directory right under the root directory?

Perhaps your folder is under your own account so you should use "~/Downloads/wsjtx-2.4.0.x86_64.rpm" or "/home/shkemp//Downloads/wsjtx-2.4.0.x86_64.rpm"  ?

73's de Kari, oh2gqc


locked Re: Where I can download WSJT-X 2.9.x? #wsjt-x #IssueReport

Karza
 

Hi Pietro,

On 24.6.2021 12.10, Pietro Molina wrote:
It's impossible to resolve the problem at https://wsjtx.groups.io/g/main/topic/watchdoc_v2_4_0/83724265?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,83724265 <https://wsjtx.groups.io/g/main/topic/watchdoc_v2_4_0/83724265?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,83724265> so I need to find the previous release. Is there a repository?
what is WSJT-X 2.9.x? Anyway, old verxions can be found here:

https://sourceforge.net/projects/wsjt/files/

73's de Kari, oh2gqc


locked Re: New FT991A Hamlib Error with WSJT-X and JTDX #WSJTX_config

invl160 Davis
 

Bill....Thanks Bill.  About an hour after I posted I solved it.  Menu item 109 SSB Port Select ---> DATA/USB  was missed and needed to be set to USB.  And also set the COM PORT to the "Enhanced" Port which in my case is com port 7.   The solution probably more to do with the Com Port then  other..
Here is the error message just to close the item:

Thanks for your reply

Frank VO1HP


locked Re: Lost cat (Old problem new to me) #FT8 #Cat_RigControl #WSJTX_config

Dennis Jacobson
 

Thanks Bill your right of course… Bt the problem is resolved .. I saw there was a new beta version out so I installed that one.  It worked just fine after that… I went back to the previous one I was having problems with and it worked just fine also… Can’t explain. It but it is working well again…

Thanks as usual.
Dennis N6NG


locked Some messages are being delayed #special

Roger
 

Before anyone complains again some messages have been slow to reach moderation over the past day or two and I've just cleared a few which are timed before my previous moderation session.

Roger
G#4HZA
moderator


locked Re: Can't open RPM on RHEL 8.4 #IssueReport #linux

Bill Somerville
 

On 24/06/2021 15:42, kempint@... wrote:
[shkemp@unknown00155d000c17 ~]$ sudo dnf install /Downloads/wsjtx-2.4.0.x86_64.rpm
Updating Subscription Management repositories.
Last metadata expiration check: 0:00:56 ago on Thu 24 Jun 2021 10:37:32 AM EDT.
Can not load RPM file: /Downloads/wsjtx-2.4.0.x86_64.rpm.
Could not open: /Downloads/wsjtx-2.4.0.x86_64.rpm

Any suggestions?
OM,

the RPM from the WSJT-X web site (or the project Source Forge site) targets Fedora 33, it may be incompatible with RHEL 8.4 although that is not the error I would expect, it sounds more like a corrupt download (there are SHA256 checksums for each distribution file on in the Source Forge project site files area https://sourceforge.net/projects/wsjt/files/wsjtx-2.4.0/). You should probably build from sources.

73
Bill
G4WJS.


locked Re: Lost cat (Old problem new to me) #FT8 #Cat_RigControl #WSJTX_config

Bill Somerville
 

On 24/06/2021 18:27, Dennis Jacobson wrote:
Well this is a new one for me.. I was running along just fine on FT8, then one day I turned on the radio brought up FT8 and everything looked fine.  Decodes were coming across just fine The minute I tried to tune up, the dreaded HamLib error came up. I was told the configuration was wrong.  I went back and compared the current config. and the original one that I had when I had it running just fine. They are both the same.  Theoretically it should be working.  Nothing else has changed.. I checked the cabling and it as all solid.   The only thing I can think of that just came to mind is a Windows 10 update.. I'll check that and try to undo the latest ones to see if I can find where it happens.  Any other ideas would be welcome. I did check all the USB power options and the are all not allowed to sleep.
OM,

there is no singular Hamlib error, if you don't shared the text of the error message, including details, we can't help you.

73
Bill
G4WJS.


locked Re: New FT991A Hamlib Error with WSJT-X and JTDX #WSJTX_config

Bill Somerville
 

On 24/06/2021 14:51, invl160 Davis wrote:
I have just spent the entire morning trying to figure our why WSJT-X will not interface with a NEW out of the box FT991A.
I am getting a HAMLIB error in both cases.  Using single USB cable.  Will not interface with DX Commander  but appears to connect with
OMNIrig .When the interface setup with OMNIRig it keyed the radio into TX Mode.
I am running WSJT-x Ver 2.4 on a Win 10 Laptop.  I have gone through all of the radio settings and I  think I have them correct having
followed several Youtube setup videos.

The HAMLIB error indicates something wrong in the install of WSJT-X?

Any help?

Frank VO1HP
Frank,

without the text of the error message, including details, there's not much we can do to help you.

73
Bill
G4WJS.


locked #WSJTX_config -- USB vs DATA-USB Modes #WSJTX_config

Charles Albert
 


This is driving me crazy, but I'm not sure I'm even asking the right question. At the risk of giving too much information, please bear with me...

I have a Yaesu FT-991A (with all current firmware) and I want to use FLDIGI and WSJT-X. The rig is connected to the PC running Linux Mint 19.3 (also with all updates) via the USB cable and ports.
FLRIG/FLDIGI can control the rig 100% with no issues. The same goes for WSFT-X and it's limited CAT control.

If I select and use DATA-USB mode, everything seems to work fine...the rig keys, I get data transmission, and all the rest.

And this is where the problem starts...in DATA-USB mode, I never see anything on the respective waterfall and I never hear anything that sounds like data tones from the speaker UNLESS the signal is very strong. However, if I put the rig/software into plain vanilla USB mode, I can see and hear a bunch of signals across the passband, and the software will decode these signals.

BUT...when in USB mode and I try to transmit the rig keys but no data is sent. If the mic "hears" background noise or if I tap the mic, that sound is transmitted.

I've tried Menu Item #106 (SSB MIC SELECT) with the only change being that when in REAR mode, the mic will no longer pick up noise. That is to say, the data is still not transmitted.

I should note that Menu Item #071 (DATA IN SELECT) is set to the default of REAR.

All of this tells me that there is some issue with the rig settings. Maybe.

I'm not sure if there is a problem with the data mode settings that is making the receiver a little deaf or if there is an issue with the software settings that it's not getting the data signals when in DATA-USB mode.

What I'm trying to say is I have run out of ideas!

Any help would be greatly appreciated!

Take Care & 73
de KC6UFM
Charles



locked Re: WSJT-X and Yeasu FT-450D-no transmit power #txaudio

Bill Seward
 

OK, I follow. You can't get db in the mixer. Got to love Windows.

In good news, I've figured out the problem. I feel like an idiot, but I misunderstood the labels on the cable. I thought the labeling was indicative of where to plug them in-IN for mic, OUT for speakers. Uh, no. They're labeled for the signal you're sending via each jack, so OUT is the speaker output and IN is the mic input.

Derp. Sorry to waste everyone's time. At least I'm ready for Field Day. Listen for W4PAR on FT8 or FT4, that will be me on Saturday.


locked Lost cat (Old problem new to me) #FT8 #Cat_RigControl #WSJTX_config

Dennis Jacobson
 

Well this is a new one for me.. I was running along just fine on FT8, then one day I turned on the radio brought up FT8 and everything looked fine.  Decodes were coming across just fine The minute I tried to tune up, the dreaded HamLib error came up. I was told the configuration was wrong.  I went back and compared the current config. and the original one that I had when I had it running just fine. They are both the same.  Theoretically it should be working.  Nothing else has changed.. I checked the cabling and it as all solid.   The only thing I can think of that just came to mind is a Windows 10 update.. I'll check that and try to undo the latest ones to see if I can find where it happens.  Any other ideas would be welcome. I did check all the USB power options and the are all not allowed to sleep.


locked Re: #mac Support for Icom radio Silicon Labs a big issue getting bigger all the time #macOS

Frederick Kent
 

Thanks Joel for the info, however the" /dev/tty.usbserial-1444410" didn't show up or anything close in steps 3-5. I've read in other posts that Catalina is supposed to have the needed drivers. But I don't see them, maybe I need to download a developer Driver Kit?

Fred ND4DX


locked Re: WSJT-X Reporting to PSK Reporter #Beacons

invl160 Davis
 

Settings-->Reporting is enabled but VO1FN does not show as a  Monitor.   MAybe it does not show if it is not continually sending spots.
Puzzling?


locked Can't open RPM on RHEL 8.4 #IssueReport #linux

kempint@...
 

[shkemp@unknown00155d000c17 ~]$ sudo dnf install /Downloads/wsjtx-2.4.0.x86_64.rpm
Updating Subscription Management repositories.
Last metadata expiration check: 0:00:56 ago on Thu 24 Jun 2021 10:37:32 AM EDT.
Can not load RPM file: /Downloads/wsjtx-2.4.0.x86_64.rpm.
Could not open: /Downloads/wsjtx-2.4.0.x86_64.rpm

Any suggestions?


locked New FT991A Hamlib Error with WSJT-X and JTDX #WSJTX_config

invl160 Davis
 

I have just spent the entire morning trying to figure our why WSJT-X will not interface with a NEW out of the box FT991A.
I am getting a HAMLIB error in both cases.  Using single USB cable.  Will not interface with DX Commander  but appears to connect with
OMNIrig .When the interface setup with OMNIRig it keyed the radio into TX Mode.
I am running WSJT-x Ver 2.4 on a Win 10 Laptop.  I have gone through all of the radio settings and I  think I have them correct having
followed several Youtube setup videos.

The HAMLIB error indicates something wrong in the install of WSJT-X?

Any help?

Frank VO1HP

9541 - 9560 of 35397