Actions
Bug #5635
closedFT2D variant, opening message, smart beaconing limit issues
Start date:
03/11/2018
Due date:
% Done:
0%
Estimated time:
Chirp Version:
0.4.0
Model affected:
(All models)
Platform:
Linux
I read the instructions above:
Description
I have several issues with my Chirp against my FT2DR.
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.
The FT2D's Opening message is stored in ASCII, the FT1D base driver is stored in a different format.
The FT2D has a higher max speed for beaconing than the FT1D.
Actions