Paul:
You might be correct here, but I suspect the reasons may be different from most radios. FT-1Ds come with either a Yaesu SCU-18 or SCU-19 cable depending on their vintage. Yaesu provides Windows drivers. I just went back and looked and there are no Mac instructions. The drivers for the '18 and the '19 are packaged separately and I suppose that they may be different. I suspect that I just didn't get lucky and find that the standard out-of-the-box Linux driver worked.
I'd like to know if the author of the Chirp code for the FT-1D tested with Linux. On 04 Feb. I sent a note to this list asking if the SCU-18s or SCU-19s presented any issues under Linux. I wonder if I'm the first to try it.
I'm game to try to wrestle this to the ground if I have a modest expectation of success. Knowing that I'm not the first would be sufficient. If all I wanted to do was back the radio up I could try 1) Chirp with Windows, 2) Yaesu's ADM-6 software with Windows, and 3) I suspect that if I re-read the manual I'd find a backup command to the microSD card in the radio.
Backtracking to previous issues, I just discovered that the default scrollback limit with Ubuntu is 512 lines. Gak!!
thanks,,, Alan,,, n4lbl
On Thu, Feb 12, 2015 at 7:40 AM, W Paul Mills AC0HY@wpmills.com wrote:
Problem is, this is an operating system / cable hardware issue. There would need to be different instructions for each operating system and possible cable type. All for something that is not a part of chirp. If anyone should be providing this information, it should be the manufacturer of the cable you are using.
By default, linux users tend to be somewhat on their own on these things, regardless of manufacturer. Things linux users need to understand to some degree are the /dev/ directory, lsusb command, and groups and sometimes file permissions.
And windows users don't get a free ride either, because of the things that often get done behind your back. One needs to be familiar with device manager, and need to know about rolling back drivers in some cases. And this can become a major pain. This can even be a problem when using factory supplied software.
Add to this numerous problems caused by some manufacturers using counterfeit chips, and chip makers attempting to protect themselves from this.
On 02/12/2015 05:44 AM, Brian Carling wrote:
I wish they would put all the stuff on the chirp website so we can actually use it!
Best regards - Brian Carling AF4K Crystals Co. 117 Sterling Pine St. Sanford, FL 32773
Tel: +USA 321-262-5471
On Feb 11, 2015, at 10:37 PM, Amber Fechko <amber@dendriticspine.com mailto:amber@dendriticspine.com> wrote:
Make sure you're not running through an external USB hub or anything; connect directly to the computer.
Try disconnecting the cable, and then running:
user@host:~$ dmesg (a ton of system messages should stream by)
Then reconnect your cable, turn on radio/volume up (shouldn't be necessary for dmesg output, but might as well do it now), and run the same command:
user@host:~$ dmesg (all of the previous system messages, and hopefully something new indicating a usb->serial device like below) [430941.789785] usb 2-1.7: new full-speed USB device number 49 using ehci-pci [430941.883258] usb 2-1.7: New USB device found, idVendor=067b, idProduct=2303 [430941.883267] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [430941.883272] usb 2-1.7: Product: USB-Serial Controller [430941.883277] usb 2-1.7: Manufacturer: Prolific Technology Inc. [430941.883801] pl2303 2-1.7:1.0: pl2303 converter detected [430941.885384] usb 2-1.7: pl2303 converter now attached to ttyUSB0
Assuming your system registers the usb->serial cable, you should see it in dmesg w/the device it was assigned (/dev/ttyUSB0 in my case -- vdir /dev/ttyUSB* is faster if you just need the device ID, but if vdir isn't showing anything, dmesg might give you a hint as to why).
I had to enter /dev/ttyUSB0 manually in the "Port" section of CHIRP -- it didn't show by default unless I restarted CHIRP after the cable was connected.
-Amber
On Wed, Feb 11, 2015 at 7:11 PM, n4lbl <alan.schulman@gmail.com mailto:alan.schulman@gmail.com> wrote:
Thanks. I suspect that this is interesting: n4lbl@eel:~$ vdir /dev/ttyUSB vdir: cannot access /dev/ttyUSB: No such file or directory On Wed, Feb 11, 2015 at 4:10 PM, W Paul Mills <AC0HY@wpmills.com <mailto:AC0HY@wpmills.com>> wrote: Should be showing as /dev/ttyUSB0 or something similar. From a text box or terminal screen type "vdir /dev/ttyUSB*" and see what the results show. If nothing shows, your cable is not being recognised. If it shows, but not in chirp text box, type it in, and it should work. On 02/11/2015 02:49 PM, n4lbl wrote: > When trying to download I get the message: > > An error has occurred > Could not configure port: (5, 'Input/output error') > > The environment is Ubuntu 14.04, Chirp daily -20150210, cable SCU-18 > with power light on, HT in CLONE mode. > > The Radio box presents port choices /dev/ttyS0 thru /dev/ttyS31 and I > have tried many of these but not all, and always received the same exact > message. There were no USB possibilities presented. > > The message said nothing of permissions. I did check anyway and saw: > > n4lbl@eel:~$ groups n4lbl > n4lbl : n4lbl adm dialout fax cdrom floppy tape audio dip video > plugdev fuse scanner lpadmin netdev sambashare > > so that seems OK. > > The HT's internal code is ancient: from when I bought it in Nov. or > Dec. '13. My intention was to back it up before upgrading the code. > > This is sure to be a knuckleheaded mistake or something I didn't read or > forgot. > Thanks,,, > > Alan,,, n4lbl > > > _______________________________________________ > chirp_users mailing list > chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > Unsubscribe: http://intrepid.danplanet.com/mailman/options/chirp_users--/*************************************************
- Amateur Radio Station AC0HY *
- W. Paul Mills SN807 *
- Assistant EC Alpha-1 ARES Shawnee/Wabunsee, KS *
- President Kaw Valley Amateur Radio Club *
*************************************************/ _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users Unsubscribe: http://intrepid.danplanet.com/mailman/options/chirp_users