Thanks,

the change from:
PROGRAM="/getID /dev/ttyACM%n q"
to:
PROGRAM="/getID %N q"
did solve the problem.

- Jochen

>
> Hi Jochen,
>
> Here is what we are running on the PR2. It seems to work almost all the
> time (still trying to track down those few times that don't work, but
> thy are rare). It seems pretty close to what you are doing. Have you
> tried "udevadm monitor" to watch what is going on when you plug in?
>
> Udev rule:
>
>
> SUBSYSTEMS=="usb", KERNEL=="ttyACM[0-9]*", ATTRS{manufacturer}=="Hokuyo
> Data Flex for USB", ATTRS{product}=="URG-Series USB Driver",
> PROGRAM=="/etc/ros/run.sh hokuyo_node getID %N q",
> SYMLINK+="sensors/hokuyo_%c"
>
> /etc/ros/run.sh
>
> #!/bin/sh
> . /etc/ros/setup.sh
> rosrun $@
>
> On Mon, 2010-04-12 at 17:51 +0200, Jochen Kl?? wrote:
>> Hi,
>>
>> I tried using the hokuyo getID program to identify a hokuyo.
>> The program works correct and returns the serial-number by using it from
>> a
>> normal shell.
>> However udev doesn't create a symlink when the hokuyo is plugged in.
>> Oddly, running a "udevadm test" on the ttyACM device the rule is
>> executed
>> and the symlink is created.
>>
>> here is my udev rule (karmic system):
>> SUBSYSTEM=="usb", KERNEL=="ttyACM*",PROGRAM="/getID /dev/ttyACM%n q",
>> ATTRS{manufacturer}=="Hokuyo Data Flex for USB",
>> ATTRS{product]=="URG-Series USB Driver", SYMLINK+="hokuyo_%c",
>> MODE="0666"
>>
>> Has anyone seen this behavior before?
>>
>> - Jochen Kl??
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>
>
>
>
> ------------------------------
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users