Hi,
Today I was trying to PID my FC (hexa).
Start point: hexa fly "not bad": yaw was ponderous, ALT hold was too nervous and not satisfy (bump up and down).
End point: almost crashed.
Story: after few PID changes (I take YAW) it was worse and worse. I use sequence:
1. change PID value
2. transmit to AQ - wait for green "light" go black
3. write to ROM
4. read from ROM - just for shure
sometimes I missed transmit to AQ (after change) - mystake, so I made sequence from begging.
After few flyight and repeated procedure, HEXA start to going unstable, YAW was almost not resposed.
Going back with 1, than 2, then 3 last changed parameters nothing changed for better.
Befor last start i all changed parameters, one after one, to go back to start point.
All went OK (it seems OK).
Start and HEXA goes on side.
Checked HUD in GCS - horizon was vericaly !!!
Used "tools":
- Android GCS 2.8.5 from this post on Samsung Galxy SIII with 4.1.2 Android
- FW r76 rev 2
After that I saved ALL PARAMETERS (on Windows GCS) and find some interesting diffrence for parameters (example below)
IMU_ACC_BIAS2_X
IMU_ACC_BIAS3_Y
IMU_ACC_BIAS3_Z
IMU_ACC_SCAL2_X
IMU_ACC_SCAL2_Y
IMU_ACC_SCAL3_X
IMU_GYO_BIAS3_X
IMU_MAG_BIAS2_Y
IMU_MAG_BIAS3_Z
...
all this parameters are calculated values and current value for each of them was changed to 0.
I think that there is some serious problem with GCS or what FC procedures.