Uprev Tuner , Need help here !
Thread Starter
Registered User
iTrader: (7)
Joined: May 2007
Posts: 433
Likes: 1
From: Ontario, Canada
I ask a favor to anybody who has an HR and can datalog their Intake & Exhaust cams at IDLE
Im having a big trust issue with Uprev right now,
Since I swaped the HR heads into my 370z, I couldn't datalog with Cipher until I tried again today.
I never had problem with the Rom Editor for logging..
so doing a test map I make sure the IDLE area is at 0deg on both Intake & Exhaust Table.
I get this with the Rom Editor;
Intake Bank 1 = 0
Intake Bank 2 = 0
Exhaust Bank 1 = 0
Exhaust Bank 2 = 130
If I add 10deg on both ,, the result is like this
Intake Bank 1 = 10
Intake Bank 2 = 10
Exhaust Bank 1 = 10
Exhaust Bank 2 = 148 (+18 !!)
Then under Cipher datalogging I get this with 0deg in IDLE area Int. & Exh
Intake Bank 1 = 0
Intake Bank 2 = 0
Exhaust Bank 1 = 130
Exhaust Bank 2 = 130
if I add 10deg Exh Cam I get this
Intake Bank 1 = 0
Intake Bank 2 = 0
Exhaust Bank 1 = 112
Exhaust Bank 2 = 111
so I cant trust anything in this.
My Favor is to see what other HR owner gets please
.....
edit; the engine idle fine, no DTC, doing a 1/4 mile performance run with my AiM Solo DL , I got 103.5mph which look to be alright for a lightly modded HR engine.
Im having a big trust issue with Uprev right now,
Since I swaped the HR heads into my 370z, I couldn't datalog with Cipher until I tried again today.
I never had problem with the Rom Editor for logging..
so doing a test map I make sure the IDLE area is at 0deg on both Intake & Exhaust Table.
I get this with the Rom Editor;
Intake Bank 1 = 0
Intake Bank 2 = 0
Exhaust Bank 1 = 0
Exhaust Bank 2 = 130
If I add 10deg on both ,, the result is like this
Intake Bank 1 = 10
Intake Bank 2 = 10
Exhaust Bank 1 = 10
Exhaust Bank 2 = 148 (+18 !!)
Then under Cipher datalogging I get this with 0deg in IDLE area Int. & Exh
Intake Bank 1 = 0
Intake Bank 2 = 0
Exhaust Bank 1 = 130
Exhaust Bank 2 = 130
if I add 10deg Exh Cam I get this
Intake Bank 1 = 0
Intake Bank 2 = 0
Exhaust Bank 1 = 112
Exhaust Bank 2 = 111
so I cant trust anything in this.
My Favor is to see what other HR owner gets please
.....edit; the engine idle fine, no DTC, doing a 1/4 mile performance run with my AiM Solo DL , I got 103.5mph which look to be alright for a lightly modded HR engine.
Last edited by XChacalX; Aug 6, 2013 at 06:22 PM.
Thread Starter
Registered User
iTrader: (7)
Joined: May 2007
Posts: 433
Likes: 1
From: Ontario, Canada
it was on the street average out of 2 run, not a 1/4mile track prepped on. Its quite different
and don't tell me a relatively stock HR engine with street tire will do much better than 103.5
Btw, this thread it not about how fast I went or 2-3 mph faster with a better driver , but the datalog issues with the Cams so if you have nothing else to share on that topic, avoid posting.
Thanks.
and don't tell me a relatively stock HR engine with street tire will do much better than 103.5
Btw, this thread it not about how fast I went or 2-3 mph faster with a better driver , but the datalog issues with the Cams so if you have nothing else to share on that topic, avoid posting.
Thanks.
Last edited by XChacalX; Aug 7, 2013 at 02:41 AM.
Usually the values presented are bigger than actual degrees, in this example i'd assume that what Uprev translates to "degrees" is listed in smaller units in the PCM language, so you are seeing 18 'units' change for a commanded ten degrees. That may not be abnormal.
The fact that it presents two different base values from left to right bank makes me think there is a possible cam sensor communication issue. Are you re-using the 3.7 sensors, or the 3.5? I'm not aware of if they are interchangeable or not, excuse my ignorance. I would assume you cannot based on the VVEL setup being different but anything is possible.
I'd have to guess, if the 3.5 sensors are sending a different type of signal that what the ROM editor is used to from a 370 you could be getting that errant value. Were you getting normal degree values before the head swap?
I know on my HR with my Cobb, the logging/reporting on the screen isn't correct for cam timing either. It stays pegged on one cam at times. I think there is something in the ECM that they don't have fully descrambled.
The fact that it presents two different base values from left to right bank makes me think there is a possible cam sensor communication issue. Are you re-using the 3.7 sensors, or the 3.5? I'm not aware of if they are interchangeable or not, excuse my ignorance. I would assume you cannot based on the VVEL setup being different but anything is possible.
I'd have to guess, if the 3.5 sensors are sending a different type of signal that what the ROM editor is used to from a 370 you could be getting that errant value. Were you getting normal degree values before the head swap?
I know on my HR with my Cobb, the logging/reporting on the screen isn't correct for cam timing either. It stays pegged on one cam at times. I think there is something in the ECM that they don't have fully descrambled.
Thread Starter
Registered User
iTrader: (7)
Joined: May 2007
Posts: 433
Likes: 1
From: Ontario, Canada
Usually the values presented are bigger than actual degrees, in this example i'd assume that what Uprev translates to "degrees" is listed in smaller units in the PCM language, so you are seeing 18 'units' change for a commanded ten degrees. That may not be abnormal.
The fact that it presents two different base values from left to right bank makes me think there is a possible cam sensor communication issue. Are you re-using the 3.7 sensors, or the 3.5? I'm not aware of if they are interchangeable or not, excuse my ignorance. I would assume you cannot based on the VVEL setup being different but anything is possible.
I'd have to guess, if the 3.5 sensors are sending a different type of signal that what the ROM editor is used to from a 370 you could be getting that errant value. Were you getting normal degree values before the head swap?
.
The fact that it presents two different base values from left to right bank makes me think there is a possible cam sensor communication issue. Are you re-using the 3.7 sensors, or the 3.5? I'm not aware of if they are interchangeable or not, excuse my ignorance. I would assume you cannot based on the VVEL setup being different but anything is possible.
I'd have to guess, if the 3.5 sensors are sending a different type of signal that what the ROM editor is used to from a 370 you could be getting that errant value. Were you getting normal degree values before the head swap?
.

To answer the big question about if I used the 3.7 sensor..
no
all sensor connected on the engine up to the ECU, came from the HR engine ... because everything had to be transferred over.
so, after talking with Sasha (SG-Motorsport now Onpointdyno.com)
told me last night that he remember seeing the exhaust cams to be around the number I had. (130deg)
since the ROM Editor doesn't read the same from each bank but under Cipher it detect both side to be the same. .. I would assume now there is a bug into the Rom Editor that Uprev should fix asap.
I'm just quite **** at Uprev because ,, well that ECU/Roms has been around since 2007 ! its not like they couldn't or someone couldn't detect it before ! Or it was just a bad timing on my part that happened to have started tuning on this ECU while a bug/conflict was integrated into the software not long ago... who knows.
Still, it would be awesome if somebody would datalog both of their Intake & Exhaust cams banks at Idle to confirm my possible issue.
It's not uncommon for odd issues with uprev. They had to reverse engineer every ECM (multiple per model year and engine type). Also, ROM editor is where they spend all their time these days and Cipher is on life support. Have you contacted Jared about this? He's been fairly responsive (responds within a few days but then communicates regularly) with all my queries some of them pretty detailed. I'd also be a bit curious how your ECM is even dealing with sensors it wasn't designed to work with - and it's not like they spend time testing every possible Frankenstein setup. Just as curious as you are about if it's a bug in the ROM editor though.
Last edited by djamps; Aug 7, 2013 at 08:09 PM.
You'd need logs from a 3.7 though, 3.5HR logs aren't telling you much because the ECU interface is different.
I get Intake cam values pegged at +50 all the time and exhaust cam reports correctly on my Cobb AP, just saying.
I get Intake cam values pegged at +50 all the time and exhaust cam reports correctly on my Cobb AP, just saying.
Trending Topics
Thread Starter
Registered User
iTrader: (7)
Joined: May 2007
Posts: 433
Likes: 1
From: Ontario, Canada
. Have you contacted Jared about this? He's been fairly responsive (responds within a few days but then communicates regularly) with all my queries some of them pretty detailed. I'd also be a bit curious how your ECM is even dealing with sensors it wasn't designed to work with - Just as curious as you are about if it's a bug in the ROM editor though.
I guess I wasn't clear, ...
my HR head swap on the 3.7bottom require the use of the HR ECU ...
so the HR ECU is controlling the engine at 100%.
the only sensor I kept from the 370z were the 2x 02sensor which are use by the HR ECU , same setting.
Thank you for you Input though.
Last edited by XChacalX; Aug 8, 2013 at 02:55 AM.
Thread Starter
Registered User
iTrader: (7)
Joined: May 2007
Posts: 433
Likes: 1
From: Ontario, Canada
Rom editor values are fine. Took a look at my logs, intake follows numerically, but exhaust is different.
At idle:
ICB1 3.5
ICB2 5.5
ECB1 -0.5
ECB2 128
Looking at long term logs, the ECams like to oscillate more than the ICams. Don't forget that adding 10 "degrees" on the Uprev table is really trying to add 5 degrees of actual cam advance. So a swing of "8" on the raw value, is really a +-2 degrees while in operation. You can trust ECam B1 to be the value that correlates best with the cam table value.
At idle:
ICB1 3.5
ICB2 5.5
ECB1 -0.5
ECB2 128
Looking at long term logs, the ECams like to oscillate more than the ICams. Don't forget that adding 10 "degrees" on the Uprev table is really trying to add 5 degrees of actual cam advance. So a swing of "8" on the raw value, is really a +-2 degrees while in operation. You can trust ECam B1 to be the value that correlates best with the cam table value.
Last edited by T_K; Sep 14, 2013 at 09:03 AM.
i have a 370z and i've been chasing an intermittent loss in throttle response.
when fully warmed up, my intake cams are advanced to 34.5 degrees at idle. this is based on Cipher logs. thing is, the engine idles fine with the exception of some rpm fluctuation. other than that, it seems ok. the engine feels flat after 4000rpm though.
i thought the intake cams were meant to be retarded/zero degrees advance at idle?
i dont think it's a glitch because Cipher does show zero advance at idle when the coolant is below 65 degrees celsius.
hope that helps
when fully warmed up, my intake cams are advanced to 34.5 degrees at idle. this is based on Cipher logs. thing is, the engine idles fine with the exception of some rpm fluctuation. other than that, it seems ok. the engine feels flat after 4000rpm though.
i thought the intake cams were meant to be retarded/zero degrees advance at idle?
i dont think it's a glitch because Cipher does show zero advance at idle when the coolant is below 65 degrees celsius.
hope that helps
Thread
Thread Starter
Forum
Replies
Last Post
Colombo
Forced Induction
35
Nov 9, 2020 10:27 AM
Dark Knight
Wheels Tires
7
Nov 11, 2015 08:40 PM




