Bug #9597: FT-2900R - CHIRP

Custom queries

All CHIRP-next Bugs
All CHIRP-next Feature Requests
All closed issues
All open issues
New Model Requests
Open bugs by Developer
Open bugs by Target Version
Potentially Stalled Bugs

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:

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

Download all 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 open — 1 closed)

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

Rejected

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

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

Copy link

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

Copy link

Updated by Paulo Henrique over 2 years ago

File debug.log debug.log added

Actions

Copy link

Updated by Paulo Henrique over 2 years ago

File debug.log debug.log added

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

Actions

Copy link

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

Copy link

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

Copy link

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

Copy link

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

Copy link

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

Copy link

#10