rusefi.com

Wow.

I cannot explain any of this. I love my bits and bytes, but this is not bits and not bytes. It's a very pleasant surprise that it works

First drive with RusEFI!!!


Drives really good!
Boosting about 8psi, and I definitely found the limit of my stock injectors.
Can't get much over 5000 rpm with that much boost before I max them out.
The 460cc's are on the bench because one of them doesn't flow right.

This is just the beginning!

I love the sound of a BOV in the morning.

Congratulations

I sent my 460cc injectors in to injector-rehab for cleaning and flow testing.
Hopefully they'll be back soon, and I can see what sort of power this thing is really capable of

460cc injectors in, 7psi so far!
I found that my 3lb wastgate spring is too soft, so the exhaust pressure can force it open without the aid boost. Once I install a stiffer spring I'll crank it up some more.

Here is my latest tune with 550CC injectors.
Far from finished, but seems to be pretty dialed in for fuel flow rate and injector dead time.
The VE table is pretty close since most cells of the target AFR table now match my actual AFR.

If you want to make a juicy video and a sweet log file I would love to post at https://www.facebook.com/rusEfiECU/

We have so few happy users, you could be the first happy user of the month

Hook up a Boost valve (Cheap MAC Valve), and you can control boost from TS as well..

Then you can lower boost in critical rpms/areas and increase in others


Happy users are great

And we need to learn from the issues users have until they get there..

I would love to be able to control boost with TS.
I will be looking into this.

If we get another warm spell here in MI, I will see if I can get a nice video.

Yeah, just get a 3-port solenoid.

Just 12V and one wire from ecu. Fast and easy.

The MAC valves like this works great:

https://www.ebay.com/itm/MAC-3-Port-Electronic-Boost-Control-Solenoid-Valve-DC12V-5-4W-35A-AAA-DDBA-1BA/184179523715?hash=item2ae1f48083:g:NWwAAOSw8MZbvjJQ

Here's my happy user content



My current tune as well as a recent data log are attached here.
For some reason, the data log was written as a .mlg file, and wasn't attachable.
I manually changed the extension to .mls, so it may possibly not be viewable.

Still no electronic boost control, but I junkyard picked a boost solenoid off a volvo, and have started exploring the tune a little.

Thank you for the happy user content, helps to know that some of these are moving on their own power

960 wrote: ↑

Sat Feb 29, 2020 10:52 am

Hook up a Boost valve (Cheap MAC Valve), and you can control boost from TS as well..

Then you can lower boost in critical rpms/areas and increase in others

Question about Open loop boost control.
The table is RPM vs MAP.
Seems like it should be RPM vs TPS like the closed loop boost table.
Is this correct?
If so, how is it supposed to be tuned?
What are the Z axis values? Solenoid DC?

At the moment the answer is: unknown.

We have this code but we have no officially recognized reports of usage.

Sorry different subject - do you know the answer to https://rusefi.com/forum/viewtopic.php?p=35881#p35881?

The Z axis is duty-cycle in %

Not sure why your table and axis dont have values in it..

You can load this tune to fill some default values(Only alters boost)

960 wrote: ↑

Tue Mar 31, 2020 1:14 pm

Not sure why your table and axis dont have values in it..

As discussed a few times now, this is what happens when you update firmware with an incompatible change to the config layout. There was nothing there before, so it just reads out whatever garbage used to be there.

mck1117 wrote: ↑

Tue Mar 31, 2020 9:49 pm

960 wrote: ↑

Tue Mar 31, 2020 1:14 pm

Not sure why your table and axis dont have values in it..

As discussed a few times now, this is what happens when you update firmware with an incompatible change to the config layout. There was nothing there before, so it just reads out whatever garbage used to be there.

I am not following you?
Default values are set in engine_configuration, and should be there if it's updated.
In that case, the .ini must have been updated without updating firmware.

The only thing I can think of are if you select send tunerstudio-configuration at first connect after update,
this will happen.

960 wrote: ↑

Tue Mar 31, 2020 11:54 pm

Default values are set in engine_configuration, and should be there if it's updated.
In that case, the .ini must have been updated without updating firmware.

The only thing I can think of are if you select send tunerstudio-configuration at first connect after update,
this will happen.

I am afraid that this is not how things work. There is a chance that this is bad advice.

Default settings in the firmware are only applied for brand new ECUs. If you have some settings and some old firmware and then update the firmware, your old settings are used and defaults related to new features are not automatically applied. I hope that we would not be debating or discussing how to change this in this thread related to the specific application.

In this case defaults have to be applied manually. In order for @scramblr to apply those defaults someone would have to post a screenshot of default settings for this feature.

Got the boost solenoid installed.
One wire is getting 12V, the other wire is routed to pin w37 for injector driver PE5.
However, the solenoid starts cycling at the calibrated frequency (30hz) even when the boost control table is set to all zeros.
It will continue to cycle even if I disable boost control all together as long as the pin is still assigned.
The only way to stop the solenoid is to change the output assignment to none.

Any ideas what is going on?
Is using an injector driver the right approach?
This is what I did for my IAC valve, with good results.

Remember that you are the first user of boost and the contributor never showed any proof of this feature working.
Let's first see if software or hardware issue?
Do you have fly-back diode? Is fly-back diode needed here I am not sure to be honest.

Please use "boost control" debug mode to see commanded duty cycle.

Debug fields is an advanced troubleshooting feature allowing one to monitor internal state of some rusEfi subsystems.

In TunerStudio, select "Base Engine Settings -> Debug Mode" and use gauges from "Debug" category.

https://github.com/rusefi/rusefi/wiki/Debug_Mode

I recorded a log with boost control debug, but unfortunately I can't attach it here. Can't attach .mgl file type apparently.
What variable would be the boost control duty cycle?
All the debug variables show a value of 0.

https://github.com/rusefi/rusefi/wiki/Support now answers the logs question

Tune and data log attached in the zip file

debugF1 is Boost Open Loop Duty
debugF2 is Boost Closed Loop Duty

in your logs both seem to be showing zero. I cannot explain why is your HW producing 30 Hz what is the duty cycle?

I would have to hook up a scope to see the duty cycle.
Probably worth doing.

Is there a different pin I can use, or does it need an injector driver?
I'm all out of injector drivers, so that's why I ask.
Maybe there's a short somewhere causing the misbehavior?

scramblr wrote: ↑

Tue Apr 21, 2020 2:25 am

Is there a different pin I can use, or does it need an injector driver?

not sure what you mean here. all low side drivers are the same aren't they?

i think it could be time for you to join slack chat https://rusefi.com/forum/viewtopic.php?f=13&t=1198 to make this troubleshooting more efficient

So there are more than 12 low side drivers?

Is there a slack chat started on this topic?
I'd be happy to join.

https://app.slack.com/client/T4NJHQ8QZ/CRGAFLQUE/details/members is probably the most relevant