This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
USB Manager
#1
I feel a little dumb asking but what is the USB Manager used for ?
Reply
#2
Linux choose the ttyUSBx sequence number sometimes different.
When you want to configure kplex with an AIS, GPS, VHF Radio, Plotter, Autopilot, Seatalk, NMEA2000... You have much work.
all instruments must be online when starting the raspi. Otherwise the ttyUSB0, ttyUSB1, ttyUSB2, ttyUSB3, ttyUSB4 change.
If you use udev rules. You can give the USB-serial adapter your own name (ttyOP_AIS, ttyOP_GPS, ttyOP_VHF, ttyOP_PLOTTER, ttyOP_AUTOPILOT).
Then you have to dig deep in linux udevadm and /etc/udev/rules.d.
There are two ways of udev rules. If you are using USB-serial adapter which have a unique serial or all have different chip sets, then it is easy.
If you have 2 or more of the same type without any difference, the normal udev rules can't find a difference. In this case the only chance is using the port number of your 4 Raspi USB-Ports or
the port number of your USB-Hub. But be careful to connect these USB-serial devices every time on exactly the same port (You know normally you can plug in for example a mouse in any usb-port and it will work)
So the USB manager does help you to configure the udev rules in OP. It creates the file /etc/udev/rules.d/10-openplotter.rules.

If you forget to turn on your AIS before starting the raspi or you want to save power and shut down a device no problem (only problem kplex must be restarted).
And configuring kplex and signalk with an self explanatory name is also easier.[Image: wink.png]
Reply
#3
(2016-04-08, 10:34 PM)e-sailing Wrote: Linux choose the ttyUSBx sequence number sometimes different.
When you want to configure kplex with an AIS, GPS, VHF Radio, Plotter, Autopilot, Seatalk, NMEA2000... You have much work.
all instruments must be online when starting the raspi. Otherwise the ttyUSB0, ttyUSB1, ttyUSB2, ttyUSB3, ttyUSB4 change.
If you use udev rules. You can give the USB-serial adapter your own name (ttyOP_AIS, ttyOP_GPS, ttyOP_VHF, ttyOP_PLOTTER, ttyOP_AUTOPILOT).
Then you have to dig deep in linux udevadm and /etc/udev/rules.d.
There are two ways of udev rules. If you are using USB-serial adapter which have a unique serial or all have different chip sets, then it is easy.
If you have 2 or more of the same type without any difference, the normal udev rules can't find a difference. In this case the only chance is using the port number of your 4 Raspi USB-Ports or
the port number of your USB-Hub. But be careful to connect these USB-serial devices every time on exactly the same port (You know normally you can plug in for example a mouse in any usb-port and it will work)
So the USB manager does help you to configure the udev rules in OP. It creates the file /etc/udev/rules.d/10-openplotter.rules.

If you forget to turn on your AIS before starting the raspi or you want to save power and shut down a device no problem (only problem kplex must be restarted).
And configuring kplex and signalk with an self explanatory name is also easier.[Image: wink.png]

Thanks for the explanation.
I haven't used my OP Pi on the boat yet (fitting it next week) so I hadn't realised about the USB port ID problem. Thanks again
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)