rusefi.com

Can you tell me what values to start with for tuning closed loop boost control? I have my open loop pretty much dialed in like I want it. What values where? Here's an example of a tune with pretty good boost control (I've endurance raced on it with good control!): https://rusefi.com/online/view.php...

NickZ wrote: ↑

Mon Jun 27, 2022 8:50 am

ive renamed the with TXT on the end to be able to upload them, but Im Know you already knew this.

This was a suggestion to use rusefi.com/online

NickZ wrote: ↑

Mon Jun 27, 2022 8:50 am

trigger is set to 36/1 I am assuming this is for 36-1 or is it 36+1 cam and this is why Im having trouble?

You said this is a BMW? No BMW that I know of is 36-1.

Shall we touch Porsche 996

no

Your SD card is probably fine (and compatible), we can't get it to work on that model ECU either. Pending whether it's a software or hardware issue...

ridewhencan wrote: ↑

Mon Jun 20, 2022 9:24 pm

I was making a critical error in the log sequence

BTW, I just wrote a doc page on logging: https://wiki.rusefi.com/Logging-Guide/

If you're trying to get something stable and predictable, I would disable closed loop idle completely, and get that dialed in first. Closed loop should just be "icing on the cake" once the open loop is dialed in.

Agh, your problem is probably the "offset" field in the closed loop idle section. Set that to 0 and see if the problem goes away.

nmstec wrote: ↑

Mon Jun 20, 2022 9:18 pm

In the rare case you have a car that has no actual VSS, but need an idea of speed, this would be the future LUA script to do so.

In the rare case you have no VSS, want one, and ALSO HAVE GEAR POSITION SENSING!

Maybe the same as RX8 36/2/2/2?

I have one idea. Can I calibrate TPS manualy from "default position" to WOT and after that, have Idle control "from 0% TPS to -5%" ,, ?? Please do not do this. It's not safe. The TPS error you see is a safety feature, intended to prevent the throttle from doing something unexpec...

AndreyB wrote: ↑

Mon Jun 13, 2022 11:48 pm

GPPWM should be the easy way but it does not support CLT axis yet

Not true, it supports it already for the Y axis. I use it to control my electric water pump.

We don't support the 360 tooth wheel - I'd recommend one of the inexpensive 24 tooth wheels that fits in your CAS, those are well supported.

What does the tunerstudio high speed trigger logger look like?

Can you upload a normal tunerstudio log (with the communication rate set to max) of the problem to rusefi.com/online?

Affirmative.

In case of loss of sync it would require dropping RPM back down below the threshold to re-sync with the cam. Once back below the max sync rpm, it'll consider the cam input again, and get back to full sync. The point of that setting is to deal with a cam sensor that provides bogus information when sp...

What's an actual upper limit you'd expect to see from CHT on an air cooled engine? 150? 200? 250? The only air cooled I've dealt with were carbureted aero engines that I'm not sure even had real numbers on the CHT gauge (if they had one at all), so we're a bit in the dark here on what it "shoul...

It checks against our synthetic "driver throttle intent" channel. In case of cable throttle it uses TPS, in case of electronic throttle it uses the pedal.

The result from that table just gets multiplied in at the end, we make no automatic correction. Somewhat counterintuitively, that actually isn't the correct shape of that table. The MAP sensor already compensates for almost all of the change on the intake side of the engine, so you're actually compe...

If you can take another TS trigger log with the updated settings, I can have a look at it tonight. You can also try updating to the latest pre-release (soon to be a real release: https://github.com/rusefi/rusefi/releases/tag/20220602_release

Now the real problem: I got the .bin from https://github.com/mck1117/wideband/blob/master/for_rusefi/wideband_image_with_bl.bin But only the version at july 2021 works, all the other versions not! what I mean works: july 2021 .bin wbo starts, exits bootloader and wait for sensor. If there is sensor...

Ok - had a chance to look. I would also set "invert primary", since it looks like your sensor is designed to run on falling edges (instead of rising edges as we're decoding now). Check the timing after that since it could move the timing by ~1/2 tooth width. That's a minor problem though, ...

Try setting "use only rising edge" on the trigger config page. Currently away from a PC, but I can have a look tomorrow.

I run them and my tune is reasonably accurate:
https://rusefi.com/online/view.php?msq=969&dialog=injectorConfig

Can you post your tune and a log of this happening to rusefi.com/online? Much easier to interact with it if stored there.

I see that you run unit tests without an IDE and that's strange. not strange, there are dozens of us! Is there some kind of documentation about the unit tests? I didn't find any information about it besides this thread. I compiled the unit_tests, ran the rusefi_test.exe and got the trigger images f...

I know those values should be swapped BTW there's no such thing as "should be swapped" - that's the point of the TPS calibration process. So long as the sensor does something linear, it does the right thing. Electronic throttle bodies have a redundant pair of sensors that are usually roug...

Also, can you take a photo of the missing tooth on your wheel?