On start tracking the warning "Message not understood!" is written to the console several times. It takes a long time then (up to five minutes) till tracking is started.
The problem occurs in "mitkNDIProtocol" as the result of the command "SFLIST:03" is not as expected. The reply gotten from the tracking device changes when different tools are connected to the system. The problem does not occur when no tools are connected.
[bf92f9]: Merge branch 'bug-17089-ErrorHandlingForListingOfTrackingVolumes'
2014-02-05 16:48:17 Adrian Winterstein [31965a]
Abort getting of tracking volumes if the replies of the tracking device are not as expected.
This is more a workaround than a fix, as the cause for the problem is still not found. Error handling is done now when getting wrong values for the tracking volumes, but the values shouldn't be wrong.
The problem still occures on at least one pc, testet with a 32-bit and a 64-bit build. The values returned by the tracking device differ between the 32- and the 64-bit build, but they are wrong in either case.
Hi there! 🙂
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑
Best wishes,
The MITK devs