03-04-2013 06:41 AM
Hello there,
I am trying to create a 3-D imaging of my Mti-Xsens sensor while connected via the RS-232 MTi cable (CA-USB2). I have found an already build in driver that has that feature for the sensor, but unfortunately I always get an error "VISA: (Hex 0xBFFF006C) An overrun error occurred during transfer. A character was not read from the hardware before the next character arrived." I have tried to add in a buffer, but I still get the same error. I have taken a screen shot of the driver I have. I hope some one can help, as I really need to get a 3D imaging of the sensor for my project. I am new to the LabView environment. I would appreciate your help. Thanks for you time.
Best regards,
Hosam
03-05-2013 11:44 AM
Have you tried using the signle read function rather than reading continously? Setting the skip factor to 65535 allows the MT to only send data when it is requested. Try setting this up first and see if you are able to communicate correctly.
03-05-2013 01:52 PM
03-06-2013 06:30 PM
So now you are able to get the VI to communicate properly but you are getting a different error? Or the same VISA run time error that was mentioned in the first post? When you say that the error is not generated directly, do you mean that the object stops changing its orientation? Maybe before setting the rotation of the object check to make sure that the radians to be rotated is not more than pi. I believe that objects can be plus pi rotated about the positive axis and then negative pi rotated about the negative axis so if the rotation to be set is greater than pi then it will not set the orientation correctly.
03-07-2013 07:06 AM
The error is probably because the 3D picture controls are taking too long to finish execution. The MT is continuously sending data to serial port buffer on your PC and LabVIEW can't read it fast enough because the 3D picture is taking too long.
This is why it takes some time for the error to occur, the buffer doesn't fill up straight away.
You can either read from the buffer faster or decrease your sample rate.
03-08-2013 09:26 AM
This might be a good situation for producer consumer loop using queues to enqueue the matrix elements in one loop and dequeue the elements and display the 3D image in another loop.
03-08-2013 09:33 AM
03-09-2013 10:32 AM
The values of roll pitch and yaw will change a small amount (<1 degree) because the MT is ESTIMATING them and its not absolute.
How much are they changing by?
Have you configured the MT to use the correct scenario for your application?
Which VIs are you using to communicate with the MT? Install this driver.
There are examples of how to communicate included with the driver.