Possible defect with IC-7300 and WSJTx #Cat_RigControl


Tim
 

Hi all,

I'm getting random disconnects with the obligatory pop-up window when WSJT looses contact with the radio.

I have an IC7300 s/w version 1.4, connected via USB to my PC running Ubuntu 20.04 LTS and WSJTx v2.4.0

The problem exists using either hamlib 4.2 & 4.3.

No TX is involved, the radio is just sitting there in RX, so its not an RF interference issue.

I've tried changing between "Split" and "Fake it" but the problem remains.

I've tried changing the baud rate from 115200 down to 38400 to see if that would help, but no.

I've changed the USB cable to no effect.

I spent a couple of hours on 20m today and the random disconnects happen during TX cycles too.

Not sure where else to check, so I thought I'd ask here.

any help appreciated.

thanks

Tim

-------include some log excerpts -----------------------


Timestamp: 2021-09-15T04:18:29.697Z
Hamlib error: Command rejected by the rig
rig_get_freq(2088): freqMainA=14074000, modeMainA=PKTUSB, widthMainA=3000
rig_get_freq(2088): freqMainB=0, modeMainB=, widthMainB=0
rig.c(2090):rig_get_freq return(-9) while getting other VFO frequency

Timestamp: 2021-09-15T05:04:31.081Z
Hamlib error: Command rejected by the rig
rig_get_freq(2088): freqMainA=0, modeMainA=, widthMainA=0
rig_get_freq(2088): freqMainB=0, modeMainB=, widthMainB=0
rig.c(2090):rig_get_freq return(-9) while getting current frequency

Timestamp: 2021-09-15T05:28:16.094Z

Hamlib error: Command rejected by the rig
rig_get_freq(2088): freqMainA=14074000, modeMainA=PKTUSB, widthMainA=3000
rig_get_freq(2088): freqMainB=14074500, modeMainB=PKTUSB, widthMainB=2400
rig.c(2090):rig_get_freq return(-9) while getting current VFO frequency

Timestamp: 2021-09-15T07:48:08.474Z
Hamlib error: Command rejected by the rig
icom_get_ptt: wrong frame len=9
icom.c(3873):icom_get_ptt return(-9)
rig.c(3035):rig_get_ptt return(-9) while getting PTT state

Timestamp: 2021-09-15T10:32:20.010Z
Hamlib error: Command rejected by the rig
rig_get_freq(2088): freqMainA=7074000, modeMainA=PKTUSB, widthMainA=3000
rig_get_freq(2088): freqMainB=7074500, modeMainB=PKTUSB, widthMainB=3000
rig.c(2090):rig_get_freq return(-9) while getting current VFO frequency

Timestamp: 2021-09-15T10:36:53.979Z


--
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA


Bill Somerville
 

On 15/09/2021 12:16, Tim wrote:
Hi all,

I'm getting random disconnects with the obligatory pop-up window when WSJT looses contact with the radio.

I have an IC7300 s/w version 1.4, connected via USB to my PC running Ubuntu 20.04 LTS and WSJTx v2.4.0

The problem exists using either hamlib 4.2 & 4.3.

No TX is involved, the radio is just sitting there in RX, so its not an RF interference issue.

I've tried changing between "Split" and "Fake it" but the problem remains.

I've tried changing the baud rate from 115200 down to 38400 to see if that would help, but no.

I've changed the USB cable to no effect.

I spent a couple of hours on 20m today and the random disconnects happen during TX cycles too.

Not sure where else to check, so I thought I'd ask here.

any help appreciated.

thanks

Tim
Hi Tim,

do you have "CI-V Transceive Mode" enabled on your IC-7300? It should be disabled.

73
Bill
G4WJS.


Tim
 

On 15/9/21 9:43 pm, Bill Somerville wrote:


Hi Tim,

do you have "CI-V Transceive Mode" enabled on your IC-7300? It should be disabled.
Hi Bill,

:) that was the 1st thing I checked, and its disabled.

cheers

Tim


--
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA


Michael Black
 

On Wednesday, September 15, 2021, 08:59:20 AM CDT, Tim <vk2xax@...> wrote:


On 15/9/21 9:43 pm, Bill Somerville wrote:

>
> Hi Tim,
>
> do you have "CI-V Transceive Mode" enabled on your IC-7300? It should
> be disabled.

Hi Bill,

:) that was the 1st thing I checked, and its disabled.

cheers


Tim



--
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA






Martin G0HDB
 

On Wed, Sep 15, 2021 at 12:41 PM, Tim wrote:
Hi all,

I'm getting random disconnects with the obligatory pop-up window when
WSJT looses contact with the radio.
[Snipped]

Hi Tim, I have no knowledge or experience whatsoever of the inner workings of Hamlib (or WSJT-X!) but having looked at the error messages you included in your posting it struck me as slightly odd that the mode, eg. modeMainA, is shown as PKTUSB - I might have expected the mode to be shown as, for example, USB-D1 or something like that.

What have you selected for the radio mode setting in WSJT-X - is it Data/Pkt or just plain USB?  If you've selected the Data/Pkt mode option then it might be worth trying the USB option to see if that makes any difference.

73
--
Martin G0HDB


Michael Black
 

PKTUSB is the hamlib name for any data mode on all the rigs.

Mike W9MDB




On Wednesday, September 15, 2021, 09:47:02 AM CDT, Martin G0HDB <marting0hdb@...> wrote:


On Wed, Sep 15, 2021 at 12:41 PM, Tim wrote:
Hi all,

I'm getting random disconnects with the obligatory pop-up window when
WSJT looses contact with the radio.
[Snipped]

Hi Tim, I have no knowledge or experience whatsoever of the inner workings of Hamlib (or WSJT-X!) but having looked at the error messages you included in your posting it struck me as slightly odd that the mode, eg. modeMainA, is shown as PKTUSB - I might have expected the mode to be shown as, for example, USB-D1 or something like that.

What have you selected for the radio mode setting in WSJT-X - is it Data/Pkt or just plain USB?  If you've selected the Data/Pkt mode option then it might be worth trying the USB option to see if that makes any difference.


73

--
Martin G0HDB




Martin G0HDB
 

On Wed, Sep 15, 2021 at 03:49 PM, Michael Black wrote:
PKTUSB is the hamlib name for any data mode on all the rigs.
Thanks for the clarification, Mike.

A further thought re: Tim's original posting - assuming the 7300 has a CI-V 'Remote' port, is anything connected to and using that?  If there is then it's possible that there are collisions between the two streams of CAT data, one arriving via the USB port and one via the Remote port, unless the menu option 'Unlink from Remote' is selected.  Presumably such collisions could cause the Hamlib 'Command rejected by the rig' errors that were documented in Tim's posting.

--
Martin G0HDB


Tim
 

Hi Michael,

Good question! - I'll investigate this path further.

thanks

Tim


On 16/9/21 12:43 am, Michael Black via groups.io wrote:

-- 
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA


Tim
 

Hi Martin,

No additional CI-V involved - but good thinking and something to be aware of.

regards

Tim

On 16/9/21 4:45 am, Martin G0HDB wrote:
On Wed, Sep 15, 2021 at 03:49 PM, Michael Black wrote:
PKTUSB is the hamlib name for any data mode on all the rigs.
Thanks for the clarification, Mike.

A further thought re: Tim's original posting - assuming the 7300 has a CI-V 'Remote' port, is anything connected to and using that?  If there is then it's possible that there are collisions between the two streams of CAT data, one arriving via the USB port and one via the Remote port, unless the menu option 'Unlink from Remote' is selected.  Presumably such collisions could cause the Hamlib 'Command rejected by the rig' errors that were documented in Tim's posting.

-- 
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA


Tim
 

Hi all,

Re-examining my whole set-up I realised that the problem only happened when I had CQRlog open.

CQRlog spawns rigctld to control the 7300 _BUT_ I also had WSJT configured to talk to the 7300 directly.

This was a result of some experimentation I was doing and I had failed to put hamlib NET back into WSJT's rig control section after my tests.

Thus CQRlog & WSJT were competing for control of the 7300.

thanks to everyone who had suggestions.

regards

Tim


--
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA