ecutek and cruise control
 

hey guys so ive been working on my tune using ecutek and this last weekend i went for a very long drive (16 hours) and for some reason my cruise control is not working. they say that the racerom doesnt effect the use of cruise control so supposedly its not that causing the issue. i have tuned out some O2 codes due to my header not having a cat in it. is that a problem? is there something else? any help would be great. i am making the same drive back home this weekend and would love to have my cruise back.

If you have catless header on a stock tune you will trip CEL code P0420 get cel light and cruise control will be disabled.


edit tune and disable P0420

yeah i did that. still nothing

what other CEL codes are you getting ?

did you force ecutek to load a different calid rom to your car than standard ?


where did the tune come from ?
what changes have you made


is the cruise control icon in dash green or orange colour

do you have flex fuel kit ? using rear 02 sensor input

other codes im getting is U0100, U0155, and i dont remember the code but the one for the fuel gauge voltage. also gotten other o2 codes. the cruise control icon does not illuminate at all. it will come on if i do not have U0155 tuned out but soon as i hit it the check engine light comes on for U0155 and it stays on with the check engine light. ive tuned out the other o2 codes along with u0155. the tune is from the ecutek program. and as for your question about if i forced ecutek to load a different calid rom i have no idea what that means. when i identified the ecu it showed me a list of what roms were compatible with it and i picked one.

U0155 is lost communication with instrument panel control cluster ie CAN-BUS comms fault.
It seems all "U" type codes are for communication. I can't see what U0100 is though.
Check your calibration ID (calid) and choose the same calid in EcuTek
IE I run A01G so I'd only pick that (or possibly A02G). Even though the others are compatible, they may not work properly.

Ok U0155 is lost communication with dash cluster which will cause issues.


If you have any devices plugged into obd port this may cause problems like obd scanners etc. The ecutek cable will be fine.


That code can also come up if you have flashed an incompatable base rom to your car. eg your car was say originally a B01C/D and you flashed a D00C/D or later rom.


alternatively you may have a real problem with the dash cluster or ECU


What year/month is your car and what rom is flashed currently


Ecutek usually warns you saying possible rom incompatability but its possible to push through and flash it.

It definitely sounds like an incompatible ROM calibration. I know recently EcuTeK has been allowing people to reflash their 2013 -2014 ECU's with newer 2015+ ROM ID's and this is causing the exact issue you are seeing. I have informed EcuTeK of this already, so they may have update for their software.

If you happen to be using a 2015+ ROM on your 2013 - 2014 vehicle I would suggest switching back to the older ROM for proper compatibility.

Cheers,
William Knose
Delicious Tuning

thanks guys for all your help. steve and delicious yall were right it was an incorrect base rom. i wasnt able to find the instructions and got impatient waiting for a response from the tuner i bought the ecutek from and just picked one that worked assuming they were all basically the same in the list of compatible roms. got the right base rom and now it works again. thanks again i appreciate your time and help