9 #ifndef XSRESULTVALUE_H 10 #define XSRESULTVALUE_H 2: InitBus and/or SetBID are not issued
284: Not enough sensors were found
XSTYPES_DLL_API const char * XsResultValue_toString(XsResultValue result)
30: Timer overflows during measurement
263: Unexpected message received (e.g. no acknowledge message received)
301: The object has an unrecognized version, so it's not safe to perform the operation ...
267: The specified i/o device can not be opened
277: Invalid instance called
4: The message is invalid or not implemented
299: A device is not sending enough data
295: The single connected device is configured as a slave
269: An I/O device is already opened with this object
27: Timer overflows during measurement
256: A generic error occurred
294: The operation is once only and has already been performed
278: A trusted data stream proves to contain corrupted data
41: The device generates more data than the bus communication can handle (baud rate may be too low) ...
40: The device generated an error, try updating the firmware
0: Operation was performed successfully
286: Something else was received than was requested
26: Total bytes of data of Motion Trackers including sample counter exceeds 255 bytes ...
32: Baud rate does not comply with valid range
261: No internal memory available
272: No data is available
17: An incorrect answer received after WaitForSetBID
303: The requested functionality is not supported by the device
XsResultValue
Xsens result values.
296: More than one master was detected
257: Operation not implemented in this version (yet)
21: Other than SetBIDAck received
16: A slave did not respond to WaitForSetBID
259: Operation aborted because of no data read
33: An invalid parameter is supplied
291: The low-level port handler failed to initialize
25: Motion Tracker responds with other than SlaveData message
3: Period sent is invalid
300: The version of the object is too low for the requested operation
304: A packet counter value was missed
42: The sample buffer of the device was full during a communication outage
36: TX PC Buffer overflow, cannot fit full message
266: Insufficient buffer space available
305: An error occured while trying to put the device in measurement mode
281: Found only one responding Xbus Master
274: Tried to supply a NULL value where it is not allowed
260: Checksum fault occurred
280: Could not find any MVN-compatible hardware
268: The specified i/o device can not be opened
273: Tried to change a read-only value
XsDeviceErrorType
These enum values can be used to specify a device error (XRV_DEVICEERROR 0x28), i.e. a xbus message like [FA FF 42 05 28 XXXXXXXX CS].
1: No bus communication possible
285: Failure during initialization of Fusion Engine
270: End of file is reached
265: Operation is invalid at this point
271: A required settings file could not be opened or is missing some data
262: The requested item was not found
297: A device was detected that was neither master nor slave
302: The process was aborted by an external event, usually a user action or process termination ...
276: Busy processing, try again later
18: After four bus-scans still undetected Motion Trackers
24: Timer overflow - period too short to collect all data from Motion Trackers
283: One or more sensors are not where they were expected
29: No correct response from Motion Tracker during measurement
288: No serial port opened for reading/writing
292: A calibration routine failed
287: No file opened for reading/writing
275: Insufficient data was supplied to a function
289: No file or serial port opened for reading/writing
290: A required port could not be found
20: No reply to SetBID message during SetBID procedure
279: Failure during read of settings
28: Timer overflows during measurement
293: The in-config check of the device failed