I opened a bug here [ https://chirp.danplanet.com/issues/10510?tab=history | https://chirp.danplanet.com/issues/10510?tab=history ] .

I don't like the bug tracking system. Dan closed the ticket without allowing any further discussion or addition of additional evidence and I find it rude and frustrating. github.com and other issue tracking systems allow comments even after an issue is closed without changing the status of the issue.

Regarding this part: "If RTS or DTR are getting set, it's not because CHIRP is asking for it... But, since CHIRP is already requesting neither assertion, there's nothing more it can do."

Icom Memory Manager v1.1.0.14 can read the radio memories and it does not asset RTS unless you tell it to in the app - same USB serial port - Silicon Labs device driver.

Perhaps CHIRP NEXT is not "asking" for RTS but it is being turned on when CHIRP runs anyway. That could be because it is not specified so could be the USB driver turns it on by default if not specified.

Perhaps a toggle on the CHIRP Radio connect dialog to specifically set it low would work?

From: "Ken Hansen" ken@n2vip.org To: "chirp users" chirp_users@intrepid.danplanet.com Sent: Sunday, April 9, 2023 9:58:51 PM Subject: Re: [chirp_users] CI-V port flow control RTS on DigiRig

Isn't this something you would set in device manager for the port you are connecting to your radio? Try searching for "device manager", then examine the serial port connected to the radio by right-clicking on it and changing the port settings...

Ken, N2VIP

On Apr 9, 2023, at 20:59, K5CG k5cg@hamoperator.org wrote:

BQ_BEGIN

Hello all,

I am not new to CHIRP but I'm setting up a new laptop and trying to manage memories on a (new to me) IC-7000.

I am using a DigiRig radio interface which has a built in sound card, CI-V port and uses RTS of 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 either RTS or DTR or both would also solve this issue.

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

In the meantime I can disconnect the 13 pin accessory connector on the back of the radio to prevent it from keying.

73 Danny K5CG

_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ken Hansen at ken@n2vip.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

BQ_END

_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Danny at k5cg@hamoperator.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

Dan contacted me directly by email and we did some testing and there is a fix coming in a future build.

----- Original Message ----- From: "chirp users" chirp_users@intrepid.danplanet.com To: "chirp users" chirp_users@intrepid.danplanet.com Sent: Monday, April 10, 2023 9:29:30 AM Subject: Re: [chirp_users] CI-V port flow control RTS on DigiRig

I don't like the bug tracking system. Dan closed the ticket without allowing any further discussion or addition of additional evidence and I find it rude and frustrating. github.com and other issue tracking systems allow comments even after an issue is closed without changing the status of the issue.

You should still be able to comment on the bug even in its current state. I can -- if you really can't, please let me know (off list) and I'll look into why. I certainly did not mean to cut off discussion, but rather just categorize the ticket appropriately.

Regarding this part: "If RTS or DTR are getting set, it's not because CHIRP is asking for it... But, since CHIRP is already requesting neither assertion, there's nothing more it can do."

Icom Memory Manager v1.1.0.14 can read the radio memories and it does not asset RTS unless you tell it to in the app - same USB serial port - Silicon Labs device driver.

Perhaps CHIRP NEXT is not "asking" for RTS but it is being turned on when CHIRP runs anyway. That could be because it is not specified so could be the USB driver turns it on by default if not specified.

Perhaps a toggle on the CHIRP Radio connect dialog to specifically set it low would work?

There's nothing to toggle because it's asking for RTS/CTS and DSR/DTR handshaking to be disabled.

--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Danny at k5cg@hamoperator.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com