CHIRP

Bernhard Hailer wrote:

Could you please provide a debug log as described in the Wiki: "How To Report Issues"? Thanks!
I do this with the latest version available the latest version ?

!https://i.imgur.com/jxImaiG.png!
!https://i.imgur.com/qyoxmMn.png!
and still not communicating with the radio

is there any way to listen to the serial port for the commands it receives via software or just physically by hardware
anything or can I put another serial port on the output to listen

!https://i.imgur.com/Ff6PA3p.png!
using the same cable I tried to use on chirp

Have you been able to resolve this?

Still, perhaps my previous questions could give us some pointers: Is the correct COM port being used, and are the settings for it correct? Is COM1 really the COM port your cable establishes? Look up in Device Manager.

Chirp tries to download the data header from the radio once every 250 milliseconds and gets nothing. Perhaps there's a setup problem on your computer. Look up the serial settings in the working software, and ensure you're using the same settings in Chirp.

I can't test again everything is configured correctly how to show the other program reads the data normally

I saw that the program changed but the problem remains

My radio is in extended transmission mode (mars mode)

[2023-03-11 18:22:56,017] chirp.drivers.ft2900 - DEBUG: Header:

[2023-03-11 18:22:56,017] chirp.drivers.ft2900 - DEBUG: len(header) = 0

[2023-03-11 18:22:56,272] chirp.drivers.ft2900 - DEBUG: Header:

[2023-03-11 18:22:56,272] chirp.drivers.ft2900 - DEBUG: len(header) = 0

[2023-03-11 18:22:56,527] chirp.drivers.ft2900 - DEBUG: Header:
000: 56 43 32 33 00 02 c3 02 VC23....
008: 01 01 ........

does the reading if I choose FT-1802M
however it only shows the frequencies