Bug #10510: CHIRP Next Serial port flow control - CHIRP

Actions

Copy link

Bug #10510

closed

CHIRP Next Serial port flow control

Added by Danny Siminiuk about 1 year ago. Updated about 1 year ago.

Status:

Closed

Priority:

Normal

Assignee:

Dan Smith

Category:

Target version:

chirp-py3

Start date:

04/09/2023

Due date:

% Done:

100%

Estimated time:

Chirp Version:

Model affected:

Icom IC-7000 and others

Platform:

Windows

Debug Log:

I read the instructions above:

Description

I am using a DigiRig radio interface which has a built in sound card, CI-V port and uses RTS o the same COM port to key PTT.

When CHIRP Next 20230409 reads the radio it asserts RTS on the serial port which keys the transmitter.

RTS nor DTR are needed for CI-V so CHIRP should not assume that the port requires flow control. This should be the default for all CI-V based radios but a pair of checkboxes on the initial READ RADIO dialog to disable RTS and DTR would solve this issue.

I don't see a configuration dialog where port parameters can be changed.

Actions

Copy link

Updated by Dan Smith about 1 year ago

Status changed from New to Not a bug

CHIRP is specifically asking for no hardware flow control on the Icom CIV drivers. Also just to be clear (from the conversation on the mailing list), the setting in Device Manager has no impact on CHIRP. Even if it were set differently, CHIRP's request overrides at open time.

If RTS or DTR are getting set, it's not because CHIRP is asking for it. Most USB-to-serial devices do not do hardware flow control correctly anyway, so it may be something with your device or driver. But, since CHIRP is already requesting neither assertion, there's nothing more it can do.

Actions

Copy link