[chirp_users] Error Trying To Download From FT-1D
n4lbl
Thu Feb 12 09:56:56 PST 2015
Thanks Aubrey. lsusb is at least familiar to me. The before and after are:
n4lbl at eel:~$ lsusb
Bus 001 Device 004: ID 13d3:5702 IMC Networks UVC VGA Webcam
Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 045e:0737 Microsoft Corp. Compact Optical Mouse 500
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
n4lbl at eel:~$ lsusb
Bus 001 Device 004: ID 13d3:5702 IMC Networks UVC VGA Webcam
Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 0584:b03a RATOC System, Inc.
Bus 002 Device 002: ID 045e:0737 Microsoft Corp. Compact Optical Mouse 500
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
At this moment the radio isn't connected to the cable as it is being
recharged.
n4lbl at eel:~$ tail -f /var/log/syslog
Feb 12 10:45:17 eel mtp-probe: bus: 2, device: 6 was not an MTP device
Feb 12 10:46:21 eel kernel: [155678.200326] usb 2-2: USB disconnect, device
number 6
Feb 12 10:47:35 eel kernel: [155752.168182] usb 2-2: new full-speed USB
device number 7 using uhci_hcd
Feb 12 10:47:35 eel kernel: [155752.370019] usb 2-2: New USB device found,
idVendor=0584, idProduct=b03a
Feb 12 10:47:35 eel kernel: [155752.370035] usb 2-2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Feb 12 10:47:35 eel kernel: [155752.370046] usb 2-2: Product: USB-Serial
Converter
Feb 12 10:47:35 eel kernel: [155752.370056] usb 2-2: Manufacturer: RATOC
Systems,Inc.
Feb 12 10:47:35 eel mtp-probe: checking bus 2, device 7:
"/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2"
Feb 12 10:47:35 eel mtp-probe: bus: 2, device: 7 was not an MTP device
Feb 12 10:49:39 eel kernel: [155876.104263] usb 2-2: USB disconnect, device
number 7
comment: inserted cable here
Feb 12 10:51:18 eel kernel: [155975.080158] usb 2-2: new full-speed USB
device number 8 using uhci_hcd
Feb 12 10:51:18 eel kernel: [155975.280118] usb 2-2: New USB device found,
idVendor=0584, idProduct=b03a
Feb 12 10:51:18 eel kernel: [155975.280129] usb 2-2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Feb 12 10:51:18 eel kernel: [155975.280138] usb 2-2: Product: USB-Serial
Converter
Feb 12 10:51:18 eel kernel: [155975.280146] usb 2-2: Manufacturer: RATOC
Systems,Inc.
Feb 12 10:51:18 eel mtp-probe: checking bus 2, device 8:
"/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2"
Feb 12 10:51:18 eel mtp-probe: bus: 2, device: 8 was not an MTP device
I wish I knew what to do next!
thanx,,,
Alan,,, n4lbl
On Thu, Feb 12, 2015 at 9:40 AM, Aubrey Turner <aubrey.c.turner at gmail.com>
wrote:
> Alan,
>
> Something that might be easier to work with than dmesg is lsusb.
>
> If you run the 'lsusb' command you will see what devices Linux thinks are
> attached to the USB. What I do if I'm in doubt is to run lsusb before
> plugging in the cable, then run it again after plugging in the cable to see
> what, if anything, shows up that is different.
>
> On my system, running lsusb before plugging in the cable shows the
> following:
>
> Bus 002 Device 002: ID 8087:8000 Intel Corp.
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 003: ID 13d3:3404 IMC Networks
> Bus 001 Device 002: ID 8087:8008 Intel Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 003: ID 051d:0002 American Power Conversion Uninterruptible
> Power Supply
> Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>
> Running it *after* plugging in the cable shows this:
>
> Bus 002 Device 002: ID 8087:8000 Intel Corp.
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 003: ID 13d3:3404 IMC Networks
> Bus 001 Device 002: ID 8087:8008 Intel Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> *Bus 003 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
> Port*
> Bus 003 Device 003: ID 051d:0002 American Power Conversion Uninterruptible
> Power Supply
> Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> Note the difference.
>
> Another approach is to use the 'tail' command to watch the system logs as
> you plug in the cable.
>
> For example, if you run "tail -f /var/log/syslog" (this is in Ubuntu
> 14.04) and then plug in the cable, you should see something like the
> following:
>
> Feb 12 10:24:35 runabout kernel: [696555.274063] usbcore: registered new
> interface driver usbserial
> Feb 12 10:24:35 runabout kernel: [696555.274073] usbcore: registered new
> interface driver usbserial_generic
> Feb 12 10:24:35 runabout kernel: [696555.274080] usbserial: USB Serial
> support registered for generic
> Feb 12 10:24:35 runabout kernel: [696555.275486] usbcore: registered new
> interface driver pl2303
> Feb 12 10:24:35 runabout kernel: [696555.275495] usbserial: USB Serial
> support registered for pl2303
> Feb 12 10:24:35 runabout kernel: [696555.275511] pl2303 3-9:1.0: pl2303
> converter detected
> Feb 12 10:24:35 runabout kernel: [696555.276716] usb 3-9: pl2303 converter
> now attached to ttyUSB0
>
> The above is pretty much what dmesg will give you, although you are seeing
> it in "real time" as it were.
>
> (Note that "-f" means that tail will continuously follow the file, so you
> have to press Ctrl-C to stop)
>
> Of course, you mileage may vary, as it will depend on what chipset the
> Yaesu cable is using. I suspect they aren't using the PL2303 that I'm
> using (the above is for a typical Chinese UV-5R programming cable as I
> don't have a FT-1D or either of its programming cables).
>
> Good luck,
> Aubrey - K5ACT
>
>
>
>
> On 02/12/2015 10:02 AM, n4lbl wrote:
>
> 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 at 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 at dendriticspine.com
>> > <mailto:amber at 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 at 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 at 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 at gmail.com
>> >> <mailto:alan.schulman at gmail.com>> wrote:
>> >>
>> >> Thanks. I suspect that this is interesting:
>> >>
>> >> n4lbl at 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 at wpmills.com
>> >> <mailto:AC0HY at 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 at 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 at intrepid.danplanet.com
>> >> <mailto:chirp_users at 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 at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> Unsubscribe: http://intrepid.danplanet.com/mailman/options/chirp_users
>>
>
>
>
> _______________________________________________
> chirp_users mailing listchirp_users at intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users
> Unsubscribe: http://intrepid.danplanet.com/mailman/options/chirp_users
>
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> Unsubscribe: http://intrepid.danplanet.com/mailman/options/chirp_users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20150212/d35993d6/attachment.html
More information about the chirp_users
mailing list