Hello My answers inside the email. (Thank you for your reply ;-) )
On 06/13/2011 09:40 PM, Dave Platt wrote:
On 06/13/2011 12:24 PM, f8arr wrote:
Hello Hams !
Apologies for the bandwich, but perhaps someone has allready faced it ...
Here is the case :
In order to have a TX port on WSJT I use /dev/ttyUSB0 from prolific pl2303.
At boot, the serial comes up to TX.
I'm not certain what you mean here. Does this mean that the
transmitter is keyed up into TX, as soon as the system boots
and the USB serial port adapter is recognized by the kernel?
YES
If so, this would suggest one of several things:
- Your PL2303 adapter is asserting either DTR or RTS
when it is first initialized, without waiting for some
program to open the USB serial port.
you are right
[Question - which of these lines are you using to drive
PTT on your transmitter?]
I'm using DTR
- Some (unexpected) program is opening /dev/ttyUSB0 as soon
as the adapter is connected.
may be.. but witch one ?? grrr
On messages I have only this message :
Jun 13 17:00:08 f8arr2-station kernel: [ 3574.706035] usb 3-1: new full
speed USB device using uhci_hcd and address 8
Jun 13 17:00:08 f8arr2-station kernel: [ 3574.852805] usb 3-1: New USB
device found, idVendor=067b, idProduct=2303
Jun 13 17:00:08 f8arr2-station kernel: [ 3574.852814] usb 3-1: New USB
device strings: Mfr=1, Product=2, SerialNumber=0
Jun 13 17:00:08 f8arr2-station kernel: [ 3574.852819] usb 3-1: Product:
USB-Serial Controller
Jun 13 17:00:08 f8arr2-station kernel: [ 3574.852823] usb 3-1:
Manufacturer: Prolific Technology Inc.
Jun 13 17:00:08 f8arr2-station kernel: [ 3574.855943] pl2303 3-1:1.0:
pl2303 converter detected
Jun 13 17:00:08 f8arr2-station kernel: [ 3574.868109] usb 3-1: pl2303
converter now attached to ttyUSB0
Of course, If I run WSJT it can't commute the TX with an error message
"Can't connect to /dev/ttyUSB0"
That suggests that either the permissions are wrong, or that some
other program/process has already opened the serial port for
some reason.
I think that is due to program blocking. Because if I do some
manipulations with my only real RS232 serial it is working like a charm.
This is due to RS232<->USB (driver?)
My user is on the "dialout" and "uucp" group.
When the system is in this state, try the following:
ls -l /dev/ttyUSB0
lsof | grep ttyUSB0
The output for the first command will show you what
owner/group information was set up for the port during
the hot-plugging.
crw-rw-rw-. 1 root uucp 188, 0 Jun 13 21:15 /dev/ttyUSB0
(My user is under uucp group)
uucp:x:14:uucp,f8arr
dialout:x:18:f8arr
f8arr:x:500:
The output for the second command should help you see
whether there's another program "busying out" the
USB serial port.
nothing...
I tried exactly the same manipulation with my only real RS232 port and
it works like a charm.. (but dedicated to an other action).
Of course, same configuration was ok under my ubuntu 10.04. but I
switched to Fedora 15...
That suggests that the adapter itself is OK, and that it's either
an issue of permissions for the port (which would be set via
a configuration file in /etc/udev/), or an issue of some other
program opening the port (maybe something looking for a serial
mouse or a modem?)
I had this in udev rules :
SUBSYSTEM=="usb", SYSFS{idVendor}=="067b", MODE="0666"
with lsusb :
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0603:00f2 Novatek Microelectronics Corp.
Bus 002 Device 003: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
Port
Bus 003 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial
Port
(I have two usb to RS232 adpaters.)
Thaks for help !
Guillaume
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux Newbie]
[Kernel Newbies]
[Memory]
[Git]
[Security]
[Netfilter]
[Linux Admin]
[Bugtraq]
[Photo]
[Yosemite Photos]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[ARM Linux Kernel]
[Linux Networking]
[Linux Security]
[Linux RAID]
[Samba]
[Video 4 Linux]
[Linux Resources]