The InterSense server should not add a significant amount of latency (should generally be close to unmeasurable at the default 1000 Hz internal rate, although depends on the update rate). The specific errors above are due to a DLL mismatch between the application's DLL and InterSense server's DLL; typically they occur if one attempts to use an older DLL such as 3.84 with a newer application, since some of the API calls have changed (i.e. ISD_GetData() in the old DLL is now ISD_GetTrackingData() and so forth). Although the new DLLs support the old calls, applications written with the current API cannot be used with older DLLs. If the application has a copy of the DLL in its folder, it can be replaced with the relevant DLL from the InterSense downloads page (
http://www.intersense.com/support.aspx?id=373); 4.08 should work fine. Note that local copies are searched before the version in C:\WINDOWS\SYSTEM32 (for 32-bit DLLs in a 32-bit OS or 64-bit DLLs in a 64-bit OS) or C:\WINDOWS\SYSWOW64 (for 32-bit DLLs in a 64-bit OS).
That said, if you are connecting to a UDP broadcast from an IS-900 as it appears, it should not be necessary to run IServer, and it can be disabled from startup by right-clicking and removing the checkbox from "Launch at Startup". Please feel free to contact us if you have any further problems with this or need more information.
Best Regards,
Rand
Rand Kmiec
Technical Support Engineer
techsupport@intersense.com
InterSense Inc.
1-888-FLY-THRU (1-888-359-8478), ext. 624 [Toll free, US]
+1 781-541-7624 [Worldwide]
+1 781-541-6329 [Fax]