locked Hamlib 4.5 testing #hamlib


Michael Black
 

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).
===========================================================New hamlib for installation directions
#1 Shut down WSJTX/JTDX
#2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times.
If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there.
http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll
http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll
Linux/Unix/Mac users need to compile the latest tar file from http://n0nb.users.sourceforge.net/\Note: If compiling on Unix-like systems please uninstall any Hamlib package you have before installing the new build
#3 If you don't save directly you need to open a file browser and move the file that way.
If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk
Mike W9MDB


Jim Preston N6VH
 

On 7/29/2022 8:49 AM, Michael Black via groups.io wrote:
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).
Joe,

I tested with both "Rig" (which is what I normally use) and "Fake It". In both cases, the rig control behaved as it should.

However, with the new file, it takes about five seconds to connect to the rig. With previous version, this was almost immediate. After it connected, everything worked as it shoul.

I have included the part of the syslog.log from the time I started using the new file. I don't know how much is important, but I did notice what might be some important issues (or not).

73,

Jim N6VH


[SYSLOG][2022-07-29 21:26:05.236864][00:00:00.000409][info] Log Start
[SYSLOG][2022-07-29 21:26:05.237861][00:00:00.000435][info] WSJT-X   v2.5.4 d28164  by K1JT, G4WJS, K9AN, and IV3NWV - Program startup
[SYSLOG][2022-07-29 21:26:05.242848][00:00:00.005463][info] locale: language: English script: Latin country: United States ui-languages: en-US
[SYSLOG][2022-07-29 21:26:05.242848][00:00:00.005591][info] Loaded Qt translations for current locale from resources
[SYSLOG][2022-07-29 21:26:05.242848][00:00:00.005615][info] Loaded WSJT-X base translation file from :/Translations based on language en
[SYSLOG][2022-07-29 21:26:05.242848][00:00:00.005660][info] Loaded WSJT-X translations for current locale from resources
[SYSLOG][2022-07-29 21:26:05.264817][00:00:00.027903][info] shmem size: 48275456
[RIGCTRL][2022-07-29 21:26:05.276757][00:00:00.040304][info] Hamlib version: Hamlib 4.5~git Fri Jul 29 04:26:35 2022 +0000 SHA=36c777
[RIGCTRL][2022-07-29 21:26:09.500219][00:00:04.262818][warning] read_string_generic(): Timed out 3.123 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:26:12.662561][00:00:07.425209][warning] read_string_generic(): Timed out 3.116 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:26:12.662561][00:00:07.425265][error] newcat_open: FTDX5000 CAT RATE error: rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1
cmd_str = EX0331
    4:newcat.c(10425):newcat_set_cmd_validate entered
newcat_set_cmd_validate: priv->cmd_str=EX0331
newcat_set_cmd_validate: EX0331 not implemented
    4:newcat.c(10519):newcat_set_cmd_validate returning(-4) Feature not implemented

newcat_set_cmd: newcat_set_cmd_validate not implemented...continuing
write_block(): TX 6 bytes, method=2
0000    45 58 30 33 33 31 EX0331
cmd_str = ID;
write_block(): TX 3 bytes, method=2
0000    49 44 3b ID;
read_string_generic called, rxmax=129 direct=1
read_string_generic(): Timed out 3.116 seconds after 0 chars, direct=1
   3:newcat.c(10764):newcat_set_cmd returning(-5) Communication timed out

Communication timed out
Communication timed out
[SYSLOG][2022-07-29 21:26:29.399816][00:00:24.161050][warning] Detected dropped audio source samples: 768 (0.016 S)
[RIGCTRL][2022-07-29 21:26:50.409232][00:00:45.167278][warning] newcat_set_cmd_validate: cmd validation failed, 'FB18100000;'!='FB18099000;', try#1
[RIGCTRL][2022-07-29 21:26:56.700531][00:00:51.457807][warning] newcat_set_cmd_validate: cmd validation failed, 'FB18100500;'!='FB18100000;', try#1
[SYSLOG][2022-07-29 21:27:14.455652][00:01:09.211544][warning] Detected dropped audio source samples: 624 (0.013 S)
[RIGCTRL][2022-07-29 21:27:33.278047][00:01:28.030823][warning] read_string_generic(): Timed out 2.096 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:27:35.396281][00:01:30.149050][warning] read_string_generic(): Timed out 2.096 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:27:35.396281][00:01:30.149097][error] newcat_open: FTDX5000 CAT RATE error: rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1
cmd_str = EX0331
    4:newcat.c(10425):newcat_set_cmd_validate entered
newcat_set_cmd_validate: priv->cmd_str=EX0331
newcat_set_cmd_validate: EX0331 not implemented
    4:newcat.c(10519):newcat_set_cmd_validate returning(-4) Feature not implemented

newcat_set_cmd: newcat_set_cmd_validate not implemented...continuing
write_block(): TX 6 bytes, method=2
0000    45 58 30 33 33 31 EX0331
cmd_str = ID;
write_block(): TX 3 bytes, method=2
0000    49 44 3b ID;
read_string_generic called, rxmax=129 direct=1
read_string_generic(): Timed out 2.096 seconds after 0 chars, direct=1
   3:newcat.c(10764):newcat_set_cmd returning(-5) Communication timed out

Communication timed out
Communication timed out
[RIGCTRL][2022-07-29 21:28:18.881722][00:02:13.629536][warning] read_string_generic(): Timed out 2.093 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:28:21.010333][00:02:15.758147][warning] read_string_generic(): Timed out 2.107 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:28:21.010333][00:02:15.758191][error] newcat_open: FTDX5000 CAT RATE error: rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1
cmd_str = EX0331
    4:newcat.c(10425):newcat_set_cmd_validate entered
newcat_set_cmd_validate: priv->cmd_str=EX0331
newcat_set_cmd_validate: EX0331 not implemented
    4:newcat.c(10519):newcat_set_cmd_validate returning(-4) Feature not implemented

newcat_set_cmd: newcat_set_cmd_validate not implemented...continuing
write_block(): TX 6 bytes, method=2
0000    45 58 30 33 33 31 EX0331
cmd_str = ID;
write_block(): TX 3 bytes, method=2
0000    49 44 3b ID;
read_string_generic called, rxmax=129 direct=1
read_string_generic(): Timed out 2.107 seconds after 0 chars, direct=1
   3:newcat.c(10764):newcat_set_cmd returning(-5) Communication timed out

Communication timed out
Communication timed out


Michael Black
 

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

https://www.dropbox.com/s/7aejdv74nfjxr0q/libhamlib-4.dll?dl=0


If it still takes too long...
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=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

On Friday, July 29, 2022 at 04:56:32 PM CDT, Jim Preston N6VH <n6vh@...> wrote:






On 7/29/2022 8:49 AM, Michael Black via groups.io wrote:
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).

Joe,

I tested with both "Rig" (which is what I normally use) and "Fake It".
In both cases, the rig control behaved as it should.

However, with the new file, it takes about five seconds to connect to
the rig. With previous version, this was almost immediate. After it
connected, everything worked as it shoul.

I have included the part of the syslog.log from the time I started using
the new file. I don't know how much is important, but I did notice what
might be some important issues (or not).

73,

Jim N6VH


[SYSLOG][2022-07-29 21:26:05.236864][00:00:00.000409][info] Log Start
[SYSLOG][2022-07-29 21:26:05.237861][00:00:00.000435][info] WSJT-X  
v2.5.4 d28164  by K1JT, G4WJS, K9AN, and IV3NWV - Program startup
[SYSLOG][2022-07-29 21:26:05.242848][00:00:00.005463][info] locale:
language: English script: Latin country: United States ui-languages: en-US
[SYSLOG][2022-07-29 21:26:05.242848][00:00:00.005591][info] Loaded Qt
translations for current locale from resources
[SYSLOG][2022-07-29 21:26:05.242848][00:00:00.005615][info] Loaded
WSJT-X base translation file from :/Translations based on language en
[SYSLOG][2022-07-29 21:26:05.242848][00:00:00.005660][info] Loaded
WSJT-X translations for current locale from resources
[SYSLOG][2022-07-29 21:26:05.264817][00:00:00.027903][info] shmem size:
48275456
[RIGCTRL][2022-07-29 21:26:05.276757][00:00:00.040304][info] Hamlib
version: Hamlib 4.5~git Fri Jul 29 04:26:35 2022 +0000 SHA=36c777
[RIGCTRL][2022-07-29 21:26:09.500219][00:00:04.262818][warning]
read_string_generic(): Timed out 3.123 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:26:12.662561][00:00:07.425209][warning]
read_string_generic(): Timed out 3.116 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:26:12.662561][00:00:07.425265][error]
newcat_open: FTDX5000 CAT RATE error: rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1
cmd_str = EX0331
    4:newcat.c(10425):newcat_set_cmd_validate entered
newcat_set_cmd_validate: priv->cmd_str=EX0331
newcat_set_cmd_validate: EX0331 not implemented
    4:newcat.c(10519):newcat_set_cmd_validate returning(-4) Feature not
implemented

newcat_set_cmd: newcat_set_cmd_validate not implemented...continuing
write_block(): TX 6 bytes, method=2
0000    45 58 30 33 33 31 EX0331
cmd_str = ID;
write_block(): TX 3 bytes, method=2
0000    49 44 3b ID;
read_string_generic called, rxmax=129 direct=1
read_string_generic(): Timed out 3.116 seconds after 0 chars, direct=1
   3:newcat.c(10764):newcat_set_cmd returning(-5) Communication timed out

Communication timed out
Communication timed out
[SYSLOG][2022-07-29 21:26:29.399816][00:00:24.161050][warning] Detected
dropped audio source samples: 768 (0.016 S)
[RIGCTRL][2022-07-29 21:26:50.409232][00:00:45.167278][warning]
newcat_set_cmd_validate: cmd validation failed,
'FB18100000;'!='FB18099000;', try#1
[RIGCTRL][2022-07-29 21:26:56.700531][00:00:51.457807][warning]
newcat_set_cmd_validate: cmd validation failed,
'FB18100500;'!='FB18100000;', try#1
[SYSLOG][2022-07-29 21:27:14.455652][00:01:09.211544][warning] Detected
dropped audio source samples: 624 (0.013 S)
[RIGCTRL][2022-07-29 21:27:33.278047][00:01:28.030823][warning]
read_string_generic(): Timed out 2.096 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:27:35.396281][00:01:30.149050][warning]
read_string_generic(): Timed out 2.096 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:27:35.396281][00:01:30.149097][error]
newcat_open: FTDX5000 CAT RATE error: rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1
cmd_str = EX0331
    4:newcat.c(10425):newcat_set_cmd_validate entered
newcat_set_cmd_validate: priv->cmd_str=EX0331
newcat_set_cmd_validate: EX0331 not implemented
    4:newcat.c(10519):newcat_set_cmd_validate returning(-4) Feature not
implemented

newcat_set_cmd: newcat_set_cmd_validate not implemented...continuing
write_block(): TX 6 bytes, method=2
0000    45 58 30 33 33 31 EX0331
cmd_str = ID;
write_block(): TX 3 bytes, method=2
0000    49 44 3b ID;
read_string_generic called, rxmax=129 direct=1
read_string_generic(): Timed out 2.096 seconds after 0 chars, direct=1
   3:newcat.c(10764):newcat_set_cmd returning(-5) Communication timed out

Communication timed out
Communication timed out
[RIGCTRL][2022-07-29 21:28:18.881722][00:02:13.629536][warning]
read_string_generic(): Timed out 2.093 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:28:21.010333][00:02:15.758147][warning]
read_string_generic(): Timed out 2.107 seconds after 0 chars, direct=1
[RIGCTRL][2022-07-29 21:28:21.010333][00:02:15.758191][error]
newcat_open: FTDX5000 CAT RATE error: rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1
cmd_str = EX0331
    4:newcat.c(10425):newcat_set_cmd_validate entered
newcat_set_cmd_validate: priv->cmd_str=EX0331
newcat_set_cmd_validate: EX0331 not implemented
    4:newcat.c(10519):newcat_set_cmd_validate returning(-4) Feature not
implemented

newcat_set_cmd: newcat_set_cmd_validate not implemented...continuing
write_block(): TX 6 bytes, method=2
0000    45 58 30 33 33 31 EX0331
cmd_str = ID;
write_block(): TX 3 bytes, method=2
0000    49 44 3b ID;
read_string_generic called, rxmax=129 direct=1
read_string_generic(): Timed out 2.107 seconds after 0 chars, direct=1
   3:newcat.c(10764):newcat_set_cmd returning(-5) Communication timed out

Communication timed out
Communication timed out


Jim Preston N6VH
 

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.

My computer is Win 10, I7 9700 3 GHz, 32 gig RAM, SSD as the main drive.

Incidentally, I notice the newest libhamlib-4.dll file is about twice the size of even the one I downloaded earlier today, as well as the one I had been using.

Here is the selection from the wsjtx_syslog.log I mentioned:

[SYSLOG][2022-07-30 05:14:44.541098][00:00:00.000382][info] Log Start
[SYSLOG][2022-07-30 05:14:44.541098][00:00:00.000407][info] WSJT-X   v2.5.4 d28164  by K1JT, G4WJS, K9AN, and IV3NWV - Program startup
[SYSLOG][2022-07-30 05:14:44.556693][00:00:00.006993][info] locale: language: English script: Latin country: United States ui-languages: en-US
[SYSLOG][2022-07-30 05:14:44.556693][00:00:00.007145][info] Loaded Qt translations for current locale from resources
[SYSLOG][2022-07-30 05:14:44.556693][00:00:00.007169][info] Loaded WSJT-X base translation file from :/Translations based on language en
[SYSLOG][2022-07-30 05:14:44.556693][00:00:00.007226][info] Loaded WSJT-X translations for current locale from resources
[SYSLOG][2022-07-30 05:14:44.563198][00:00:00.027595][info] shmem size: 48275456
[RIGCTRL][2022-07-30 05:14:44.578840][00:00:00.039559][info] Hamlib version: Hamlib 4.5~git Fri Jul 29 22:18:51 2022 +0000 SHA=388012
[SYSLOG][2022-07-30 05:15:14.384093][00:00:29.830946][warning] Detected dropped audio source samples: 1152 (0.024 S)
[RIGCTRL][2022-07-30 05:15:55.004020][00:01:10.446214][warning] newcat_set_cmd_validate: cmd validation failed, 'FB03573500;'!='FB03572000;', try#1
[RIGCTRL][2022-07-30 05:16:04.784023][00:01:20.225016][warning] newcat_set_cmd_validate: cmd validation failed, 'FB03573000;'!='FB03573500;', try#1
[RIGCTRL][2022-07-30 05:16:11.671805][00:01:27.111784][warning] newcat_set_cmd_validate: cmd validation failed, 'FB03572500;'!='FB03573000;', try#1
[RIGCTRL][2022-07-30 05:16:20.668571][00:01:36.107416][warning] newcat_set_cmd_validate: cmd validation failed, 'FB03573000;'!='FB03572500;', try#1
[RIGCTRL][2022-07-30 05:16:23.667523][00:01:39.105877][warning] newcat_set_cmd_validate: cmd validation failed, 'FB03572000;'!='FB03573000;', try#1
[RIGCTRL][2022-07-30 05:16:32.797011][00:01:48.234232][warning] newcat_set_cmd_validate: cmd validation failed, 'FB03571500;'!='FB03572000;', try#1
[RIGCTRL][2022-07-30 05:18:14.682987][00:03:30.107162][warning] newcat_set_cmd_validate: cmd validation failed, 'FB03572000;'!='FB03571500;', try#1
[SYSLOG][2022-07-30 05:19:29.400862][00:04:44.815212][warning] Detected dropped audio source samples: -480 (-0.01 S)
[SYSLOG][2022-07-30 05:20:44.400199][00:05:59.805305][warning] Detected dropped audio source samples: -480 (-0.01 S)

73,

Jim N6VH


Jim Preston N6VH
 

Mike,

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

https://www.dropbox.com/s/o97q3d0c773p750/WSJT-X_RigControl.log?dl=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.


Michael Black
 

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://www.dropbox.com/s/o97q3d0c773p750/WSJT-X_RigControl.log?dl=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.


Michael Black
 

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://www.dropbox.com/s/o97q3d0c773p750/WSJT-X_RigControl.log?dl=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.


Jim Preston N6VH
 

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%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.













Michael Black
 

Try this DLL

https://www.dropbox.com/s/7aejdv74nfjxr0q/libhamlib-4.dll?dl=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%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.




   










Jim Preston N6VH
 

Mike,

I owe you an apology, and I feel like a dummy. I forgot about one other variable in the mix. I use Win4Yaesu to interface to the rig, going through microHam microKeyer router. When I take Win4Yaesu out of the mix, and go directly through the microHam router, there aren't any warnings. These must come from a very short delay, however, be cause the frequency readout for VFO B in Win4Yaesu changes immediately.  This quick change in the readout was why I hadn't considered Win4Yaesu at first. At any rate, this doesn't seem to cause any operational problems.

73,

Jim N6VH

On 7/30/2022 9:59 AM, Michael Black via groups.io wrote:
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.


















dl8le
 

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


John Reardon
 

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 Ravella
 

Hi John,

Which USB cable finally worked specifically? Could you provide a description or a link ?

Thanks,
Russ KR6W

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











Dave AA6YQ
 

+ AA6YQ comments below

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.

+ When WSJT-X controls a radio directly, it uses HamLib. When WSJT-X controls a radio via DXLab, it's using the Commander application. HamLib and Commander are entirely different applications; the only thing common between them is the serial port (and driver) used to communicate with the radio. I assume that your IC-7300's USB port is directly connected to your PC with a standard USB A-B cable. If you have a USB-to-serial-port adaptor and an Icom CI-V interface, use them to replace the USB A-B cable; any difference in behavior?

73,

Dave, AA6YQ


Chuck Moore <wd4hxg@...>
 

IC-7300's are reported to be sensitive to RF. I own one
and it has been no end of pain to use with the USB
interface. Initially I thought that my computer was the
problem with sensitivity to RFI but after using a 3rd party
box with integral codecs in the 3rd party box, all worked
well. My conclusion was the computer was not the problem,
the Icom USB interface is. And I cannot prove it, but
suspect the rf inside the radio is hiccuping the radio's
USB lines. While using the 3rd party interface solves
my issues, it defeats the purpose of me buying the
radio, that was to get rid of multiple external cables
and the 3rd party box, as I wanted to set up a portable
system without all the clutter.

In discussing the problem with the USB interface with
another op, he pointed out that the internal codecs in
the IC-7300 do not have line isolation transformers nor
does the audio chain appear to have any protection
from external interference.

I gave up on using the integral Icom USB interface.
My recommendation is to find another radio. You will
beat your brains into the ground trying to get a grip
on the interface crashing everytime your stomach
rumbles.

Chuck WD4HXG


Chuck Moore <wd4hxg@...>
 

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


Tim Dawson
 

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




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


Larry Banks
 

Does the IC7300 have a serial port?

Larry / W1DYJ

On 8/9/2022 21:05, Tim Dawson wrote:
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





Russ Ravella
 

Thanks very much Chuck. I’m not a fan of Icom either. Good luck !
Russ KR6W

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





Michael Black
 

My QRZ page has two links to USB adapters that break the shield on the USB cable like the IC-7300 needs.  Also usable on most other ham devices that are USB.The A/B adapter can do the other end too but needs a regular USB cable instead of the "printer" USB cable.
Mike W9MDB