Spyder power commander problem

[danielnor123]

I have a 2009 can am spyder with a power commander 5, two bros pipes on it and a kewl metal air filter, and when I ride I get up to about 60 mph and after I increase speed on the bike it will go into "hi temp", then finally it goes into "limp home mode", I pull over on the freeway turn off the bike for about 10 seconds and start the bike again and it is back to normal operating temperature.

I took the spyder to a mechanic we determined it was not the cooling system and not a blown head gasket.

So I purchased a new temperature sensor and a new oxygen sensor and replaced them, and no change.

So now I'm wondering if it is the power commander 5, I downloaded some maps but would like to either uninstall the power commander or tune the power commander.

I have no idea how to uninstall the power commander 5 or which map to use.

The maps I have downloaded are:
-power commander 5 (which shows the current setting on the power commander)
-stock exhaust/stock air filter
-two bros dual slip on stock air filter
-two bros single slip on green air filter
-two bros slip on green air filter
-two bros slip on stock air filter
-zero map

I watched a video on how to upload a map to the power commander 5 and it seems easy, but not sure which map to use.

OR

how do I disconnect the power commander 5 from the vehicle safely?

yesterday with the computer attached to the bike I started the bike with the power commander 5 and this is the reading I got:

RPM: 5026
% Throttle: 4
AFR: 0.00
Duty: 13%
Fuel: 10
Gear: 1
Speed: 0

 

[Snowbelt Spyder]

Just to clarify, were those readings taken at idle?

 

[danielnor123]

Just to clarify, were those readings taken at idle?

High idle yes

 

[Snowbelt Spyder]

Ok then. Let's focus on what we know. Normally the easiest and quickest way to neutralize a Power Commander is to install the Zero Map. Remember from the video, those differences between the Open, Get, Save, and Send Map commands. Those readings you see when you look at it on the computer with engine running are live data. And in your case there is clearly something wrong with the RPM value. I know your bike doesn't idle at 5000 RPM. At least it's not supposed to. The other thing we know or are pretty sure of is that your motor is not actually overheating. If it was, it couldn't cool down in just 10 seconds. That also seems to be an electronic issue.

So, since you didn't install the Power Commander, and don't know why it was installed, and it might be screwing something up electronically, if it was me I would begin by uninstalling it and see what issues that solves. You can download the installation instructions here....

http://www.powercommander.com/downloads/25-004/install/pcv/engI25-004.03.pdf

You could walk through the instructions from front to back and get familiar with what was done and see if it was done correctly. Then just go through them and restore everything to the stock configuration. Once you go through it, you'll find it's fairly easy. I just read through them and did notice a typo in step 11. It should say FRONT fuel injector, not REAR. You'll know what I mean when you go through it.

I don't think it's time to be concerned about maps yet, unless you want to try the Zero Map as a quick test. The false indications of high temperature needs to be solved first. If you want to follow up with me further, I'm happy to do it by PM if you'd rather take it off line. Let me know what happens.

 

[danielnor123]

Ok then. Let's focus on what we know. Normally the easiest and quickest way to neutralize a Power Commander is to install the Zero Map. Remember from the video, those differences between the Open, Get, Save, and Send Map commands. Those readings you see when you look at it on the computer with engine running are live data. And in your case there is clearly something wrong with the RPM value. I know your bike doesn't idle at 5000 RPM. At least it's not supposed to. The other thing we know or are pretty sure of is that your motor is not actually overheating. If it was, it couldn't cool down in just 10 seconds. That also seems to be an electronic issue.

So, since you didn't install the Power Commander, and don't know why it was installed, and it might be screwing something up electronically, if it was me I would begin by uninstalling it and see what issues that solves. You can download the installation instructions here....

http://www.powercommander.com/downloads/25-004/install/pcv/engI25-004.03.pdf

You could walk through the instructions from front to back and get familiar with what was done and see if it was done correctly. Then just go through them and restore everything to the stock configuration. Once you go through it, you'll find it's fairly easy. I just read through them and did notice a typo in step 11. It should say FRONT fuel injector, not REAR. You'll know what I mean when you go through it.

I don't think it's time to be concerned about maps yet, unless you want to try the Zero Map as a quick test. The false indications of high temperature needs to be solved first. If you want to follow up with me further, I'm happy to do it by PM if you'd rather take it off line. Let me know what happens.

New problem: rode the spyder today, noticed that the temp got hot once again went into hi temp then limp home mode, funny thing the radiator reservoir was not hot and the coolant in the radiator reservoir was not hot. I'd like to talk offline if you'd want (213) 841-1959, also found an error code of p1116

 

[trikermutha]

are you sure its not the thermostat that is stuck?

 

[danielnor123]

are you sure its not the thermostat that is stuck?

Thermostat has been removed

 

[PaladinLV]

Power Commander should not effect Engine Temp or cause a Limp Mode.

If you have questions you should call DynoJet at (702) 639-1157 ask for Chuck.

AJ

I have a 2009 can am spyder with a power commander 5, two bros pipes on it and a kewl metal air filter, and when I ride I get up to about 60 mph and after I increase speed on the bike it will go into "hi temp", then finally it goes into "limp home mode", I pull over on the freeway turn off the bike for about 10 seconds and start the bike again and it is back to normal operating temperature.

I took the spyder to a mechanic we determined it was not the cooling system and not a blown head gasket.

So I purchased a new temperature sensor and a new oxygen sensor and replaced them, and no change.

So now I'm wondering if it is the power commander 5, I downloaded some maps but would like to either uninstall the power commander or tune the power commander.

I have no idea how to uninstall the power commander 5 or which map to use.

The maps I have downloaded are:
-power commander 5 (which shows the current setting on the power commander)
-stock exhaust/stock air filter
-two bros dual slip on stock air filter
-two bros single slip on green air filter
-two bros slip on green air filter
-two bros slip on stock air filter
-zero map

I watched a video on how to upload a map to the power commander 5 and it seems easy, but not sure which map to use.

OR

how do I disconnect the power commander 5 from the vehicle safely?

yesterday with the computer attached to the bike I started the bike with the power commander 5 and this is the reading I got:

RPM: 5026
% Throttle: 4
AFR: 0.00
Duty: 13%
Fuel: 10
Gear: 1
Speed: 0

 

[danielnor123]

Spyder Overheating

Power Commander should not effect Engine Temp or cause a Limp Mode.

If you have questions you should call DynoJet at (702) 639-1157 ask for Chuck.

AJ

Just to state, I did goto can am dealer and had the codes read, below is what was seen on the codes, can anyone help me on this?


[TABLE="width: 667"]
[TR]
[TD][/TD]
[TD][TABLE="width: 667"]
[TR]
[TD]code
[/TD]
[TD]state
[/TD]
[TD]module
[/TD]
[TD]count
[/TD]
[TD]total time
[/TD]
[TD]description
[/TD]
[/TR]
[TR]
[TD]p0130
[/TD]
[TD]occurred
[/TD]
[TD]ECM
[/TD]
[TD]1
[/TD]
[TD]1070h55
[/TD]
[TD]02 Sensor circuit no activity detected
[/TD]
[/TR]
[TR]
[TD]p0170
[/TD]
[TD]occurred
[/TD]
[TD]ECM
[/TD]
[TD]255
[/TD]
[TD]1070h55
[/TD]
[TD]Lambda regulation high limit
[/TD]
[/TR]
[TR]
[TD]p0170
[/TD]
[TD]occurred
[/TD]
[TD]ECM
[/TD]
[TD]3
[/TD]
[TD]1070h55
[/TD]
[TD]Lambda regulation: temporary adaptation +/- %
[/TD]
[/TR]
[TR]
[TD]p0600
[/TD]
[TD]occurred
[/TD]
[TD]ECM
[/TD]
[TD]11
[/TD]
[TD]1070h55
[/TD]
[TD]Communication fault with VCM, no response
[/TD]
[/TR]
[TR]
[TD]p0600
[/TD]
[TD]occurred
[/TD]
[TD]ECM
[/TD]
[TD]1
[/TD]
[TD]1070h55
[/TD]
[TD]Communication fault with Cluster, no response
[/TD]
[/TR]
[TR]
[TD]p2545
[/TD]
[TD]occurred
[/TD]
[TD]ECM
[/TD]
[TD]5
[/TD]
[TD]1070h55
[/TD]
[TD]VSS Failure
[/TD]
[/TR]
[TR]
[TD]p2545
[/TD]
[TD]occurred
[/TD]
[TD]ECM
[/TD]
[TD]5
[/TD]
[TD]1070h55
[/TD]
[TD]VSS light on
[/TD]
[/TR]
[TR]
[TD]?0122
[/TD]
[TD]occurred
[/TD]
[TD]DPS
[/TD]
[TD]N/A
[/TD]
[TD]
[/TD]
[TD]N/A VCM Communication Fault
[/TD]
[/TR]
[TR]
[TD]C0061
[/TD]
[TD]occurred
[/TD]
[TD]VCM
[/TD]
[TD]1
[/TD]
[TD]
[/TD]
[TD]N/A Lateral Acceleration Sensor Failure
[/TD]
[/TR]
[TR]
[TD]P1116
[/TD]
[TD]occurred
[/TD]
[TD]ECM
[/TD]
[TD]123
[/TD]
[TD]1070h55
[/TD]
[TD]Engine Overheat
[/TD]
[/TR]
[TR]
[TD]
[/TD]
[TD]
[/TD]
[TD]
[/TD]
[TD]
[/TD]
[TD]
[/TD]
[TD]*codes occurred and are not active
[/TD]
[/TR]
[/TABLE]
[/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[/TABLE]

 

[trikermutha]

If you think it is the power commander unplug it and plug the stock connector back into the ECM. See if that solves the issue.

 

[danielnor123]

Spyder Overheating

No I don't think it is the power commander, in fact I found a wonderful app on android that lists all the problems associated with the codes:

[TABLE="width: 616"]
[TR]
[TD="width: 57"]

code​

[/TD]
[TD="width: 71"]

state​

[/TD]
[TD="width: 61"]

module​

[/TD]
[TD="width: 47"]

count​

[/TD]
[TD="width: 75"]

total time​

[/TD]
[TD="width: 305"]

description​

[/TD]
[/TR]
[TR]
[TD="width: 57"]p0130
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]ECM
[/TD]
[TD="width: 47"]1
[/TD]
[TD="width: 75"]1070h55
[/TD]
[TD="width: 305"]02 Sensor circuit no activity detected
[/TD]
[/TR]
[TR]
[TD="width: 57"]p0170
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]ECM
[/TD]
[TD="width: 47"]255
[/TD]
[TD="width: 75"]1070h55
[/TD]
[TD="width: 305"]Lambda regulation high limit
[/TD]
[/TR]
[TR]
[TD="width: 57"]p0170
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]ECM
[/TD]
[TD="width: 47"]3
[/TD]
[TD="width: 75"]1070h55
[/TD]
[TD="width: 305"]Lambda regulation: temporary adaptation +/- %
[/TD]
[/TR]
[TR]
[TD="width: 57"]p0600
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]ECM
[/TD]
[TD="width: 47"]11
[/TD]
[TD="width: 75"]1070h55
[/TD]
[TD="width: 305"]Communication fault with VCM, no response
[/TD]
[/TR]
[TR]
[TD="width: 57"]p0600
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]ECM
[/TD]
[TD="width: 47"]1
[/TD]
[TD="width: 75"]1070h55
[/TD]
[TD="width: 305"]Communication fault with Cluster, no response
[/TD]
[/TR]
[TR]
[TD="width: 57"]p2545
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]ECM
[/TD]
[TD="width: 47"]5
[/TD]
[TD="width: 75"]1070h55
[/TD]
[TD="width: 305"]VSS Failure
[/TD]
[/TR]
[TR]
[TD="width: 57"]p2545
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]ECM
[/TD]
[TD="width: 47"]5
[/TD]
[TD="width: 75"]1070h55
[/TD]
[TD="width: 305"]VSS light on
[/TD]
[/TR]
[TR]
[TD="width: 57"]p0122
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]DPS
[/TD]
[TD="width: 47"]N/A
[/TD]
[TD="width: 75"]
[/TD]
[TD="width: 305"]N/A VCM Communication Fault
[/TD]
[/TR]
[TR]
[TD="width: 57"]C0061
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]VCM
[/TD]
[TD="width: 47"]1
[/TD]
[TD="width: 75"]
[/TD]
[TD="width: 305"]N/A Lateral Acceleration Sensor Failure
[/TD]
[/TR]
[TR]
[TD="width: 57"]P1116
[/TD]
[TD="width: 71"]occurred
[/TD]
[TD="width: 61"]ECM
[/TD]
[TD="width: 47"]123
[/TD]
[TD="width: 75"]1070h55
[/TD]
[TD="width: 305"]Engine Overheat
[/TD]
[/TR]
[TR]
[TD="width: 57"]
[/TD]
[TD="width: 71"]
[/TD]
[TD="width: 61"]
[/TD]
[TD="width: 47"]
[/TD]
[TD="width: 75"]
[/TD]
[TD="width: 305"]*codes occurred and are not active
[/TD]
[/TR]
[/TABLE]

P0130 module:ECM ​

​

​

---

​

​

​

LAMDA sensor #1 upstream cat.

Damaged O[SUB]2[/SUB] sensor wires

connector ECM output pins.

Check fuse

Disconnect HO[SUB]2[/SUB]S 1

Measure voltage between harness connector HO[SUB]2[/SUB]S 1-1 & ground
(expected value 11-13 V[SUB]DC[/SUB])

Measure resistance between HO[SUB]2[/SUB]S 1 pin 1 & 3
(expected value=14 to 15 Ω)

Disconnect ECM B Measure resistance between harness connector HO[SUB]2[/SUB]S 1-3 & ground
(expected value >Open)

Measure resistance from harness connector: HO[SUB]2[/SUB]S 1-3 to ECM B-L2
(expected value: <2 Ω)

---

​

​

​

The following terms were used in the code explanation.
(pinch gesture to expand)

ACRONYM​	TERM​
ECM	Engine Control Module	One of the computers that talks to the(vehicle stability system) lives.

[TD="colspan: 3"]

TERMS USED IN P0130​

[/TD]

P0170 module:RS/GS​

​

​

---

​

​

​

Lambda regulation low limit.

Fuel supply problem or air supply problem or mechanical issue on admission parts or exhaust leakage.

Verify fuel pressure verify injectors verify air box throttle body intake manifold and exhaust system.

---

​

​

​

ACRONYM​	TERM ​

[TD="colspan: 3"]

TERMS USED IN P0170​

[/TD]

P2545 module:RS/GS​

​

​

---

​

​

​

VSS failure

VSS light on VSS CAN message missing

Check VCM fault

Measure between harness connector (9-VCM-28 for 46 pins or VCM-32 for 38 pins) and ground (expected value: = 11 to 13 volts). Disconnect MI-IL from DLC connector. Measure resistance between 1-DLC-1 and 1-DLC-2 {expected value 50 to 70 Ω). Measure resistance between 1-DLC-1 and (9-VCM-35 for 46 pins or VCM-37 for 38 pins) (expected value: < 2 Ω). Measure resistance between 1-DLC-2 and (9-VCM-14 for 46 pins orVCM-24 for 38 pins) (expected value: < 2 Ω).

---

​

​

​

The following terms were used in the code explanation.
(pinch gesture to expand)

ACRONYM​	TERM​
DLC	Data Link Connector	The connector in the front that BUDS uses to communicate.
VCM	Vehicle Control Module	This mechanical/electronic beauty is the heart of the VSS.
VSS	Vehicle Stability System	The overarching system that helps keep all 3 Spyder wheels on the ground.

[TD="colspan: 3"]

TERMS USED IN P2545​

[/TD]

P1116 module:RS/GS​

​

​

​

​

​

---

​

​

​

Engine overheat


Damaged coolant circuit or thermostat or low coolant level Check coolant level add if needed

Check radiator and coolant circuit

Disconnect CTS

Measure CTS resistance value (expected value: 2280 to 2736 Ω at 19 to L1°C (66 to 70°F}). Measure resistance from connector: 5-ECM-A11 to 5-CTS-1 (expected value: < 2 Ω). Measure res1stance from connector: 5-ECM-A27 to 5-CTS-2 (expected value: < 2 Ω).

​

​

​

---

​

​

​

The following terms were used in the code explanation.
(pinch gesture to expand)

ACRONYM​	TERM​
CTS	Coolant Temperature Sensor	Provides coolant temp data to the ECM
ECM	Engine Control Module	One of the computers that talks to the(vehicle stability system) lives.

[TD="colspan: 3"]

TERMS USED IN P1116​

[/TD]

.

C0061 module:VCM​

​

​

---

​

​

​

Lateral acceleration sensor failure.

Defective lateral acceleration sensor Internal offset fault of he sensor.

Measure voltage between harness connector YRS-4 & GND with ignition on
(expected value=12 V[SUB]DC[/SUB]).

Measure voltage between harness connector YRS-1 & GND with ignition on
(expected value=0 V.
(B.U.D.S.)

---

​

​

​

The following terms were used in the code explanation.
(pinch gesture to expand)

ACRONYM​	TERM​
B.U.D.S.	BRP Universal Diagnostic Software	BRP Dealers have access to this sophisticated software. Some repairs cannot be done without it.
GND	Electrical Ground	'This is the Frame Ground. The negative terminal of the battery
VCM	Vehicle Control Module	This mechanical/electronic beauty is the heart of the VSS.
YRS	Yaw Rate Sensor	sensor that senses where in space your Spyder is heading.

[TD="colspan: 3"]

TERMS USED IN C0061​

[/TD]

P0122 module:ECM ​

​

​

---

​

​

​

First TAS shorted to GND.

Damaged: TAS sensor wires shorted to ground.

Make sure sensor connector is fully inserted

Measure resistance from connector:ECM A-K1 to TAS-A
(expected value <2 Ω)
Measure resistance from connector:ECM A-K3 to TAS-B
(expected value <2 Ω)

Measure resistance from connector:ECM A-E1 to TAS-C
(expected value <2 Ω)

---

​

​

​

The following terms were used in the code explanation.
(pinch gesture to expand)

ACRONYM​	TERM​
ECM	Engine Control Module	One of the computers that talks to the(vehicle stability system) lives.
GND	Electrical Ground	'This is the Frame Ground. The negative terminal of the battery
TAS	Throttle Acceleration Sensor	' Mounted on the handlebars and determines what you you want the Spyder''s engine to do.'

[TD="colspan: 3"]

TERMS USED IN P0122​

[/TD]

 

[Snowbelt Spyder]

There's a lot going on with this bike, so I think you need to do some things to wade throughout the weeds.

About the Power Commander: Since it is the oddball thing that was installed on the bike, you've been focusing on that pretty much all along, but it may not have anything to do with anything. But I think it should be eliminated as a question, then you won't have to guess anymore. Just return the connectors to the stock configuration using the instructions. It should only take an hour and then you'll know. Take your time, you'll be fine.

About the thermostat: Removing the thermostat on the V-Twin Spyder motor does NOT maximize cooling. Please people stop doing that. It doesn't work that way. It's not an old car. The thermostat is more like a 3-way mixing valve than an open-closed valve. Removing it could just as well make matters worse. So, your cooling system needs to be returned to a stock configuration, too. Put a thermostat in it, flush it while you're there, make sure the fan cycles properly on temperature and make sure it blows air the proper direction - which is to the rear.

About the codes: All those codes are shown as "occurred". Once a code has occurred, it is stored in memory on the bike - forever - until that code history is cleared by the dealer using BUDS. So really, except for the P1116 code, you don't know how old those other codes are, unless you know when the last time the occurred list was cleared. In order to make any conclusions from occurred codes, you should have a dealer clear the list and then keep track of codes as they happen. So yeah, as was stated in your other post, those codes could all be related to an old battery issue and unrelated to this at all, so I wouldn't put too much stock in this at this time.

So to summarize, my recommendation is to disconnect the Power Commander, restore the cooling system to stock and test it, and ignore the code list for now until you get it cleared. I think your problem is solvable, but there's no magic bullet. It's going to take a little work. After the overheating issue is solved, then you can work on the Power Commander thing again.