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...
-----Original Message----- From: esarfl@gmail.com [mailto:esarfl@gmail.com] On Behalf Of Tom Hayward Sent: Friday, March 22, 2013 10:27 PM To: ran@bgu.ac.il; chirp_devel@intrepid.danplanet.com Subject: Re: [chirp_devel] CHIRP programming
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