Tim,

I did, 19200. I also tried 9600. And again, a good suggestion. But there have been further developments since our last email exchange.

Michael Black called me this afternoon and took control of my computer via AnyDesk. He was able to see the issue first hand and do some diagnostics. It does appear that in WSJT-X 2.5.4 there is an issue with the FT-5000 interface. It wasn't a ID10T error ;-) I had been holding off upgrading to the latest release given that it's only a few days old and I wanted to spend some time learning the rig now that I had everything working. There's a lot you can do with the 5000. I did download the latest version of WSJT-X yesterday and was planning on installing it in a couple of weeks. I wanted to see if it would resolved the FT 5000 problem. Additionally, most experienced Windows users have learned the hard way that you never install v1 of any GA release, ya wait for the damn patches..... Michael went ahead and installed it and everything worked just fine using my same settings. So it does appear the issue is resolved with the newer version of WSJT-X.

So for all you FT DX 5000 owners, don't be afraid to install the latest version of WSJT-X. I've not spent hours and hours with it - but it did resolve the issue with the Yaesu FT dx 5000 and so far appears to be a solid build on Windows 10.

Gene

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Tim Dawson
Sent: Friday, January 20, 2023 12:34 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #Yaesu FT DX 5000, SCU-17 - won't transmit (solved)

Have you tried any other speeds? In all the searches I have done on your combo, folks seem to be running 4800 . . . Wondering if WSJTX might be orking the higher speeds . . .

Just a thought . . .

On January 20, 2023 1:29:57 PM CST, Eugene Morgan <ee_morgan@...> wrote:

Yes they match 38400, #32 in the rig, OmniRig, and WSJT-X. If they didn't OmniRig would also not be able to communicate with the radio, nor would PCC-5000, they all work fine except WSJT-X. I also confirmed in device manager 38400,8,n,1. All match. But thanks for the suggestion. That would be the first thing I would check as well, so good suggestion.

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Tim Dawson
Sent: Friday, January 20, 2023 12:23 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #Yaesu FT DX 5000, SCU-17 - won't transmit (solved)

Baud rate on the radio (item #32, iirc) and on the computer?

On January 20, 2023 12:03:29 PM CST, Eugene Morgan <ee_morgan@...> wrote:

Michael,

I uploaded the files as you requested. I hope they can shed some light on what’s not working. So that you know how these logs were generated I have detailed out my process of creating the two files I uploaded.

1. Turned my FTDX 5000 on and brought up WSJT-X and started decoding
2. I changed the configuration from OmniRig to the FT-5000. I made no other changes to my configuration. I didn’t confirm the settings for COM 8, they were 8,n,1. I left both the RTS and DTS unchecked.
3. I shutdown WSJT-X
4. I deleted the old syslog
5. Rebooted my machine to make sure that OmniRig didn't load
6. Confirmed that OmniRig didn’t load. FYI: it’s not listed in the my startups tab in Task manager
7. I brought up WSJT-X and it made a new syslog.
8. I waited to collect several minutes of decoding - WSJT-X was not able to talk to the FT-5000 the entire time
9. I shutdown WSJT-X
10. I copied the syslog and renamed it to (FTDX5000)wsjtx_syslog.log (it’s uploaded to dropbox)
11. I deleted the syslog
12. I loaded OmniRig
13. I brought up WSJT-X and changed the configuration back to OmniRig
14. Everything started working fine
15. I let it do a few decodes and then shutdown WSJT-X
16. I copied the syslog to another folder and uploaded to dropbox
17. Wrote this email

If you have any suggestions or questions please don’t hesitate to ask. I’ll hold off installing the new hamlib. I down loaded both it and the new GA release of WSJT-X but have not installed them. I’m kind of at a place where I’m thinking, “if it aint broke don’t fix it.” But I will installed them if you would like me to.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.