PID logging idea

[elaw]

From time to time I've seen people ask here to have individual P/I/D values for things like idle and boost control logged. And I understand that's a lot of work for the coders and would take up a lot of space in a log.

But here's an idea: how about an option to log the PID values for any one control?

For example: reserve a byte in memory somewhere. If the value stored is 0, log no PID data. If it's 1, log PID for idle control only. If it's 2, log PID for boost control (only), and so on. Obviously then you'd expose that value in TS somehow so people could select what to log.

It wouldn't be any less work to write the code, but it would save log space.

[masterx81]

Maybe a screen like the tooth log, that show current signal, output of pid, and p i d components. Will help a lot tuning pid.

[lagos]

Maybe a screen like the tooth log, that show current signal, output of pid, and p i d components. Will help a lot tuning pid.

Id love to see something like that and was thinking of requesting it.

[hardline]

I also would like to see this

[Barton]

Maybe a screen like the tooth log, that show current signal, output of pid, and p i d components. Will help a lot tuning pid.

Id love to see something like that and was thinking of requesting it.

x2