Debugging inside the class NDITrackingDevice is confusing because:

• NDITrackingDevice uses the class NDIProtocol and vice versa: this means the program flow is jumping between both classes
• There is only one class for the Aurora and Polaris tracking system, but there are differences (e.g. automatic detection of tools)

We recommend for restructuring:

• separation of classes for Aurora and Polaris
• hierarchical structure, e.g. a class which only communicates with the hardware and is then used by NDITrackingDevice...