LibrePilot/shared/uavobjectdefinition/receiveractivity.xml

<xml>
    <object name="ReceiverActivity" singleinstance="true" settings="false">
        <description>Monitors which receiver channels have been active within the last second.</description>
	<field name="ActiveGroup" units="Channel Group" type="enum" elements="1"
	       options="PWM,PPM,DSM (MainPort),DSM (FlexiPort),S.Bus,GCS,None"
	       defaultvalue="None"/>
	<field name="ActiveChannel" units="channel" type="uint8" elements="1"
	       defaultvalue="255"/>
        <access gcs="readonly" flight="readwrite"/>
        <telemetrygcs acked="false" updatemode="manual" period="0"/>
        <telemetryflight acked="false" updatemode="onchange" period="0"/>
        <logging updatemode="never" period="0"/>
    </object>
</xml>
rcvractivity: Add tracking of Rx channel activity 2011-08-02 07:27:37 +02:00			`<xml>`
			`<object name="ReceiverActivity" singleinstance="true" settings="false">`
			`<description>Monitors which receiver channels have been active within the last second.</description>`
			`<field name="ActiveGroup" units="Channel Group" type="enum" elements="1"`
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			`options="PWM,PPM,DSM (MainPort),DSM (FlexiPort),S.Bus,GCS,None"`
rcvractivity: Add tracking of Rx channel activity 2011-08-02 07:27:37 +02:00			`defaultvalue="None"/>`
			`<field name="ActiveChannel" units="channel" type="uint8" elements="1"`
			`defaultvalue="255"/>`
			`<access gcs="readonly" flight="readwrite"/>`
			`<telemetrygcs acked="false" updatemode="manual" period="0"/>`
			`<telemetryflight acked="false" updatemode="onchange" period="0"/>`
			`<logging updatemode="never" period="0"/>`
			`</object>`
			`</xml>`