Error enabling closed loop kpro v4 (PRA)

[Spunkster]

I actually think running in closed loop at WOT will be more dangerous as you could cause a catastrophic failure if your wideband goes out on you.

[DonMizzi]

Thanks for your reply, however Short term trim should avoid catastrophic failure. I will set +- 10% of trim.

I will continue with my questions:

1) Why, when my analog input is 5V, on KPro I measures 18.8 AFR ?? (it should be 19.0 AFR)
At 0V, the KPro measures 0 AFR properly.
The techedge configuration, that you have added in the 4.2.4, is properly configured?

2) In the tables "Closed Loop Max TPS" (high and low), I tried to set the last value at 2687 rpm, after that, the first value of the TPS (high) is changed from 99% to 58% automatically (value at 500 rpm)

I then tried to put again 99% (instead 58%) and as soon as I did, the last RPM value of the low table has gone to 8000.

Why some values seem to change automatically?
You tell me, please, how to set this table for a closed loop always active (also at WOT)?

Thanks
Don

[Spunkster]

Where are you connecting for power and ground for the wideband?

Right click on the table in question and select reset to default.

[DonMizzi]

For wideband controller source, I get power from stereo connector and ground directly from battery.

I measured always 5V using various GND (with tester) GND from controller, GND from ECU, GND from battery, GND of sensor ground

All give me 5V, so I can tell you that GND seems correct.

But on Kpro I log 18.8 AFR
Values should be 0V = 9, 5V = 19, with linear interpolation (AFR = 9 + V*2)

For "Closed Loop to Open Loop Switch - TPS Tables" I know how set default values.
But I would like to understand how it works (and if it works with external wideband and PRA)

As you can read in my last post, some value change automatically with each other.
Precisely TPS% of first column (low) and RPM of last column (high) are linked.

some example images, setting 7000, 5000 and 3000 rpm







Do you know why this happens?

Last 3 questions about this tables (that, I remember, hondata documentation write to set 100% to enable closed loop)

- When I set 100 TPS%, table write 99, when I set 50 TPS%, table write 49. Always value-1. Why?

- When I download a calibration and I'm online, blue selection is always on the first column, also if my car is at any RPMs



- Why TPS% is greater in low table then in high table, only in the first column (default values)?



A finaly note:
I make a lot of effort to try to make myself understood with English.
And from a distance it is even harder.
I also ask you kindly to try to answer my questions trying to understand what I write.

Thanks for help
regards
Don

[Spunkster]

Power should be from one of the switched fuse box connections for aux components. The ground should be the same one that the ECU uses, such as the on that needs to be relocated from the manifold to the valve cover.

Some values will change slightly when entered because the value in raw form, they do not always convert to whole numbers and it rounds them.

Unless you are datalogging it will not know what section of the table it is running off of.

These are default values and I cannot explain the reason an engineer did what they did originally.

[Spunkster]

Redownload the software again from the link you were emailed a few weeks ago. IT will be thee same version but should have todays date.

[DonMizzi]

Thanks for the new version, I have downloaded it
Can you tell me what has changed so I can check?
In my testing I did not see any obvious change (publish date is changed, 16 March)

- I confirm that the blue (current) selection in Open-Closedloop switch Rpm-TPS% table is always on the first column also with the engine running and recording active.
And also, some values change automatically, each other.
However, it is NO longer important to understand how this table works.
With everything at 99%, I can go in closedloop also at WOT


New question, this seems like a GREAT question:

I use an offset to get the wideband value of the external LED display (the one with the lowest error) equal to Analog0 signal.
For this I set an offset of -0.1 Volt for Analog0.
In the datalog, Analog0 value changes, but not the AF value.
Therefore, the correction of closedloop works on erroneous data, since it used AF, and not Analog0

I would say that the offset applies even to the AF signal (see attached image)
What do you say?



Thanks

[DonMizzi]

news?

[DonMizzi]

Excuse me, news for the offset not applied to the AF value?

Thanks

[Hondata]

The voltage offset is not applied to direct analog lambda inputs.

[DonMizzi]

Thanks for reply, I don't understand very well.

AF sensor is used to run closed loop.

If I change offset of my analog input (external wideband) changes only value of AN0.

So, offset don't have effect to closed loop operation, that's wrong, because my analog input is not correct (but needed offset)


NOTE: With PRA I have only external wideband, and AF sensor copies the value of the analog input (but without considering offset)

[DonMizzi]

Can you help me?

[Hondata]

We can change the KPro firmware to use the voltage offset, but this will take some time.