Project

General

Profile

Actions

New Model #1107

closed

FT1900

Added by Ian Munro almost 12 years ago. Updated over 8 years ago.

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

100%

Estimated time:
Equipment Loan/Gift Offered:
No
I read the instructions above:

Description

Any chance that support can be added for the FT1900 rig?


Files

FT-1802_2014_03_13.csv (368 Bytes) FT-1802_2014_03_13.csv FT1802 read with FT1802, 4 channel list. Reference file. Jim Zigan, 03/18/2014 09:27 PM
FT-1900_read_with_FT1802_2013_03_13.img (7.82 KB) FT-1900_read_with_FT1802_2013_03_13.img FT1900 setup the same way as FT1802, 4 channel reference file. Jim Zigan, 03/18/2014 09:27 PM
FT-1802_2014_03_13.img (7.82 KB) FT-1802_2014_03_13.img FT1802 read with FT1802, 4 channel list. Reference file. Jim Zigan, 03/18/2014 09:28 PM
ft1802.py (8.98 KB) ft1802.py FT-1900 driver Tom Hayward, 03/19/2014 10:48 AM

Updated by Jim Zigan about 11 years ago

Hi CHIRP gang, 2014-03-18

Played with the FT1802 and FT1900 for about 10 hours looking a clues and wanted to share a couple of things I learned.
Radio ID FT1802 0x4148303222 FT-1900 0x564323300.
Same number of memory channels 0 – 199.
Same number of PMS Memories L0 – U9
Same Home Frequency.
Same VFO frequency.
Same 8 banks of linked scan lists.
Same 60 item configuration list as far as I can see.
The big difference appears to be the FT1900 has progammable CTCSS-TX tone (Hz) (1 word?), DCS Tx Code (magic table lookup) (1 byte?) instead of Rx=Tx settings. So guessing 200 channels * 3 bytes worth of extra data.
The download block of data appears to be the same length for both radios.
What I did was hand program both radios to be exactly the same (to the best I could do) and dump both radios for your comparison. Was thinking by file comparison, and knowing the FT1802, you might get lucky with some simple offsets to adjust for the new CTCSS-TX and DCS TX bytes.
There are only 4 channels programmed, but both radios the same.

Actions #2

Updated by Jim Zigan about 11 years ago

Arg moved wrong file. What a newby... So here is the FT1802 reference file.

Actions #3

Updated by Tom Hayward about 11 years ago

I'm not sure how you determined the download block was the same size. If you used the FT-1802 driver to download, of course it is the same size, because it only requests the number of bytes in the FT-1802.

Actions #4

Updated by Tom Hayward about 11 years ago

  • File ft1802.py ft1802.py added
  • Status changed from New to Incomplete
  • % Done changed from 0 to 50

In an intriguing turn of events, I have discovered what appears to be a complete FT-1900 driver on my dev computer. I cannot verify its accuracy, but it seems to read your sample file just fine. It simply uses the FT-1802 driver with a different memory map. You can try it yourself with Load Module.

Actions #5

Updated by Jim Zigan about 11 years ago

We like good turn of events! Tried your updated FT1802 with .img file, worked fine. Would not read from real radio. Guessed solution from "_block_lengths = [14, 8001]" --> "_block_lengths = [10, 8001]" and in a matching good turn of events, now reads from radio. I'm guessing this 10 is the 10 bytes from the header before the first ACK?
---- sniffer trace ------
FT1900 Answer: 3/17/2014 10:38:08 PM.32264

56 43 32 33 00 02 46 01 01 01 VC23..F...

Request: 3/17/2014 10:38:08 PM.40164 (+0.0625 seconds)

06 .

Answer: 3/17/2014 10:38:08 PM.40164 (+0.0000 seconds)

06 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF .ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF ...... rest of the memory dump...

I will check out other features after I get some sleep ;-)
Can bump to 60% :-)

Actions #6

Updated by Tim Smith over 8 years ago

  • Status changed from Incomplete to Closed
  • % Done changed from 50 to 100
Actions

Also available in: Atom PDF