Discussion:
"Fixing" serial port addresses, session to session.
(too old to reply)
'Dave B' g8kbvdave-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org [linuxham]
2014-10-07 10:49:17 UTC
Permalink
OK. Not Flxxx related, but definately Linux and Ham related...

Anti flame suit at the ready...

I've done my Googling (or whatever you want to call it) regarding this, and
though I can find lots of information, none of what I've tried so far, works how I
would like it to. I do know it's been mentioned here before, so here's a
question for the collective...

I need two(maybe three) indipendant serial ports, I have the hardware, and
software (GPS, TH-D7, other rig control etc, all for use with YAAC. "Yet Another
APRS Client" for an upcomming 4x4 trip away next month.)

One of the "problems" seems to be, that I'm using two identical USB/RS232
devices, so the maker and product name data are the same. (Prolific.)

Plus. Just to add insult, the USB GPS RX, also uses an embedded Prolific chip!
All the USB VID/PID numbers are the same as a result. Just the individual
device serial number are different, and as yet, I can't find a way to get Linux to
diferentiate between them, in a predictable way.

I would greatly like to not have to plug the gadgetry in, in a set order after the
OS boots just to make sure that they "appear" to the application in the same
order they were, before a power down the day before.

ttyUSB0 = GPS, ttyUSB1 = TH-D7, ttyUSB2 = HF rig PTT control for example.

So, how to make sure they "Always" appear at the same /ttyUSBx address where
they were last seen.

When manually inserted in order, then all works well, all devices are recognised,
and the software uses them all just fine. Just that as above, I'd like them to
"come back" in the same places they were before the shutdown the day before.
(Easy to fix with that "Other" OS!)

I'm using Lubuntu 13.x.x LTS on an Acer One netbook. It's different enough
from Ubuntu/Debian, that though I can see much of what many pages talk
about, I'm still missing some understanding, as many times when the machine is
started from cold with everyting connected, the individual devices re-appear at
different ttyUSBx addresses, causing "Utter Mayhem" within YAAC (and the D7)
to say the least.

Can this be done easily, or, do I have to keep messing about with
unplugging/replugging the things etc? USB connectors in hostile mobile
environments are less than reliable too I find, but not a lot of choice at present,
other than to duct-tape all the cables etc, and that makes the
unplug/boot/replug thing even more difficult!

In a cramped mobile environment, that's "less than ideal!", especially for the
first start of the day, when the wetware grey cell may not yet be fully up to
speed itself ! ;-)

73.

Dave G0WBX.



------------------------------------
Posted by: "Dave B" <g8kbvdave-gM/Ye1E23mwN+***@public.gmane.org>
------------------------------------
mm0fmf mm0fmf-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org [linuxham]
2014-10-07 10:59:47 UTC
Permalink
OK. Not Flxxx related, but definately Linux and Ham related...
Anti flame suit at the ready...
I've done my Googling (or whatever you want to call it) regarding this, and
though I can find lots of information, none of what I've tried so far, works how I
would like it to. I do know it's been mentioned here before, so here's a
question for the collective...
I need two(maybe three) indipendant serial ports, I have the hardware, and
software (GPS, TH-D7, other rig control etc, all for use with YAAC. "Yet
Another
APRS Client" for an upcomming 4x4 trip away next month.)
One of the "problems" seems to be, that I'm using two identical USB/RS232
devices, so the maker and product name data are the same. (Prolific.)
http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/




------------------------------------
Posted by: mm0fmf <mm0fmf-***@public.gmane.org>
------------------------------------
Charles Brabham n5pvl-eeV24iX8Xvtg9hUCZPvPmw@public.gmane.org [linuxham]
2014-10-07 13:35:26 UTC
Permalink
I've gotten around this problem by using a USB-Serial device that has
two ports instead of one, utilizing only one USB port. They make four
port devices too. Works great for me, no problems associated with
restarts, etc..

73 DE Charles, N5PVL
OK. Not Flxxx related, but definately Linux and Ham related...
Anti flame suit at the ready...
I've done my Googling (or whatever you want to call it) regarding this, and
though I can find lots of information, none of what I've tried so far, works how I
would like it to. I do know it's been mentioned here before, so here's a
question for the collective...
I need two(maybe three) indipendant serial ports, I have the hardware, and
software (GPS, TH-D7, other rig control etc, all for use with YAAC.
"Yet Another
APRS Client" for an upcomming 4x4 trip away next month.)
One of the "problems" seems to be, that I'm using two identical USB/RS232
devices, so the maker and product name data are the same. (Prolific.)
Plus. Just to add insult, the USB GPS RX, also uses an embedded
Prolific chip!
All the USB VID/PID numbers are the same as a result. Just the individual
device serial number are different, and as yet, I can't find a way to get Linux to
diferentiate between them, in a predictable way.
I would greatly like to not have to plug the gadgetry in, in a set order after the
OS boots just to make sure that they "appear" to the application in the same
order they were, before a power down the day before.
ttyUSB0 = GPS, ttyUSB1 = TH-D7, ttyUSB2 = HF rig PTT control for example.
So, how to make sure they "Always" appear at the same /ttyUSBx address where
they were last seen.
When manually inserted in order, then all works well, all devices are recognised,
and the software uses them all just fine. Just that as above, I'd like
them to
"come back" in the same places they were before the shutdown the day before.
(Easy to fix with that "Other" OS!)
I'm using Lubuntu 13.x.x LTS on an Acer One netbook. It's different
enough
from Ubuntu/Debian, that though I can see much of what many pages talk
about, I'm still missing some understanding, as many times when the machine is
started from cold with everyting connected, the individual devices re-appear at
different ttyUSBx addresses, causing "Utter Mayhem" within YAAC (and the D7)
to say the least.
Can this be done easily, or, do I have to keep messing about with
unplugging/replugging the things etc? USB connectors in hostile mobile
environments are less than reliable too I find, but not a lot of choice at present,
other than to duct-tape all the cables etc, and that makes the
unplug/boot/replug thing even more difficult!
In a cramped mobile environment, that's "less than ideal!", especially for the
first start of the day, when the wetware grey cell may not yet be fully up to
speed itself ! ;-)
73.
Dave G0WBX.
'Ekki Plicht (DF4OR)' eplicht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [linuxham]
2014-10-07 14:04:59 UTC
Permalink
Use udev rules. They are simple and clean.

My (symlinks to) devices are called "/dev/ic7400-ptt" or
"/dev/ic756pr3-cat" etc.

'lsusb -v' helps me in finding the proper pid/vid and serial number
informations required for udev-Rules.

See http://www.reactivated.net/writing_udev_rules.html

73,
Ekki, DF4OR
OK. Not Flxxx related, but definately Linux and Ham related...
Anti flame suit at the ready...
I've done my Googling (or whatever you want to call it) regarding this, and
though I can find lots of information, none of what I've tried so far, works how I
would like it to. I do know it's been mentioned here before, so here's a
question for the collective...
I need two(maybe three) indipendant serial ports, I have the hardware, and
software (GPS, TH-D7, other rig control etc, all for use with YAAC. "Yet
Another
APRS Client" for an upcomming 4x4 trip away next month.)
One of the "problems" seems to be, that I'm using two identical USB/RS232
devices, so the maker and product name data are the same. (Prolific.)
Plus. Just to add insult, the USB GPS RX, also uses an embedded Prolific
chip!
All the USB VID/PID numbers are the same as a result. Just the individual
device serial number are different, and as yet, I can't find a way to get Linux to
diferentiate between them, in a predictable way.
I would greatly like to not have to plug the gadgetry in, in a set order after the
OS boots just to make sure that they "appear" to the application in the same
order they were, before a power down the day before.
ttyUSB0 = GPS, ttyUSB1 = TH-D7, ttyUSB2 = HF rig PTT control for example.
So, how to make sure they "Always" appear at the same /ttyUSBx address where
they were last seen.
When manually inserted in order, then all works well, all devices are recognised,
and the software uses them all just fine. Just that as above, I'd like
them to
"come back" in the same places they were before the shutdown the day before.
(Easy to fix with that "Other" OS!)
I'm using Lubuntu 13.x.x LTS on an Acer One netbook. It's different enough
from Ubuntu/Debian, that though I can see much of what many pages talk
about, I'm still missing some understanding, as many times when the machine is
started from cold with everyting connected, the individual devices re-appear at
different ttyUSBx addresses, causing "Utter Mayhem" within YAAC (and the D7)
to say the least.
Can this be done easily, or, do I have to keep messing about with
unplugging/replugging the things etc? USB connectors in hostile mobile
environments are less than reliable too I find, but not a lot of choice at present,
other than to duct-tape all the cables etc, and that makes the
unplug/boot/replug thing even more difficult!
In a cramped mobile environment, that's "less than ideal!", especially for the
first start of the day, when the wetware grey cell may not yet be fully up to
speed itself ! ;-)
73.
Dave G0WBX.
'Frank Dinger ,GM0CSZ' gm0csz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [linuxham]
2014-10-07 18:51:10 UTC
Permalink
quote ====

I'm using Lubuntu 13.x.x LTS on an Acer One netbook. It's different enough
from Ubuntu/Debian, that though I can see much of what many pages talk
about, I'm still missing some understanding, as many times when the machine
is
started from cold with everyting connected, the individual devices
re-appear at
different ttyUSBx addresses, causing "Utter Mayhem" within YAAC (and the
D7)
to say the least.

unquote ====

Lubuntu 13.x.x LTS ??

LTS versions are 10.04 ; 12.04 and 14.04

Frank , GM0CSZ
OK. Not Flxxx related, but definately Linux and Ham related...
Anti flame suit at the ready...
I've done my Googling (or whatever you want to call it) regarding this, and
though I can find lots of information, none of what I've tried so far, works how I
would like it to. I do know it's been mentioned here before, so here's a
question for the collective...
I need two(maybe three) indipendant serial ports, I have the hardware, and
software (GPS, TH-D7, other rig control etc, all for use with YAAC. "Yet
Another
APRS Client" for an upcomming 4x4 trip away next month.)
One of the "problems" seems to be, that I'm using two identical USB/RS232
devices, so the maker and product name data are the same. (Prolific.)
Plus. Just to add insult, the USB GPS RX, also uses an embedded Prolific
chip!
All the USB VID/PID numbers are the same as a result. Just the individual
device serial number are different, and as yet, I can't find a way to get Linux to
diferentiate between them, in a predictable way.
I would greatly like to not have to plug the gadgetry in, in a set order after the
OS boots just to make sure that they "appear" to the application in the same
order they were, before a power down the day before.
ttyUSB0 = GPS, ttyUSB1 = TH-D7, ttyUSB2 = HF rig PTT control for example.
So, how to make sure they "Always" appear at the same /ttyUSBx address where
they were last seen.
When manually inserted in order, then all works well, all devices are recognised,
and the software uses them all just fine. Just that as above, I'd like
them to
"come back" in the same places they were before the shutdown the day before.
(Easy to fix with that "Other" OS!)
I'm using Lubuntu 13.x.x LTS on an Acer One netbook. It's different enough
from Ubuntu/Debian, that though I can see much of what many pages talk
about, I'm still missing some understanding, as many times when the machine is
started from cold with everyting connected, the individual devices re-appear at
different ttyUSBx addresses, causing "Utter Mayhem" within YAAC (and the D7)
to say the least.
Can this be done easily, or, do I have to keep messing about with
unplugging/replugging the things etc? USB connectors in hostile mobile
environments are less than reliable too I find, but not a lot of choice at present,
other than to duct-tape all the cables etc, and that makes the
unplug/boot/replug thing even more difficult!
In a cramped mobile environment, that's "less than ideal!", especially for the
first start of the day, when the wetware grey cell may not yet be fully up to
speed itself ! ;-)
73.
Dave G0WBX.
mitchwinkle-/E1597aS9LQAvxtiuMwx3w@public.gmane.org [linuxham]
2014-10-07 19:55:22 UTC
Permalink
They all have the exact same name in /dev/serial/by-id?

------------------------------------
Posted by: mitchwinkle-/***@public.gmane.org
------------------------------------
Marty Hartwell mhartwe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [linuxham]
2014-10-08 00:29:56 UTC
Permalink
Hi Mitch
It isn't my problem but not the same name but same ID and they come up
in different order on
reboot/restart. It can be solved by setting udev rules for the ports. I
have sent Dave a direct email
to see if he had seen the response.

Marty kd8bj
Post by mitchwinkle-/***@public.gmane.org [linuxham]
They all have the exact same name in /dev/serial/by-id?
------------------------------------
Posted by: Marty Hartwell <mhartwe-***@public.gmane.org>
------------------------------------
ab4mw
2014-10-08 17:36:27 UTC
Permalink
Udev is the hard way, but it works. Symbolic links to the files in /dev/serial/by-id are easier for me and I can put the link in the program's working Dir.

I am old enough now to forgot how I accomplished things like udev rules. ;). Symlinks are in your face.

------------------------------------

------------------------------------
David Cole dave-0ILqX6cLdjY@public.gmane.org [linuxham]
2014-10-08 00:22:12 UTC
Permalink
Anyone else have the latest Chrome update blow up? Mine seg faults upon
start...
--
Thanks and 73's,
For equipment, and software setups and reviews see:
www.nk7z.net
for MixW support see;
http://groups.yahoo.com/neo/groups/mixw/info
for Dopplergram information see:
http://groups.yahoo.com/neo/groups/dopplergram/info
for MM-SSTV see:
http://groups.yahoo.com/neo/groups/MM-SSTV/info


On Tue, 2014-10-07 at 19:51 +0100, 'Frank Dinger ,GM0CSZ'
Post by 'Frank Dinger ,GM0CSZ' gm0csz-***@public.gmane.org [linuxham]
quote ====
I'm using Lubuntu 13.x.x LTS on an Acer One netbook. It's different enough
from Ubuntu/Debian, that though I can see much of what many pages talk
about, I'm still missing some understanding, as many times when the machine is
started from cold with everyting connected, the individual devices re-appear at
different ttyUSBx addresses, causing "Utter Mayhem" within YAAC (and the D7)
to say the least.
unquote ====
Lubuntu 13.x.x LTS ??
LTS versions are 10.04 ; 12.04 and 14.04
Frank , GM0CSZ
OK. Not Flxxx related, but definately Linux and Ham related...
Anti flame suit at the ready...
I've done my Googling (or whatever you want to call it) regarding this, and
though I can find lots of information, none of what I've tried
so far, works how I
would like it to. I do know it's been mentioned here before, so here's a
question for the collective...
I need two(maybe three) indipendant serial ports, I have the hardware, and
software (GPS, TH-D7, other rig control etc, all for use with
YAAC. "Yet Another
APRS Client" for an upcomming 4x4 trip away next month.)
One of the "problems" seems to be, that I'm using two
identical USB/RS232
devices, so the maker and product name data are the same. (Prolific.)
Plus. Just to add insult, the USB GPS RX, also uses an
embedded Prolific chip!
All the USB VID/PID numbers are the same as a result. Just the individual
device serial number are different, and as yet, I can't find a
way to get Linux to
diferentiate between them, in a predictable way.
I would greatly like to not have to plug the gadgetry in, in a
set order after the
OS boots just to make sure that they "appear" to the
application in the same
order they were, before a power down the day before.
ttyUSB0 = GPS, ttyUSB1 = TH-D7, ttyUSB2 = HF rig PTT control for example.
So, how to make sure they "Always" appear at the same /ttyUSBx
address where
they were last seen.
When manually inserted in order, then all works well, all
devices are recognised,
and the software uses them all just fine. Just that as above,
I'd like them to
"come back" in the same places they were before the shutdown
the day before.
(Easy to fix with that "Other" OS!)
I'm using Lubuntu 13.x.x LTS on an Acer One netbook. It's different enough
from Ubuntu/Debian, that though I can see much of what many pages talk
about, I'm still missing some understanding, as many times
when the machine is
started from cold with everyting connected, the individual
devices re-appear at
different ttyUSBx addresses, causing "Utter Mayhem" within
YAAC (and the D7)
to say the least.
Can this be done easily, or, do I have to keep messing about with
unplugging/replugging the things etc? USB connectors in hostile mobile
environments are less than reliable too I find, but not a lot
of choice at present,
other than to duct-tape all the cables etc, and that makes the
unplug/boot/replug thing even more difficult!
In a cramped mobile environment, that's "less than ideal!",
especially for the
first start of the day, when the wetware grey cell may not yet
be fully up to
speed itself ! ;-)
73.
Dave G0WBX.
------------------------------------
Posted by: David Cole <dave-***@public.gmane.org>
------------------------------------
'Dave B' g8kbvdave-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org [linuxham]
2014-10-08 09:34:14 UTC
Permalink
3d. Re: "Fixing" serial port addresses, session to session.
Date: Tue Oct 7, 2014 7:05 am ((PDT))
Use udev rules. They are simple and clean.
My (symlinks to) devices are called "/dev/ic7400-ptt" or
"/dev/ic756pr3-cat" etc.
'lsusb -v' helps me in finding the proper pid/vid and serial number
informations required for udev-Rules.
See http://www.reactivated.net/writing_udev_rules.html
73,
Ekki, DF4OR
Thanks Ekki. More good info.

Note however that the "udevinfo" command line tool does not exist in the
Ubuntu family of OS's (or so it seems, "command not found" and all that.)

However:-

$ sudo udevadm info -q all -n /dev/ttyUSB0 (for example)

does the trick to show a lot of info about the plugged device. Showing much
the same (and a bit more) info than Usbview.

Found on:-
http://ubuntuforums.org/showthread.php?t=1265469

via:-
http://ubuntuforums.org/showthread.php?t=1635946

73.

Dave G0WBX (going for a long read...)




------------------------------------
Posted by: "Dave B" <g8kbvdave-gM/Ye1E23mwN+***@public.gmane.org>
------------------------------------
'Dave B' g8kbvdave-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org [linuxham]
2014-10-08 09:45:59 UTC
Permalink
3b. Re: "Fixing" serial port addresses, session to session.
Date: Tue Oct 7, 2014 3:59 am ((PDT))
<Snipped>
http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/
Thanks for that.

As before, off for "a long read".

I have found out though after some fiddling about last night, that I have at least
two Prolific USB<>Serial devices, that are utterly indistinguisable as far as Linux
goes. ALL the udev information about them is identical, there is not even a
unique serial number to filter on. Luckily, I have enough such things, I can find
a selection of them that do show something different.

FTDI devices (and others) do seem to have unique serial numbers, so would be a
better choice in multiple port situations I think, if you have a choice...

73.

Dave G0WBX.



------------------------------------
Posted by: "Dave B" <g8kbvdave-gM/Ye1E23mwN+***@public.gmane.org>
------------------------------------
Andy mm0fmf-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org [linuxham]
2014-10-08 09:55:30 UTC
Permalink
Post by 'Dave B' g8kbvdave-gM/Ye1E23mwN+***@public.gmane.org [linuxham]
FTDI devices
I'm sure other devices work but FTDI devices are my preferred choice for several reasons.

1) I have never had an FTDI device physically fail
2) I have never had an issue finding a driver for Windows XP/Windows 7 (32&64bit) that works
3) I have never had an issue finding a driver for any Linux (32/64bit) derived from Debian that works
4) They perform exactly as I would expect.
5) My mate works for them
6) They are based near where I live and supporting local enterprise is good.

I have had problems with assorted "cheap Chinese" devices using Prolific chipsets. Whether this is because they contain counterfeit chips or not I don't know. But I have some nice USB<>RS232 devices that work fine on my Debian/Mint machines but are not recognised by Windows 7 and I cannot find a driver for them. This would not be the case with FTDI.

So for me, FTDI get my money everytime. FTDI devices "just work" for me.

Andy
MM0FMF
'Dave B' g8kbvdave-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org [linuxham]
2014-10-08 11:26:34 UTC
Permalink
3b. Re: "Fixing" serial port addresses, session to session.
Date: Tue Oct 7, 2014 3:59 am ((PDT))
<Snipped (again)>
http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/
Many thanks again Andy. The info in that link has allowed me to create some
udev rules that do "Exactly" what I need, even when an extra USB Hub is placed
inline. Magic!

To be deployed in anger later on, then I can secure everything with as much duct
tape as needed. ;-)

"Plan A" is...

/dev/GPS
/dev/THD7
/dev/IC706

Irrespective of the order they are plugged in, or where found at system startup.

Happy bunny for now. Thanks again.

73.

Dave G0WBX.



------------------------------------
Posted by: "Dave B" <g8kbvdave-gM/Ye1E23mwN+***@public.gmane.org>
------------------------------------
mm0fmf mm0fmf-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org [linuxham]
2014-10-08 22:35:02 UTC
Permalink
Post by mm0fmf mm0fmf-***@public.gmane.org [linuxham]
http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/
Many thanks again Andy. The info in that link has allowed me to create some
udev rules that do "Exactly" what I need, even when an extra USB Hub is placed
inline. Magic!
I sold my soul to Beelzebub and used Google :-) But I cannot recall what
I searched for exactly but it was probably "usb serial constant name
same VID" or similar.

The important thing is it worked for you and now when I have forgotten
how to do it and need to again I can search the group archives and find
it again. Without selling my soul again!

Andy
MM0FMF


------------------------------------
Posted by: mm0fmf <mm0fmf-***@public.gmane.org>
------------------------------------
'Dave B' g8kbvdave-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org [linuxham]
2014-10-08 11:32:48 UTC
Permalink
3c. Re: "Fixing" serial port addresses, session to session.
Date: Tue Oct 7, 2014 6:35 am ((PDT))
I've gotten around this problem by using a USB-Serial device that has
two ports instead of one, utilizing only one USB port. They make four
port devices too. Works great for me, no problems associated with
restarts, etc..
73 DE Charles, N5PVL
Hi Charles.

I have one of them too, used on a Winderz lappy, but that also needed the 4
individual ports having their feet nailed down so to speak.

See the Fldigi Wiki, and the "Taming the wild com port in Windows" how-to.

Yes, it does work with Linux too, but I did find that the resulting assigned ports
would still change once in a while, to be *Really* annoying!

Anyway, I now have the needed info (see other recent post) to fix the port
assignments in stone, AND with much more descriptive names relating to what
they are connected to and used for. (Better than in Windows in fact!)

73.

Dave G0WBX.



------------------------------------
Posted by: "Dave B" <g8kbvdave-gM/Ye1E23mwN+***@public.gmane.org>
------------------------------------
'Dave B' g8kbvdave-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org [linuxham]
2014-10-09 16:23:41 UTC
Permalink
1e. Re: "Fixing" serial port addresses, session to session.
Date: Wed Oct 8, 2014 10:36 am ((PDT))
Udev is the hard way, but it works. Symbolic links to the files in
/dev/serial/by-id are easier for me and I can put the link in the
program's working Dir.
I am old enough now to forgot how I accomplished things like udev
rules. ;). Symlinks are in your face.
Hi.

I see what you mean. At present, I prefer the udev rule method personally. At
least then "ports" of a consistant name get symbolically created, triggered by
some part of the devices USB identity. Plus, if I need to duplicate things on
another machine, I think I only need to copy one file to the new box, so the
same things happen with the same external hardware. I think.

But I get the idea.

However, I seem to have stumbled over a "feature" of the RXTX library used for
serial comm's under Java. Its somewhat fussy regarding the format of "names"
it can use.

Only those in the form of /dev/ttyUSB* (or /dev/tty*) Where * must be a
numeric string. 0, 1, 33, 101, 103 etc.

Any non numeric string after the "ttyUSB" part, and the RXTX lib throws it's toys
out of the pram, kicking and screaming at the same time.

I suspect that would also affect any script or manualy created symlinks to the
/dev/serial/by-id "files" too of course.

Thanks for the info anyway, all good to know, and probably forget later.

One of the good things about 'nix, that there are multiple valid ways to do
something. It's also one of the infuriatingly confusing things too at times! :)

73

Dave G0WBX.



------------------------------------
Posted by: "Dave B" <g8kbvdave-gM/Ye1E23mwN+***@public.gmane.org>
------------------------------------
ab4mw
2014-10-12 17:15:22 UTC
Permalink
Replicating is one reason that I put the sym-links in the program's working directory, because when the program complains or you see the big RED link indicating that it's broken, you remember to re-create it.

Usually, in replicating the devices are all different anyway. Can you tell I spend some time making systems for other people? :D
'Dave B' g8kbvdave-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org [linuxham]
2014-10-13 17:33:18 UTC
Permalink
2a. Re: "Fixing" serial port addresses, session to session.
Date: Sun Oct 12, 2014 10:15 am ((PDT))
Replicating is one reason that I put the sym-links in the program's
working directory, because when the program complains or you see the
big RED link indicating that it's broken, you remember to re-create
it.
Usually, in replicating the devices are all different anyway. Can
you tell I
spend some time making systems for other people? :D
Hi.

What I've found so far, is that the Newer Prolific chipsets are better for this than
the older ones, just. (The older ones, early 2303 chipsets) all appear identical
to the system, so the only way to diferentiate between them, is the particular
hub/port they are connected to. That's OK for some uses, but not others.

The best by far are FTDI based devices of course. If you do the udev thing, and
filter on VID/PID pair and the serial number, then that rule will work on different
systems so long as they support the same udev rule syntax.

Irrespective of where in the /dev/serial they appear, the VID/PID/s'num will
always be the same for a particular USB/Serial hardware device from FTDI at
least. Even if you add another USB hub (or two) between them and the PC!

Anyway, horses for corses, many ways to get the wanted result.

73.

Dave G0WBX.



------------------------------------
Posted by: "Dave B" <g8kbvdave-gM/Ye1E23mwN+***@public.gmane.org>
------------------------------------

Loading...