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