Cruise Control Headache (RTS) - Goes ON, but will not engage! Any ideas?

[BertRemington]

Based on your symptoms so far (was working, no change when flasher disconnected) the most likely cause is a sticking brake switch as noted above. The switch is an SPST N-O microswitch which provides +12V to both the ECM and the brake lights. The brake lights (and taillights) are LEDs so respond instantly to the +12V. Any flicker in the brake lights is also observed by the ECM. If the ECM has debounce logic I doubt it's longer than 50ms.

Best wishes.

 

[Old Prof]

Based on your symptoms so far (was working, no change when flasher disconnected) the most likely cause is a sticking brake switch as noted above. The switch is an SPST N-O microswitch which provides +12V to both the ECM and the brake lights. The brake lights (and taillights) are LEDs so respond instantly to the +12V. Any flicker in the brake lights is also observed by the ECM. If the ECM has debounce logic I doubt it's longer than 50ms.

Best wishes.

I appreciate your advice. "If the ECM has debounce logic I doubt it's longer than 50ms." Translation please. :dontknow:

 

[BertRemington]

The ECM is essentially a tailored computer operating at computer speeds performing among other tasks sampling its analog and digital inputs. The brake switch is a digital input operating at mechanical speeds. From the perspective of the ECM brake switch closure is multiple digital signals as the switch contacts bounce until the spring holds them permanently closed. To prevent false positives the ECM takes several samples over some mechanically realistic time period. I suggested 50ms but that's probably too short. I use 200ms in my switch closure detection processing.

WRT the switch spring since the switch is a microswitch the spring is the mechanical lever on the outside of the switch.

You asked an excellent question. Let me know if you have more.

 

[Jetfixer]

Does anyone have any troubleshooting suggestions for a 2014 RTL that will not allow the cruise control to engage? I'm working on a friends' bike. The cruise control will turn on and indicate "on" in the cluster. However, when I try to engage it by pressing the button down at speeds above 25, it will not engage. Watching the display, the "cruise on" indicator goes blank every time I try to engage it. It will stay blank if I hold the button down; then come back on when the button is release, but still no cruise control. According to the service manual there must be a fault in one or more of the modules, such as ECM, Cluster, VSS, TCM, etc. However, according to BUDS, this bike has absolutely no faults. Any suggestions will be appreciated.

 

[BertRemington]

JMK -- as you probably know the MSR CC buttons are wired to the MSL where they are converted to CANBUS messages. Maybe just maybe you have a problem with the contacts in the MSR.

 

[K80Shooter]

Also check the brake light switch for proper operation.

 

[Old Prof]

Thanks again for all the advice. Turns out it was a wiring issue. "Mr. Spyder", Reggy Tan found the issue and made the repair.

 

[Peter Aawen]

Thanks again for all the advice. Turns out it was a wiring issue. "Mr. Spyder", Reggy Tan found the issue and made the repair.

Jetfixer is now chasing the same problem - see post#24.

Do you have any detail for him on what that wiring issue actually was that might help him? Or a link to/contact details for "Mr. Spyder", Reggy Tan?? :dontknow:

 

[WRCLVR]

Old Prof, yes please, give us all the details of the wiring fix. The community needs things like this to be safer and be able to fix BRP's sloppy QC. Yah never know; if you report this to BRP, they might just actually insert a QC check into the assembly line, or at least put it on the check list for the dealer to look at during final assembly!

 

[Wingerdinger]

I had this happen when I tried to add a lighted license plate frame. It even put it in limp mode.