-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement the $DTS command in order to remotely set some data fields before computation #63
Comments
Implementation started (commit 315e132). |
The implementation now includes the absolute and the differential pressure, with their relative temperatures (commit 0255e11). |
One observation about the external temperature: When the temperature sensor is not present, the value can be regularly updated via the In the second case we could compensate with the altitude drop considering the standard ISA Environmental lapse rate of 6.49 [K/km]? |
Right, and the possibility of transfer data between the ADC and the attached devices is useful. ISA altitude(with standard troposphere temperature lapse) can be calculated using AirDC::ISAAltitude(int mode=1). That calculation, as standard, does not use temperature as input data. This attitude is considered as a baseline. On the other hand, ground pressure and ground temperature can be used to obtain a better altitude measurement. ISAAltitude(int mode=2) uses ground pressure(#60) to get better altitude readings. See https://www.basicairdata.eu/projects/barometric-altimeter/ (Altitude compensated by pressure at sea level). This method is used on full-size aircraft. Mode=3 includes temperature and pressure correction; I will paste the method into the code as soon as possible The use of outside temperature impacts directly on the calculation of the true airspeed |
The idea to handle temporary or permanent measurements unavailability is good too. We can also think of cope with basic sensor failure detection and reconfiguration. However, I rather postpone that kind of task until implementation and test of basic features are completed. |
It would be a great task to implement more sophisticated and accurate way to calculate the altitude using the temperature and the pressure too. However, I would now to bring the focus on the temperature in input: The external temperature could be measured by the ADC using the external temperature sensor. In the second case, the temperature should be kept updated at a good rate, but this is not always possible. In the extreme case, the user could set the external temperature once at the start (let me say, once every flight). Thus, if we consider the following known data:
I wondered if it could be a good idea (in case the sensor is not present) to compensate the external temperature in input this way (when a new value is not available):
This could be a very easy job to do for the main sketch before every computation. |
Of course that can be implemented into the main sketch |
With the
$DTS
string we could set some useful data, like the external temperature.The firmware could use the status matrix to choose between two behaviors (in acquisition phase):
The text was updated successfully, but these errors were encountered: