Cold IMU cal would not do this.. The IMU has a heater and still heats all the way up. You're just giving a wider range of cal data, in turn gives a better cal.Im just wondering.. for all of you that are having VPS issues, who has done a cold IMU calibration? Im going to jump out there on a limb and bet that all of these issues are tied to IMU failure/discrepancies caused by cold IMU Cal..All of your problems are centered around massive failure in the data from the barometer, sonic altimeters, and gyros.
I understand the affects and intended purpose completely. But I also understand the affects of wide temperature variations on electronics, especially extremely small electronics! Firmware changes alone aren't going to cause a barometer to suddenly change in reading from say... 4.0 to -2.8. But a faulty barometer, or barometer data stream will. Its just a thought. I personally have no issues so I cant do any testing, just applied a little bit of logic to the Phantoms own logic.Cold IMU cal would not do this.. The IMU has a heater and still heats all the way up. You're just giving a wider range of cal data, in turn gives a better cal.
I cant argue that.. its a bit beyond my understanding. It was just a thought. Trying to help find a solution, or preventative.Actually FW can, it's called a "span", If they tighten that up in the code, some devices could be seeing this issue.
I've been having trouble with VPS since updating to the 1.2.6 firmware. Tried a full IMU re-calibration, cold, yesterday, and am still having an unstable hover at VPS heights (in exactly the same locations that it used to be perfectly stable).
Try what I stated in the first post and report back.
Packet: P3X_FW_V01.02.0006.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.
Correct some people are seeing this bug. A temporary fix is to just disbale vps for now.
In ATTI or P-GPS mode? I'm not seeing a big difference in stability with VPS on or off. The lateral drift is still very difficult to deal with at lower altitudes, where it was basically a hovering tripod before the firmware update.
Like I mentioned in post #29, I did yesterday. I also did another today as part of trying the process that Sammyneis described. I even double checked that the table I used was level:
View attachment 23043
I would then contact phone support
It only began happening immediately after I upgraded to 1.2.6, like so many others have reported. I have to assume there's a firmware fix on the way with so many people having this issue. How would calling phone support help the firmware update be available any sooner?
Be sure to lay that level the other way too, on the other axis of the surface. It could be level width-wise but not level depth-wise.Like I mentioned in post #29, I did yesterday. I also did another today as part of trying the process that Sammyneis described. I even double checked that the table I used was level:
View attachment 23043
Be sure to lay that level the other way too, on the other axis of the surface. It could be level width-wise but not level depth-wise.
We use essential cookies to make this site work, and optional cookies to enhance your experience.