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

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

Some progress on connecting CI-V USB dongle to IC-746Pro remote port

   - Tested FTDI CI-V adapter with another radio, IC-9700, same problem,
      - unable to receive responses from radio
      - oscope show response from radio
      - So the problem is the USB converter or Linux
   - Tested with real FTDI, real Prolific 2303 and fake Prolific 2302 Ci-V
   converters, none work
   - Test with QinHeng CH341, success!
      - initially failed to create ttyUSB0
      - Internet search said remove braille device package "brltty", due to
      udev rule issue
      - Now creates ttyUSB0
      - Works well with both 746PRO and IC-9700

All these USB to CI-V serial adapters were purchased from Amazon and had
various Chinese company names.  I looked back through order history and
can't figure out which of the three ordered is the CH341.

Any other ideas about why this should be so fragile?

jeff, wa1hco

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

> Hi Mike,
>
> Thanks for the quick reply,  There is only one serial port, and it is
> ttyUSB0. dmesg show it as ttyUSB0.
>
> I put a scope on the CI-V line and it shows the transmission from rigctl
> followed by the response from the radio.  If I change the baud rate, the
> radio doesn't respond. So, I think the characters are not getting
> received by the dongle, linux, hamlib, or rigctl and can't imagine why.
>
> There are two hamlibs on the pc, any weirdness there?  I have been playing
> with building wsjtx from source.
>
>    - /usr/local/bin/rigctl --version ... reports Hamlib 4.6~git
>    - $HOME/ham/build/build/hamlib-prefix/bin/rigctl --version ... reports
>    Hamlib 4.5.4
>
> Both binaries work and fail to talk to the radio.
>
> jeff, wa1hco
>
>
> On Wed, Apr 5, 2023 at 4:25 PM Black Michael <mdb...@ya...> wrote:
>
>> Sounds like you have the wrong port.
>> What does "dmesg | grep tty" show?  Another USB device maybe?
>>
>> Mike W9MDB
>>
>> On Wednesday, April 5, 2023 at 03:03:21 PM CDT, 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
>>
>>
>>
>> _______________________________________________
>> Hamlib-developer mailing list
>> Ham...@li...
>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>>
>