Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Notes

  • LOS Pos would handle providing AM with the information regarding the plane’s position and attitude which can be obtained from the sensor drivers in the driver layer of LOS.

  • It should also be able to determine where its getting the information based on a config file, where it would be able to determine which sensor’s driver to call on. E.g it should be able to determine if it should call on the VN-300 or the BMX160.

    • This means that ZP wouldn’t have to care which drivers are being used, but would just call on LOS Pos and would expect position information.

Input

LOS Pos would look into the config file on the plane to determine which sensor drivers to call on to obtain the necessary information

  • e.g calling on the VN-300 to get information

Output

When called on by AM, LOS Pos return a pointer to the following information:

  • Longitude ( decimal degrees )

  • Latitude ( decimal degrees )

  • Longitude speed ( m/s )

  • Latitude speed ( m/s )

  • Altitude ( m )

  • Rate of Climb ( m/s )

  • Track ( degrees )

  • Heading ( degrees )

  • Airspeed ( m/s )

  • Roll, Pitch and Yaw ( radians )

  • Roll Rate, Pitch Rate and Yaw Rate ( radians/s )

  • No labels