Date
1 - 6 of 6
Locked Getting wsjtx to run on mac monterey with Yaesu ft991 Transceiver #Cat_RigControl
Tom Arny
I am trying to get wsjtx to run on a new iMac using Monterey OS and M chip and a Yaesu FT991 transceiver. I am confused about whether I need SiLab drivers or not. I've searched Google and watched several videos, but none seem to address my problem. WSJT opens and displays signals but the CAT control doesn't work. Audio codec shows in both wsjt and the mac preferences. A SiLabs driver shows in the Mac extensions, but it says "not loaded". When I click on "Test CAT", a diagnostic flashes on screen saying "resource busy". On the Radio Settings menu I see nothing that identifies a SiLab driver. The serial port choice that seems most likely shows "/dev/tty.wlan-debug", but that doesn't look very promising. I am using a single USB cable to connect the transceiver to the mac. It works fine on my old macbook pro, so I suspect I'm doing something really dumb, but can't figure out what. Suggestions welcome and thank you.
|
|
Keith Onishi
I am not sure if your problem is same as mine.
toggle quoted message
Show quoted text
When I migrated from my old MacBook Pro to Mi Pro MacBook Pro and Monterey, I found that the FTDI driver which worked fine with KX3 on my old MacBook Pro did not run on the new environment. I downloaded and installed the latest version of FTDI driver, still beta version. This solved the problem and WSJT-X works fine with KX3. 73 de JH3SIF, Keith 2022/05/06 3:57、Tom Arny <tarny@...>のメール: |
|
Good Morning Gentlemen,
I am running Monterey on my MacBook Pro M1 pro and version 2.5.4 of WSJTX. You will need to install the latest Silicon Labs drivers. I believe the current version is 6.0.1(approximate version number). Once the drivers are installed you will need to configure them using the Midi Setup app in the Utilities/Other folder which is accessible from Launchpad. Bare in mind that there is a bug in 2.5.4 where the Transmit audio out is wonky and the setting is reversed so I would recommend using version 2.5.2 until the fix the Qt element in the next version of WSJTX. If you have any questions please feel free to email me. I am using a Yaesu 991A Regards and 73, Bob Murphy N1KWH |
|
James Todd
All:
I use WSJT-X on an M1 Mac with Monterey, but gave up on the Mac version of WSJT-X because it would not reliably turn on transmitting and required a hack to make the modification to the shared memory allocation stick. I would also prefer not to change system settings such as the shared memory. I initially though the problems I was seeing were a driver issue. But, they seem to be inherent in some aspect of WSJT-X itself, or its interaction with the system. I could literally never make WSJT-X work reliably on any of my Intel or M1 Macs. Instead I run a 32-bit Windows version of WSJT-X in Crossover Mac with RUMLOG, interfaced through a standard USB-serial interface. I have so far not found any of these that didn't work, even the super-cheap ones, with the downloaded drivers. Every transceiver I've tried with RUMLOG works with this configuration: TS-2000, Yaesu FT-8x7, TS-50, FT-920, and an Icom with the CI-V interface. This actually works better than the Mac version in terms of reliability, doesn't require any system-level modifications, and doesn't even require that Windows be installed. You can even do a small registry edit with the Windows editor, and WSJT-X will interface directly through USB without having to talk through a Mac program. Basically, this routes a COM port to a USB-serial output. I am sometimes puzzled about why I have to do a system memory allocation modification to run the Mac version of WSJT-X but not the Windows version on the same machine. Remember, this is not being run through Windows, but directly on the Mac using Crossover (a version of WINE). But, there's a caveat. The audio is relatively easy. It comes through various interfaces without drivers, usually as some version of USB AUDIO CODEC as routed by the AUDIO-MIDI settings. As many have noted, finding divers for the interface can be a problem no matter what, especially given that even the "genuine" interface chips are sometimes not that. My solution was to find a driver that finally worked with each interface, and get rid of all the ones that didn't work with anything. Jim WB0KWJ |
|
Tom Arny
Thank you all for suggestions for getting my FT991 to run on a mac. I would swear that I read someplace that drivers were not needed if you are running on Monterey with the M chip, but I couldn't make that happen. Downloading the drivers from SiLabs did get WSJTx working and I made a few QSO's. However, another problem has emerged: the time on the mac clock with Monterey is extremely hard to set to sufficient accuracy. On my old mac and macbooks, getting the dt in the wsjtx screen down to 0.1 or so seconds is straightforward. Not so with Monterey, at least on my machine, where it runs at typically a full second off. I even took the mac back to the dealer and they couldn't get it reliably to a smaller time error. I've searched a fair bit on Google and it seems to be an apple problem on OS versions later than Big Sur....at least I have seen a few complaints similar to mine about the time. I'm now researching alternative was to synchronize the mac clock. I'll continue to enjoy wsjtx on my old macs while I try to figure out the time synching. That old sinking feeling... Thank you all again.
|
|
Gary Rogers
Not sure about the M1 chip but I use Chrony Control to regulate time sync on my MacBook Pro with an Intel chip.
toggle quoted message
Show quoted text
https://www.whatroute.net/chronycontrol.html On May 7, 2022, at 11:37 AM, Tom Arny <tarny@...> wrote: |
|