You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
if all u need is to clear codes, just get a hex terminal program (look rs232 or something is a decent one) and send hex bytes FF FF EF (reply 10), then send C1 F0 (reply streams something or other), then send 30 (reply CF), that will clear the codes.
I can't get CalumSult to work w/ my box (I blame the builder ). I can get the demo of Conzult to work just fine, SRTalk works, and I think even OBD Nissan Scan connected just fine.
When I click on the "clear codes" portion of SRTalk, it says clearing codes but the CE never goes off. Just trying to do a little trouble-solving (and eliminating) on my new to me G. I bought it w/ a CE light on which didn't bother me.
I've got a Code 33 (O2 sensor), and I changed the sensor to a brand new Bosch; but I can't get the CE light to go out to make sure the sensor was the problem and that I don't have an issue elsewhere. When I view any of the programs, it says Code 33 - 15 starts ago (it did last night).
I think I'm just going to disconnect the battery for 10 minutes, and go from there. The car runs really well as it is, so I hope that code is just lingering in the memory.
This is actually the first CE light that I have had on my SE-R, NX, and now G. So I'm a newbie at this.
Whats the error from CalumSult? Does it ever detect the ecu?
In conzult, watch the o2 sensor voltage. At idle with the car up to temp it should fluctuate back and forth. If its doing that then its working properly and the code is full of crap.
Calumsult detects the ecu - I think it even says connected. I know it pops up w/ the part number. The gauges never move or show anything.
Last night, I played w/ it somemore using both SRTalk and free Conzult; and the o2 moves pretty quickly back and forth (what I consider normal) which it should since it is only 4 days old. Since one of the programs tells me the that it has been 15 starts since it was detected leads me to believe everything is ok, it just needs the memory cleared.
I had a questionable O2 in for a day, and when I pulled that thinking it was bad also - it was very light gray colored when it was black when I put it in (just to test the other one).
I wonder if Calumsult doesn't like my USB converter?
You have to turn the gauges on. There's a button in the top right corner of the guage screen. You also have to do that before datalogging btw, or you'll just log 0s.
I thought I did that, but I'll check again. If I didn't, then I'll post here so I can be publicly humilated....similar to buying a variable cam motor and failing to have it fully variably cam. This is why it says what it does under my screen name.
Well, the gauges did have me. CalumSult works just fine - atleast the portions I tried.
I used the debug option and typed the code was necessary, but still no dice on clearing the codes. I even used SRTalk again for its code clearing, but it doesn't want to go away.
I'm going to do a little bit more inspecting this weekend, and compare to the FSM for diagnosing this code. There has to be a small short or something somewhere in the system.
I'm not positive what brand of serial to USB converter I have, I'll have to check but it was just at some local computer store.
All of the gauges work fine through CalumSult and SRTalk, so I don't think it is the converter. I even had the battery disconnected for atleast 20 minutes (probably closer to 30) and the code was right there when I got back. There has to be something goofy somewhere.
Off-topic: are the 95 G20 ecus the same as the B13? I might toss in a spare ecu to make sure it isn't an ecu issue.
I'm 99% sure you are correct. After doing some searching, and then I did some more thinking, last night to get SRTalk to work I had choose the S14 ecu which I remember you saying uses the same address file as the B14, and it read the ecu. So my spare B13 ecu won't work, dog gone.
I guess now I'll have to push you on those B14 boards. Or maybe not since this is the beater/daily driver.
i have the nisdata scan fro the forum store, with a serial to usb cable, i cannot get the pc to recongize it, does it have to be in rs232 mode? am i missing something?
__________________
SHIFT_multiplication!
01. Audi TT 225
98. the zips machine
95. t28 setup
95. Celica, 3SGTE
90. Miata BP swap
The AutoGuide.com network consists of the largest network of enthusiast-owned enthusiast-operated automotive communities.
AutoGuide.com provides the latest car reviews, auto show coverage, new car prices, and automotive news. The AutoGuide network operates more than 100 automotive forums where our users consult peers for shopping information and advice, and share opinions as a community.
). I can get the demo of Conzult to work just fine, SRTalk works, and I think even OBD Nissan Scan connected just fine.
