When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Just got off the phone with Frank. UpRev knew exactly what the issue was but for some reason they didn't include it in the documentation. The lightened flywheel was causing the misfire codes which jacked the timing up. Should be an easy fix. Back on the dyno tomorrow.
great to hear it was a minor issue that will be fixed. i'm still debating whether to just go with osiris or haltech... looking forward to your results!!
if thats the case, then everyone with a light flywheel would have the same problem with misfire codes
whats the solution?
Originally Posted by MDHRZ
Just got off the phone with Frank. UpRev knew exactly what the issue was but for some reason they didn't include it in the documentation. The lightened flywheel was causing the misfire codes which jacked the timing up. Should be an easy fix. Back on the dyno tomorrow.
disabling the misfire codes? wow. good luck with that...
I'll get more details tomorrow. What would be the problem with doing that? Pros/cons? A lot of this is new to me so I'm kind of learning as I go. From what I've read and been told, the UpRev software has the capability of doing that.
I'll get more details tomorrow. What would be the problem with doing that? Pros/cons? A lot of this is new to me so I'm kind of learning as I go. From what I've read and been told, the UpRev software has the capability of doing that.
Sure, it can, but disabling the codes will also disable your first warning (ses light) if a misfire issue arises. The ecu is likely to catch it before it becomes audible/noticable......thus it put the system into limp mode or shuts it of as a damage prevention. I'd imagine frank will attempt to fix the issue first and foremost.
For the record, my HR is running a lightened clutch/fly combo (os giken) and I have yet to see a misfire code.
MD, how much lighter than stock is your flywheel?
So what mods did you do to your transmission for the new clutch, and have you had any problems with your OS Gilken? I'm going to have Injected Performance look into this because i'm really tired of the stock clutch!
Sure, it can, but disabling the codes will also disable your first warning (ses light) if a misfire issue arises. The ecu is likely to catch it before it becomes audible/noticable......thus it put the system into limp mode or shuts it of as a damage prevention. I'd imagine frank will attempt to fix the issue first and foremost.
Hmm, good point. I'll try to get some more clarification on this when he gets to the shop.
Originally Posted by 08NismoZ
So what mods did you do to your transmission for the new clutch, and have you had any problems with your OS Gilken? I'm going to have Injected Performance look into this because i'm really tired of the stock clutch!
Pretty sure he hasn't had any issues which makes me wonder why I am the only one throwing codes. I haven't seen this issue with any other HR's. More info on the clutch -> https://my350z.com/forum/8402009-post8.html
Every car and setup is different. Just because one guy doesnt have an issue doesnt mean that its not the cause of the issue here. LOL @ some peoples comments.
So what mods did you do to your transmission for the new clutch, and have you had any problems with your OS Gilken? I'm going to have Injected Performance look into this because i'm really tired of the stock clutch!
I have done nothing at all to the transmission or CSC assembly, and I have had absolutely ZERO problems with this clutch. Been running it since November.