Was this limp mode?

[phmichel]

2017 Quest 105k miles. Had the valve body replaced about 15k ago due to the F1 (not F0) code. Been running fine EXCEPT today. We were in a drive thru just idling and it suddenly would barely move. Half throttle and it started rolling. Went about 100' then shut it off for about 60 seconds. No CVT codes present. Ran normal after a restart then went on a 200 mile trip. It did run about 5-10 degrees hotter than usual on the freeway per CVTz50. Any ideas? Man, I hope this thing is not failing.

[VStar650CL]

Go to "Information" in CVTz50 and see what it says for CVT-A/CVT-B. If the transmission went into turtle mode for self-protection then both of them will be non-zero. If they're both zero then something else caused it, maybe a bug in the MAF that dislodged when you shut it down.

[phmichel]

Go to "Information" in CVTz50 and see what it says for CVT-A/CVT-B. If the transmission went into turtle mode for self-protection then both of them will be non-zero. If they're both zero then something else caused it, maybe a bug in the MAF that dislodged when you shut it down.

It says:
5 Past/Inactive DTC:
No Data
CVT-A:0
CVT-B:1
What do you think?

[VStar650CL]

IIRC, CVT-B is around 220F and will definitely turtle the transmission. It's a little weird because I think it should have set a CVT-A as well, but that may be something different in the Quest firmware. Either way, it definitely did overheat.

[phmichel]

IIRC, CVT-B is around 220F and will definitely turtle the transmission. It's a little weird because I think it should have set a CVT-A as well, but that may be something different in the Quest firmware. Either way, it definitely did overheat.

Hmmm - then something is really screwy because I had CVTz50 on for our 200 mile trip up and it never went over 174 according to the temp gauge. The morning it hit limp mode we drove about 15 miles at 50 (no hills), then idled at the drive through as mentioned above, then shut it down, restarted and went on our way. On the 200 mile return trip It hit 185 because we were stuck in stop and go traffic for about an hour.

Now I'm wondering if the valve body was not programmed correctly when replaced? I did notice the TC lockup can be pretty rough (clunky) sometimes.

[VStar650CL]

Did you have the VB replaced at a dealer or an independent? If the dealer did it then the IP Char data should have been loaded in and the TCM should have been reprogrammed to clear CVT-A/CVT-B plus any "permanent" DTC's like P17Fx codes. If the former wasn't done then some clunky shifting can be expected, and if the latter wasn't done then that CVT-B may be a hangover from your bad old days. That would bring us back to a probable MAF bug for your present issue, but if that's the case, you really should at least get the IP's done. Running with incorrect solenoid curves may not cause immediate harm, but it isn't long-term healthy.

[phmichel]

Did you have the VB replaced at a dealer or an independent? If the dealer did it then the IP Char data should have been loaded in and the TCM should have been reprogrammed to clear CVT-A/CVT-B plus any "permanent" DTC's like P17Fx codes. If the former wasn't done then some clunky shifting can be expected, and if the latter wasn't done then that CVT-B may be a hangover from your bad old days. That would bring us back to a probable MAF bug for your present issue, but if that's the case, you really should at least get the IP's done. Running with incorrect solenoid curves may not cause immediate harm, but it isn't long-term healthy.

Independent shop. I went over the process with them in detail and they have a reputable history with CVT's and Nissan's in particular. The P17F1 was cleared for sure. I'm still under warranty so I'll go and talk to him. Thanks VStar - I appreciate it as always...