Yes, but if you remove the standard ECU, nothing related to the engine is sent via OBD.
It is a problem when you have firmwar 3.046, if you upgrade it will appear.
It will be fixed in next build.
If you provide me porsche data I will implement it. It is not a problem.
We dont have such car for reverse engineering CAN nor the DBC file.
I’m not sure if I understand you correctly. You can set output as Virtual, then only function value will change.
Then you can assign function to Can switch board outputs:
Ok. I tested it with virtual as you said but I was unsure if it would work.
Thanks
Is there any method of duplicating output logic for two seperate aux outs? For this specific case it is to use two seperate boost controllers for a V6 twin turbo engine to simplify vacuum hose routing.
For example on Maxx ecu you can simply select “boost control” for two seperate outputs in their output config table .
You can connect both solenoids to 1 output if you want to control two solenoids with the same PWM signal.
1 Like
Hi there! May be I’m wrong, i’m not a master tuner and so on, but: The problem is, when i rev up my engine (2jz) about 5000 or more rpms, when rpms decrease - map is below 20, may be below 15. Idle in this moment is inactive, because of idle settings is work only above 21 kpa. May be i/m wrong, but its seems not correct to see only on map. I would like to see a threshold of RPM, a lower thrashold to active IDLE without any conditions. Lets say if my target 800, I would like to swtich from RPM decreasing to IDLE about 1000-950 RPM, just not to drop it below about 750. Another side of the problem: if I do MAP threshold (lets say 15 kpa), do PID starts decrease TPS (by DBW) while the engine has, for example 3000 rpm, and for idle it’s too high, and correction do its deal and as result I will have a stopped engine by DBW closed?
And another question: Why there is no Idle ing.corr? PID is TOO MUCH for this simple task (my opinon)
It’s seems just an option to disable ingition PID for idle, custom curve is sometimes the best option
I have put the DBC/info in the Software Opinions thread 
I am sad that there is still no support for controlling the Diff control strategy of the stepper motor for Haldex 1 gen.
1 Like
Please advise.
The cylinder that detected the knock voltage peak is #3, but #1 and #2 are displayed in “Knocking Cylinder”.
Is “Knocking Cylinder” always correct?
By trial and error of the parameters, the knock strategy has come to show a roughly satisfactory response.
What puzzled me was whether to modify the Gain or Integrator when trying to reduce knock judgments that are clearly not knocking.
The sample map had a very large Integrator set up, but when I did the same, I felt like I was only getting a small peak.
I understand that it is difficult to adjust the knock strategy to get the correct response, but I would like detailed information on the parameters in the help file in the future.
1 Like
Please read the help for the idle especially part of the target rampdown.
You can set very low MAP and just base on target rampdown and the pedal position.
Proper settings of Active state air flow, armed airflow, ramp down offset parameters and proper stable lambda in all idle are will give you consistent RPM drop to desired level.
Then setup the PID controllers to provide proper idle RPM in any conditions.
1 Like
Could you please publish the project and the log file ?
It’s around 4:37 in this log.
QNC10_Passo_K3VET15.emub3 (67.6 KB)
20250514_2123.emublog3 (2.3 MB)
I’ve put your project on simulator, and all works as expected. Knocking on cyl 3 set cyl 3 Knocking channel.
In your log it is something wrong.
Could you please make the following test ?
When the engine is running try to increase the knock sensor cylinder gain to simulate knocking on the specific cylinder and check in log what is going on.
I reviewed the code, run tests and everything seems to be good.
Hello, is there any plans or way to add capability to log data from MAF grams/sec in the V3 future update ?
OK. I will run the test.
As for how to do this, should I run it with the cylinder gain
raised?
The above log was logged with EDL-1, then loaded into V3 software and saved again. This is because the file size of the EDL-1 log data was too large to upload as is.
Will it be okay to use the same procedure next time?
Which setting is adopted as an alternative, or is there a way to allow this to be displayed in version 3.048?