rusefi.com

Hey guys,

Nice forum you got here.
I have been setting up a MRE board with our CBR600RR PC07. Or rather trying to.
I have a lot of problems that I would like to get some input/feedback on, but the first one is regarding the DBW.
I connected the TPS1 and TPS2, the APPS1 and APPS2 and the DBW Motor. We use the typic Bosch ETB.
So the signals for the Pedal and TPS are read properly, both of them also for both channels. The ETB Calibration yielded some plausible values. The gauges for all raw values make sense ans show the correct values.
But know, If I press the Pedal, for APPS 0 to about 90%, nothing happens on the ETB, and then between 90% and 100% APPS, the ETB opens suddenly from 0 to 100%.
I could debug this far that this occurs exactly when the "TPS accel Threshold" is succeeded so I suppose this is related to this var. Can somebody pinpoint me to what I have to do to get a proper behavior?

Thank you all in advance!

please share at least your tune https://github.com/rusefi/rusefi/wiki/HOWTO-upload-tune for us to have at least some data

With microRusEFI a popular pitfall is https://github.com/rusefi/rusefi/wiki/microRusEFI-Manual#pin-reuse

Hello,
Thanks for the reply.
I uploaded the tune as instructed:
https://rusefi.com/online/view.php?msq=1486
All I did was take the base config .ini from the MRE and define the pins for the TPS and APPS and did a ETB Autotune. Th ETB is also very noisy so I suppose the PID gains need further adjustment. They read the voltages correctly as mentioned, but the ETB doesnt behave as it should as described in the first post.

Thank you for pointing me to the Pin Reuse. I dont see a problem with this tho as I havent configured anything "special" or different from the stock pin map. So this Should be fine. As I mentioned earlier, the Voltages etc are read and displayed fine, I think its a software thing more than a wiring issue.

Thank you very much for the input.

You do not use any of the tricky analog inputs - no issue here

https://rusefi.com/online/view.php?msq=1486&dialog=pedalSensor pedal calibration does not look very redundant? I would expect software to block ETB control because of that, with a relevant indicator displayed on the bottom? Does your pedal have two separate sensors?

Yes, it is redundant. It's a bit weird because after reviewing the tuning myself I saw that they basically have the same value. But when measuring them by hand with a multimeter I get about 0v6 of difference between both. I use a Toyota Corolla Pedal Sensor.
It is also weird that I can only calibrate one sensor? As in get up and get down command for the voltages in TS are only available for the first input. I measured the second one by hand with a Multimeter and entered this values in there. But it seems like Tunerstudio just doesn't want to accepted these for some reason, as the uploaded fine shows basically the same value for them. That's ...weird?

I've actually experienced a variation of that. Please try typing calibration in manually - i know I was able to over-come it with some persistence

Anyway defect issue created https://github.com/rusefi/rusefi/issues/5329

Hello,

So I played a bit with settings etc. And then did a firmware update. This solved all issues.......
The ETB works now with my pedal sensor. It translates the pedal movement to the ETB aperture, but I have a very high pitched noise going on all the time. I tried to Autotune the PID for the ETB but this didnt help yet. Any input on this? I also tried to play with the PWM freq but I cant get it out of the audible spectrum.

Try "Disable ETB if engine is stopped"
So far with rusEFI you always hear etb.