sambas f7f1b37c62 OP-25 Flight/GPS: More object fields for GPS module ... git-svn-id: svn://svn.openpilot.org/OpenPilot/trunk@664 ebee16cc-31ac-478f-84a7-5cbb03baadba		2010-05-25 05:14:52 +00:00
..
inc	OP-25 Flight/GPS: More object fields for GPS module	2010-05-25 05:14:52 +00:00
actuatorcommand.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
actuatordesired.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
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
altitudeactual.c	Flight/Altitude Update altitude object with new metafields, modified update rates in XML and flight s/w	2010-05-20 01:21:44 +00:00
attitudeactual.c	Flight/Attitude Minor change in field names and task priority	2010-05-25 00:49:46 +00:00
attitudedesired.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
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/Alarms Implemented Alarms library, now checking for stack overflow, out of memory, event and other errors (see the SystemAlarms object). All modules will be reporting their alarms using this library.	2010-04-27 01:55:28 +00:00
exampleobject1.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
exampleobject2.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
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
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
gpsobject.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	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
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
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
stabilizationsettings.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
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	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
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	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
uavobjectsinit.c	Add AHRS attitude module and driver skeletons	2010-05-24 16:33:36 +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