Preferred Method of EBC Tuning MS3 1.4.1
09-01-2017, 07:16 PM
#41
Finally got around to posting the PID logging function available in 1.5.3. I'm having to redo the clbc as I replaced my boost actuator. Just trying to handle it myself rather than bugging my tuner for it. My maps have solid fuel and timing higher than I am seeing on boost overshoot, and I have boost cut enabled, so I don't expect I'll break anything. It is still somewhat rough though. There are a couple more pulls past 118 sec. First time snipping one of these files.
You need to enable INTERNAL_LOG_FIELDS in your project properties, then you can add fields like these to your SDcard datalog. These are not available in regular datalogs.
pid_log_boost_p
pid_log_boost_i
pid_log_boost_d
pid_log_boost_count
Settings:
P=35
I=1
D=195
Slider=490
Lower Delta=30
Per the developers...
Note that these are in internal units which won't necessarily correspond to the externally visible units e.g. for idle the 0-100% scale is handled 0-255 internally. Viewing the "idle steps" field gives you 0-255. The "count" field increments each time the calculation is run, so log this as well.
You need to enable INTERNAL_LOG_FIELDS in your project properties, then you can add fields like these to your SDcard datalog. These are not available in regular datalogs.
pid_log_boost_p
pid_log_boost_i
pid_log_boost_d
pid_log_boost_count
Settings:
P=35
I=1
D=195
Slider=490
Lower Delta=30
Per the developers...
Note that these are in internal units which won't necessarily correspond to the externally visible units e.g. for idle the 0-100% scale is handled 0-255 internally. Viewing the "idle steps" field gives you 0-255. The "count" field increments each time the calculation is run, so log this as well.
Last edited by fwman1; 09-01-2017 at 07:21 PM. Reason: add comment
Reply
0
0
09-02-2017, 01:00 AM
#42
Retired Mech Design Engr
Thread Starter
iTrader: (3)
Join Date: Jan 2013
Location: Seneca, SC
Posts: 5,009
Total Cats: 857
Finally got around to posting the PID logging function available in 1.5.3. I'm having to redo the clbc as I replaced my boost actuator. Just trying to handle it myself rather than bugging my tuner for it. My maps have solid fuel and timing higher than I am seeing on boost overshoot, and I have boost cut enabled, so I don't expect I'll break anything. It is still somewhat rough though. There are a couple more pulls past 118 sec. First time snipping one of these files.
You need to enable INTERNAL_LOG_FIELDS in your project properties, then you can add fields like these to your SDcard datalog. These are not available in regular datalogs.
pid_log_boost_p
pid_log_boost_i
pid_log_boost_d
pid_log_boost_count
Settings:
P=35
I=1
D=195
Slider=490
Lower Delta=30
Per the developers...
Note that these are in internal units which won't necessarily correspond to the externally visible units e.g. for idle the 0-100% scale is handled 0-255 internally. Viewing the "idle steps" field gives you 0-255. The "count" field increments each time the calculation is run, so log this as well.
You need to enable INTERNAL_LOG_FIELDS in your project properties, then you can add fields like these to your SDcard datalog. These are not available in regular datalogs.
pid_log_boost_p
pid_log_boost_i
pid_log_boost_d
pid_log_boost_count
Settings:
P=35
I=1
D=195
Slider=490
Lower Delta=30
Per the developers...
Note that these are in internal units which won't necessarily correspond to the externally visible units e.g. for idle the 0-100% scale is handled 0-255 internally. Viewing the "idle steps" field gives you 0-255. The "count" field increments each time the calculation is run, so log this as well.
This is absolutely awful, by the way:
20 kPa oscillation with huge swings in duty cycle
Insufficient Integral to pull PV (boost) back to SP (Target)
Reply
0
0
09-02-2017, 12:52 PM
#43
Yep, it is awful. I haven't set up the bias table for 90 & 100% yet.
There is an Auburn football game today. Yesterday when I went out to work on these sections there was a State trooper literally in the turnaround I use on one end of the stretch of hwy I use. Didn't get anything done at all.
What I try to do is to have the bias set where the initial set once I'm in range be a value the is very close to that needed to maintain that target. I need to do some runs to establish those values.
I thought it would be good to finally show where you can watch the PIDs.
There is an Auburn football game today. Yesterday when I went out to work on these sections there was a State trooper literally in the turnaround I use on one end of the stretch of hwy I use. Didn't get anything done at all.
What I try to do is to have the bias set where the initial set once I'm in range be a value the is very close to that needed to maintain that target. I need to do some runs to establish those values.
I thought it would be good to finally show where you can watch the PIDs.
Reply
0
0
09-02-2017, 12:57 PM
#44
Retired Mech Design Engr
Thread Starter
iTrader: (3)
Join Date: Jan 2013
Location: Seneca, SC
Posts: 5,009
Total Cats: 857
And we appreciate the data. My point is that, I don't think your tuner utilized that data to obtain a good end. I had questioned the PID settings when you mentioned them before. Seeing the log only confirmed my suspicions that they are way off.
EDIT: go https://www.miataturbo.net/megasquir...3/#post1437218 to see the results of my very different settings. Not saying that my aggressive setttings would be appropriate for a larger (slower responding) Turbo, but they make more sense to me in general. P & I driving things with a sprinkling of D.
EDIT: go https://www.miataturbo.net/megasquir...3/#post1437218 to see the results of my very different settings. Not saying that my aggressive setttings would be appropriate for a larger (slower responding) Turbo, but they make more sense to me in general. P & I driving things with a sprinkling of D.
Last edited by DNMakinson; 09-02-2017 at 01:11 PM.
Reply
0
0
