rusefi.com

Hi,
I am currently running a BTR transmission that outputs a analog voltage for the shifter position eg.
P=4.0v R=3.5v N=3.0v D=2.5v 3=2.0v 2=1.5v and 1=1.0v

The car is currently running on a Proteus 0.7 and a microsquirt for the transmission but i would like to move the transmission control over the the proteus.

is there currently any way to use the analog voltage as the range selector input?

Only via Lua something along the lines of https://github.com/rusefi/rusefi/blob/master/firmware/controllers/lua/examples/analog-gear-input.txt

viper128 wrote: ↑

Tue Jul 23, 2024 4:00 am

i would like to move the transmission control over the the proteus.

I wonder what's the plan here? as far as I know we have driven only 30 miles only on one transmission so far.

Thanks Andrey,
I was having hardware issues with the current MS2 based TCU setup and it looks like i can make rusEFI work for the current setup, even if its full Manual control for now.
Eventually the car will be getting converted to a ZF 6HP26 but am waiting on parts before i can finish the script and start testing that.

It also looks like there might be a problem with the TCU code in the current ProteusF4 firmware builds.
if i select "True" in Enable TCU, i immediately get the Red Error led on the Proteus and get a unrecognized device error in windows.
if it is already enabled and you write tune, the only way to get comms back is to enter boot mode and re-load the firmware.
get the errors using builds from 2024_07_12 and 2024_07_26
no error if i revert to the April Release "release_20240418"

viper128 wrote: ↑

Sat Jul 27, 2024 2:49 am

i immediately get the Red Error led on the Proteus and get a unrecognized device error in windows.

You are not providing sufficient details see https://github.com/rusefi/rusefi/wiki/rusEFI-Quick-Start-PDF