peabody124 cfd20922cd AHRS: Added the filtered data to the attitude raw object. Even though this seems like an oxymoron it's still raw to the EKF algorithm, and nice to see the real values after filtering to make sure nothing weird is going on. However, if people don't like this I'm open to suggestions/patches. I'd maybe suggest the whole attituderaw object be converted to ahrsraw anyway since it's more like that (eg. none of the values are actually attitude estimates). ... git-svn-id: svn://svn.openpilot.org/OpenPilot/trunk@1325 ebee16cc-31ac-478f-84a7-5cbb03baadba		2010-08-18 14:54:24 +00:00
..
inc	AHRS: Added the filtered data to the attitude raw object. Even though this seems like an oxymoron it's still raw to the EKF algorithm, and nice to see the real values after filtering to make sure nothing weird is going on. However, if people don't like this I'm open to suggestions/patches. I'd maybe suggest the whole attituderaw object be converted to ahrsraw anyway since it's more like that (eg. none of the values are actually attitude estimates).	2010-08-18 14:54:24 +00:00
actuatorcommand.c	Flight/UAVObjects Modify update rate and acked flag of periodic objects, added new gpsobject fields	2010-05-30 01:56:43 +00:00
actuatordesired.c	Flight/UAVObjects Modify update rate and acked flag of periodic objects, added new gpsobject fields	2010-05-30 01:56:43 +00:00
actuatorsettings.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
ahrsstatus.c	ahrs status: Add AhrsStatus UAVObject	2010-07-04 02:21:34 +00:00
altitudeactual.c	Flight/UAVObjects Modify update rate and acked flag of periodic objects, added new gpsobject fields	2010-05-30 01:56:43 +00:00
attitudeactual.c	Flight/Attitude Minor change in field names and task priority	2010-05-25 00:49:46 +00:00
attitudedesired.c	Flight/UAVObjects Modify update rate and acked flag of periodic objects, added new gpsobject fields	2010-05-30 01:56:43 +00:00
attituderaw.c	attituderaw: Replace HeadingActual with AttitudeRaw	2010-08-14 23:42:14 +00:00
attitudesettings.c	Add AHRS attitude module and driver skeletons	2010-05-24 16:33:36 +00:00
attitudesettings.py	Add AHRS attitude module and driver skeletons	2010-05-24 16:33:36 +00:00
eventdispatcher.c	Flight/Telemetry Avoid bunching of periodic updates by spreading them.	2010-06-11 02:24:26 +00:00
exampleobject1.c	Flight/UAVObjects Modify update rate and acked flag of periodic objects, added new gpsobject fields	2010-05-30 01:56:43 +00:00
exampleobject2.c	Flight/UAVObjects Modify update rate and acked flag of periodic objects, added new gpsobject fields	2010-05-30 01:56:43 +00:00
examplesettings.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
flightbatterystate.c	new object: FlightBatteryState	2010-06-13 17:21:31 +00:00
flightsituationactual.c	Added UAVObjects: FlightSituationActual NavigationSettings NavigationDesired	2010-07-26 21:26:28 +00:00
flighttelemetrystats.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
gcstelemetrystats.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
manualcontrolcommand.c	Flight/UAVObjects Modify update rate and acked flag of periodic objects, added new gpsobject fields	2010-05-30 01:56:43 +00:00
manualcontrolsettings.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
navigationdesired.c	Added UAVObjects: FlightSituationActual NavigationSettings NavigationDesired	2010-07-26 21:26:28 +00:00
navigationsettings.c	Added UAVObjects: FlightSituationActual NavigationSettings NavigationDesired	2010-07-26 21:26:28 +00:00
objectpersistence.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
positionactual.c	Flight/GPS Renamed GPSObject to PositionActual and implemented field for GPS status (NoGPS, NoFix, Fix2D and Fix3D)	2010-06-10 01:28:06 +00:00
stabilizationsettings.c	Added UAVObjects: FlightSituationActual NavigationSettings NavigationDesired	2010-07-26 21:26:28 +00:00
systemalarms.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
systemsettings.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
systemstats.c	Flight/UAVObjects Modify update rate and acked flag of periodic objects, added new gpsobject fields	2010-05-30 01:56:43 +00:00
telemetrysettings.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00
uavobjectmanager.c	Deleted OpenPilot.posix branch. Integrated portability modifications into main tree	2010-07-13 16:23:41 +00:00
uavobjectsinit.c	attituderaw: Replace HeadingActual with AttitudeRaw	2010-08-14 23:42:14 +00:00
uavobjectsinittemplate.c	Updates on UAVObjects required by the object generator	2010-03-27 03:19:56 +00:00
uavobjecttemplate.c	OP-48 Flight/UAVObjects Add access mode field in the metadata. This field can be used to disable local UAVObject updates in the flight or GCS software. It is transparent to any modules and plug-ins, the access control is done by the UAVObjectManager. This functionality is needed for the HITL simulation since certain objects that are normally updated by the flight software (e.g. AttitudeActual, Airspeed etc) will now need to be updated by the GCS. The modules reading those objects do not need to know if the object is updated by the GCS or by the flight software, when HITL is enabled it is transparent to the modules.	2010-05-20 00:58:40 +00:00