You will need a raw CAN log from the car with the original ECU in place and working without error.
Then a raw log again with the EMU in place instead (as it is now).
From that he can differentiate what messages are missing (i.e normally being sent by the original ECU) and emulate them in the EMU firmware, so the ABS knows no different
Could you review the Jeep trigger? It doesn’t run fast on my setup. Synchronization usually takes 0.5 seconds, and the injectors pulses another 0.7–0.8 seconds later. The starter cranks the engine for a long time without firing.
Hello ! Can we have the channel “Fuel Pressure Error” working WITHOUT enabling the Fuel Pressure Regulator Setting “Map Referenced + Fuel Pressure” on the fuel calculation model ?
I can NOT make the “Fuel Pressure Protection” work, because the error stays at 0 if the Fuel Setting Calculation: “Map Referenced + Fuel Pressure” is not chosen…
So basically “Fuel Pressure Protection.” is useless for any other fuel calculation model
Example if you choose on the fuel calculation basic settings " Fuel Pressure Regulator: Map Referenced " , Error just stays 0… It doenst move… As soon as you choose The fuel calcutaion to “Map Referenced + Fuel Pressure Sensor”, Fuel Pressure Error follows accordingly.
I guess choosing the “+ Fuel Pressure Sensor” options, opens up the comparison in the calculation for the Fuel Pressure Error… And thus making the Engine protection for the fuel Pressure prot. working.
I only care to have Engine Protection : Fuel Pressure Error Protection working no matter what the fuel calculations option you choose.
It used to be on EMU BLACK V2 and classic. Fuel pressure Delta and Fuel Pressure Delta Correction, two seperate channels… And the fuel pressure Delta was working no matter what options you selected…
I tried that last night on a sierra cosworth for the 3.070, i know this “bug” since day one of using the V3 but i write a lot of stuff many things pass under the radar. I was actually toggling the fuel calculation with my arrow keys up and down, and watching the fuel delta error going 0 and then working properly when i was toggling
Jadzwin, I’ve been testing the flat shift with the new disable function and it still seems to have a very very slight delay which causes about a 300 RPM flareup before flat shift is active after clutch engagement. Is there any fix for this? Green is clutch, purple is flat shift active
Looking back at my old logs before there was a disable switch, my flat shift active and clutch switch is a direct 1:1 with zero delay at all
The logged INJ ouputs (bottom track) appear to be missing some/most pulses. Executed sparks count increases smoothly as expected. I would expect to see an injection pulse corresponding with every spark in correct firing order. This is a 6 cyl engine in sequential mode.
Use built in scope for that it register exact injection and ignitio outputs start / end.
The log for inj outputs has resolution of 25Hz what is not enough to register all injections (aliasing). 25Hz means that each sample is taken every 40ms, the injection duriation is in shorter so not all can be recorded.
I’m just using my CAN Keypad button for my disable / enable switch. I did a test with no disable button and flat shift works instantly with clutch switch. But has a delay with my CAN keypad disable/enable set