1984
New Member
If I don't have a Dynon transponder or electric fuel probes, or ADSB connectivity, do I need to bother with v12.2?
V 12.2
- Thread starter 1984
- Start date
jdubner
Member
Please clarify this item from the change list:
I had a serious problem when this feature was added in the 11.0 firmware that was finally "fixed" by a special firmware load that effectively "uncalibrated" my AOA. See Case 171670 from September 2014. I still run with no AOA (uncalibrated and also the port on the wing plugged) to avoid the problem. Does the "Fixed" item (above) mean that the sensor test will be run regardless of the status of my AOA calibration if I update from 12.0 to 12.2?
Thanks,
Joe
Is the word now supposed to be not? ^^^
I had a serious problem when this feature was added in the 11.0 firmware that was finally "fixed" by a special firmware load that effectively "uncalibrated" my AOA. See Case 171670 from September 2014. I still run with no AOA (uncalibrated and also the port on the wing plugged) to avoid the problem. Does the "Fixed" item (above) mean that the sensor test will be run regardless of the status of my AOA calibration if I update from 12.0 to 12.2?
Thanks,
Joe
jakej
Well-Known Member
I'd say yes on both counts
Jake J
We fixed more fundamental breakage there. After you upgrade, you should still not get any errors due to your your AOA sensors being capped (because you don't have an AOA calibration performed)
jdubner
Member
Thank you. This is why I like to hear directly from Dynon Support; the reply from a user, although well-meaning, was just wrong.
After our phone conversation I upgraded and found this to be true. Did two complete power cycles and flew 0.6 without the problem appearing.
Nice to have the date in the log files' timestamps correct again along with the other 12.2 goodness.
--
Joe
DBRV10
Active Member
not seen any fuel gauge problems. They may be more stable though :-?
- Joined
- Mar 23, 2005
- Messages
- 13,226
This actually changed in 12.0, but depending how you updated, you could have missed it, as it's in the sensor file, not the main software.
From the 12.0 release notes:
The filtering changed from about 2 seconds to show 66% of the change to 128 seconds. Nothing should be on the order of 30 minutes! No real fuel tank changes a noticeable amount in 2 minutes, so this seemed like a good balance of reaction and filtering out slosh and un-coordinated flight. We implemented this to minimize low fuel alerts when aircraft are maneuvering.
This filter also initializes when you boot, so it doesn't take a few minutes for an accurate reading at boot.
Finally, this is only on the resistive fuel levels. Capacitive ones do not have these filters since the sender is not powered by SkyView and thus we can't initialize it at boot.
We can give you a sensor file with this filtering reduced, but can you first tell us why this filter doesn't work in your plane? The more of the unique situations we know the better we can make our product.
From the 12.0 release notes:
The filtering changed from about 2 seconds to show 66% of the change to 128 seconds. Nothing should be on the order of 30 minutes! No real fuel tank changes a noticeable amount in 2 minutes, so this seemed like a good balance of reaction and filtering out slosh and un-coordinated flight. We implemented this to minimize low fuel alerts when aircraft are maneuvering.
This filter also initializes when you boot, so it doesn't take a few minutes for an accurate reading at boot.
Finally, this is only on the resistive fuel levels. Capacitive ones do not have these filters since the sender is not powered by SkyView and thus we can't initialize it at boot.
We can give you a sensor file with this filtering reduced, but can you first tell us why this filter doesn't work in your plane? The more of the unique situations we know the better we can make our product.