Evo 6 WBO & 3 Bar MAP for logging
#1
Newbie
Thread Starter
Join Date: Sep 2019
Location: Finland
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
Evo 6 WBO & 3 Bar MAP for logging
Hi. I'm installing my AEM uego wideband & GM 3 bar map w/ pigtail harness to my E6 GSR for datalogging. Could only find instructions for E7-9 and I'm not certain if these apply to earlier (doubt). Here is what I've dug info wise.
- MAP sensor hooked to FP line with T-piece, wire to ecu following: 75 signal, 81 power & 92 ground should log @ C3?
-Wideband lower portion of downpipe ~2" from flange 3 o'clock position. Wiring same for power and ground 81, 92? White wire (signal) 73 pin? Seems blank in ecu pinout but no idea where it logs.
Someone shine some light to me & tell what i'm missing / what is to correct.
-
- MAP sensor hooked to FP line with T-piece, wire to ecu following: 75 signal, 81 power & 92 ground should log @ C3?
-Wideband lower portion of downpipe ~2" from flange 3 o'clock position. Wiring same for power and ground 81, 92? White wire (signal) 73 pin? Seems blank in ecu pinout but no idea where it logs.
Someone shine some light to me & tell what i'm missing / what is to correct.
-
#2
Newbie
Sounds right mate, I know I had to change the logging request if in evoscan from the default ceddymod xml. It needs to be changed to the request I'd as the rear o2 sensor when connected to pin 75. Pin 73 was used in earlier versions but wasn't able to give consistent results. It seems that the code in the rpm was switched to pin 75 but the evoscan xml was never updated to match.
I also noticed that the clutch switch and map switch request ids must be wrong also as they dont work, but the feature does, havnt found the correct request ids for those yet..
I also noticed that the clutch switch and map switch request ids must be wrong also as they dont work, but the feature does, havnt found the correct request ids for those yet..
#3
Newbie
Thread Starter
Join Date: Sep 2019
Location: Finland
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
Sounds right mate, I know I had to change the logging request if in evoscan from the default ceddymod xml. It needs to be changed to the request I'd as the rear o2 sensor when connected to pin 75. Pin 73 was used in earlier versions but wasn't able to give consistent results. It seems that the code in the rpm was switched to pin 75 but the evoscan xml was never updated to match.
I also noticed that the clutch switch and map switch request ids must be wrong also as they dont work, but the feature does, havnt found the correct request ids for those yet..
I also noticed that the clutch switch and map switch request ids must be wrong also as they dont work, but the feature does, havnt found the correct request ids for those yet..
You mean when logging with ceddy efi setup in evoscan the id's are wrong for 3bar map? If so, have you figured it out? I'mma try check some of those over the weekend. You run SD or MAF?
#4
Sounds right mate, I know I had to change the logging request if in evoscan from the default ceddymod xml. It needs to be changed to the request I'd as the rear o2 sensor when connected to pin 75. Pin 73 was used in earlier versions but wasn't able to give consistent results. It seems that the code in the rpm was switched to pin 75 but the evoscan xml was never updated to match.
I also noticed that the clutch switch and map switch request ids must be wrong also as they dont work, but the feature does, havnt found the correct request ids for those yet..
I also noticed that the clutch switch and map switch request ids must be wrong also as they dont work, but the feature does, havnt found the correct request ids for those yet..
9 = binary: 1001 and 25 = binary: *00011001 indicating in BOLD is the mapswitch
For clutch switch you need to log Port A on address B0
Last edited by rjwkerkhof; Sep 17, 2019 at 03:24 AM.
Thread
Thread Starter
Forum
Replies
Last Post
EVO8_PR
For Sale/WTB - Engine / Drivetrain / Power
3
Jul 7, 2006 03:17 PM