There is an SAE standard J670 on this topic, and automotive industry follows the convention:
+X to the front
Y is lateral
Z-down:
![Image](https://claraty.jpl.nasa.gov/man/software/development/conventions/images/coords_vehicle.gif)
or Z-up
![Image](http://cfr.regstoday.com/data/CFR/T49/cfr_49_571_I094.gif)
e.g. Z-Down orientation, figure directly from SAE J670
![Image](https://claraty.jpl.nasa.gov/man/software/development/conventions/images/coords_tire.gif)
Also referenced in this paper:
Vehicle Dynamics Modeling
Moderators: JeffC, rdoherty, stieg, brentp
Filed https://github.com/autosportlabs/RaceCa ... issues/452 to track the issue. Lets see if we can get something resolved in 2.9.0. We don't have any intention of supporting multiple standards as that would add a lot of complication to our system, but we can try to make it so that you can configure your unit in this manner and have calibration work.I know that I can make any axis configuration in Race Capture App, but if i change the orientation of Z axis from normal to inverted, calibration doesn't work correctly for this axis (it shows 3G after calibration). Can you please take a look at this bug?