Ya PCM tec makes it look like you can go past 20 but I tried and anything past 20 won't appear.Excuse me it should be 20 total cells. 0-19, 0 being one of the available cells.
Pretty typical tuning software stuff.Ya PCM tec makes it look like you can go past 20 but I tried and anything past 20 won't appear.
![]()
This for example won't show any values past 6750. So I can't expand the table but I can rescale it for higher rpm values
I wonder why there software shows that you can expand this particular table but then won't actually let you do it.Pretty typical tuning software stuff.
I think HPT has made custom OS for other cars that expanded the tables axis. Im sure if some how 20 cells was not enough, PCMtech could expanded it. 20 cells should be more than enough.
Im sure PCMtech could expand it, but why would they when its not needed.
8000 is a good value for a 18+ manifold and cams. You have a lot of scaling to do to have a calibration that fully covers up to 8000 for everything. There is a lot thats goes behind properly scaling not just changing the axis values. You don't want to inadvertently change table values for the given axis values. This is very important when scaling as many new tuners unknowningly cause major changes to values and get into dangerous operating conditions.I wonder why there software shows that you can expand this particular table but then won't actually let you do it.
What do you think I should scale it to? I currently plan to rev to ~8000. Will have to see what the car runs faster on but from previous testing I know it likes to rev high.
Also what MP do you think I should test the SD correction on? Im planning on going out and getting some data and try to do the math like you showed to correct. I would prefer to do a point that is decent for driveability to start with.
Car seems to like MP20 but It doesn't have a corresponding imrc closed point. Should I just lock imrc open?
I think even when imrc was open with MP17 it was still slow but I’ll try locking it open and commanding and see what happens8000 is a good value for a 18+ manifold and cams. You have a lot of scaling to do to have a calibration that fully covers up to 8000 for everything. There is a lot thats goes behind properly scaling not just changing the axis values. You don't want to inadvertently change table values for the given axis values. This is very important when scaling as many new tuners unknowningly cause major changes to values and get into dangerous operating conditions.
I know why you started at MP5 as the stock distance tables puts you at this MP pretty much right off idle and its a good place to start with what is in a base file. Just commanding distance 5 may be too limiting as IMRC is commanded to be closed even at high torque/ load demands. Its not til distances 6-9 that the IMRC opens at lower loads. Try commanding MP 17 which is MP 5/ distance 5 but with the IMRC commanded open. You do this by lowering the desired percentage load values at distance 5 in the best FE and best drive open/close tables. If this allows your load to get higher than .45-5 in those low RPM ranges then you know its not your cams but the IMRC remaining closed thats causing that MP to feel weak. You would need to adjust the IMRC open and close tables for what you determine best suits fuel economy and drivability modes. If load is still limited then you know its the cam positions and you may consider just not commanding those angles.
![]()
This was the only spot I saw MP5 to 17 transition with IMRC opening. MAF, load, torque did not change from the event, so I don't think this was commanded open and it was more the vacuum, or lack of vacuum just allowing the IMRC to open. I Just want to confirm that and this wasn't a commanded open and nothing changed from them opening because the throttle was still in control of airflow.I think even when imrc was open with MP17 it was still slow but I’ll try locking it open and commanding and see what happens
I just started playing with commanding shifts from what I understand it is based on the OSS table and an rpm table and it will shift at whichever comes first?Then set the desired shift RPM in the OSS tables, making sure your engines RPM limits are a fare bit above the shift points as to not interfere with the shift trying to limit engine RPM.
Thats basically it.
6R80s are slow shifting, compared to modern day standards, but they are still near 350-400ms shifts and can be full power on shifts that feel great.
So you think once I get SD and the torque model better the shifts will be more accurate?You need to get this part right and not skip it. WOT shifting when this is not right is not good, you could get slipping from pressures too low or dragging from pressures that are too high. Not being able to command a shift via the OSS table is a bad sign. All shifts are done with this table, WOT shouldn't have to be done differently.
"Trans TV Pressure Slope - Non Shifting: This is the Slope value for TV Pressure per Ft. Lbs. of Torque the engine is producing. When not shifting, TV Pressure is calculated by taking the current torque and multiplying against the slope and adding the intercept value. When shifting, the TV Pressure tables for the shift is added.
What this basically says is tune the engine brake torque value the ECU thinks the engine is making to an accurate value and the pressures in the transmission will increase, but also remain accurate and not be too high. Engine torque tuning is the most important thing to do. "
Shift are anticipated.So you think once I get SD and the torque model better the shifts will be more accurate?
Is the OSS shifting commanding the shift when it hits the target OSS or is it commanding sooner to try and target the shift at the OSS?
Here is a log and here is what my OSS shift table was set to
![]()