does only provide the IDs and bus info as you say.
was more generally referencing getting the information
on the USB part of the GPS puck.
GPS units don't report as USB serial devices (either
FTDI or CP2102 type devices) so never link
to /dev/ttyUSB# at all. One example I experienced was
based on the Atmega 32u4F with firmware that reports as
a GPS USB device. As another exmaple, I don't think the
Argent Data T3 inside the F301 data radio did not show
as a ttyUSB# device. Most assigned /dev/ttyACM# as the
in those cases, you really I created udev rules based
off the lsusb information to created files in /dev that
can be linked to COM# in WINE.
had several for different :
Standard USB-to-TTL I used for CAT control of my FT100D,
/dev/ft100, /dev/ft900, ...
the case of the T3, it had vendor=0x134a product=0x9000,
so an example udev rule would be:
have found it best to use as few comparisons as
possible, but make it to ensure the rule becomes
unique. serial numbers are the best way. Since many
usb to ttl adaptors are TDI, the vender ID is same, so
the serial number will determine which link.
"Greg D ko6th.greg@...
Thursday, December 13, 2018 2:09 PM
Re: [aprsisce] Recompile for Linux.
For your USB GPS puck,
that will depend on how the GPS
reports itself to the Linux OS.
Greg's advice of using 'dmesg' will
provide the information, or you can
plug in the device and at the prompt
At least on my system, lsusb only
displays the USB device information
(manufacturer IDs, strings), but not
the /dev/ttyUSBx info. Do you get
more on yours?