<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Andinet,<div><br></div><div>The problem stemmed from IEEE-1394 bus resets.  These can occur with cabling that is too long, repeaters that aren't quite up to spec, or just bad connections.  It seems the Bumblebee driver can't gracefully recover from this reset, which is why you have to manually reset the tracking.  There is an article from PtGrey here:  <a href="http://www.ptgrey.com/support/kb/index.asp?a=4&q=189&ST=freeze">http://www.ptgrey.com/support/kb/index.asp?a=4&q=189&ST=freeze.</a></div><div><br></div><div>On the other hand, I was able to invoke an error event and create an observer to reset the camera when the error was happening.  Thank you for the help you provided and continue to provide.</div><div><br></div><div>Chris</div><div><br><div><div>On May 28, 2008, at 3:26 PM, Andinet Enquobahrie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Chris,<br><blockquote type="cite"><br></blockquote><blockquote type="cite">Secondly, could you clarify what you mean in that second paragraph by #567 (a.k.a. where do you think I should invoke that error event?)<br></blockquote><blockquote type="cite"><br></blockquote>Line # 567 in igstkMicronTracker.cxx<br><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On May 21, 2008, at 2:51 PM, Andinet Enquobahrie wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Hi Chris,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">"Error grabbing a frame" occurs when Cameras_GrabFrame method (MTC library method)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">that is internally used by MCamera returns an error.  I personally never had such type of problem<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">once communication is established and tracking starts.   If the problem persists, we should ask<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">advice from Claron folks. Have you observed similar error with the demo application that comes<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">with the tracker or is it only your IGSTK-based application?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Your next question is how to restart tracking whenever there is such an error. You could invoke<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">an error event right after #567 ( right after igstkLogMacro..)and then setup an observer in your application<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">that listens to this error event. Then, use ResetTracking method as a callback to your observer.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">This might work as a short term solution. But w should definitely troubleshoot why you are getting a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the error after communication is established and tracking starts<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Let us know what you find out..<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-Andinet<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Hello all,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I have created a program based largely on the "OneViewAndTrackingNewUsingMicronTracker" example found in the Sandbox.  The program works great for  while, until it stops responding to input from the Claron.  The error given in the log is listed as:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">(CRITICAL) Error grabbing a frame<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">It seems that once there is an error grabbing a frame, the communication fails completely, and I continually see the error over and over again and am no longer able to track (which seems to go against the point number 2 listed as a requirement for the communication object).<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">If I turn tracking off then on again, tracking will resume for a while, until once again it fails in the same manner.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The approach that I think may work in the short term, until I can figure out why this error pops up at all, is to create a method in my implementation.h file as follows:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">void ResetTracking()<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">{<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">   m_Tracker->RequestReset();<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">   m_Tracker->RequestStartTracking();<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">}<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I would want to call this method whenever the communication object reports an error grabbing a frame.  My question is, how could I access this error report?  I can see it in the logger, do I need to use the logger object to do so or will the communication object return an error code?  I would appreciate any advice.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thanks,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Chris<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">IGSTK-Users mailing list<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:IGSTK-Users@public.kitware.com">IGSTK-Users@public.kitware.com</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users">http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-- <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">==========================================================<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Andinet A. Enquobahrie, PhD<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">R&D Engineer<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Kitware Inc.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">28 Corporate Drive<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Clifton Park, NY 12065-8662<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Phone: 518-371-3971 x124<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://www.kitware.com">www.kitware.com</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><br><br>-- <br>==========================================================<br>Andinet A. Enquobahrie, PhD<br>R&D Engineer<br>Kitware Inc.<br><br>28 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-371-3971 x124<br><a href="http://www.kitware.com">www.kitware.com</a><br><br><br></div></blockquote></div><br></div></body></html>