Project

General

Profile

Actions

Bug #9597

open

FT-2900R

Added by Paulo Henrique almost 3 years ago. Updated over 1 year ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
12/12/2021
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Yaesu FT-2900R
Platform:
Windows
Debug Log:
I read the instructions above:

Description

comunication error
it is not reading but the FTB2900 program is communicating with the radio when I use the same cable


Files

debug.log (35.5 KB) debug.log Paulo Henrique, 04/27/2022 09:26 PM
debug.log (38.5 KB) debug.log Paulo Henrique, 04/27/2022 09:31 PM

Related issues 1 (0 open1 closed)

Related to CHIRP-next model report #10438: how to compile for windows/linux the filesRejectedActions
Actions #1

Updated by Bernhard Hailer over 2 years ago

  • Status changed from New to Feedback
  • Target version deleted (chirp-legacy)
  • Model affected changed from FT-2900R to Yaesu FT-2900R
  • Platform changed from Windows to All

Could you please provide a debug log as described in the Wiki: "How To Report Issues"? Thanks!

Actions #2

Updated by Paulo Henrique over 2 years ago

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 ?

Actions #3

Updated by Paulo Henrique over 2 years ago

Actions #4

Updated by Paulo Henrique over 2 years ago

ready in the 2 more failure modes if I use this program here https://ftb2900.software.informer.com/download/
it reads normally

Actions #5

Updated by Bernhard Hailer over 2 years ago

  • Platform changed from All to Windows

There is no communication with the radio. 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.

Actions #6

Updated by Paulo Henrique over 2 years ago

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

Actions #7

Updated by Paulo Henrique over 2 years ago

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

Actions #8

Updated by Paulo Henrique over 2 years ago

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

Actions #9

Updated by Bernhard Hailer almost 2 years ago

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.

Actions #10

Updated by Paulo Henrique almost 2 years ago

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

Actions #11

Updated by Paulo Henrique over 1 year ago

I saw that the program changed but the problem remains

Actions #12

Updated by Dan Smith over 1 year ago

Actions #13

Updated by Paulo Henrique over 1 year ago

My radio is in extended transmission mode (mars mode)

Actions #14

Updated by Paulo Henrique over 1 year ago

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

Actions #15

Updated by Paulo Henrique over 1 year ago

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

Actions

Also available in: Atom PDF