OK, will come back after trying.

-----Original Message----- From: esarfl@gmail.com [mailto:esarfl@gmail.com] On Behalf Of Tom Hayward Sent: Friday, March 22, 2013 7:56 PM To: ran@bgu.ac.il Cc: chirp_devel@intrepid.danplanet.com Subject: Re: CHIRP programming

On Fri, Mar 22, 2013 at 10:40 AM, Ran Giladi ran@bgu.ac.il wrote:

Thanks. My apologies.

I connected my Baofeng UV-5R to Chirp (under Linux) - and it works.

Now, to the main issue - can we work on the FT-1900 on-line, to include it?

We need physical access to the radio to add support for it.

You can try to write support for it yourself. Start by copying another Yaesu radio module, like ft1802.py, and changing the names to FT-1900. Attempt a download from the radio. In the console/debug.log, you will see a counter as it is reading data. If this counter stops incrementing and you get a clone timeout, you have found the memsize of your FT-1900. Lower the memsize value in your new ft1900.py file until you get a successful read. This assumes the FT-1900 speaks the same protocol as other Yaesus, which is most likely true.

Now you can start guessing the locations and encoding of the memory contents. The way I do this is by resetting the radio, reading its contents, then saving the img file. Now add a memory from the radio's front panel, download, and save another img. Compare the two img files with hexdump and diff. Now you will see what changes in the file when a memory is added.

PS - what should be done to see the menu?

This is a "feature" of Ubuntu that we have no control over. You can remove the feature from Ubuntu with "sudo apt-get remove indicator-appmenu" but be warned this may break other things.

Tom KD7LXL

On Fri, Mar 22, 2013 at 1:22 PM, Ran Giladi ran@bgu.ac.il wrote:

The FT1900R was in CLONE mode (same as 1802, i.e., on+A/N LOW), but failed to read. Where is the debug.log?

The console output is the debug log... you found it.

I got this message on the console:

User selected Yaesu FT-1900R on port /dev/ttyUSB0 Clone thread started

-- Exception: -- Traceback (most recent call last): File "/home/ran/Downloads/chirp-0.3.0/chirpui/clone.py", line 225, in run self.__radio.sync_in() File "/home/ran/Downloads/chirp-0.3.0/chirp/yaesu_clone.py", line 199, in sync_in self._mmap = _clone_in(self) File "/home/ran/Downloads/chirp-0.3.0/chirp/yaesu_clone.py", line 84, in _clone_in raise errors.RadioError("Failed to communicate with the radio: %s" % e) RadioError: Failed to communicate with the radio: No response from radio

---

Clone failed: Failed to communicate with the radio: No response from radio Clone thread ended --- Exception Dialog: Failed to communicate with the radio: No response from radio --- None

---

This looks like you didn't attach the cable or didn't hit the button on the radio to start the clone. When you started the clone on the radio, did the progress bar (s-meter) on the radio advance until full, then return to clone mode?

Tom KD7LXL

On Fri, Mar 22, 2013 at 1:31 PM, Ran Giladi ran@bgu.ac.il wrote:

Great debug.log!

The cable is attached, the FT1900 comes on (with the A/N LOW pressed) directly with a "CLONE" message on its screen, no S-bar, just music...

Excellent, sounds like everything is working as intended. By hitting OK in Chirp, you have successfully completed step 4 of the cloning procedure in the FT-1900 manual. Now complete the rest of the steps.

Tom KD7LXL