Project

General

Profile

Actions

Bug #5635

closed

FT2D variant, opening message, smart beaconing limit issues

Added by Ray Cielencki about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/11/2018
Due date:
% Done:

0%

Estimated time:
Chirp Version:
0.4.0
Model affected:
(All models)
Platform:
Linux
Debug Log:
I read the instructions above:

Description

I have several issues with my Chirp against my FT2DR.

  1. It reports as a AH60G, instead of AH60M. My buddy has one too, but with older 1.07 firmware and it is reports as AH60M. I suspect this may be the difference. We both have done the MARS/CAP mod.

  2. The FT2D's Opening message is stored in ASCII, the FT1D base driver is stored in a different format.

  3. The FT2D has a higher max speed for beaconing than the FT1D.

Actions #1

Updated by Ray Cielencki about 6 years ago

This can be closed.

Actions #2

Updated by Dan Smith about 6 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF