PCMtec Shift characteristics-Which one is Track Mode?

[Robottrainer]

So I understand Base is normal. Sport is sport. Drag is apparently Sand. There is a snow mode so I assume snow is snow. I'm also assuming mud is Track. There is definitely a difference when switching from 0, to Alt1 to Alt 2. What makes me wonder is that in Track mode, it wont downshift to 1st from second until you are practically not moving, which I assume again one would see 0 in the downshift shift schedule for mud at zero throttle percent. Im seeing to first at 220 rpm and to second at 0 rpm at 0 percent throttle. Makes me think it isnt mud mode. Anyone have any insight?

Sponsored

 

[Robottrainer]

So I understand Base is normal. Sport is sport. Drag is apparently Sand. There is a snow mode so I assume snow is snow. I'm also assuming mud is Track. There is definitely a difference when switching from 0, to Alt1 to Alt 2. What makes me wonder is that in Track mode, it wont downshift to 1st from second until you are practically not moving, which I assume again one would see 0 in the downshift shift schedule for mud at zero throttle percent. Im seeing to first at 220 rpm and to second at 0 rpm at 0 percent throttle. Makes me think it isnt mud mode. Anyone have any insight?

Or is coast down the more appropriate table.

 

[engineermike]

I've run across similar issues myself. The shift table axis labelling is actually native, not really a characteristic of PCMTech, if that makes sense.

I learned that snow mode does not equal winter mode in the truck. Snow mode is either mud or grass; still not sure which.

I would suggest this.....
1. Zero out the coastdown table
2. Zero out the downshift table
3. Populate the upshift table with different shift points for every mode, like make 1-2 at 1000 rpm in base, 2000 rpm in sport, 3000 in mud, 4000 rpm in sand, etc.
4. Flash the file and drive it.
5. Record which drive mode results in what shift rpm.
6. Use the data to decode the drive mode relationships.

I've been doing this sort of thing for a while and, while it may seem like unnecessary flashing, it will wind up being the fastest way to figure it out. I've created dozens of "test" files just to figure things like this out.

 

[Robottrainer]

I've run across similar issues myself. The shift table axis labelling is actually native, not really a characteristic of PCMTech, if that makes sense.

I learned that snow mode does not equal winter mode in the truck. Snow mode is either mud or grass; still not sure which.

I would suggest this.....
1. Zero out the coastdown table
2. Zero out the downshift table
3. Populate the upshift table with different shift points for every mode, like make 1-2 at 1000 rpm in base, 2000 rpm in sport, 3000 in mud, 4000 rpm in sand, etc.
4. Flash the file and drive it.
5. Record which drive mode results in what shift rpm.
6. Use the data to decode the drive mode relationships.

I've been doing this sort of thing for a while and, while it may seem like unnecessary flashing, it will wind up being the fastest way to figure it out. I've created dozens of "test" files just to figure things like this out.

My one clue about mud was when I set the shift characteristics for sport to 0 and left mud at 1, the flare was gone on sport but not track. I then changed mud to 0 and the flare was gone.

I did the same with the ALT 2 setting in mud. Track shifted like sport mode did when I set it to ALT2, without the shutter from 2-3. Fast and firm, higher shift points, but not harsh. I wish I could figure out what makes it that why and apply it to Sport with ALT2. I left mud set to 2.

 

[Robottrainer]

My one clue about mud was when I set the shift characteristics for sport to 0 and left mud at 1, the flare was gone on sport but not track. I then changed mud to 0 and the flare was gone.

I did the same with the ALT 2 setting in mud. Track shifted like sport mode did when I set it to ALT2, without the shutter from 2-3. Fast and firm, higher shift points, but not harsh. I wish I could figure out what makes it that why and apply it to Sport with ALT2. I left mud set to 2.

More clues and conclusive proof that Mud is in fact Track. So I got a chance to try all the modes yesterday with sport/+ set to Alt 0 characteristics. Set track(mud) to Alt 2 and left drag as is.

The shift feel in Alt 2 in Track is perfect. Firm quick and not abrupt or harsh. Alt 2 isn't as well behaved in sport mode. A bit harsh in the 2 to 3 and 3 to 4 shift. The only problem with Track is the shift points are higher, and the down shifts slower. Soo...

I copied the sport shift tables (coast, down, shift and upshit) into mud(track). Track is now spectacular. And I get track exhaust and stiffer magnaride. It's like super sport plus.

Question...sport, track have their own converter lock/unlock settings. Any issue leaving them as is. Car has never felt this good.

 

[engineermike]

I believe the tcc slip and unlock speeds are essentially independent of the other transmission parameters. I make lots of cjanges there, some drastic, and never seen ill effect.

 

[Robottrainer]

I believe the tcc slip and unlock speeds are essentially independent of the other transmission parameters. I make lots of cjanges there, some drastic, and never seen ill effect.

Since it works to my satisfaction now, I will leave it. Thanks for all your help. I have better understanding of what goes on in there.

 

[Rolls]

We have down our best to name columns/axis where possible, You should now see 2->1 3->1 etc in the axis opposed to 1,2,3 especially in the more common tables as seen below here. Most of the naming is based around the Mustang world, in the truck world some of these schedules are actually different as mentioned above, it also changes in different countries that don't have snow etc. However you'll find typically it's always the something similar eg snow/mud/sand etc are all going to have a loose converter and want to shift early.

Something that may assist you is the DMRX/DMRY descriptions that are listed in the table itself, these are available for many tables that have global loggable values.

Eg datalog MID77918 and you'll see what gear is desired.

Datalog MID77499 and you'll get the Y axis value. You can then map trace these back over the table to see exactly what happened.

Here is a video explaining map tracing. No pasting columns or guessing what to log, its fully automatic providing you've datalogged the values.

 

[Rolls]

Everyone our 25% workshop discount will be ending tomorrow, get it in quick if you missed out!

This is for the global workshop package and any upgrades to the full global workshop package.

https://www.pcmtec.com/american-market

Sponsored