dankers 69d2c1b546 Add flightbatterystate to the GCS, ran uavobjgenerator on all XML files. .cpp and .h included for GCS now, uncommented out these files from the uavobjects.pro. ... Moving sounds folder to shared. Some sounds will be uploaded later. git-svn-id: svn://svn.openpilot.org/OpenPilot/trunk@792 ebee16cc-31ac-478f-84a7-5cbb03baadba		2010-06-17 10:06:51 +00:00
..
inc	FlightBatteryState object changed	2010-06-16 13:41:10 +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
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
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
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
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	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	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	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 flightbatterystate to the GCS, ran uavobjgenerator on all XML files. .cpp and .h included for GCS now, uncommented out these files from the uavobjects.pro.	2010-06-17 10:06:51 +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