Normal mode skip shift elimination-PCMtec

[Robottrainer]

If one wanted to eliminate the skip shift in normal mode on the 10R80 with PCMtec, would it be as simple as setting the rpm to 10000 on each skip shift column in table AuF67261? Asking for a friend.

Sponsored

 

[K4fxd]

would it be as simple as setting the rpm to 10000 on each skip shift column in table AuF67261? Asking for a friend.

That is what it looks like. Won't hurt anything to try it. Looks like it is factory set to skip shift at low throttle input

 

[engineermike]

Yes and no. That must be done as the first step to eliminate skip shifting. However, you have to confirm and fix the 2-3 and 3-4 shift points where they had locked them out as well. Areas needing attention are circled below:

Personally, in my car I messed with mine for a while trying to get it to drive good, then eventually just stole a stock map from a 2022 and like it much better. It still skips 1-2 but it works fine IMO. I know someone else who stoke a DarkHorse shift map and put it in is 2019 and he loves it. He also nabbed the coastdown and downshift maps as well, because they all work together.

 

[Robottrainer]

Is that the same 67261 table?

 

[K4fxd]

Yes, but the OS I have opened does not have the additional lock out.

 

[engineermike]

Is that the same 67261 table?

I just opened one of the 4 Roush osid’s matching yours. It’s the base upshift table but
Might be a little different due to Roush updates.

 

[Robottrainer]

Yes, but the OS I have opened does not have the additional lock out.

I dont think mine is locked. These are 2021 values

 

[Robottrainer]

I dont think mine is locked. These are 2021 values

I'd assume you change all the skip columns to 10000

 

[K4fxd]

Yours has the additional lock outs. Change the skips to 10000 and then interpolate where Mike has circled in his post.

 

[K4fxd]

Make your table look like this

 

[engineermike]

That's a good start. I almost always past this table into excel to graph and problem areas jump out at you when you use a line chart. I don't mean to pick nits, but the circled areas will cause some minor issues. The red ones trigger a shift to a gear that it will immediately shift out of, so in effect it will still skip-shift. You could lower them but then the spacing between shifts will be wonky (2-3 and 3-4 only 50 rpm apart). Again, plotting them in excel makes these issues easier to see and edit. The yellow part shows a decrease in shift rpm as pedal increases, so it should be changed to make it a constant increase.

Some time back I resolved a bizarre issue with the Roush F150 OS where the downshift 100% pedal row, and only that row, was somehow affecting/corrupting the entire associated column. That took me forever to figure out. I was able to resolve it by simply putting 0's in the 100% row and then suddenly the table worked fine. My buddy, who is a hex wiz, figures there's some sort of table call address error in the logic. PCMTec suggested I let Roush know, which I declined. Can you imagine how that phone call would have gone?

 

[Robottrainer]

Interpolate? Not sure how that's done.

 

[engineermike]

@Robottrainer if you want, post your full OSID and I'll take a shot at a good table.

 

[K4fxd]

That's a good start.

I just copied what Ford had in a tune. I figured he would fine tune after he drove it a bit.

The yellow part shows a decrease in shift rpm as pedal increases,

Ford does that in a lot of the auto tunes.

 

[Robottrainer]

@Robottrainer if you want, post your full OSID and I'll take a shot at a good table.

Thanks! At this point I'm happy with what I have done. It's more out of curiosity that I ask. I had to go back and zero out other columns as track mode was doing the same crazy stuff. One thing I noticed on PCMtec is I'm seeing some notices in yellow when I open any of my files including the original untouched files. Binary error. It's references tables I didn't even look at or touch. I wonder if I just didn't notice before.

Sponsored