making basemap for dohc zc

sakpase · Post by **sakpase** » Wed Jul 02, 2008 10:52 pm

This car ran on turboedit @ 5psi I know it can do more which is why i've switch to OBD1. DOHC ZC all stock T04-B 63 triim DSM 450's FMIC P06 everything is in except for the O2 sensor, in making the base map I pretty sure I choose Po6 for the ECU type but what do I choose after that? I don't see my motor, what's the next best thing? addition of the ZC would be nice, I hope I'm not the only one. Also my injectors are the black tops. I can't remember which ones are the newer ones, BlueTops or BlackTops.

Bindegal · Post by **Bindegal** » Thu Jul 03, 2008 3:03 am

By ZC you mean the old brown-top/black-top ZC1 or D16A1? I can never tell, as some people call more or less every Honda motor out there \"ZC\". So maybe IÂ´m not the only one without a Vtec engine of my own in here?

IÂ´m running a ZC1. And well basically, you just tune it. ThatÂ´s what the software is for. ItÂ´s a nice simple engine to work with, although I have found it hard to find MBT for some reason. It still soldiers on, although it needs a new headgasket now. For a 22 year old, unopened turbocharged engine I couldnÂ´t really expect more from it. Remember though, the OBD0 distributor you used for Turboedit cannot work with OBD1. /Allan

sakpase · Post by **sakpase** » Thu Jul 03, 2008 8:15 am

Bindegal wrote:By ZC you mean the old brown-top/black-top ZC1 or D16A1? I can never tell, as some people call more or less every Honda motor out there "ZC".

My valvecover is black and has B-series type acorn nuts to hold it down. this is the jdm motor that I shouldn't have bought but I did. I know cause I could only use a TD43-U distributor to upgrade to OBD1.

Bindegal wrote:IÂ´m running a ZC1. And well basically, you just tune it. ThatÂ´s what the software is for. ItÂ´s a nice simple engine to work with, although I have found it hard to find MBT for some reason. It still soldiers on, although it needs a new headgasket now. For a 22 year old, unopened turbocharged engine I couldnÂ´t really expect more from it.

but what stock rom should I start with. I've read on here that If I start with the wrong one I will have more work to do because of the differences in ROM's. Do I at least need to choose something with Dual Cams to be close to start with?

RoadXY · Post by **RoadXY** » Thu Jul 03, 2008 9:47 am

Bindegal wrote:So maybe IÂ´m not the only one without a Vtec engine of my own in here?

Your not. Running an D15B2 and an D16A6 shortly

sakpase · Post by **sakpase** » Thu Jul 03, 2008 6:52 pm

i got everything hooked up, I just went with the P06 as the motor but couldn't get the ecu recognized so i restarted XP and now i get message 004h. I've read that it means that an unauthorized pc is trying to run eC, but that's not the case I'm still using the same computer. ARrghh maybe somebody has a very simple solution to this one P.S. I also get an \"A4\" message at program startup. my only option is to hit OK. is this normal.

Garrett · Post by **Garrett** » Thu Jul 03, 2008 7:32 pm

Calvin make the ignition map for ZC DOHC (P29) in eCtune use it, add the boost tables, et tune your fuel/timing maps

sakpase · Post by **sakpase** » Thu Jul 03, 2008 9:21 pm

Garrett wrote:Calvin make the ignition map for ZC DOHC (P29) in eCtune use it, add the boost tables, et tune your fuel/timing maps

P29 huh. I have to go change that. thanks Garret.

Garrett · Post by **Garrett** » Thu Jul 03, 2008 9:24 pm

http://forum.ectune.com/viewtopic.php?t ... hlight=p29

sakpase · Post by **sakpase** » Fri Jul 04, 2008 5:38 pm

OMFG........... somebody please put down the BBQ and help. I can't get datalogging to work, I don't have a solid CEL, I'm using xenocron's serial datalogging cable, PO6 ecu, autoscan unchecked......................... I think I've read every post on here about no datalogging and still can't get this to work for me. I've checked my chipping job J12 cut I don't know what else to do I'm tired of reading plugging and unplugging........I need a beer. I've tried different calibrations but nothing, i didn't want to post without trying EVERYTHING first, and I think I have, could it be the cable? I have read that eC is more compatible with the moates cable IDK, I changed the value in the settings.xml to \"true\" but where is the result? I'm not bitching I really need some direction, I'm not afraid of diagnosing the problem but I\"m just lost now.

Garrett · Post by **Garrett** » Fri Jul 04, 2008 5:40 pm

when you upload the cal do you verify it?

sakpase · Post by **sakpase** » Fri Jul 04, 2008 6:20 pm

yes, everytime I'v tried differnt calibrations Where does this information show? I've done the below procedure

Posted: Thu Aug 02, 2007 9:02 am Post subject: Logger Version: 0019r1/ Comm trace& debug info -------------------------------------------------------------------------------- if you having problem with connect don't use auto-scan.. Also there is a switch you can turn on.. goto \\setting\\settings.xml... change Code: <SerialCommDebug value=\"false\" /> to Code: <SerialCommDebug value=\"true\" /> this will create comm_trace.txt in the ectune root. Try to connect set the right comm port and then try to connect datalogging. Send me the comm_trace.txt please.. Baud rate should always be 38400 FTDI drivers have latency(moates) zet to 6 Be sure you have USDM/EDM ecu J12 // JDM ecu j4 removed

Post by **calvin** » Fri Jul 04, 2008 6:27 pm

did you upload base rom + cal? How do you know you are running on a chip? If you disconnect ostrich do you have solid cell? http://forum.ectune.com/viewtopic.php?t=1060

sakpase · Post by **sakpase** » Fri Jul 04, 2008 6:44 pm

Yes I upload Base/Cal I just unplugged my Ostrich and got a solid CEL. I'm going to read that PDF right now. thanks........I hope

sakpase · Post by **sakpase** » Fri Jul 04, 2008 7:17 pm

I read the whole thing and downloaded the new ftdi drivers, KOEO two second MIL on 3 flashes stays off I don't have a problem communicating with ostrich my problem is with ecu through serial cable is there a way to test this cable

sakpase · Post by **sakpase** » Fri Jul 04, 2008 8:42 pm

I just ran these tests on the serial cable I purchased from xenocron: and nothing worked. http://zone.ni.com/devzone/cda/tut/p/id/3450 these instructions should be adapted to the troubleshooting guide. damn I wish I did some reading before I made my purchases. so there's nothing I can do right now without this damn cable, I can't even experiment with the WB logging

I just purchased the hulog from moates. From now on I purchase right from the source. edit: thanks for the help so far calvin, garret, bindegal.