The Official Unichip Q Tuning Thread

Scanxl does support the plx devices, but I read on the Palmer forum that its tough to get it to work properly. It might be easier in the long run to add it as an aux...

Sent from my BlackBerry 9850
 
No idea what you guys are talking about:). I just hope we can data log now with the air fuel meter:)

Aaron is great, you got it fast too.
 
Hahaha, I think I hit it off with Aaron quite well? Every time I called, he pick up the phone and very pleasant and cool dude to talk with. If he said he'll call me back, he will. So far for past 3 -4 months with Unichip, I feel their support (Aaron) is awesome. I will try to get the data log working before Sunday's meet.
 
Hahaha, I think I hit it off with Aaron quite well? Every time I called, he pick up the phone and very pleasant and cool dude to talk with. If he said he'll call me back, he will. So far for past 3 -4 months with Unichip, I feel their support (Aaron) is awesome. I will try to get the data log working before Sunday's meet.

I totally agree. Sometimes work takes me within a few miles of their shop and I just show up randomly to ask questions or pick up equipment. Aaron and Jack (shop manager) are both super easy going and always up for answering questions or just chatting about car ish.

Andy, this is what I was talking about regarding the supported plx devices. I'm not exactly sure how ScanXL wants to see the input from the devices (maybe just usb via that cable you just received?) but at least they are already calibrated in the software...

scanxlsupportedplxdevices.jpg

Also, regarding the +2 mod. Here's the map I made to test it prior to adding it to my running custom map.

2Timingadvance.jpg

I've logged several runs after the +2 was done and, contrary to my original findings, my ecu does pull the timing back at some rpm above 4K. In fact it pulls between 2 and 4 degrees out when the knock sensor is triggered, which sucks. I'm still trying to get the log resolution high enough to try to pinpoint where exactly it's happening, but so far I can only say for sure that it happens between 4000 and 5300 rpm.

Here are few clips of a recent log file to illustrate my point. (all three pics are the same file with the cursor adjusted slightly):

#1) At this point you'll see the throttle position is at 62%, which is in the unmodified portion of the timing map. Here the timing is at 23 degrees, which is the oem commanded value at full throttle from 2-5k rpm.

timingpulled1.jpg

#2) Here you'll see the throttle position reach the modified portion of the map (82%), and the timing advances to 25 degrees at 3975rpm. It actually advanced before 3975rpm, but that's when the ScanXL resolution caught up.

timingpulled2.jpg

#3) And here is where it goes south. No change in the throttle position timing advance map (still in the +2 area), but the timing has dropped back to 23 degrees at 5500 rpm. In my baseline runs the timing stayed at 24-25 here depending on intake air temps.

timingpulled3.jpg

I assume the knock sensor is to blame, but I can't be sure until I get this resolution issue worked out. According to Palmer, the resolution bottleneck is the vehicle itself and reducing the number of monitored PIDs will help. My next step is to cut out the fuel and MAF monitoring PIDs. Hopefully limiting ScanXL to three PIDs will give me some decent resolution... The good news is that running the wideband gauge directly into the computer via usb will circumvent the OBD-II resolution limitations. Assuming a capable computer we should be able to log that at speeds close to realtime. at least close enough for who it's for...
wink%20%282%29.png
 
PM replied. Thanks for the help. FX ECU pinout is different so I'm going to go custom with the harness. I'll keep you guys updated.

I haven't heard back from Unichip about tuning my car though.

When I hard wired my unichhip, I used a 350z diagram from unichip and verified it with the FX fsm. The pin locations are the same but some of the wires are different colors. I'd bet you have a similar thing going with your Mand the FX45, but you'll need the fsm for the M to be sure. Also, the unichip connects with all of 7 wires iirc... Not a big deal at all to figure out.

Sent from my BlackBerry 9850
 
See, that's the weird thing, the 03-04 M45 and 02-06 Q45 don't have the same ECU connector as ANY of the other Nissan vehicles out there except for each other. I've checked the 350Z, Maxima, FX, etc etc. They're also the only ones to come from the JDM essentially unchanged save for the VK45 being put in the M so I'm guessing that's the MAIN problem. I'm trying to get a custom connector made so I can go PnP before digging into hardwiring or splicing. I'd like to keep my stock wiring intact if at all possible but I'm running a little short on options.
 
More datalogging today with ScanXL on the +2 350z map. I excluded all but 6. PID's (rpm, vss, tp, sa, stft, iat), and am seeing much higher resolution now - about 2 updates per second as opposed to one update every two seconds. ScanXL still seems a little finicky however, and sometimes certain logged values drop out temporarily for no reason or just fail to log altogether. I still haven't installed the wideband sensor but I'm not real comfortable making fueling changes without a proper and somewhat reliable logging system anyway so it's not very high on my list.

I need to spend more time with the scan tool before proceeding with Unichip tuning. I may make a ScanXL thread if I cant get it going soon. I'm already looking at other datalogging options...
 
Hmmm Unichip have any comments? They recommended the scanXL.

Andy, have you tried data logging yet?
 
Tim,

that's a lot of 2's vs my map:
2Timingadvance.jpg

WhiteiPhone4Pictures1742.jpg

I've never seen the map on which the the original "+2 mod" was created. What you see in those screens are Andy's and my interpretation of the changes. On the vertical axis you have load, and on the horizontal there is rpm, so everywhere there is a "2" on the map is where 2 degrees of timing have been added (advanced). Once we (Unichip users) start logging some runs we can fine tune the timing maps individually, but for now it's sort of a guessing game with an eye toward safety and staying off the oem ecm's safeguard protocols. In a nutshell, the differences you're seeing on the maps is due to the fact that Andy and I don't share a brain.........yet. :tongue (2):

---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------

can someone translate any of this so i can at least pretend like i know what is going on?

I think it would be more efficient if you asked specific questions. The extremely shortened version of the above is "tuning".
 
Last edited:
Hey Tim - just a quick question (and maybe I missed it from earlier posts)....how does the "standard" 350z map compare to your current map? I.e., were the +2's coming from the 350z map?

Secondly...is +/- 2 the default change, or can you go more granular with +/- 1? Any attempts with +3 yet? :-)

Finally, this is just your timing advance, right? Have you/can you mess with the A/F ratio or fuel delivery at all?

Thanks,

Steve
 
You can do +1, +3, probably not good for the engine...

You can mess with the A/F ratio, I'm having mine done by UniChip soon. I'll have the UniChip Tuner remote into my (Handy_Andy's) laptop as he'll compile the real time data and A/F ratios and adjust. Pretty cool.

Hey Tim - just a quick question (and maybe I missed it from earlier posts)....how does the "standard" 350z map compare to your current map? I.e., were the +2's coming from the 350z map?

Secondly...is +/- 2 the default change, or can you go more granular with +/- 1? Any attempts with +3 yet? :-)

Finally, this is just your timing advance, right? Have you/can you mess with the A/F ratio or fuel delivery at all?

Thanks,

Steve
 
Hey Tim - just a quick question (and maybe I missed it from earlier posts)....how does the "standard" 350z map compare to your current map? I.e., were the +2's coming from the 350z map?

Secondly...is +/- 2 the default change, or can you go more granular with +/- 1? Any attempts with +3 yet? :-)

Finally, this is just your timing advance, right? Have you/can you mess with the A/F ratio or fuel delivery at all?

Thanks,

Steve

In terms of how this compares to the "standard" map; The figures you see are delta values as opposed to absolute values, so any number you see in a cell represents a departure from the stock value. The timing map is unique in that the accepted values always represent degrees of timing so there is no tuning strength. You can input "+10" if you want, but the reality is that the OEM knock sensors will signal the ecm to pull it and more right back out. The reason we chose +2 is that lots of people have done it successfully via Uprev.

The fueling, MAF, TPS, and any other custom map you create can accept inputs in hundredths (X.XX) and then be calibrated using the "tuning strength" value.

Also, I STILL haven't installed my wide band O2 sensor/gauge, so with the exception of the +2 timing deal, I have only as of yet run the maps already created by Unichip.
 
Last edited:
Back
Top