||Welcome to wifilapper
You are currently viewing our boards as a guest, which gives you limited access to view most discussions and access our other features. By joining our free community, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, and access many other special features. In addition, registered members also see less advertisements. Registration is fast, simple, and absolutely free, so please, join our community today!
EnduroRacer wrote:It shouldn't really matter which way the phone is facing because the recorded g forces are just relative to how the phone was when at rest.
Right now the App expects the phone to be at-rest in the ideal orientation at values of x,y,z (10,0,0) m/s^2. If instead the phone is at-rest at (9.5, -0.2, 0.5) then correction values of (+0.5, +0.2, -0.5) should be introduced. If they are (-0.2, 9.5, 0.5) then the correction values are (+10.2, -9.5, 0.5). Please tell me I'm wrong because it seems too simple to work.
There are a couple apps on the Play Store that use at-rest calibration. One of them is a bubble level, the other is a Racing Data Acquisition app. I forget which one, probably Torque.
The bubble level app actually does differential calibration by having the user flip the phone end-to-end and averaging the 2 values to find true level just like purpose built digital levels. Great for setting camber values with a phone. Most bubble levels only calibrate to a "known level surface" whatever that is.
WifiLapperDev wrote:And even if I knew how, how do you make a user-friendly and accurate way to input the phone's exact orientation?
EnduroRacer wrote: Please tell me I'm wrong because it seems too simple to work.
rbeam wrote:even if the GPS altitude number is 90% junk, I can decide if it's junk later
Users browsing this forum: No registered users and 0 guests