@pkendall64 is this what you expected?

tested with oscilloscope, all ok

This is on the right track, but I think the UI part will need some work. We need to somehow merge the PWM and channel mapping together to create a concise simple UI for users.

This is on the right track, but I think the UI part will need some work. We need to somehow merge the PWM and channel mapping together to create a concise simple UI for users.

I was thinking about that - and did separate channel list for serial, reasons:

• there are serial only receivers, without PWM
• number of PWM channels is different from fixed 16 channels on serial ports
• adding that to PWM channels, where you must select Serial output was super confusing

What I tried as well and looked slightly better was to have 2 columns with 2 channels per row.

Should I prepare 2nd PR with Serial config in the upper config part?

@pkendall64: prepared updated preview:

Original implementation:

For me is the original bit less confusing.

did some more previews - having the Channels in 2/4 columns looks way better:

Yeah, maybe the second is clearer.
If we go with the second then we'd be able to also select LQ and RSSIdBm as values to be output on some channels and that would resolve another issue as well.

Another issue is that we now have 2 potential serial outputs. So it may be better to relabel the columns, and hide the column is that serial is not configured and hide the entire section if no serial output is configured.

Or something similar.

Yeah, maybe the second is clearer. If we go with the second then we'd be able to also select LQ and RSSIdBm as values to be output on some channels and that would resolve another issue as well.

Another issue is that we now have 2 potential serial outputs. So it may be better to relabel the columns, and hide the column is that serial is not configured and hide the entire section if no serial output is configured.

Output Channel Serial 1 Serial 2
Or something similar.

Not 100% sure, what second mean :-) I will add 2nd serial option as well the LQ and RSSIdbm. But I need a bit of guidance - how to map both values to CRSF/SBUS/other serial protocols.

second was referring to the second screenshot, in the seperate section.

second was referring to the second screenshot, in the separate section.

Just to be completely sure - separate section with 1 column.

How what about the mapping of RSSI and LQ mapping?

and one more question - what is a good receiver with possibility of 2 serial ports?

The BetaFPV SuperP 14 channel receiver is a good one. You can configure the second serial on any of the pins.

Yeah, maybe the second is clearer. If we go with the second then we'd be able to also select LQ and RSSIdBm as values to be output on some channels and that would resolve another issue as well.

Another issue is that we now have 2 potential serial outputs. So it may be better to relabel the columns, and hide the column is that serial is not configured and hide the entire section if no serial output is configured.

Output Channel Serial 1 Serial 2
Or something similar.

Like this? There still might be space for 2 channels on one row. More needs to be done for LQ and RSSI. will try to finish it during weekend.

@pkendall64 who was doing the webUI things for serial port? It's a bit mess, the updates now are coming from various sources - Airport settings, Serial, Serial 2, etc.

What would be better solution - small refactor or introduction of a small controller handling all the events and getting UI in one state (showing/hiding the particular config options?).

Please consider a more general approach which mixes the incoming channels so it is not serial output specific.

I've been working on a generic mixer to support RX gyros #2869

Please consider a more general approach which mixes the incoming channels so it is not serial output specific.

I've been working on a generic mixer to support RX gyros #2869

ok, will do... summer break now, but might get to finish that next week :-)