Hi All

Just wondering if anyone has used either of these OBD-II diagnostic scan tool products (www.uprev.com and www.autoenginuity.com) and which one they would recommend. I mainly want one for reading/clearing codes, monitoring/recording ECU parameters as i am purchasing a VMS car pc and in particular adjusting RPM and ignition timing as i have a slight engine ping in the 2000-3000 rpm range.

Thanks

 

I have the autoenginuity utility. It will work fine for idle adjust and timing advance as well as code monitoring and reset, etc. Just like with Cipher you get only +-2 degrees for timing. From what I have seen from Cipher though, it seems to be a little more user friendly, and the focus is on our cars, plus more people on this board are familiar with it. In hindsight I would probably go with Cipher if I were to do it again, but the AE tool is fine.

 

Thanks Mikead, as i initially wasn't sure if the AutoEnginuity allowed the timing to be retarded as i heard conflicting info from their techsupport guys that it was only advance. Thanks 4 the update.

 

No problem 350zee03. To be honest, between an ecu reflash and the utec tune I haven't had the need to play with timing with the tool. I think I would like to hook up to the car and verify the - timing control before I stand by that statement. I won't be able to do so until pretty late tonight, but if this tool is still one you are considering, and for that specific reason, I will do that.

FWIW, my whole issue with the tool is the poor sampling rate while logging sensors. I really wanted this to log afr from the oem widebands. It turns out that with additional things like throttle position sensor, MAF voltage, and rpms turned on (the things that would make this log useful for tuning) I don't get the afr resolution I would like to see. Maybe one entry per sensor every 800 rpm's or so. This is something to chew on if you are seriously looking at this tool.

 

FWIW, the ignition timing change with these tools only adjusts the base timing which is only from idle to around 2300 RPM. Only a reflash, UTEC, e-manage Ultimate etc. and standalones can adjust it throughout the rev-range.

 

I have a Cipher and am happy with it. I wanted a tool to check engine codes (I don't have any yet) and log the A/F ratio to see if additional timing would be appropriate. Cipher is a true Windows program and very easy to use. I especially like the way Cipher lets you group the parameters you save into a single graph. That way you can see the relationship of timing, A/F Ratios, RPM, and miles per hour on one graph... or you can see all the engine temperatures on one graph... whatever you choose.

I'll have to look at some of my Cipher data to see if it is more granular than your data. I suspect it will be the same... probably the limit of this type of data capture. I can post a screen capture of one of my Cipher graphs if anyone is interested.

That's very interesting. I tried to verify the timing change through the Cipher data capture and have had trouble doing so. Made two base dyno runs with the timing set at +2 with the Cipher. Then moved the timing back to +0 with the Cipher, but nothing changed on the dyno run.

 

I think it is actually a limit with the way the tool interfaces. (serial vs. CAN bus) I have had several iterations of the autoeng sw now and with one of the builds I was able to connect using CAN. Data sample rate was much higher, but subsequent updates screwed me again. I think if I were to actually uninstall the sw, delete all the remnants, and then re-install I would probably get CAN back, that is how I got it with the release that it was first supported in and actually worked for me. I'm just a little lazy with this tool now since I can use TXs to log tuning info.

FWIW, I have seen some Cipher logs posted that had pretty usable resolution.

 

So for data logging the cipher is the best choice to go with?

 

Not surprising...

 

I think that if you adjust the base timming it will still affect the overall timming curve at WOT. I could be wrong but i thought i remember reading that somewhere.

 

That's virtually impossible. When the ECU is in open-loop there are preset timing values (based on load and RPM) that aren't touched by adjusting the base timing. That's all it is, base timing.

 

I ended up taking the car into the Nissan dealer to retard the timing by 2 degrees using their Nissan Consult II but yet i am still experiencing engine pinging which has totally confused me. Can the timing be retarded more or is 2 degrees the maximum u can go. Also what effect will this have on the car with this further retard?
I am prob going to look at upgrading the stock computer but won't be looking at doing this just yet.

 

Retarding the timing via the consult II won't help. My guess is there's a lil more oil vapor entering the combustion chamber than normal. Oil vapors lower the effective octane of the fuel. My suggestion to you would be to install a catch can in-line with the PCV system.

Are you experiencing oil consumption?

 

I am not experiencing any oil consumption problems.

 

Well the pinging is unrelated to your ignition timing, IMO. Try a catch can.