From all I know, this is due to a new version of the Intersense driver after they came out with their USB devices, and is pretty much more or less an Intersense bug.
However, there is a workaround that works very well which is to specify the port the Intersense is connected to (you can look it up under windows device manager under com-ports ).
What you do in Vizard is to specify the exact port the InertiaCube is connected to by placing the command
PORT_INTERSENSE = 3 #in case the InertiaCube is connected to COM port 3
right in the line in front of initiallizing the Intersense device
orientation = viz.add('intersense.dls')
so the total code for adding an InertiaCube2 then reads as
PORT_INTERSENSE = 3 #in case the InertiaCube is connected to COM port 3
orientation = viz.add('intersense.dls')
|