on your forum can you provide stock tune files so that we can see what nissan has done and compare to our own stuff.

i understand you do not want to provide your guys' e-tune files, but i for one would like to see diff tuning strategies by nissan over the years.

thanks

 

Patched ROMs for different vehicles should be available for people to start from, there honestly isn't much variance between the years, except to deal with different cam profiles/injectors etc as the motors go from DE to RevUp to HR.

But you should have access to other peoples shared tunes also if you want to get an idea of what other customers are doing.

 

not with in the stock ecu on a lap top, put the data in then it crunches some #'s, and then gives you a file to upload back to the ECU with an optimized tune on it.

 

so since im providing like a million ideas how about a discount!

 

 

LOL

 

It’s been asked before, and UpRev was understanding of the request, but didn’t seem to think there is “enough” of a need/desire… But I’m gonna ask again.

I would LOVE to set the ECU to ignore accelerator and break at the same time… AT break torque launching is dismal (at least in my car, and other I know) because there is a slight bog after break is release (ECU cutting power I presume)… I get better 60’ and ET by launching off idle which is pathetic! If I could rev to 2K or 2500 (and take advantage of dedicated map for 2-step launch), I could bring times down notably!

Please consider this!

 

recent ETC update Rawks! Saved my low end woes after cam install - Thanks UpRev!

 

I'm going to venture to say that is caused by the transmission computer, not something that we access at this time.

I don't think we've even had a chance to look into that, but knowing what I know about where certain commands come from I'd say the transmission computer would need an update to allow that.

 

I'd like to see monitoring of the knock sensor and end users ability to clear vtc learning. I have low rpm detonation under semi-moderate to moderate load, but not under WOT and only on hot days. Plus worse when completely heat-soaked from sitting for a bit then drive again.

 

Uprev needs to develop something that will support nonWB O2 equipped Z's. That is the only hurdle i have with buying this ASAP.... i have sent many email about info and have got nothing in return...

 

Working on including PLX and Zeitronix wideband sensor information into Cipher. Hopefully it will be done before the end of the year, so that you can have an aftermarket wideband that Cipher can log along with all the other ECU data.

 

Knock sensors be black magic and sorcery, easier to slay a dragon. We're working on doing it but without getting yourself a $2k+ aftermarket knock sensor and tooling software around that, it's hard to have reliable information.

We are working on updating the software to atleast show what the knock sensor sees, even though it may not be reliable data, it's something.

 

That would be better than nothing to at least see what it's doing or if even seeing that condition. Would possibly help me prove the knock sensor being defective or not.

Any thoughts on clearing VTC learn like the current ability of clearing fuel learn? Thanx

 

Pertaining specifically to codes triggered by the addition of HFCs, but it could be useful for other codes. It would be nice to have the ability to completely disable a DTC and the ECU's awareness of the feedback that triggers it instead of just clearing or turning off the DTC. Or, the ability to modify the ECU threshold range of the feedback provided back to it that triggers the DTC.

 

Instead of the Cable use the new ElmCanII-WLAN!

 

except the cable you speak of doesn't talk to the ECU but rather reads only OBD II. It also doesn't do the most valuable thing that the Cipher Cable does which is read our stock O2 WB sensors.

 

Unless you are in an 03 or 04 then you have to get a Wideband.....

 

You're still missing the point, it doesn't speak to the ECU, it's just a code scanner type device that pulls ODBII data. There are far cheaper cables that do the same thing.

Plus that unit is vaporware.

 

SAE J1979 OBDII scan compliance would be great. I had to purchase another generic scan tool to test readiness status (SRT). Now I find out that the SAE spec has multiple modes that the FSM refers to for testing by generic scan tools. It would be super if Cipher could be used as a fully SAE J1979 compliant generic scan tool (all modes).

I cannot get my EVAP system to show ready with my Osiris flash (all DTC enabled). Driving me nuts trying to drive in the FSM-specified patterns to get the SRT code to read "COMPLETE"...