LukeZ

Ausf, you mentioned depth sensing - the TCB also has two general purpose I/O ports that can be set to input or output. When set to input, they become triggers themselves that can be assigned to any of the existing functions. A silly example is to attach a potentiometer to one of these inputs, and assign that as an input to control the brightness of an LED. However you could instead connect a depth sensor (assuming the sensor provides or can be made to provide a variable voltage), then assign that as a control to a servo output (perhaps your dive planes), or to one of the custom user functions and have it do whatever you want.

This could be accomplished quite easily with the hardware and software in its present state, and you can still use the convenient interface to assign triggers to functions.

I should also mention that all the hardware on the board can be re-purposed without much effort. For example, yes there is a plug to attach a HL/Taigen smoker. And if that is what you want, that is all you need to do. But if you don't need a smoker on a sub, but you could use another uni-directional speed control - OP Config easily allows you to "disconnect" the smoker output from the smoker function, and use it instead as a speed control. You can then assign any RC channel or other trigger to that control. The same goes for running additional speed controls not related to the drive motors, more servos, whatever.

This all probably sounds more complicated than it really is. When you understand the simple concept of functions (do stuff) and triggers (commands like RC channels from your transmitter), and you see the vast array of possible functions and the multitudes of ways they can be connected to triggers, the power and flexibility start to become apparent, and the potential applications go far beyond tanks to any RC controlled object.