I was also warned off MoTeC by many.
But the other bunch of data logger people said essentially to "FRO", but in a very politely way.
So I inquired with MoTeC-HQ in Croyden South...
I have a MicroStrain IMU. This contains a 3-axis Accelerometers, 3-Axis Rate-Gyro, and 3-Axis magnetometer.
MoTeC HQ were great and produced a template for it.
(MoTeC were so good on customer support I bought an M800, and E888.)
The IMU data is ingested into an ACL throught the RS232.
The GPS goes to a MoTeC-STC (Serial to CAN) which then presents the CAN stream to the ACL.
It lives the a car 1/2 of the time.
https://www.flickr.com/photos/32230177@N06/8730947343/in/photostream/player/https://www.flickr.com/photos/32230177@N06/8729691143/player/The other half is lives on a ski with the ACL in a bum-bag.
That sort of data looks like this:
https://www.flickr.com/photos/32230177@N06/5317415681/in/set-72157625732186998/player/The "Dash Cam" from a different day looks like this:
https://www.youtube.com/watch?v=c_qJ8caCDpEThe data associated with the video has a mean lateral G of about 1.5G (1.8 G of RSS of the three axes).
Longer term goals are to create some .dll libraries to do the heavy lifting and apply strap-down inertial navigation approach and RTS filter so that with only spotty GPS updates I can maintain position and attitude (and Vel and Acc). But her Ladyship also has metrics for success which can be at odds with my time in the laboratory.
============
I know that the Microstrain can work, and newer versions are smaller.
What are your goals? Chassis development, driver development, other?
How do you intend to make it use of the data?
And what are your metrics for success?