CHIRP

I wrote a message on the developer mailing list too.

Using the file that the radio made on the micro-SD card and a hex editor I tried to analyze the file and look for probable locations of different data. After I made a general memory map I looked at the mapping used by the FTM-350 module of Chirp, and the basic address blocks seem to be the same. There are new features and setting I will have to locate, but first I might want to implement the methods of importing the data into Chirp, which in this case can be done in two ways, memory card or cable.

As I mentioned on the developer mailing list, the actual radio I bought has the transmit frequencies unlocked and it is claimed to be able to transmit on 137-174 and 400-480 MHz, which is quite useless for a law abiding ham, but it can help us locate the TX limits in memory if anyone else can provide a memory dump from a normal radio.

One thing I noted in the common Chirp code is the lack of channel spacing 8.33 MHz for Air Band, which this radio can receive (AM, of course).

Inherit the clone routines from the FTM-350. Those will probably work.

The @match_model()@ routine will allow you to open the files copied from the radio. We usually just use length as the identifier as long as there's not a conflict.

Regarding the file I attached, the callsign is not mine, since I do not have one yet. This radio demands a callsign to be entered in order to be able to use the radio at all, and since I will not be transmitting, only receiving, a friend allowed me to enter his callsign.

The callsign is found in two places, at 0x2b8 and at 0x508, the latter with added APRS data.

Thanks for the help, Tom. I had to make a small change to make it read bank B correctly, and I have only worked with the full file so far. Either it does not recognize tone mode, or I have failed to set it in my rig.

I have done more analyzing of the memory dump, so I think I will be able to add some to this soon.

In the character set for labels it seems that the number 0 is now 0xbf, which shows as a qeustion mark in Chirp.

I will keep working on it at my end.

Seems like the FTM400 effort is stalled.. Maybe I can kickstart it..

I have successfully populated a FTM400 (v1.9) dat file with a chirp CSV. This is the only radio that I have that chirp doesn't work with, so I wrote my own tool.

The data in this spreadsheet has been confirmed:
https://docs.google.com/spreadsheets/d/1Qn5wanBEPYKfFTT_YugJCQU-J17CJAZhdD8cft4vBLs/edit#gid=1778955122

Hope this helps someone do what needs to be done to get it working in chirp.

Just (finally!) got my FTM-400XDR and love it! Would love it even more if it would work with Chirp, any progress on this thread?
Thanks much!

73 de K6JPE

I am running "CHIRP daily-20161208" on Windows 7 and there is no "drivers" subdirectory in the chirp installation (which is in c:\Programs (x86)\CHIRP). Can you let me know where the .py file needs to go?

Once you enable developer functions under Help, you can use File > Load Module to load this driver. You will need to do this every time you open Chirp.

Thanks, Tom. I tried this but I get the error, "Unable to load module: invalid syntax (ftm400.py, line 1)". Any suggestions?

John Murphy wrote:

I have started using this file to read/write the FTM400 I have. This appears to be working, and supporting independent top/bottom memories.

I don't have a laptop handy to test cloning with this. This needs to be placed into the drivers/ subdirectory of the chirp installation to use it.

Hello John,

Just got my FTM-400 and tried this. On my Linux machine, nothing happens at all when I try to download from the radio. No attempt to communicate at all.

In my Windows machine, the transfer fails with "Failed to download from radio (String index out of range)

John Murphy wrote:

I have started using this file to read/write the FTM400 I have. This appears to be working, and supporting independent top/bottom memories.

I don't have a laptop handy to test cloning with this. This needs to be placed into the drivers/ subdirectory of the chirp installation to use it.

More info on the linux error. Got this when I tried to start the download:

Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/mainapp.py", line 1582, in mh
self.do_download(*args)
File "/usr/lib/python2.7/dist-packages/chirp/ui/mainapp.py", line 681, in do_download
timeout=0.25)
File "/usr/lib/python2.7/dist-packages/serial/serialutil.py", line 261, in init
self.open()
File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 282, in open
self._reconfigurePort()
File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 417, in _reconfigurePort
set_special_baudrate(self, custom_baud)
File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 60, in set_special_baudrate
raise ValueError('Failed to set custom baud rate: %r' % baudrate)
ValueError: Failed to set custom baud rate: 48000

Tom Henderson wrote:

Just got my FTM-400 and tried this. On my Linux machine, nothing happens at all when I try to download from the radio. No attempt to communicate at all.

In my Windows machine, the transfer fails with "Failed to download from radio (String index out of range)

Did you go to the [RESET/CLONE] menu in your radio and select [7 CLONE] then [This radio -> Other] to start the data transfer on the radio?

+1 what's up with this request? 6 years?