<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi Jason,<br>
<br>
For accuracy consideration, IGSTK only reports tracking data within
the manufacturer specified ideal tracking range.<br>
<br>
You can change this setting by using the VSEL command. Try insert
the following line into the igstkNDITracker.cxx file after line 134<br>
<br>
m_CommandInterpreter->Command("VSEL:2");<br>
<br>
See if it will give you a larger tracking volume.<br>
<br>
Let me know how it goes,<br>
<br>
Patrick<br>
<br>
<br>
<br>
On 6/10/2011 2:47 PM, Jason Gibbs wrote:
<blockquote
cite="mid:BANLkTikobjLy9JGoaYd97hM4KTL2ELw8EA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Hello IGSTK Community,
<div><br>
</div>
<div>We are having an issue that we aren't able to resolve, even
with the friendly assistance of some of the NDI support people.
We are using an NDI Polaris Spectra tracker and are noticing
that tools are losing track at a Z depth of approximately 2400mm
in our IGSTK-based app. When using the NDI Track GUI, however,
the extended volume is set and can track to around 3000mm in the
same direction. We have flashed the tracker with a
configuration file which is supposed to change the default
tracking volume to the extended pyramid, however we obviously
aren't seeing this in our IGSTK-based app.</div>
<div><br>
</div>
<div>The NDI support staff suggested sending an appropriate VSEL
command to the tracker to select the tracking volume at runtime
in our IGSTK app. This, however, seems to be pretty-well
encapsulated away from standard library usage (indeed, no VSEL
command is sent), so we suspect this isn't the best way to go
with respect to the IGSTK architecture. We are fine modifying
our version of the library to do this, but would very much
appreciate guidance on how to form the serial communication
instructions and where to properly fit these commands into the
existing library.</div>
<div><br>
</div>
<div>Alternatively, if there are any tricks to initializing/saving
this information on the tracker itself so that we don't have to
modify any IGSTK internals, but the tracking volume used in
IGSTK mirrors what appears in the NDI Track GUI, we would much
prefer to go that route. We suspect that this is a fairly
common desire for users (to change the tracking volume to the
biggest one available) so we're hoping that I'm just missing
something quite obvious either in IGSTK or in the NDI
configuration apps.</div>
<div><br>
</div>
<div>We would very much appreciate any advice/suggestions that the
community may have.</div>
<div><br>
</div>
<div>Thank you!</div>
<div><br>
</div>
<div>-Jason Gibbs</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Follow this link to subscribe/unsubscribe:
<a class="moz-txt-link-freetext" href="http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users">http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users</a></pre>
</blockquote>
</body>
</html>