Problem with newer Intersense Inertiacube 2

[esmith4]

We have two of these trackers, bought a year or
more apart. The serial numbers are:
Old: SC2-0208045-D
New: 100-IMU00-0210
SC2-0408427-D

The old one works fine, while the new one is
not being detected by Vizard at all (on one computer)
or only intermittently (on another computer).
Informal testing with the Intersense drivers
show that both seem to work OK. So
evidently there is something in the Vizard
driver that is not working properly with the
newer tracker? Has Intersense made some
minor change in data format or whatever
since we got our older one?

Has anyone else had such a problem with a newer
inertiacube 2?
Vizard 2.17 here.

--Eliot Smith
Indiana University

[tobin]

The Intersense driver that searches across all ports often unfortunately mistakes other devices (especially USB devices) as a valid sensor. The workaround is to tell Vizard the port number on which the IC2 is plugged in. You do this by specifying PORT_INTERSE = XX before the call to add the intersense.dls.

Here's an example:

PHP Code:

PORT_INTERSENSE = 3
ori = viz.add('intersense.dls') 


This would instruct Vizard to look on COM3 for the Intersense tracker. If you're using a USB-based IC2, you need to figure out which COM port that USB port is getting mapped to.

Please say if you need further assistance.

[esmith4]

That fixed it, at least the one or two times we
tried it -- thanks!
Evidently the difference between the older and
newer cubes is in some aspect that makes the
older one easier for the driver to find than the
newer one... strange. But telling it which
port now lets it find both.

--Eliot Smith

[tobin]

Thanks for letting us know all is well.