Uberdata problem...possibly my wiring
I've been running an SiR2 b16 in my 96 dx for the past 2 years...no problem. The ecu that came with my swap was for an A/T, so I had it converted to a manual and chipped at the same time (gay mugen proggy).
I finally feel comfortable enough with uberdata to replace that mugen chip, but a problem arises. With the Full Throttle Launch control turned on and set to disengage at 14 mph, it does not. I thought maybe I had done something wrong with the other settings, so I burned another chip disabling the FTL completely while keeping my fuel / ign maps and other misc and rpm related items the same. Hmm, now theres no constant fuel cut at 3500 rpm, but after about 5 minutes of driving (conditions are completely random) the CEL comes on.
Code 17 kids, Vehicle Speed Sensor fault. Well, that would explain the non-disengaging FTL if there were a problem with my VSS signal, but for the past 2 years running the Mugen chip, no problems. Also, the speedo works fine even when this CEL is thrown.
Beginning to get stumped now...throw the mugen chip back in, WHALA, no more code....anyone have any ideas?
(Additional information: I AM using uberdata correctly, version 1.66, open the StockGSR.bin, change all my rpm and misc settings, Save, close/reopen uber, open my saved bin, then import my fuel/ign maps...which I pulled from the mugen chip i've been running to keep everything consistent til i can figure out this VSS problem. Then save again, and burn that bin to the chip...I will include my bin file in case anyone cares to take a look....maybe I missed something)
http://www.ecimulti.org/uberda...L.bin
I finally feel comfortable enough with uberdata to replace that mugen chip, but a problem arises. With the Full Throttle Launch control turned on and set to disengage at 14 mph, it does not. I thought maybe I had done something wrong with the other settings, so I burned another chip disabling the FTL completely while keeping my fuel / ign maps and other misc and rpm related items the same. Hmm, now theres no constant fuel cut at 3500 rpm, but after about 5 minutes of driving (conditions are completely random) the CEL comes on.
Code 17 kids, Vehicle Speed Sensor fault. Well, that would explain the non-disengaging FTL if there were a problem with my VSS signal, but for the past 2 years running the Mugen chip, no problems. Also, the speedo works fine even when this CEL is thrown.
Beginning to get stumped now...throw the mugen chip back in, WHALA, no more code....anyone have any ideas?
(Additional information: I AM using uberdata correctly, version 1.66, open the StockGSR.bin, change all my rpm and misc settings, Save, close/reopen uber, open my saved bin, then import my fuel/ign maps...which I pulled from the mugen chip i've been running to keep everything consistent til i can figure out this VSS problem. Then save again, and burn that bin to the chip...I will include my bin file in case anyone cares to take a look....maybe I missed something)
http://www.ecimulti.org/uberda...L.bin
Well I traced all my wiring today, and found the bane of my evil! Thank God!
The B10 wire (VSS) going into the ecu was cut off about 16 inches up the wire harness from the ECU. I remember now when I did the swap 2+ years ago that the speedo didn't work when I started her up for the first time. Dumbass me, I guess I just cut the VSS wire and hard wired it to the speedo wire for a quick fix for a test drive and forgot to ever re-wire the VSS back to the ECU.
Being that the Mugen clone chips disable the VSS completely and don't read the sensor for anything regarding Vtec or any other engine control, I never threw any codes.
I'm heading out now to hard-wire the B10 connection back into the ECU harness and get things going....just thought I'd share my findings.
The B10 wire (VSS) going into the ecu was cut off about 16 inches up the wire harness from the ECU. I remember now when I did the swap 2+ years ago that the speedo didn't work when I started her up for the first time. Dumbass me, I guess I just cut the VSS wire and hard wired it to the speedo wire for a quick fix for a test drive and forgot to ever re-wire the VSS back to the ECU.
Being that the Mugen clone chips disable the VSS completely and don't read the sensor for anything regarding Vtec or any other engine control, I never threw any codes.
I'm heading out now to hard-wire the B10 connection back into the ECU harness and get things going....just thought I'd share my findings.
Thread
Thread Starter
Forum
Replies
Last Post




