¿Obtengo lecturas más precisas o más rápidas de acelerómetros con movimiento central?

Question

Puedo usar este método del marco de movimiento central:

- (void)startAccelerometerUpdatesToQueue:(NSOperationQueue *)queue withHandler:(CMAccelerometerHandler)handler

como una alternativa a la

- (void)accelerometer:(UIAccelerometer *)accelerometer didAccelerate:(UIAcceleration *)acceleration

Método de uiaccelerationDelegate de UIKIT.Allí, tengo que especificar la frecuencia de las actualizaciones.Quiero obtener datos de aceleración lo más rápido y preciso posible.

es el movimiento central mi amigo aquí?¿Cuál es la frecuencia de las lecturas que puedo esperar de ese método de movimiento central?La documentación no habla de ello.

Answer 1

Edit! Now that this answer is OVER A YEAR OLD, certainly it is only of historic value. At this stage, I guess, everyone should only be using CoreMotion and that's that. Hope this historic answer it helps an history students!

---

My impression is that: CMAttitude and CMDeviceMotion give you the benefit of both the accel'r and the gyro (if the gyro is present). Whereas CMAccelerometerData is only the accel'r. (Exactly like in the old days before Core Motion.)

My impression is that the two specific advantages of CoreMotion are:

(One) the mindboggling convenience of having Quaternions and attitude given to you on a silver platter

(Two) apparently, both gyro and accel'r are used on machines with a gyro, with no extra work from you ... a huge advantage.

I believe there is no actual technical difference in the quality of usage of the accelerometer per se.

Thus: if (for some reason) you want only the accel'r, and you can do the math (if relevant to your task at hand), you could use the old-school accel'r delegate.

It seems that in short, none of us will ever again use the old-school accelerometer delegate!