Chad-<div>The Nunchuk piece of the driver was written without access to a MotionPlus and the Wiimote/MotionPlus part was written without a nunchuk. You might be the first to actually assemble all of the pieces. </div><div>

<br></div><div>I&#39;ll try to see if I can find a MotionPlus to debug, but in the meantime, I&#39;ll give the lame answer and say feel free to submit a patch :)</div><div><br></div><div>-David<br><br><div class="gmail_quote">

On Tue, Aug 10, 2010 at 4:30 PM, Chad Rockey <span dir="ltr">&lt;<a href="mailto:chadrockey@gmail.com">chadrockey@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

It appears that our current ROS driver can only ouput the Nunchuk values when the MotionPlus is not attached.  Can anyone confirm is this is true?  I didn&#39;t see a ticket and I&#39;m not sure if this is a problem with ROS or with cwiid.<div>



<br></div><div>I am using ROS cturtle from debs on ubuntu 10.04 64bit on a thinkpad t-61 with integrated bluetooth.  The specific problem is that the Nunchuk topic does not publish data when the motion plus is attached.</div>



<div><br></div><div>Works:</div><div>Wiimote accelerometers and buttons: always</div><div>Wiimote and gyros</div><div>Wiimote and nunchuk</div><div><br></div><div>Does not work:</div><div>Wiimote, gyros, and nunchuk (although wiimote and gyros still report, the Nunchuk topic never publishes any data)<br>



<div><br>Thanks,<br><font color="#888888"> - Chad</font></div></div>
<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></div>