Problem with Launch Control on new version 1.2.3.5

Lewis40044004 · Post by **Lewis40044004** » Wed May 14, 2008 5:41 pm

Hey guys, I got an issue with the launch control on the new version, it doesnt engage at all. I posted this on clubrsx and put the switch to Always on with the full throttle shift off but i still cant get it to work like in the older version. I tried to set the speed limit higher thinking it would help but its not working at all. I got the Launch Control checked, 4200 Rpm launch limiter, and the switch imput to Always on, Still not working. Any ideas? I dont wanna keep running the 1.2.3.3..

Bflaker · Post by **Bflaker** » Fri May 16, 2008 4:50 am

Can you post a screen shot of your settings?

1. Press the Prt Scr button on your keyboard.
2. Go to the Paint Program and click paste.
3. Save the file.
4. Host it on photobucket.com
5. Post the IMG code in the reply area and click submit.

Post by **Spunkster** » Fri May 16, 2008 9:31 am

don't post screen shots. Post datalogs and calibrations

LK7R · Post by **LK7R** » Fri May 16, 2008 10:04 am

Same problem here.

Civic Type R (EUR)
K20A2
PRA ECU
Innovate LC-1 WB on ELD pin

roboticfailure · Post by **roboticfailure** » Sun May 18, 2008 7:04 pm

I have the exact same problem, please if anyone knows I hondata has adressed this issue let me know.

Bflaker · Post by **Bflaker** » Sun May 18, 2008 7:51 pm

It's odd that so many people are having trouble, yet mine is working fine. I noticed one of the poeple have a Civic Type-R. What are the details for everyone else that is having this problem?

HONDA GHANDI · Post by **HONDA GHANDI** » Fri May 23, 2008 6:52 am

Works fine in my Element, and in one customer car (EG with K20a3). Does not work at all in other customer car (EG with K20Z1). I didnt have time to mess around with it yesterday to see what the deal was, so I dont have a datalog of the situation. VSS reads 0mph on the sensor screen and I have the settings to: Switch: always on Transition MPH: 2mph. Hope this helps. Here is the KAl for the non working unit.

dc5_559 · Post by **dc5_559** » Fri May 23, 2008 1:58 pm

I have the same problem.
K20Z1

talonxracer · Post by **talonxracer** » Sat May 24, 2008 6:18 am

I have the same issue and I know of at least 4 others with the same issue, all are K20A2's with 1.2.3.5 installed in Kpro. The launch limiter worked up untill this version.

HONDA GHANDI · Post by **HONDA GHANDI** » Sat May 24, 2008 7:46 am

I might see my customer with the issue this weekend. If so I will grab some info off his ECU and a quick datalog of the problem to post up so we can find a solution.

Lewis40044004 · Post by **Lewis40044004** » Sun May 25, 2008 5:59 pm

Well its still not working.. I dont think the calibration has something to do with it at all. Or maybe since we use a calibration from 1.2.3.3 it could interfere when we upgrade to 1.2.3.5? Just guessing im out of ideas.. Ill keep running the 1.2.3.3 i guess..

Lewis

bomerman19 · Post by **bomerman19** » Mon May 26, 2008 10:02 pm

I'm having the same problem with my D17 Launch control worked perfect and then as soon as I updated to version 1.2.3.5 I completely lost my launch control

Bflaker · Post by **Bflaker** » Tue May 27, 2008 11:13 am

What settings are you guys using for the launch control and the switch? You guys do realize it's different from before. You have to setup the switch to always on if you don't want to add an additional clutch switch. Also you can't use the Full Throttle Shift unless you add the additional clutch switch. Mine works perfectly fine. I used it at the track this weekend without a problem.

Here's a screen shot of my settings so you can understand a little better about how you have to do it now.

shadowmd · Post by **shadowmd** » Wed May 28, 2008 6:46 pm

same problems with the launch control on the new kmanager verson..

mods:
2005 civic si
k20a2 swap with z3 cams and bolt-ons...launch control worked fine before now it doesnt work at all

Post by **Spunkster** » Fri May 30, 2008 11:31 am

We still have not seen a single datalog or calibration showing the problem. We are still waiting.

We need this information to see if it is calibration type specific or just a setting.