Hello,<br><br>Using a udev script like that is exactly what we are doing right now on our robots with all of our serial ports. We have udev scripts matching the FTDI serial number to the device name. <br><br>For example: <br>
KERNEL=="ttyUSB[0-9]*", ATTRS{product}=="FT232R USB UART", ATTRS{serial}=="A700ek5i", SYMLINK+="imu"<br><br>My end goal, was to have udev launch an avr_bridge script that queries the device for the name programmed into it. This name would then become the /dev symbol. However, I haven't gotten the udev script working for that yet.<br>
<br>-Adam<br><br><div class="gmail_quote">On Wed, Mar 16, 2011 at 10:50 AM, Eric Perko <span dir="ltr"><<a href="mailto:wisesage5001@gmail.com">wisesage5001@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, Mar 16, 2011 at 10:17 AM, Jeff Rousseau <span dir="ltr"><<a href="mailto:drzaiusx11@gmail.com" target="_blank">drzaiusx11@gmail.com</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Just a thought, but make sure that /dev/ttyUSB0 is actually the razor.<br>
I'd be careful doing a symlink from USB0 to /dev/imu unless you really<br>
only have a single usb serial device in your system. I have 3 on my<br>
robot, so I just created some udev scripts like shown on the hokyo<br>
tutorial:<br>
<br>
<a href="http://www.ros.org/wiki/hokuyo_node#Using_udev_to_Give_Hokuyos_Consistent_Device_Names" target="_blank">http://www.ros.org/wiki/hokuyo_node#Using_udev_to_Give_Hokuyos_Consistent_Device_Names</a></blockquote><div>
<br></div></div><div>For an example udev script that will assign a unique device name to an FTDI chip (which is what does serial->usb for the Sparkfun IMU), see <a href="http://answers.ros.org/question/65/how-can-i-get-a-unique-device-path-for-my" target="_blank">http://answers.ros.org/question/65/how-can-i-get-a-unique-device-path-for-my</a> . You could then symlink /dev/imu to that unique device path and be 100% sure that /dev/imu is definitely the IMU, regardless of how many other ttyUSB devices you have or the order they were plugged in in.</div>
<div><br></div><font color="#888888"><div>- Eric</div></font><div><div></div><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<div><div></div><div><br>
On Sat, Mar 12, 2011 at 10:03 AM, Patrick Goebel <<a href="mailto:patrick@pirobot.org" target="_blank">patrick@pirobot.org</a>> wrote:<br>
> Hi Adam,<br>
><br>
> Thanks for making this wrapper available. I have a Sparkfun 9d_razor and I<br>
> have upgraded the firmware using the .pde files in<br>
> imu_9drazor/src/SF9DOF_AHRS. I did this under Windows using the Arduino IDE<br>
> (version 0022) and the upload proceeded without errors.<br>
><br>
> Back on Linux with the IMU on port /dev/ttyUSB0 I followed the Wiki<br>
> instructions:<br>
><br>
> $ sudo ln -s /dev/ttyUSB0 /dev/imu<br>
> $ roslaunch imu_9drazor imu.launch<br>
><br>
> The launch proceeded without errors with the output:<br>
> process[imu_node-1]: started with pid [23276]<br>
> process[imu_msg_converter-2]: started with pid [23277]<br>
><br>
> However, when I echo the imu topic with "rostopic echo imu" there is no data<br>
> being published. Ditto for the topic imu/imu_raw. Both topics are listed<br>
> with "rostopic list".<br>
><br>
> One silly question: aside from having the IMU connected to the USB port, do<br>
> I also have to apply power to the white power connector? I did not have to<br>
> do this under Windows to see data via the firmware test application.<br>
><br>
> Any thoughts?<br>
><br>
> Thanks!<br>
> Patrick Goebel<br>
> <a href="http://www.pirobot.org" target="_blank">http://www.pirobot.org</a><br>
><br>
><br>
> On 01/10/2011 09:06 PM, Adam Stambler wrote:<br>
><br>
> Hi,<br>
><br>
> Just an IMU won't be able to track the position of the IMU over time. It<br>
> can be combined with odometry measurements with a kalman filter to a decent<br>
> estimate though.<br>
><br>
> If you are looking for a sparkfun IMU with a premade ros-wrapper, I have a<br>
> wrapper for the sparkfun 9d razor imu called imu_9drazor. It is a part of<br>
> the rutgers-ros-pkg.<br>
><br>
> Regards,<br>
> Adam<br>
><br>
> On Mon, Jan 10, 2011 at 11:58 PM, abhy <<a href="mailto:abhy.12354@gmail.com" target="_blank">abhy.12354@gmail.com</a>> wrote:<br>
>><br>
>> hello,<br>
>><br>
>> Does ROS have Sparkfun IMU supporting driver?<br>
>><br>
>> "<a href="http://www.robotshop.com/sfe-atomic-imu-6-degrees-of-freedom-xbee-ready-1.html" target="_blank">http://www.robotshop.com/sfe-atomic-imu-6-degrees-of-freedom-xbee-ready-1.html</a>"<br>
>><br>
>> Is this IMU sufficient for giving X, Y, Z coordinates of the Robot?<br>
>><br>
>> Thanks,<br>
>> Abhy<br>
>> --<br>
>> View this message in context:<br>
>> <a href="http://ros-users.122217.n3.nabble.com/ROS-driver-supporting-Sparkfun-IMU-tp2232681p2232681.html" target="_blank">http://ros-users.122217.n3.nabble.com/ROS-driver-supporting-Sparkfun-IMU-tp2232681p2232681.html</a><br>
>> Sent from the ROS-Users mailing list archive at Nabble.com.<br>
>> _______________________________________________<br>
>> ros-users mailing list<br>
>> <a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
>> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
><br>
><br>
> _______________________________________________<br>
> ros-users mailing list<br>
> <a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
><br>
> _______________________________________________<br>
> ros-users mailing list<br>
> <a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
><br>
><br>
_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
</div></div></blockquote></div></div></div><br>
<br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br>