-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5 th generation #61
Comments
I'm not aware that Xsens updated their sensors to a fifth generation and, to my knowledge, MTi-30 AHRS is a name that fits the MTi-10 series introduced as part of the fourth generation. |
first page and Introduction |
Sorry for the delay. I was finally able to find updated documentation and it seems that they only added a few things but most of the protocol is similar. I expect most things will work and but the new feature are not yet configurable. I'm going to work on that. |
@0xd1ma Did you buy the device? If so, could you test the |
@fcolas the sensor will arrive in mid-May. I will test |
Finally, the sensor arrived and I performed some tests.
There are also no reports of speed changes, similarly #73
|
Many thanks for the information.
If that's the case, you could try with the verbose flag and paste the (end of the) output of:
This would allow us to see the content of the message that poses problem. |
@0xd1ma No news? |
Hello, I encountered the same issue. rosrun xsens_driver mtdevice.py -v
|
I edited mtdevice.py script and just put "pass" instead the "raise Exception(" couldn't parse MTData2 message.") thing. It reads all the sensor data correctly in real time. Probably some typo in the script somewhere that triggers try/except |
@Adixy Interesting. Anyway, if we wanted to solve this specific issue, we would have to guess what the 52 bytes mean. The easiest explanation is that, somewhere, a 1-byte field has been upgraded to 4 bytes. Looking inside this message is looks ok up to the end. So it might just be that the last reserved byte is actually not a byte but a float (1.28e-40?), an int (91938?) or some other 4-byte flag. |
@Adixy Can you please test the gps_sol_workaround branch? |
@Adixy Ping? |
Hello everyone.
For autonomous vehicle project, I am planning to by MTi-30 AHRS.
On http://wiki.ros.org/xsens_driver says: "This package provides a driver for the third and fourth generation..."
Do this ROS driver supports 5 th generation of Xsens sensors?
Thank you.
The text was updated successfully, but these errors were encountered: