In re different switch/speed settings, I started off with a Flipsky 75100 three months ago and ended up upgrading to the V2 Pro after it blew a fet. Before that, I was using a Cycle Analyst / Phaserunner setup, the latter of which ended up failing. I explain all this because I still have the Cycle Analyst. Let me quote part of the user manual to help explain the relevance:
With that understanding, the analog signals being described / tapped into is both ends of the shunt resistor. The Cycle Analyst doesn't need that connection to take the input voltage from a typical three wire throttle and send whatever preconfigured throttle out voltage, which you connect to one of the ADC pins on the Flipsky. The only thing the Cycle Analyst really needs is V+ and V- from the battery, which I provide with a custom harness terminated with XT90s going to the Flipsky and 18AWG wires in parallel terminated with an XT30, which ends up terminating to a JST connector connected to the to the CA, but I digress.
The CA can be configured to take input from a digital switch and have it switch between different throttle settings/profiles that ultimately affect the throttle voltage signal on the pin connected to the ADC input on the Flipsky. Since I already had a CA kicking around and some general familiarity with how it works, this solution was easiest for me. It's also an extra $150 if you don't already have kicking around (
CA-SA)
Though I might try taking a swing at coding a solution in LISP. I'm kind of annoyed this functionality isn't already baked into VESC as an ADC control type.