hamlib-developer — hamlib developers forum

[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
>
>
>
>

[Hamlib-developer] [Hamlib/Hamlib] 905c9f: Fix SDR++ giving wrong answer for get_powerstat

[Michael B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 905c9fff95f4dcaabfb2cfba4a821c895894051a
      https://github.com/Hamlib/Hamlib/commit/905c9fff95f4dcaabfb2cfba4a821c895894051a
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-04-10 (Mon, 10 Apr 2023)

  Changed paths:
    M rigs/dummy/netrigctl.c

  Log Message:
  -----------
  Fix SDR++ giving wrong answer for get_powerstat
https://github.com/Hamlib/Hamlib/issues/1266

[Hamlib-developer] [Hamlib/Hamlib] 2c283a: Fix QRP Labs QCX Morse Sending

[Michael B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 2c283ab47ae99fd404ee1950434465385f00a734
      https://github.com/Hamlib/Hamlib/commit/2c283ab47ae99fd404ee1950434465385f00a734
  Author: Nick Craig-Wood <ni...@cr...>
  Date:   2023-04-09 (Sun, 09 Apr 2023)

  Changed paths:
    M rigs/kenwood/kenwood.c

  Log Message:
  -----------
  Fix QRP Labs QCX Morse Sending

Before this fix, hamlib used the TS480 protocol for sending morse
which adds a lot of spaces on the end.

The QCX actually uses the Elecraft morse sending protocol so switch it
over to using that.

Tested with QCX Mini firmware v1.09a


  Commit: 6c1d83ed8684c8b3ff806c07e8c465d41c502685
      https://github.com/Hamlib/Hamlib/commit/6c1d83ed8684c8b3ff806c07e8c465d41c502685
  Author: Michael Black <mdb...@ya...>
  Date:   2023-04-09 (Sun, 09 Apr 2023)

  Changed paths:
    M rigs/kenwood/kenwood.c

  Log Message:
  -----------
  Merge pull request #1269 from ncw/fix-qcx-cw-sending

Fix QRP Labs QCX Morse Sending


Compare: https://github.com/Hamlib/Hamlib/compare/cf77666cc1ca...6c1d83ed8684

[Hamlib-developer] [Hamlib/Hamlib] 96bb60: Fix typos

[Michael B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 96bb604b1216547e599d06b61f73cb39ae797c17
      https://github.com/Hamlib/Hamlib/commit/96bb604b1216547e599d06b61f73cb39ae797c17
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2023-04-09 (Sun, 09 Apr 2023)

  Changed paths:
    M NEWS
    M doc/README.man-pages
    M doc/hamlib.cfg.in
    M extra/kylix/README.kylix
    M extra/kylix/hamlib_rigapi.pas
    M include/hamlib/rig.h
    M rigs/jrc/jst145.c
    M rigs/uniden/uniden_digital.c
    M rigs/yaesu/newcat.c
    M src/amplifier.c
    M src/rig.c
    M tests/ampctl_parse.c
    M tests/testcookie.c

  Log Message:
  -----------
  Fix typos


  Commit: c3d06fd043aeab69c4ade5fce1e739f8288a505f
      https://github.com/Hamlib/Hamlib/commit/c3d06fd043aeab69c4ade5fce1e739f8288a505f
  Author: Daniele Forsi IU5HKX <iu...@gm...>
  Date:   2023-04-09 (Sun, 09 Apr 2023)

  Changed paths:
    M include/hamlib/rig.h
    M include/hamlib/riglist.h
    M src/cache.c
    M src/rig.c
    M src/token.h

  Log Message:
  -----------
  Add/fix Doxygen comments


  Commit: cf77666cc1ca7a8eae96d5700deafc1adc660cc4
      https://github.com/Hamlib/Hamlib/commit/cf77666cc1ca7a8eae96d5700deafc1adc660cc4
  Author: Michael Black <mdb...@ya...>
  Date:   2023-04-09 (Sun, 09 Apr 2023)

  Changed paths:
    M NEWS
    M doc/README.man-pages
    M doc/hamlib.cfg.in
    M extra/kylix/README.kylix
    M extra/kylix/hamlib_rigapi.pas
    M include/hamlib/rig.h
    M include/hamlib/riglist.h
    M rigs/jrc/jst145.c
    M rigs/uniden/uniden_digital.c
    M rigs/yaesu/newcat.c
    M src/amplifier.c
    M src/cache.c
    M src/rig.c
    M src/token.h
    M tests/ampctl_parse.c
    M tests/testcookie.c

  Log Message:
  -----------
  Merge pull request #1268 from dforsi/fix/doxygen

Add/fix Doxygen comments


Compare: https://github.com/Hamlib/Hamlib/compare/dd874dbf7f53...cf77666cc1ca

[Hamlib-developer] [Hamlib/Hamlib] e5a00c: Fix case where netrigctl gets a 0 answer to chk_vfo

[Michael B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: e5a00cddb9fcbebcf8a41de96a6380f03618d230
      https://github.com/Hamlib/Hamlib/commit/e5a00cddb9fcbebcf8a41de96a6380f03618d230
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-04-09 (Sun, 09 Apr 2023)

  Changed paths:
    M rigs/dummy/netrigctl.c

  Log Message:
  -----------
  Fix case where netrigctl gets a 0 answer to chk_vfo
https://github.com/Hamlib/Hamlib/issues/1266


  Commit: dd874dbf7f53b09d455afa921af0938ed914bbe8
      https://github.com/Hamlib/Hamlib/commit/dd874dbf7f53b09d455afa921af0938ed914bbe8
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-04-09 (Sun, 09 Apr 2023)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Merge branch 'master' of https://github.com/Hamlib/Hamlib


Compare: https://github.com/Hamlib/Hamlib/compare/748b45b91f82...dd874dbf7f53

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

[Brian M. <bd...@fe...>]

On Fri, 7 Apr 2023 15:23:29 +0100
Dave B via Hamlib-developer <ham...@li...>
wrote:

> Don't forget to also kill off the infamous "Modem Manager", that has 
> caused stupidity in the past too.

But be careful if you use a USB cellular dongle thing, they nearly
always need it but it can be made to ignore certain ports.

-- 

Brian  G8SEZ

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

[Dave B <g8k...@go...>]

Don't forget to also kill off the infamous "Modem Manager", that has 
caused stupidity in the past too.


If you have a FTDI based device that shows a serial number like this in 
dmesg....
(Even a fake one!)


[Apr 7 15:04] usb 1-1.6.5.2: new full-speed USB device number 15 using 
ehci-pci
[  +0.115074] usb 1-1.6.5.2: New USB device found, idVendor=0403, 
idProduct=6001, bcdDevice= 6.00
[  +0.000006] usb 1-1.6.5.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  +0.000002] usb 1-1.6.5.2: Product: FT232R USB UART
[  +0.000002] usb 1-1.6.5.2: Manufacturer: FTDI
*[  +0.000001] usb 1-1.6.5.2: SerialNumber: AK06ML2R*
[  +0.002918] ftdi_sio 1-1.6.5.2:1.0: FTDI USB Serial Device converter 
detected
[  +0.000036] usb 1-1.6.5.2: Detected FT232RL
[  +0.001054] usb 1-1.6.5.2: FTDI USB Serial Device converter now 
attached to ttyUSB5

(The above, is seen by watching dmesg output, when connecting a FTDI 
equipped serial bridge device.)

It is fairly easy to use a udev rule based on the Serial Number, to 
assign it to a static'ly numbered /dev/ttyUSBx device (x is your choice) 
or even give it a name you'll remember /dev/ttyFTDIcable-a   or   
/dev/ttyIC746  (etc.)

Then it'll appear always with that designation in the device list, 
regardless of what /dev/ttyUSBx it gets assigned from the kernel (that 
will also be valid, but can change if something forces a re-enumeration.)

Hamlib will accept such names, as will a lot of other software (Flrig 
etc) just fine I've found.

Sadly, even genuine Prolific, CMedia or SiLabs chips usually do not have 
anything "unique" about them to do that with, but you can in a 
statically wired shack, use the "Path" to it, to give it a name. But if 
you change the physical port it's plugged into, or add/remove a hub, all 
bets are off!

Some other chips (serial and sound I/O) can use data in an attached 
eeprom, where you can put a unique ID into, that will be used in place 
of it's default details when it is enumerated.  Not a trivial thing to 
achieve though.

The above based on my own personal hands-on experience.

73.
     Dave G0WBX.
(Currently using LMDE 5, no brltty, but ModemManager is in there... Not 
causing issues at present.)



On 07/04/2023 13:29, Brian Morrison wrote:
> On Thu, 6 Apr 2023 17:34:08 -0400
> jeff millar<wa...@gm...>  wrote:
>
>> 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?
> A lot of it is down to clones of the originals, the manufacturers
> modified the 'real' devices to try and make them incompatible with the
> older drivers and force the fakes out of the market. It led to much
> confusion and headache. I don't know how much of that got into other
> OSs but it certainly caused trouble for Windows users.
>
> brltty is also a pain, it's hanging around in systems where it will
> never be used presumably to make it easier for those that needed
> braille displays/keyboards.
>
> Glad you found a fix.
>

-- 
Created on and sent from a Unix like PC running and using free and open source software:

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

[Brian M. <bd...@fe...>]

On Thu, 6 Apr 2023 17:34:08 -0400
jeff millar <wa...@gm...> wrote:

> 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?

A lot of it is down to clones of the originals, the manufacturers
modified the 'real' devices to try and make them incompatible with the
older drivers and force the fakes out of the market. It led to much
confusion and headache. I don't know how much of that got into other
OSs but it certainly caused trouble for Windows users.

brltty is also a pain, it's hanging around in systems where it will
never be used presumably to make it easier for those that needed
braille displays/keyboards.

Glad you found a fix.

-- 

Brian  G8SEZ

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

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

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

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
>

[Hamlib-developer] Hamlib 4.5.5 released

[Nate B. <n0...@n0...>]

Thanks to Mike and all contributors, Hamlib 4.5.5 has been released!

As usual, releases are made available via GitHub and SourceForge:

https://github.com/Hamlib/Hamlib/releases/tag/4.5.5
https://sourceforge.net/projects/hamlib/files/hamlib/4.5.5

The visible changes in this release are:

Version 4.5.5
  * 2023-04-05
  * Add park to rotorez.c
  * Fix rig power on/off from rigctl cmd line and rigctld
  * Enable async mode by default to prevent WSJT-X crash on IC9700 with transceive on
  * Fix IC7610 get_powerstat to disable it -- cannot read power status
  * Fix K3 K22 command error for remote operations
  * Fix Gemini DX1200 gemini_set_level
  * Fix async I/O to not call flush
  * Change EX startup commands for Yaesu rigs to allow errors...Win4Yaesu not recognizing EX commands
  * Fix jst145 set_freq and get_freq
  * Restore tcflush as some odd behavior was seen that tclush fixes
  * Fix XG3 operations
  * Separate the validation cmd in newcat.c to allow rig post_write_delay to be in effect
  * Increase post_write to 20ms for FT710
  * Add attenuator level control for TS890
  * Update SMeter/SWR tables for TS890
  * Add fix for TMD700
  * Improve FT-857 get_vfo response when error occurs
  * Allow FT-857 to use cached vfo on get_vfo when error occurs reading EEPROM
  * Fix FTDX10 FT710 set_level AF
  * Fix FT-450D detection
  * Fix VFO A/B swapping for gpredict -- hopefully better behavior for VFO swapping rigs
    Should avoid setting RX freq while TX and avoid TX freq while RX
  * Fix QRP QDX PTT to new TQ command due to firmware changes
  * Remove EX103 check for FTDX5000
  * Fix K3/K3S VFOB setting of mode/width
  * Fix AGC level display in rigctld
  * Change FTDX10 to no serial handshake
  * Add TS2000 to has_ps exception
  * Add FT991 to 60M exception
  * Fix get_powerstat bad call in rigctl_parse.c
  * Really fix CM108 ptt_bitnum usage
  * Fix Elecraft power2mW precision/accuracy
  * Fix power on/off/on for Icom rigs with rigctld power_on=0


73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

[Hamlib-developer] [Hamlib/Hamlib] 748b45: Update recent dates in NEWS

[Nate B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 748b45b91f8216744d9bd38baf882a592c1f804b
      https://github.com/Hamlib/Hamlib/commit/748b45b91f8216744d9bd38baf882a592c1f804b
  Author: Nate Bargmann <n0...@n0...>
  Date:   2023-04-05 (Wed, 05 Apr 2023)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update recent dates in NEWS

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

[Black M. <mdb...@ya...>]

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 enteredrig_flush: called for serial deviceread_string_generic called, rxmax=4095 direct=1, expected_len=1tcflushwrite_block(): TX 7 bytes, method=20000    fe fe 66 e0 07 00 fd                                ..f....         read_string_generic called, rxmax=200 direct=1, expected_len=1read_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.6rigctl is connected to an IC-746PRO at 9600.Using FTDI USB to CI-V adapter.FTDI adapter works on IC-7300Other adapters fail the same way (prolific, fake prolific, other chinese)Oscilloscope in CI-V line shows Tx from rigctl and response from radio, looks normalOscope 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
  

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

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

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] [Hamlib/Hamlib] 22970f: Fix Serial speed information in dumpcaps

[Michael B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 22970f16de01a30792ecd3041e55ce34bc164d5d
      https://github.com/Hamlib/Hamlib/commit/22970f16de01a30792ecd3041e55ce34bc164d5d
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-04-05 (Wed, 05 Apr 2023)

  Changed paths:
    M tests/dumpcaps.c
    M tests/dumpcaps_amp.c
    M tests/dumpcaps_rot.c

  Log Message:
  -----------
  Fix Serial speed information in dumpcaps

[Hamlib-developer] [Hamlib/Hamlib]

[Nate B. <no...@gi...>]

  Branch: refs/tags/4.5.5
  Home:   https://github.com/Hamlib/Hamlib

[Hamlib-developer] [Hamlib/Hamlib]

[Nate B. <no...@gi...>]

  Branch: refs/tags/4.5.5
  Home:   https://github.com/Hamlib/Hamlib

[Hamlib-developer] [Hamlib/Hamlib]

[Nate B. <no...@gi...>]

  Branch: refs/tags/4.5.5
  Home:   https://github.com/Hamlib/Hamlib

[Hamlib-developer] [Hamlib/Hamlib] 6eecd3: Update NEWS for 4.5.5 release

[Nate B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.5.5
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 6eecd3d0160278373875e16b77299881ff656068
      https://github.com/Hamlib/Hamlib/commit/6eecd3d0160278373875e16b77299881ff656068
  Author: Nate Bargmann <n0...@n0...>
  Date:   2023-04-05 (Wed, 05 Apr 2023)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update NEWS for 4.5.5 release

[Hamlib-developer] [Hamlib/Hamlib] ad140c: Add simid5100.c

[Michael B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.5.5
  Home:   https://github.com/Hamlib/Hamlib
  Commit: ad140cbac217ea346ebbe8042ecf67b1bbca08d7
      https://github.com/Hamlib/Hamlib/commit/ad140cbac217ea346ebbe8042ecf67b1bbca08d7
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-04-04 (Tue, 04 Apr 2023)

  Changed paths:
    A simulators/simid5100.c

  Log Message:
  -----------
  Add simid5100.c


  Commit: e5210bec1545472ef924c8fb8f21a550c6b6be3d
      https://github.com/Hamlib/Hamlib/commit/e5210bec1545472ef924c8fb8f21a550c6b6be3d
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-04-04 (Tue, 04 Apr 2023)

  Changed paths:
    M simulators/Makefile.am
    M tests/Makefile.am

  Log Message:
  -----------
  Fix bootstrap problems


Compare: https://github.com/Hamlib/Hamlib/compare/9bf8066b8363...e5210bec1545

[Hamlib-developer] 1035 FT-991A l METER

[Georgina J. <ge...@ge...>]

Hello,

Is the meter as a level the signal meter? Or does 32 mean something else.

Thanks,

Georgina


Call: M0EBP
DMR ID: 2346259
Allstar: 52178
Locater: IO83PS

[Hamlib-developer] Can I change menu settings of the FT-991A?

[Georgina J. <ge...@ge...>]

Hello,

I wondered if it was possible to change menu settings using rigctl? Looking at the caps dump of the 991A I don't see anything that suggests that this can be done. I have purchased RT Systems program which contains a menu editor but it doesn't play well with screen readers.

So I thought I would ask here.

Thanks,

Georgina


Call: M0EBP
DMR ID: 2346259
Allstar: 52178
Locater: IO83PS

[Hamlib-developer] [Hamlib/Hamlib] 9bf806: Add error message when rig is not turned on that m...

[Michael B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.5.5
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 9bf8066b836399507e0ae5cbed3f6c07a16de938
      https://github.com/Hamlib/Hamlib/commit/9bf8066b836399507e0ae5cbed3f6c07a16de938
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-03-30 (Thu, 30 Mar 2023)

  Changed paths:
    M src/rig.c

  Log Message:
  -----------
  Add error message when rig is not turned on that mentions auto_power_on

[Hamlib-developer] [Hamlib/Hamlib] 99170c: Add error message when rig is not turned on that m...

[Michael B. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 99170c10259dbe0b4903ce6ce3d47bac623769de
      https://github.com/Hamlib/Hamlib/commit/99170c10259dbe0b4903ce6ce3d47bac623769de
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-03-30 (Thu, 30 Mar 2023)

  Changed paths:
    M src/rig.c

  Log Message:
  -----------
  Add error message when rig is not turned on that mentions auto_power_on

[Hamlib-developer] [Hamlib/Hamlib] 4ab3aa: Update NEWS

[Michael B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.5.5
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 4ab3aaf3588d92c9d1d116cfa48f747737c834f4
      https://github.com/Hamlib/Hamlib/commit/4ab3aaf3588d92c9d1d116cfa48f747737c834f4
  Author: Mike Black W9MDB <mdb...@ya...>
  Date:   2023-03-29 (Wed, 29 Mar 2023)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update NEWS