[IGSTK-Users] Troubleshooting communication issue with Micron Tracker

[Chris Heath]

Hi Andinet,

Sorry for the delay, I was away for the week.  I ran the cxx demo that  
comes with the Claron, and sure enough the problem exists there as  
well.   I am going to e-mail the Claron folk to try and troubleshoot;  
I will let you know if I find anything.

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?)

Thanks,
Chris


On May 21, 2008, at 2:51 PM, Andinet Enquobahrie wrote:

> Hi Chris,
>
> "Error grabbing a frame" occurs when Cameras_GrabFrame method (MTC  
> library method)
> that is internally used by MCamera returns an error.  I personally  
> never had such type of problem
> once communication is established and tracking starts.   If the  
> problem persists, we should ask
> advice from Claron folks. Have you observed similar error with the  
> demo application that comes
> with the tracker or is it only your IGSTK-based application?
>
> Your next question is how to restart tracking whenever there is such  
> an error. You could invoke
> an error event right after #567 ( right after igstkLogMacro..)and  
> then setup an observer in your application
> that listens to this error event. Then, use ResetTracking method as  
> a callback to your observer.
>
> This might work as a short term solution. But w should definitely  
> troubleshoot why you are getting a
> the error after communication is established and tracking starts
>
> Let us know what you find out..
>
> -Andinet
>
>> Hello all,
>>
>> 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:
>>
>> (CRITICAL) Error grabbing a frame
>>
>> 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).
>>
>> If I turn tracking off then on again, tracking will resume for a  
>> while, until once again it fails in the same manner.
>>
>> 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:
>>
>> void ResetTracking()
>> {
>>    m_Tracker->RequestReset();
>>    m_Tracker->RequestStartTracking();
>> }
>>
>> 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.
>>
>> Thanks,
>> Chris
>> _______________________________________________
>> IGSTK-Users mailing list
>> IGSTK-Users at public.kitware.com
>> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users
>>
>
>
> -- 
> ==========================================================
> Andinet A. Enquobahrie, PhD
> R&D Engineer
> Kitware Inc.
>
> 28 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-371-3971 x124
> www.kitware.com
>
>