Notices
Tuning Reflashes, Piggybacks, Standalone ECUs

Cipher and UTEC timing question

Thread Tools
 
Search this Thread
 
Old May 30, 2007 | 07:37 AM
  #1  
h8bumps's Avatar
h8bumps
Thread Starter
Registered User
iTrader: (4)
 
Joined: Jun 2006
Posts: 306
Likes: 0
From: Dearborn, MI
Default Cipher and UTEC timing question

I bumped my timing 2 degrees with Cipher before installing my UTEC. Now when I data log timing with UTEC, it gives me different values than when I data log timing with Cipher.

Cipher is telling me my timing is still 2 degrees advanced, but UTEC is telling me the timing is NOT advanced. Which is correct???
Attached Thumbnails Cipher and UTEC timing question-cg4e.jpg  
Reply
Old May 30, 2007 | 08:01 AM
  #2  
BlackTuner's Avatar
BlackTuner
Registered User
iTrader: (2)
 
Joined: Jul 2004
Posts: 362
Likes: 0
From: East Coast
Default

Originally Posted by h8bumps
I bumped my timing 2 degrees with Cipher before installing my UTEC. Now when I data log timing with UTEC, it gives me different values than when I data log timing with Cipher.

Cipher is telling me my timing is still 2 degrees advanced, but UTEC is telling me the timing is NOT advanced. Which is correct???
When the UTEC is installed and you are in a UTEC Load Site with Timing plugged into the map, the car will run the UTEC Timing not what the factory ecu wants to run. Your cipher logger will be incorrect and your UTEC Mod. Ignition will be correct.

Thanks,

Jermaine~
Reply
Old May 30, 2007 | 08:04 AM
  #3  
h8bumps's Avatar
h8bumps
Thread Starter
Registered User
iTrader: (4)
 
Joined: Jun 2006
Posts: 306
Likes: 0
From: Dearborn, MI
Default

But what if my UTEC timing map is all 'ECU'?
Reply
Old May 30, 2007 | 08:07 AM
  #4  
BlackTuner's Avatar
BlackTuner
Registered User
iTrader: (2)
 
Joined: Jul 2004
Posts: 362
Likes: 0
From: East Coast
Default

Originally Posted by h8bumps
But what if my UTEC timing map is all 'ECU'?
Actually the values look very similar. The timestamp points are not the same yet they are still very close. It won't be exact for that reason.

Jermaine~
Reply
Old May 30, 2007 | 08:32 AM
  #5  
h8bumps's Avatar
h8bumps
Thread Starter
Registered User
iTrader: (4)
 
Joined: Jun 2006
Posts: 306
Likes: 0
From: Dearborn, MI
Default

There are a couple points where the difference is less than 2 degrees, but for the most part there is a 2 degree discrepancy between what UTEC is reading and what Cipher is reading. That's pretty significant.

I just want to know if UTEC can't read the 2 degree timing bump that I did with Cipher, or if UTEC is somehow preventing that timing bump.
Reply
Old May 30, 2007 | 08:41 AM
  #6  
rcdash's Avatar
rcdash
New Member
iTrader: (18)
 
Joined: Jul 2005
Posts: 6,474
Likes: 65
From: Chapel Hill, NC
Default

Is this discrepency on the stock map (map 0)?
Reply
Old May 30, 2007 | 09:14 AM
  #7  
h8bumps's Avatar
h8bumps
Thread Starter
Registered User
iTrader: (4)
 
Joined: Jun 2006
Posts: 306
Likes: 0
From: Dearborn, MI
Default

Yes, that data was all from map 0.
Reply
Old May 30, 2007 | 09:25 AM
  #8  
BlackTuner's Avatar
BlackTuner
Registered User
iTrader: (2)
 
Joined: Jul 2004
Posts: 362
Likes: 0
From: East Coast
Default

The UTEC is only interpreting the factory ecu timing curve. It is not being manipulated just "watching". From the logs you are showing me it looks fine. The time stamps for each log are not the same yet they are still very close.
Reply
Old May 30, 2007 | 03:52 PM
  #9  
Wired 24/7's Avatar
Wired 24/7
Dr. Wired
Premier Member
iTrader: (2)
 
Joined: May 2005
Posts: 17,582
Likes: 9
From: San Mateo, CA
Default

What if you use cipher to change timing to -2 degrees instead of +2 and see what the UTEC says after that.


This looks similar to what happened with me and my EU -- tried to advance timing with EU but I believe stock ECU pulled timing back. Advancing timing with cipher worked just fine though.
Reply
Old May 30, 2007 | 05:43 PM
  #10  
350zfred5283's Avatar
350zfred5283
Registered User
 
Joined: Feb 2007
Posts: 98
Likes: 1
From: Sterling Heights
Default

Wired --> It's a little tougher to bump the timing by 2° with UTEC because you have to change the entire map and not knowing what each target value is for each load/RPM value. With Cipher, it is possible to bump the entire load v RPM map without knowing the initial value.

h8bumps, I don't think UTEC is working right... This is what I would do:

- Log at IDLE with Cipher no bump
- Log at IDLE with Cipher 2° bump
- Create a map with Cipher bumping 2° @ 0%-10% load from IDLE data (ECU for rest of timing map)
- Log at IDLE with Cipher on the 2° bump @ 0%-10% load UTEC map

Also, change the range on your Y-axis for your excel charts so the difference is more apparant (you only need a range of 10°).

Late,
Nick

Last edited by 350zfred5283; May 30, 2007 at 05:48 PM.
Reply
Old May 31, 2007 | 06:30 AM
  #11  
h8bumps's Avatar
h8bumps
Thread Starter
Registered User
iTrader: (4)
 
Joined: Jun 2006
Posts: 306
Likes: 0
From: Dearborn, MI
Default

Sitting at idle, I was able to hook up both Cipher and UTEC and log simultaneously. At idle, there was over a degree difference between what Cipher read and what UTEC read for timing.

Also, when I moved my timing back down 2 degrees with Cipher, UTEC's timing readout moved lower 2 degrees. So it wasn't just the 2 degree bump that was causing the issue.

I'm just trying to figure out which is reading my timing correctly, UTEC or Cipher. I guess my next step is to create a timing map and log it with Cipher to see if it coincides. Has anyone else noticed this issue?
Attached Thumbnails Cipher and UTEC timing question-cgdf.jpg  
Reply
Old Jun 1, 2007 | 05:19 AM
  #12  
DaveFunction2ND's Avatar
DaveFunction2ND
Banned
iTrader: (8)
 
Joined: Oct 2006
Posts: 650
Likes: 0
From: Sterling, VA
Default

The possibility exists that they are both reading timing correctly. This depends on where the stock ECU and where the UTEC take their timing information from. The stock ecu may be reading off the base timing table or the mean timing table. Mean is the final ignition timing once modifiers have been introducted (ie - IAT, CLT, Knock, etc). The UTEC may be reading the final output of the ECU or it may be reading a different OBDII code but I assume it is not using the OBDII interface becasue the Cypher and UTEC can operate at the same time wihtout interfering with each other. This means that most likely the UTEC is measuring the actual output of the stock ecu to the coils and comparing that to its own CAS information. These are only educated guesses BTW. BlackTuner might be able to provide more insight.
Reply
Old Jun 1, 2007 | 05:59 AM
  #13  
KPierson's Avatar
KPierson
Banned
iTrader: (1)
 
Joined: Feb 2004
Posts: 2,128
Likes: 0
From: Dayton, OH
Default

Originally Posted by h8bumps
I'm just trying to figure out which is reading my timing correctly, UTEC or Cipher. I guess my next step is to create a timing map and log it with Cipher to see if it coincides. Has anyone else noticed this issue?
The Cipher will NOT read modified UTEC timing correctly.
Reply
Old Jun 6, 2007 | 06:05 AM
  #14  
BlackTuner's Avatar
BlackTuner
Registered User
iTrader: (2)
 
Joined: Jul 2004
Posts: 362
Likes: 0
From: East Coast
Default

Originally Posted by KPierson
The Cipher will NOT read modified UTEC timing correctly.
Right, becuse the factory ecu is not driving the car. This means when ever you have a timing value in the UTEC Map and assuming you are on this same active map. The utec is firing your Ignition Coils. Your engine ignition timing can be found in the Mod. Ingnition Column.

With that said the UTEC reads the actual ignition #1 signal output from ecu. No factors, no comps, raw output to the coils.



Jermaine~
Attached Thumbnails Cipher and UTEC timing question-zignition1signal.jpg  

Last edited by BlackTuner; Jun 6, 2007 at 06:15 AM.
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Whiskers1996
Tuning
14
Aug 1, 2020 04:09 PM
Vigman
Maintenance & Repair
17
Nov 17, 2015 04:34 AM
NissanZcrazy
Forced Induction
6
Nov 2, 2015 06:03 PM
Mattg350z
Buying/Leasing
4
Oct 2, 2015 06:51 AM
sccarally
Meet-Ups / Events (Texas)
1
Sep 27, 2015 01:06 PM




All times are GMT -8. The time now is 05:18 AM.