[chirp_users] works fine with Baofeng_UV-5R
but does not download from radio with my FT60R (with a different cable, of course. ExpertPower although in Win7 it says Prolific)
Here are the conditions running under a Ubuntu derivative OS (Zorin).
chirp Daily-20120111 GTK 2.24.4 PyGTK 2.22.0 Python 2.7.1+
And the debug log last entry is
User selected Yaesu FT-60 on port /dev/ttyUSB0 Clone thread started Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... -- Exception: -- Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/chirpui/clone.py", line 225, in run self.__radio.sync_in() File "/usr/lib/pymodules/python2.7/chirp/ft60.py", line 196, in sync_in raise errors.RadioError("Failed to communicate with radio: %s" % e) RadioError: Failed to communicate with radio: Radio is not responding ------ Clone failed: Failed to communicate with radio: Radio is not responding Clone thread ended --- Exception Dialog: Failed to communicate with radio: Radio is not responding --- None
Beats me...acts like the magic word isn't recognized by the radio. Or the brand new cable is B/O.
tia
Gary WA6DTX
On Thu, Jan 17, 2013 at 11:35 PM, Gary dtx2@wa6dtx.com wrote:
but does not download from radio with my FT60R (with a different cable, of course. ExpertPower although in Win7 it says Prolific)
Here are the conditions running under a Ubuntu derivative OS (Zorin).
chirp Daily-20120111 GTK 2.24.4 PyGTK 2.22.0 Python 2.7.1+
And the debug log last entry is
User selected Yaesu FT-60 on port /dev/ttyUSB0 Clone thread started Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... Trying again... -- Exception: -- Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/chirpui/clone.py", line 225, in run self.__radio.sync_in() File "/usr/lib/pymodules/python2.7/chirp/ft60.py", line 196, in sync_in raise errors.RadioError("Failed to communicate with radio: %s" % e) RadioError: Failed to communicate with radio: Radio is not responding
Clone failed: Failed to communicate with radio: Radio is not responding Clone thread ended --- Exception Dialog: Failed to communicate with radio: Radio is not responding --- None
Beats me...acts like the magic word isn't recognized by the radio. Or the brand new cable is B/O.
tia
Gary WA6DTX
You can test the FT-60 cable without a radio. The txd and rxd lines are tied together, so if you connect the cable and open the port with a terminal emulator, anything you type should be echoed back to your terminal. This will tell you if the cable itself is working, in which case it may be a dirty or broken connector on the FT-60 causing you trouble. If letters you type are not echoed back to the screen, you've got a cable issue.
On Ubuntu, I use minicom as a terminal emulator.
Tom KD7LXL
On 01/18/2013 09:47 AM, Tom Hayward wrote:
You can test the FT-60 cable without a radio. The txd and rxd lines are tied together, so if you connect the cable and open the port with a terminal emulator, anything you type should be echoed back to your terminal. This will tell you if the cable itself is working, in which case it may be a dirty or broken connector on the FT-60 causing you trouble. If letters you type are not echoed back to the screen, you've got a cable issue. On Ubuntu, I use minicom as a terminal emulator. Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Thank you, Tom. Will come in handy in the future but in this case it was a RTFM problem. Actually, I had but did not realize the CLONING procedure on pg 65 had to be followed going computer to/from radio. Assumed it would have an auto start function, e.g. the UV-5R. I though it was only needed to initiate radio to radio cloning. No, it is need to send/receive data to a computer as well. Who'd athunk it ;-)
Gary WA6DTX
On Fri, Jan 18, 2013 at 11:51 AM, Gary dtx2@wa6dtx.com wrote:
Thank you, Tom. Will come in handy in the future but in this case it was a RTFM problem. Actually, I had but did not realize the CLONING procedure on pg 65 had to be followed going computer to/from radio. Assumed it would have an auto start function, e.g. the UV-5R. I though it was only needed to initiate radio to radio cloning. No, it is need to send/receive data to a computer as well. Who'd athunk it ;-)
Indeed, lack of computer-initiated programming is a very frustrating feature of the Yaesu rigs.
Tom KD7LXL
Indeed, lack of computer-initiated programming is a very frustrating feature of the Yaesu rigs.
Yeah, the confusion comes from the fact that Yaesu radios are actually not computer-programmable. They are, however, clone-able. The software thus acts like another radio to facilitate the job, but the obvious bits are missing (such as initiation).
They're really the only radios I come into contact with that have this horrible limitation, and it's very annoying for development of drivers for these rigs.
Vote with your wallet! :)
participants (3)
-
Dan Smith -
Gary -
Tom Hayward