Looking to what you said - and I may be wrong - your problem is related to the type of firmware installed in the driver and its incompatibility with the flashlight (or vice-versa)
You have a Convoy S2+ flashlight which works with mechanical switches (reverse clicky switch or forward clicky switch), while your driver has installed a firmware designed to be used in electronic switch flashlights (like the Emisar D4 or others).
So, unless I’m missing something important, your flashlight won’t be able to use this driver since they are not compatible.
You can choose a ramping firmware to use in a Convoy S2 but that will not be “Electronic Switch Standard” nor “D4 UI V2 (E-switch)”, it will be “Crescendo”, that is designed to be used in flashlights using mechanical switches.
Agreed. You need a driver with standard firmware for mechanical switch input. The e-switch firmware has the mcu waiting for a signal from a different input point (switch)…the mechanical tail switch is only connecting or cutting power, so half presses as usual just cut power without the mcu interpreting an instruction to do something.
I don’t think there’s any creative way to get around this in the S2+ host since there’s almost no room to add things even if you wanted to drill holes in it.
Unless you want to start flashing firmware with multiple flashlights, it may not be worth your time and costs to do so. But if you’re up for a new learning opportunity, good luck to you.
Maybe you could send it back to MTN to swap out the firmware, or it may just be cheaper to buy a new driver.