On Thu, 4 Apr 2019 08:41:09 -0700
Dan Clemmensen wrote:
> I think the micro-USB "data" port on the DFT-70 is
> really an OTG port, not an embedded pl2303 chip.
OK, I think I've got it.
The g_* modules only had g_serial, but the cdc_* were all available.
After removing the *2303 module and mo
On Thu, 4 Apr 2019 08:41:09 -0700
Dan Clemmensen wrote:
> you can test this theory by first removing the pl2303 module:
>sudo modprobe -r pl2303
> and then plugging your FT-70 back in. If my theory is
> correct, /dev/ttyACM0 will come back into existence, but pl2303 will
> not reload.
You're
After sleeping on it, I'm almost certain that we made some mistaken
assumptions. I think the micro-USB "data" port on the DFT-70 is really an
OTG port, not an embedded pl2303 chip. This explains why your Linux box
calls it /dev/ttyACM0 and instead of /dev/ttyUSB0. If this is the case, the
pl2303 mo
On Thu, 4 Apr 2019 09:08:06 -0400 (EDT)
"Nigel A. Gunn G8IFF/W8IFF" wrote:
> It's usually /dev/ttyUSB0
Not in this case, it isn't. =/
> Make sure you're a member of the dialout group.
Just tested, it's good.
-Dennis
___
chirp_users mailing list
It's usually /dev/ttyUSB0
Make sure you're a member of the dialout group.
> On 04 April 2019 at 00:51 Dan Clemmensen wrote:
>
> I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux,
> that would be assigned to a modem a fake modem such as an OTG-connect3d phone
> or some
On Wed, 3 Apr 2019 22:36:26 -0700
Dan Clemmensen wrote:
> Sorry, I made a few mistakes, apparently. You will need to get an
> answer from someone who has an FT-70.
No, you're fine, you're on the right track - but you're probably not
wrong about anyone else who's had the experience.
Of note, ha
Sorry, I made a few mistakes, apparently. You will need to get an answer
from someone who has an FT-70. See this thread:
http://intrepid.danplanet.com/pipermail/chirp_users/2017-October/012735.html
On Wed, Apr 3, 2019 at 10:20 PM Dan Clemmensen
wrote:
> that's the device ID for a pl2303. the nam
On Wed, 3 Apr 2019 22:20:07 -0700
Dan Clemmensen wrote:
> that's the device ID for a pl2303. the name of the module is
> pl2303
>
> execute
> lsmod
> to see if the module got loaded.
It's there:
dennisthetiger@goodfellow:~$ lsmod | grep pl2303
pl2303 20480 0
usbserial
that's the device ID for a pl2303. the name of the module is
pl2303
execute
lsmod
to see if the module got loaded.
If not,
sudo modprobe pl2303
to force-load the module
On Wed, Apr 3, 2019 at 10:07 PM Dennis Carr
wrote:
> On Wed, 3 Apr 2019 21:51:05 -0700
> Dan Clemmensen wrote:
>
>
On Wed, 3 Apr 2019 22:03:22 -0700
Dan Clemmensen wrote:
> Silly me. On Debian systems (and on my Gentoo system) you can just do
> this: ls -l /dev/serial/by-id
Well, that comes out with usb-26aa_001b_-if00 - which
matches the devid in lsusb.
-Dennis
_
On Wed, 3 Apr 2019 21:51:05 -0700
Dan Clemmensen wrote:
> I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux,
> that would be assigned to a modem a fake modem such as an
> OTG-connect3d phone or something like that.
Yeah, confirmed, it's /dev/ttyACM0. Tried 'watch'ing that, b
Silly me. On Debian systems (and on my Gentoo system) you can just do this:
ls -l /dev/serial/by-id
This directory has a file whose name is the ID string of each serial
device , linkte to the tty filename. With this approach you do not need to
unplug and re-plug your cable.
On Wed, Apr 3, 20
I'm a bit surprised that it's /dev/ttyACM0. on my (non-Debian) Linux, that
would be assigned to a modem a fake modem such as an OTG-connect3d phone or
something like that. Check this by first unplugging the cable from the
comouter and then doing:
ls /dev/tty*
Then plug the cable back into the co
Howdy!
Running a Yaesu Ft-70DR that just arrived today. First thing's first:
download to Chirp! Running daily 20190221 on Debian current stable,
using the builds from the website.
Just one problem - it didn't download.
After following instructions (battery off, DC and USB in (specifically
the
14 matches
Mail list logo
