[Hamlib-developer] Solved: Re: Question...rigctl timed out on receive, cannot see data from 746PRO

[jeff m. <wa...@gm...>]

Found the reason for the flake-y CI-V communication.

The IC-746PRO had no ground connection on the 1/8 inch remote jack.  And
there was a 1V DC offset between CI-V return and USB ground.

So, if the radio and laptop USB had enough connections to ground it would
work, if the radio 12V and laptop floated, it would not work.  Made more
confusing when using a signal breakout and adding the scope ground to the
circuit.  Working depended on the exact threshold for USB detecting a low
on the CI-V signal.

So how did the ground on the remote jack get open?  My theory is that hot
plugging the 12V while the CI-V cable was connected caused the 12V to find
a ground path through the very small CI-V signal return trace.

Anyway, thought I should close this out for those interested.

jeff, wa1hco

On Wed, Apr 5, 2023 at 4:02 PM jeff millar <wa...@gm...> wrote:

> Can anyone provide guidance on debugging this problem...
>
> Here is a bit of log from rigctl.  This occurs during startup.
>
> $ rigctl -m3046 -r /dev/ttyUSB0 -s 9600 -vvvvv 2> rigctl.log
>
> <...>
>
> icom_transaction: cmd=0x07, subcmd=0x00, payload_len=0
>    3:frame.c(142):icom_one_transaction entered
> rig_flush: called for serial device
> read_string_generic called, rxmax=4095 direct=1, expected_len=1
> tcflush
> write_block(): TX 7 bytes, method=2
> 0000    fe fe 66 e0 07 00 fd                                ..f....
>
> read_string_generic called, rxmax=200 direct=1, expected_len=1
> read_string_generic(): Timed out 1.002 seconds after 0 chars, direct=1
>    3:frame.c(189):icom_one_transaction returning(-13) Communqication bus
> error
> <...>
>
>
> rigctl report version 4.6
> rigctl is connected to an IC-746PRO at 9600.
> Using FTDI USB to CI-V adapter.
> FTDI adapter works on IC-7300
> Other adapters fail the same way (prolific, fake prolific, other chinese)
> Oscilloscope in CI-V line shows Tx from rigctl and response from radio,
> looks normal
> Oscope only shows response from radio when baud rate correct...so reading
> scope right
>
> any ideas or suggestions?
>
> jeff, wa1hco
>
>
>
>