rooty/LibrePilot
1
0
Fork 0
mirror of https://bitbucket.org/librepilot/librepilot.git synced 2024-11-30 08:24:11 +01:00
Code Issues Releases Activity
ff0bd87f4e
LibrePilot/shared/uavobjectdefinition/hwsettings.xml

24 lines
1.7 KiB
XML
Raw Normal View History

hwsettings: UAVObject to select hardware runtime hw config
2011-06-19 16:56:40 +02:00
<xml>
Make it possible to optionally enable the CameraStab module
2011-07-30 05:08:47 +02:00
<object name="HwSettings" singleinstance="true" settings="true">
<description>Selection of optional hardware configurations.</description>
CC: rename ReceiverPort PPM+Servo (Servo) options to PPM+Outputs (Outputs)
2011-12-11 21:52:51 +01:00
<field name="CC_RcvrPort" units="function" type="enum" elements="1" options="Disabled,PWM,PPM,PPM+Outputs,Outputs" defaultvalue="PWM"/>
spektrum: rework DSM2/DSMJ/DSMX driver for explicit DSMX resolution support - both CC serial ports are now disabled by default (no telemetry); - serial ports now have DSM2, DSMX (10bit) and DSMX (11bit) options; - ReceiverGroups now have DSM (MainPort) and DSM (FlexiPort) options. For DSM2 protocol there is an explicit resolution bit in the stream, so the DSM2 should be selected. For DSMX there is no such bit, and user should choose the resolution from the list configuring the spektrum port. ReceiverGroups have single DSM option which is handled by the same driver. Downside: this implementation saves received frame first, unrolls by the end of frame. This should be ok, but may be improved by unrolling channels on the fly in the rx callback. Another minor difference is that a ChannelGroup is now bound to port: DSM (MainPort) or DSM (FlexiPort). This was considered as acceptable solution in order to not have 6 DSM options for each ChannelGroup and even more in case of new DSM protocol variations. Known problem: it is not possible to choose same protocols like DSM2/DSM2 for two ports. It can be enabled by adding an exception to common rule, though. The DSMX throttle channel misbehavior (zero value) is not treated specially yet. It should trigger the failsafe being out of bounds. More info and data dumps are required to handle this properly.
2011-10-30 18:29:03 +01:00
<field name="CC_MainPort" units="function" type="enum" elements="1" options="Disabled,Telemetry,GPS,S.Bus,DSM2,DSMX (10bit),DSMX (11bit),ComAux" defaultvalue="Disabled"/>
<field name="CC_FlexiPort" units="function" type="enum" elements="1" options="Disabled,Telemetry,GPS,I2C,DSM2,DSMX (10bit),DSMX (11bit),ComAux" defaultvalue="Disabled"/>
rcvr: support multiple simultaneous receivers Now also supports multiple instances of the Spektrum driver. These are configured as Spektrum1 and Spektrum2.
2011-07-30 21:04:24 +02:00
spektrum: rework DSM2/DSMJ/DSMX driver for explicit DSMX resolution support - both CC serial ports are now disabled by default (no telemetry); - serial ports now have DSM2, DSMX (10bit) and DSMX (11bit) options; - ReceiverGroups now have DSM (MainPort) and DSM (FlexiPort) options. For DSM2 protocol there is an explicit resolution bit in the stream, so the DSM2 should be selected. For DSMX there is no such bit, and user should choose the resolution from the list configuring the spektrum port. ReceiverGroups have single DSM option which is handled by the same driver. Downside: this implementation saves received frame first, unrolls by the end of frame. This should be ok, but may be improved by unrolling channels on the fly in the rx callback. Another minor difference is that a ChannelGroup is now bound to port: DSM (MainPort) or DSM (FlexiPort). This was considered as acceptable solution in order to not have 6 DSM options for each ChannelGroup and even more in case of new DSM protocol variations. Known problem: it is not possible to choose same protocols like DSM2/DSM2 for two ports. It can be enabled by adding an exception to common rule, though. The DSMX throttle channel misbehavior (zero value) is not treated specially yet. It should trigger the failsafe being out of bounds. More info and data dumps are required to handle this properly.
2011-10-30 18:29:03 +01:00
<field name="OP_RcvrPort" units="function" type="enum" elements="1" options="Disabled,PWM,PPM,DSM2,DSMX (10bit),DSMX (11bit),Debug" defaultvalue="PWM"/>
Merge branch 'next' into GCS_ChangesToUI-RuntimeCFG Conflicts: flight/CopterControl/Makefile flight/OpenPilot/System/pios_board.c flight/OpenPilot/UAVObjects.inc flight/PiOS/STM32F10x/pios_spektrum.c ground/openpilotgcs/src/plugins/config/config.pro ground/openpilotgcs/src/plugins/config/configgadget.qrc ground/openpilotgcs/src/plugins/uavobjects/uavobjects.pro shared/uavobjectdefinition/hwsettings.xml
2011-08-27 07:44:58 +02:00
<field name="OP_MainPort" units="function" type="enum" elements="1" options="Disabled,Telemetry" defaultvalue="Telemetry"/>
spektrum: rework DSM2/DSMJ/DSMX driver for explicit DSMX resolution support - both CC serial ports are now disabled by default (no telemetry); - serial ports now have DSM2, DSMX (10bit) and DSMX (11bit) options; - ReceiverGroups now have DSM (MainPort) and DSM (FlexiPort) options. For DSM2 protocol there is an explicit resolution bit in the stream, so the DSM2 should be selected. For DSMX there is no such bit, and user should choose the resolution from the list configuring the spektrum port. ReceiverGroups have single DSM option which is handled by the same driver. Downside: this implementation saves received frame first, unrolls by the end of frame. This should be ok, but may be improved by unrolling channels on the fly in the rx callback. Another minor difference is that a ChannelGroup is now bound to port: DSM (MainPort) or DSM (FlexiPort). This was considered as acceptable solution in order to not have 6 DSM options for each ChannelGroup and even more in case of new DSM protocol variations. Known problem: it is not possible to choose same protocols like DSM2/DSM2 for two ports. It can be enabled by adding an exception to common rule, though. The DSMX throttle channel misbehavior (zero value) is not treated specially yet. It should trigger the failsafe being out of bounds. More info and data dumps are required to handle this properly.
2011-10-30 18:29:03 +01:00
<field name="OP_FlexiPort" units="function" type="enum" elements="1" options="Disabled,GPS" defaultvalue="GPS"/>
Merge branch 'next' into GCS_ChangesToUI-RuntimeCFG Conflicts: flight/CopterControl/Makefile flight/OpenPilot/System/pios_board.c flight/OpenPilot/UAVObjects.inc flight/PiOS/STM32F10x/pios_spektrum.c ground/openpilotgcs/src/plugins/config/config.pro ground/openpilotgcs/src/plugins/config/configgadget.qrc ground/openpilotgcs/src/plugins/uavobjects/uavobjects.pro shared/uavobjectdefinition/hwsettings.xml
2011-08-27 07:44:58 +02:00
Change back the default telemetry speed
2011-12-15 07:57:36 +01:00
<field name="TelemetrySpeed" units="bps" type="enum" elements="1" options="2400,4800,9600,19200,38400,57600,115200" defaultvalue="57600"/>
HwSettings: move Telemetry and add GPS port speed to the HwSettings object TelemetrySettings object removed (saved 200+ bytes of RAM). Telemetry port speed moved to the HwSettings object. Added GPS port speed setting. GCS code updated to reflect changes and support both fields.
2011-09-28 21:09:19 +02:00
<field name="GPSSpeed" units="bps" type="enum" elements="1" options="2400,4800,9600,19200,38400,57600,115200" defaultvalue="57600"/>
HWSettings: Allow late Initialization and Start of Modules as defined in Makefile(available modules) and UAVObject(actually started modules)
2011-08-20 01:24:06 +02:00
<field name="OptionalModules" units="" type="enum" elementnames="CameraStab,GPS" options="Disabled,Enabled" defaultvalue="Disabled"/>
Merge branch 'sambas/dsmx_stuff' of ssh://git.openpilot.org/OpenPilot into next Conflicts: shared/uavobjectdefinition/hwsettings.xml
2011-08-24 18:37:30 +02:00
<field name="DSMxBind" units="" type="uint8" elements="1" defaultvalue="0"/>
Merge branch 'next' into GCS_ChangesToUI-RuntimeCFG Conflicts: flight/CopterControl/Makefile flight/OpenPilot/System/pios_board.c flight/OpenPilot/UAVObjects.inc flight/PiOS/STM32F10x/pios_spektrum.c ground/openpilotgcs/src/plugins/config/config.pro ground/openpilotgcs/src/plugins/config/configgadget.qrc ground/openpilotgcs/src/plugins/uavobjects/uavobjects.pro shared/uavobjectdefinition/hwsettings.xml
2011-08-27 07:44:58 +02:00
Make it possible to optionally enable the CameraStab module
2011-07-30 05:08:47 +02:00
<access gcs="readwrite" flight="readwrite"/>
<telemetrygcs acked="true" updatemode="onchange" period="0"/>
<telemetryflight acked="true" updatemode="onchange" period="0"/>
<logging updatemode="never" period="0"/>
hwsettings: UAVObject to select hardware runtime hw config
2011-06-19 16:56:40 +02:00
</object>
</xml>
Reference in New Issue Copy Permalink