rusefi.com

I was actually wondering if the GDI circuitry could be dumbed down to work for non-GDI cars? I.e. since it can do boost/peak/hold, can it also just do peak/hold? And if it can do that, it can probably handle saturated/high impedance injectors too... One Board To Rule Them All! Meh, high-z injectors...

Here's an example of the pressure staying flat while injection is suspended:

Oh I forgot to mention decay rate. The HPFP has no way to lower rail pressure other than the emergency relief valve or injecting fuel. So if the target pressure rapidly decreases, you need some logic to say "no, that's not really achievable, lets only lower the pressure by a certain amount com...

I've seen the result on my engine, again configured more by guess than measurement, and this table makes pressure control very smooth. I KNEW I'd seen this idea somewhere! The OEM tune for my Focus had a "Pump VE" table, dependent upon RPM and rail pressure: image.png I guess that's exact...

I would like to improve the activation hold time logic. Motec actually has a 3d table for this on RPM and battery voltage. Personally I'm not sure why voltage matters if you have a current control output, but from the sounds of the help file I don't think they do use a peak and hold driver, instead...

Also note that at least Bosch says the solenoids are peak and hold, meaning you really should be driving this using a special circuit. I don't know if you guys did that in your initial experiments; I remember reading on one post that you burned out the driver or something, maybe it was due to eithe...

Because the pin error is happening on a few unrelated pins that are physically next to each other on the STM32, I kind of suspect that there's been a failure inside the STM32. This *smells* like some unexpected voltage found its way to one of the STM32 pins, which shorted the clamping diodes for tho...

AndreyB wrote: ↑

Wed Nov 03, 2021 9:20 pm

mck1117 wrote: ↑

Wed Nov 03, 2021 9:14 pm

We already know a firmware reload didn't fix it.

Let's clarify "firmware reload"

a) re-flashing with same version or more recent rusEFI master snapshot
b) some custom firmware version maybe related to https://github.com/rusefi/rusefi/pull/3450

a

Few fought: 1. keep settings, tables as big as you want. On storage. Preload only used tables in ram. Can also solve request having several switchable tables. Will need some kind on software MMU. Dynamic allocation. Can cause out of ram issue during execution. 2. generate ini files on MCU side. Thi...

order of things that happened:

1. tach stops working
2. engine dies
3. error on next power cycle (the error happens immediately at power on)

We already know a firmware reload didn't fix it. I think this is a hardware failure. I'd love to inspect the hardware.

Does the SD card actually fit there with the screw? The card extends far past the end of the socket.

BeerMoneyMotorsports wrote: ↑

Tue Nov 02, 2021 11:28 pm

This is what i had on my old VVT car with MS.

Did that use TPS or MAP for the Y axis?

Something like this might be worth a shot:

I was able to get the vvt to respond pretty accurately under these settings... Awesome - this log looks MUCH better with respect to VVT control! ...however the car has a very jerky takeoff from stops Any input on what to change/where I should be looking to fix that? (car takes off from stops fine w...

mk e wrote: ↑

Sat Oct 30, 2021 1:01 pm

the orange saw tooth is crank angle so you can see phasing

Say, that's a good idea for us to add. We've prodded the tunerstudio folks enough so that we can now update/log at a full 1khz, so engine phase is a fun thing to log.

Nightsknight45 wrote: ↑

Tue Nov 02, 2021 5:49 pm

https://www.facebook.com/stevesremotetuning was tuning the car.

With all due respect, this means your tuner didn't actually look at VVT at all, and likely didn't actually tune your car.

Your hardware is fine. PID settings are pretty clearly super wrong. Where did you get your VVT PID settings? Looking at the output duty cycle, your settings are not nearly strong enough. The controller is responding to input, but extremely slowly, so you end up with relatively random solenoid duty. ...

I actually disagree that it would be a lot of work to get a tuning and logging app up and running, but I may as well put my time where my mouth is. My day job is in application software. Trust me, the gulf between "up and running" and "usable" is far, far wider than you think it...

Can you set debug mode to "VVT1 PID" and take another log? That will give additional information about what's going on.

IMO TunerStudio is getting in the way of both efficient memory layout (maybe you don't care because you'll just bump the minimum required MCU and leave existing users with no upgrade path?) and in the way of usability without recompiling the firmware (for traction control I want a 2d table based on...

Already running on rusEFI?

ssmith wrote: ↑

Sat Oct 30, 2021 12:55 am

I've been reading over some of the code and have come up with some questions. Sorry if this is newbie stuff

Oh, and this isn't newbie stuff. Asking this kind of question indicates that you have a very deep level of understanding about what's going on here

1. MAP averaging is particularly useful for engines with ITBs or tiny plenums, where the MAP signal may only be valid for a short duration (ie, intake valve is open). Phase aligned sampling also can help avoid any aliasing since the MAP ripple is of course variable frequency. 2. It's a possibility, ...

Thanks, looks like there are available Nucleo boards for a reasonable price. F427/429, F767, and H743 are the best supported options there. Looks like the H753 is the same as the H743, but with added crypto hardware (different SKU to avoid ITAR problems), so it should be fully compatible with the H...

I have a spare F429 nucleo if you're in the US.

You can always underclock the MCU, but not really overclock. We're more memory strapped than we are CPU cycles, so I'd recommend against a smaller MCU.

Also the adding real time date to the log, am I to guess that when the key is turned off the board shuts down and log time resets? The STM32 has a real-time clock, but it of course requires some source of power to run. Whenever the clock has a valid time, we write SD card logs with the date/time in...

You'd have to be super careful to cut this trace between the via and cap, but yes, it would be possible:

Cadence wrote: ↑

Wed Oct 27, 2021 8:56 pm

It is possible to add a coin cell/battery to any proteus, to allow the SD logs to write with real time stamps?

Unfortunately not really. The STM32 supports it, but to hook it up you'd have to lift a pin on the stm32 and connect the coin cell there.

image.png maybe a bad sensor? Hmm, maybe. It's possible that the VR interface on Proteus is unhappy about your single tooth VR setup. Possible to replace with a hall sensor in the same hole? Alternatively you could just run wasted spark and not worry about the cam sensor at all. My approximately si...

The cam sensor is VR and is on the exhaust cam. you can see the side of it in the second picture. The target is a single peg sticking out of the cam gear. both cams have the peg but only exhaust has a sensor. TS would not allow me to set the intake cam sensor to none so i have it set on the intake ...