Wine + winebottler + azloader.exe + rs232 to usb, adapter

dandelot · Post by **dandelot** » Mon Jun 07, 2010 1:28 pm

Ubuntu creates /dev/ttyUSB0 for me when
I plug in the usb-to-serial-adapter. I have a
symbolic-link to /dev/ttyUSB0 from 'dosdevices/com1'.

What is new in 10.04 Ubuntu is that I have to sudo chmod o+r
and sudo chmod o+w on /dev/ttyUSB0 every time before I
start the app which uses that serial line. ttyUSB0 goes away when
I unplug the serial adapter from the USB port or
shut down the laptop (with Ubuntu 10.04)! And it comes back with
permissions rw-rw---- when I plug in the adapter.
'dmesg' reports 'pl2303' and Prolific 2303 USB to serial adapter driver
(in several lines of verbiage) when I plug in the adapter.

Back in 8.04 Ubuntu the 'other' read/write access and
ttyUSB0 stuck around across shutdowns of the laptop
and unplugging the adapter
(or else ttyUSB0 always came back with 'other' read/write,
I cannot recall which it really was).

Martin Gregorie · Post by **Martin Gregorie** » Mon Jun 07, 2010 2:08 pm

On Mon, 2010-06-07 at 11:28 -0700, David Anderson wrote:

Ubuntu creates /dev/ttyUSB0 for me when
I plug in the usb-to-serial-adapter. I have a
symbolic-link to /dev/ttyUSB0 from 'dosdevices/com1'.
What is new in 10.04 Ubuntu is that I have to sudo chmod o+r
and sudo chmod o+w on /dev/ttyUSB0 every time before I
start the app which uses that serial line.
ttyUSB0 goes away when
I unplug the serial adapter from the USB port or
shut down the laptop (with Ubuntu 10.04)!

This is expected behaviour with a modern kernel using UDEV rules to
configure USB devices and set their access permissions.

You can change this by (carefully!) altering the rules
in /etc/udev/rules.d so the access permissions for /dev/ttyUSB* devices
are set to 0666 (all users have read and write access). I can't be more
specific because the UDEV rules are one place where Linux distros
differ. Ask for help on the appropriate Ubuntu forum and remember to
keep copies of your modified rules in a safe place because they can be
overwritten in /etc/udev/rules.d by an upgrade or reinstall.

Martin

dandelot · Post by **dandelot** » Mon Jun 07, 2010 6:52 pm

My thanks to Martin Gregori's for his hint.
I added a file 75-serialusb.rules to /etc/udev/rules.d containing a
single line with

kernel=="ttyUSB*", SYSFS(idVendor)=="067b", SYSFS(idProduct)=="2303",
MODE="0666"

and now /dev/ttyUSB0 starts up rw-rw-rw- .
Which suffices for my purposes.

anbes · Post by **anbes** » Mon Jun 07, 2010 8:07 pm

well, i was hijacked..lol...
but, will it work in mac osx?

James McKenzie · Post by **James McKenzie** » Mon Jun 07, 2010 8:34 pm

anbes wrote:

well, i was hijacked..lol...
but, will it work in mac osx?

Open a Terminal (session) from the Applications -> Utilities folder
Type in

Code: Select all

cd /dev
ls

Look at the tty.<something> entries.

Plug in your rs232 to USB device.

type in

Code: Select all

ls

If there is a new tty. entry, then the device is recognized by your
system. If not, then it is not.

You will need to create a symbolic link as previously described to allow
the device to 'appear' in Wine.

James McKenzie