All known bugs have been fixed and Hamlib 4.5 is close to being released barring any new bugs reported.Please test the latest hamlib -- including Fake It and Rig Split.
Would also like to know any errors or warnings that show up in wsjtx_syslog.log (other than audio dropouts).

Please try this DLL -- this is the 64-bit version.  Looks like I had a typo...

https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dropbox.com%2Fs%2F7aejdv74nfjxr0q%2Flibhamlib-4.dll%3Fdl%3D0&data=05%7C01%7C%7C86d81b67c5014c66dcc708da71b0e712%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637947301854595242%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wHTGsP5L%2BwUQc2t248bONNvkLfxo5s9qPj6i2FUnJaw%3D&reserved=0


If it still takes too long...
Please place this file as described below
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dropbox.com%2Fs%2Ft52ngcalsgnpm8m%2Fwsjtx_log_config.ini%3Fdl%3D0&data=05%7C01%7C%7C86d81b67c5014c66dcc708da71b0e712%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637947301854595242%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=v%2FZnnWHtWTRP5q07QpzjSuYecMo92QYOeuH7krsRjlM%3D&reserved=0

C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location

For Linux put it in
~/.config
The WSJT-X_Rigcontrol.log file will be here:
~/.local/share/WSJT-X

Restart WSJT-X and duplicate the problem.
Shut down WSJT-X

Then send me the WSJT-X_RigControl.log file

Mike W9MDB

Mike,

Yes, WSJT-X now connects to the rig immediately. I re-checked split using "rig" and "fake it", and they work fine also. However, there were still some warnings in the wsjtx_syslog.log not related to audio dropouts. I have included that part of the log. I also followed the instructions for the WSJT-X_RigControl.log, and have attached that file.

Mike,

Yes, WSJT-X now connects to the rig immediately. I re-checked split
using "rig" and "fake it", and they work fine also. However, there
were still some warnings in the wsjtx_syslog.log not related to audio
dropouts. I have included that part of the log. I also followed the
instructions for the WSJT-X_RigControl.log, and have attached that file.

Mike,

Yes, WSJT-X now connects to the rig immediately. I re-checked split
using "rig" and "fake it", and they work fine also. However, there
were still some warnings in the wsjtx_syslog.log not related to audio
dropouts. I have included that part of the log. I also followed the
instructions for the WSJT-X_RigControl.log, and have attached that file.

Again without the danged HTML formattiing fiasco...

It looks like the FT5000 isn't executing the FB command before responding to the the follow up query.
Let's try increasing the post_write_delay

Put this into a file called hamllib_settings.json and put that file into the same place as WSJT-X.ini
The current post_write_delay is 5ms.  So let's bump it up to 20ms and see if that warning goes away.
If it does NOT go away try increasing it to 50ms and then 100ms.
If 20ms works try 15ms and then 10ms to see where the threshold is.

{
     "config": {
            "post_write_delay": "20",
     }
}

Mike W9MDB









On Saturday, July 30, 2022 at 10:20:42 AM CDT, Michael Black via groups.io <mdblack98@...> wrote:





It looks like the FT5000 isn't executing the FB command before responding to the the follow up query.Let's try increasing the post_write_delay
Put this into a file called hamllib_settings.json and put that file into the same place as WSJT-X.iniThe current post_write_delay is 5ms.  So let's bump it up to 20ms and see if that warning goes away.If it does NOT go away try increasing it to 50ms and then 100ms. If 20ms works try 15ms and then 10ms to see where the threshold is.
{     "config": {            "post_write_delay": "20",     }
}
Mike W9MDB



    On Saturday, July 30, 2022 at 08:01:58 AM CDT, Jim Preston N6VH <n6vh@...> wrote:

Mike,

The attachment didn't come through. Here is a link to the file on Dropbox:

https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dropbox.com%2Fs%2Fo97q3d0c773p750%2FWSJT-X_RigControl.log%3Fdl%3D0&;data=05%7C01%7C%7Cc95efc8f4b1c4f9e7a6708da723f3230%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637947912990575001%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=Voho4z%2F8k21o1lhQ0BVj7Z0x%2FVd3bF0dX4bbYzYBqHI%3D&amp;reserved=0

73,

Jim N6VH

On 7/29/2022 10:47 PM, Jim Preston N6VH wrote:

Mike,

Yes, WSJT-X now connects to the rig immediately. I re-checked split
using "rig" and "fake it", and they work fine also. However, there
were still some warnings in the wsjtx_syslog.log not related to audio
dropouts. I have included that part of the log. I also followed the
instructions for the WSJT-X_RigControl.log, and have attached that file.

Again without the danged HTML formattiing fiasco...

It looks like the FT5000 isn't executing the FB command before responding to the the follow up query.
Let's try increasing the post_write_delay

Put this into a file called hamllib_settings.json and put that file into the same place as WSJT-X.ini
The current post_write_delay is 5ms.  So let's bump it up to 20ms and see if that warning goes away.
If it does NOT go away try increasing it to 50ms and then 100ms.
If 20ms works try 15ms and then 10ms to see where the threshold is.

{
       "config": {
              "post_write_delay": "20",
       }
}

Mike W9MDB









On Saturday, July 30, 2022 at 10:20:42 AM CDT, Michael Black via groups.io <mdblack98@...> wrote:





It looks like the FT5000 isn't executing the FB command before responding to the the follow up query.Let's try increasing the post_write_delay
Put this into a file called hamllib_settings.json and put that file into the same place as WSJT-X.iniThe current post_write_delay is 5ms.  So let's bump it up to 20ms and see if that warning goes away.If it does NOT go away try increasing it to 50ms and then 100ms. If 20ms works try 15ms and then 10ms to see where the threshold is.
{     "config": {            "post_write_delay": "20",     }
}
Mike W9MDB



      On Saturday, July 30, 2022 at 08:01:58 AM CDT, Jim Preston N6VH <n6vh@...> wrote:

Mike,

The attachment didn't come through. Here is a link to the file on Dropbox:

https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dropbox.com%2Fs%2Fo97q3d0c773p750%2FWSJT-X_RigControl.log%3Fdl%3D0&data=05%7C01%7C%7Cc95efc8f4b1c4f9e7a6708da723f3230%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637947912990575001%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Voho4z%2F8k21o1lhQ0BVj7Z0x%2FVd3bF0dX4bbYzYBqHI%3D&reserved=0

73,

Jim N6VH

On 7/29/2022 10:47 PM, Jim Preston N6VH wrote:

Mike,

Yes, WSJT-X now connects to the rig immediately. I re-checked split
using "rig" and "fake it", and they work fine also. However, there
were still some warnings in the wsjtx_syslog.log not related to audio
dropouts. I have included that part of the log. I also followed the
instructions for the WSJT-X_RigControl.log, and have attached that file.

   

Try this DLL

https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dropbox.com%2Fs%2F7aejdv74nfjxr0q%2Flibhamlib-4.dll%3Fdl%3D0&;data=05%7C01%7C%7C3438b6c46d3e466c77d708da724ce6b1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637947971850034828%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=ZwE96F1j%2FRgecM042JD33GM1rSwwAKtNOYGomwDvtjw%3D&amp;reserved=0

Make sure the frequency does get set correctly when moving on the waterfall.
I suspect the DX5000 just can't handle two commands together in this case just like the DX3000 can't.

Mike W9MDB








On Saturday, July 30, 2022 at 11:21:57 AM CDT, Jim Preston N6VH <n6vh@...> wrote:





Mike,

I set the number as high as 10000, and still got the warnings. The
warnings are generated whenever I change the audio offset for xmit (the
red mark in the wide graph). Also, this only happens if I am using "rig"
split, not "fake it". As far as I can tell with the brief tests I have
done, it doesn't seem to cause any operational problems.

73,

Jim N6VH

On 7/30/2022 8:21 AM, Michael Black via groups.io wrote:

Again without the danged HTML formattiing fiasco...

It looks like the FT5000 isn't executing the FB command before responding to the the follow up query.
Let's try increasing the post_write_delay

Put this into a file called hamllib_settings.json and put that file into the same place as WSJT-X.ini
The current post_write_delay is 5ms.  So let's bump it up to 20ms and see if that warning goes away.
If it does NOT go away try increasing it to 50ms and then 100ms.
If 20ms works try 15ms and then 10ms to see where the threshold is.

{
       "config": {
              "post_write_delay": "20",
       }
}

Mike W9MDB









On Saturday, July 30, 2022 at 10:20:42 AM CDT, Michael Black via groups.io <mdblack98@...> wrote:





It looks like the FT5000 isn't executing the FB command before responding to the the follow up query.Let's try increasing the post_write_delay
Put this into a file called hamllib_settings.json and put that file into the same place as WSJT-X.iniThe current post_write_delay is 5ms.  So let's bump it up to 20ms and see if that warning goes away.If it does NOT go away try increasing it to 50ms and then 100ms. If 20ms works try 15ms and then 10ms to see where the threshold is.
{     "config": {            "post_write_delay": "20",     }
}
Mike W9MDB



      On Saturday, July 30, 2022 at 08:01:58 AM CDT, Jim Preston N6VH <n6vh@...> wrote:

Mike,

The attachment didn't come through. Here is a link to the file on Dropbox:

https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dropbox.com%2Fs%2Fo97q3d0c773p750%2FWSJT-X_RigControl.log%3Fdl%3D0&;data=05%7C01%7C%7C3438b6c46d3e466c77d708da724ce6b1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637947971850034828%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=hNrPZcnJN5xLf2fWGHY5aPCIsG1CcIl4AthdUH0oVQw%3D&amp;reserved=0

73,

Jim N6VH

On 7/29/2022 10:47 PM, Jim Preston N6VH wrote:

Mike,

Yes, WSJT-X now connects to the rig immediately. I re-checked split
using "rig" and "fake it", and they work fine also. However, there
were still some warnings in the wsjtx_syslog.log not related to audio
dropouts. I have included that part of the log. I also followed the
instructions for the WSJT-X_RigControl.log, and have attached that file.

On Aug 9, 2022, at 1:56 PM, John Reardon <kd9ron@...> wrote:

All things considered, if you are running an EFHW antenna it is RF causing your problems. I have the same issue and would have been frustrated but for the advice Tavis gave me when we set it up....he said, time to start buying beads and toroids. The ICOM USB cable does not reject RF at all from what I can tell. Although I did not cut the cable open it doesn't appear to be shielded. I went through several shielded cables before I landed on a good one.
Check your USB cable first.
I added about five ferrite beads to the ICOM cable without luck. Tried a toroid with five wraps, still no luck. Finally got a very thick double shielded cable with factory installed ferrites on each end which worked.
As a side note, my laptop's mousepad is also effected by each transmission. No problem unless I am using it during the transmission, then it goes where it wants.

Sent from AT&T Yahoo Mail on Android

On Tue, Aug 9, 2022 at 1:26 PM, dl8le<dl8le@...> wrote: Hello,

as I have continous problems with the IC7300 and CAT control in our clubstation I have installed the new hamlib-4.dll as well.

I was unable to get WSJT-X to work properly in communicating with the IC7300 using the W10 station PC. It is important to note, however, that all the other programs I have tried (DXLab Commander, Multipsk together with DXLab Commander, FLRig with FLDigi, JTDX) there was no problem in the communication. When I used WSJT-X, however, controlling directly the IC7300 or controlling with DXLab Commander as separate CAT program, the program failed in the CAT control after about 5 - 10 min. It was always necessary to re-start PC and radio to try again. It was interesting to see that during those failures the waterfall did not show any signals (was just black) but the signals were still decoded..

I have then tested the IC7300 with WSJT-X using my W11 Asus ZenBook. There were no problems in the CAT control of the IC7300 (connecting the IC7300 directly to WSJT-X or via DXLab Suit Commander with DXLab Commander as CAT control (I did not test with N1MM). I stopped after about 1 hour without the communication problem I have at the W10 PC. Just for information: the audio level for the input was far too low, it was impossible to get a good audio quality but I assume this is related to the IC7300 driver (the Asus ZenBook works very well with WSJT-X on a set up with other radios such as Flex 6600 or Yaesu FT1000).

Just for info: I have switchted off all power saving for the PC as well as for all devices like USB-ports etc.)

It would be nice if there would be a way to use the IC7300 with the club station PC as well and I could get some help here other than spending money for a new W11 PC.


73

Juergen, DL8LE

Russ

When I called Icom for help, their tech support recommended using the
Tripp-Lite USB cable with integral ferrite cores molded near each end of
the cable. I found the cables online and ordered a couple. In my case
there was no improvement using them. Best solution I found was to replace
the radio with something other than Icom.

Regards
Chuck WD4HXG

I don't own one of these, hut I really struggle to come up with a valid reason that using an isolated external interface like a SignaLink and a decent serial interface woild not be a simple, trivial, solution, with no financial beatdown as would be the case buying a new radio.

On August 9, 2022 7:52:24 PM CDT, "Chuck Moore via groups.io"<wd4hxg@...> wrote:

Russ

When I called Icom for help, their tech support recommended using the
Tripp-Lite USB cable with integral ferrite cores molded near each end of
the cable. I found the cables online and ordered a couple. In my case
there was no improvement using them. Best solution I found was to replace
the radio with something other than Icom.

Regards
Chuck WD4HXG

On Aug 9, 2022, at 8:52 PM, Chuck Moore via groups.io <wd4hxg@...> wrote:

Russ

When I called Icom for help, their tech support recommended using the
Tripp-Lite USB cable with integral ferrite cores molded near each end of
the cable. I found the cables online and ordered a couple. In my case
there was no improvement using them. Best solution I found was to replace
the radio with something other than Icom.

Regards
Chuck WD4HXG