Page MenuHomePhabricator

OpenIGTLink: Processing POSITION or QTDATA data format not working in case of MITK as client
Closed, WontfixPublic

Description

--> Open 2 MITK instances on your PC (in the following called MITK 1 and MITK 2)
--> In both instances: TrackingToolbox -> Options: Check "Enable Open IGT Link MicroService" and choose in the combobox the data format POSITION or QTDATA (choose the same data format in both instances)

--> MITK 1: Connect and start tracking (1 tool as virtual tracker)
--> MITK 1: Open OpenIGTLink Manager: Select Open IGTLink device source and "Go Online"
--> MITK 2: TrackingToolbox: Select as tracking device configuration the OpenIGTLink Connection
--> MITK 2: TrackingToolbox --> Click "Add Single Tool" and name the tool the same way as it is done in MITK 1 + select as "Device Type" again the "OpenIGTLink Connection" --> Click "Finish"
--> MITK 2: Click on "Connect" in the TrackingToolbox
--> MITK 1: It is now possible to click on "Start Stream" of the OpenIGTLink Manager

--> In the MITK 2 logging: it receives IGTLMessages of the type POSITION or QTDATA

However: the connection process of MITK 2 doesn't finish correctly. An error message is shown:

"Cannot connect to the device. The number of tools in the connected device differs from the tool storage, cannot add tools."

It seems that the behavior is similar to the behavior described in Task T24038
So it would be great, if POSITION and QTDATA data messages would be processed and interpreted correctly by MITK.

Event Timeline

mittmann triaged this task as Normal priority.Jan 11 2018, 11:26 PM
mittmann created this task.
kislinsk claimed this task.
kislinsk added a project: Auto-closed.
kislinsk added a subscriber: kislinsk.

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

kislinsk removed kislinsk as the assignee of this task.May 26 2020, 12:05 PM
kislinsk removed a subscriber: kislinsk.