- Joined
- Apr 5, 2023
- Messages
- 19
- Gallery
- 6
- Reaction score
- 30
- Location
- Northern Arizona
- Current Ride
- 22 TRX lvl 2
- Current Ride #2
- 2018 Tes M3P
Hey all!!
I ran a quick search to see if anyone else had run across this and didn't get any results so I figured I would share what's going on with my 22 L2 TRX.
Couple of days ago I hopped in the truck and drove about 5 mi to a gas station, filled up the tank, and then drove another 2 mi to drop off some parts at my side by side mechanic. As I was backing into a parking spot, my truck stalled out. Thinking this was definitely strange, I put it in park, and restarted it. While the truck did fire back up, I noticed the instruments clicked off and on multiple times. I managed to get the truck backed into the parking spot, put it in park and went to shut it down, only for absolutely nothing to happen when I hit the start stop button. Everything stayed on, engine continued to run. Again, finding this a little unsettling and upsetting, I let it run while I ran in and dropped off my parts. I came back out and put it in drive and began to leave - again, the instrument cluster clicked off and on a handful of times but thankfully no stall. As I got to my first stop sign before hitting the highway, I got a message on the center screen "vehicle must be in park" (I figured at this point that meant the truck thought the start stop button was being pushed again). I got it all the way home, and as I went to park in my driveway I threw it in the park and hit the stop button in one very quick swoop, and fortunately the truck shut down. Instrument cluster again started clicking off and on as if I were pushing the button more than the single time.
I called my local dealer and got a service appointment set up for this week, and it has sat in my driveway since. Tonight I decided to tinker around a little, and tried remote starting it with my app; that failed. I then remembered I have one of those little Bluetooth ODB2 readers, so I threw it in, turned the ignition to acc, and ran a full diagnostic. I should also mention that I also had went into the menu on the truck and went to the diagnostic option only for it to tell me there was nothing stored or active. No CEL either. However, when I ran the full diagnostic through the ODBII reader, I did get one active code - a u1433-implausible ignition switch status, something about high stuck?
Read a few search results on Google, and as I expected it seems to be something to do with the ignition system. I will say that I live up in the mountains, filled with happy, furry, cute, and obnoxiously destructive squirrels and chipmunks
! My first thought went to potential rodent damage, as I have had that happen one other time with one of my three hood marker lights...(One of my 3 scoop lights had crapped out, ultimately thinking it was a bad LED had the dealer get the part in and during replacement they discovered the wire had been chewed up) We did install a "deterrent " flashing strobe LED in the engine bay after that, but I honestly don't know if that has completely worked on them or not.
Anyways, I have not tried starting the truck again since this began and my fingers are crossed that I can get it started tomorrow when I take it down to the stealership for diags. I'm REALLY hoping that it's actually something other than chewed wires so it will fall under warranty coverage.
Based on my search results, I don't think any of y'all have experienced this particular code / problem with yours, so hopefully this is something new for all of us to learn about!
Please keep your fingers crossed for me that it is a simple fix and not a multi-thousand dollar wire harness replacement!!! 


I ran a quick search to see if anyone else had run across this and didn't get any results so I figured I would share what's going on with my 22 L2 TRX.
Couple of days ago I hopped in the truck and drove about 5 mi to a gas station, filled up the tank, and then drove another 2 mi to drop off some parts at my side by side mechanic. As I was backing into a parking spot, my truck stalled out. Thinking this was definitely strange, I put it in park, and restarted it. While the truck did fire back up, I noticed the instruments clicked off and on multiple times. I managed to get the truck backed into the parking spot, put it in park and went to shut it down, only for absolutely nothing to happen when I hit the start stop button. Everything stayed on, engine continued to run. Again, finding this a little unsettling and upsetting, I let it run while I ran in and dropped off my parts. I came back out and put it in drive and began to leave - again, the instrument cluster clicked off and on a handful of times but thankfully no stall. As I got to my first stop sign before hitting the highway, I got a message on the center screen "vehicle must be in park" (I figured at this point that meant the truck thought the start stop button was being pushed again). I got it all the way home, and as I went to park in my driveway I threw it in the park and hit the stop button in one very quick swoop, and fortunately the truck shut down. Instrument cluster again started clicking off and on as if I were pushing the button more than the single time.
I called my local dealer and got a service appointment set up for this week, and it has sat in my driveway since. Tonight I decided to tinker around a little, and tried remote starting it with my app; that failed. I then remembered I have one of those little Bluetooth ODB2 readers, so I threw it in, turned the ignition to acc, and ran a full diagnostic. I should also mention that I also had went into the menu on the truck and went to the diagnostic option only for it to tell me there was nothing stored or active. No CEL either. However, when I ran the full diagnostic through the ODBII reader, I did get one active code - a u1433-implausible ignition switch status, something about high stuck?
Read a few search results on Google, and as I expected it seems to be something to do with the ignition system. I will say that I live up in the mountains, filled with happy, furry, cute, and obnoxiously destructive squirrels and chipmunks

Anyways, I have not tried starting the truck again since this began and my fingers are crossed that I can get it started tomorrow when I take it down to the stealership for diags. I'm REALLY hoping that it's actually something other than chewed wires so it will fall under warranty coverage.
Based on my search results, I don't think any of y'all have experienced this particular code / problem with yours, so hopefully this is something new for all of us to learn about!




