Configurable depth data source for systems with multiple transducers

[PiotrSol]

Can depth data source path be made configurable in plugin settings (for example in Advanced Settings section)?

I have 2 transducers installed in both hull each on catamaran 17m LOA and on one side before the mini-keel and on the other after so they are around 10m apart. I use one (DST810) for Raymarine system (it only supports 1 as a source for the whole system) and the other (P17 connected via ITC5) is configured in SignalK and forwarded over NMEA183/wifi to a tablet with Navionic Boating app.
I collect depth data from both in SonarCharts Live on the plotter (from DST810) and tablet (P17).

For the crow-depth I would prefer collecting data from DST (more accurate reading as not affected by prop wash in reverse and... toilet flush :-) ) so need a way to point the plugin to the path. Ideally can collect both anyway I beleive it will make the plugin to complicated.

[bkeepers]

I wondered how long it would be until someone had multiple sounders. 😆

So how they both show up in Signal K under environment.depth.belowTransducer?

[PiotrSol]

Wasn't that long :-)

I use Data Connections to link:

environment.depth.belowSurface
environment.depth.belowTransducer
environment.depth.surfaceToTransducer
to the device I prefer to display in the Navionics app.

So all depth data paths are linked to NMEA2k device 105 or calculated by derived-data plugin:

environment.depth.belowKeel | 2.8 m | 17:05:26 | derived-data
environment.depth.belowSurface | 4.26 m | 17:05:32 | n2k-on-ve.can-socket.105  (128267)
environment.depth.belowTransducer | 3.76 m | 17:05:32 | n2k-on-ve.can-socket.105  (128267)
environment.depth.surfaceToTransducer | 0.5 m | 17:05:32 | n2k-on-ve.can-socket.105  (128267)
environment.depth.transducerToKeel | -1 m | 17:05:26 | derived-data

Trying to figure out how I can use another device in your plugin......