Quoted post[/post]]
blue shadow. i appreciate your response. thank you VERY much for clearing that up. so you do prefer the LM1 over the LC1? so then the Xenocron kit probably isnt the kit for me. and yes i watched the video on the LM1 and it made some things more clear to me. i just assumed that because it was the earlier version, the LC1 might be better and since on cromes site they reccomend it and on xenocron it comes with it. anyways i should clarify my setup, stupid of me not to say before, im running a 1993 Del sol with a 00 B16A2 motor, that is converted to obd 1. im running a chipped OBD1 P06 ecu that has a socketed 27c256 chip. its obviously modded for vtec but im not sure if modding this ecu for vtec and socketing the ecu means that im good to go for crome and a wideband. so in theory if i get the LM1 does this mean that all i really need is the LM1 and crome as well as any more ECU modifications i might need. and if more ecu mods are required i can just get the chipping kit from xeno and get tuning.
I have the LM1 and the thing I lke about it is the controller has a LCD readout which tells me the AFR/Lambda readout. I use this readout to tell me if my AFR in CromePRO is correct. You have to setup your wideband in Crome or Uberdata and you do this by inputting the voltage to AFR conversion number. But if you put in the wrong number your AFR might be slightly off. If my controller readout doesn't match the AFR in CromePRO's datalogger then I know my voltage/AFR conversion numbers are wrong.
I'm not familiar with the P06 because I have a P28. But if you buy CromePRO from John Cui and you want to datalog with CromePRO you need to cut a jumper wire at J12 in your ECU. If you are using Uberdata then you need to leave J12 intact. Also a datalogging cable needs to be soldered onto the CN2 jumpers. You can either solder the cable directly to CN2 in the ECU or solder a header onto the CN2 holes, and get a matching plug which you solder onto your datalogging cables. The header/plug allows you to install and remove the cable whenever you want.
Here is a pic from Keebler65's site which shows you where the CN2 jumpers are at in the ECU. In this picture he soldered the wire directly to the CN2 and he put a DB9 plug on the case. This will let you plug a serial cable such as the Superdroids cable to it. You can also get a USB datalogging cable but instead of a USB or header/plug connection you can substitute a DB9 plug and solder it onto the plug. You can use any method for installing a datalogging cable you just need to make sure you match the correct wires to the correct CN2 hole. USB datalogging cables only have 3 wires connected to the CN2 (TX-transmit, RX-recieve, and GND-ground). Serial cables have 4 wires you need to connect to CN2 (TX-transmit, RX-recieve, GND-ground, and +5V power). One other thing to keep in mind is you cant use any serial cable or USB cable. You need to get a cable with what's called a TTL module. Basically a TTL translates ECU language to laptop language. If you want to get a cable that is datalog capable contact 93turbo16 on honda-tech. Or e-mail him at
john@j-k-tuning.com Or you can contact xenocron and he can help you get your ECU datalog ready if it isn;t already done.
Quoted post[/post]]i think the thing im most confused on is how to save the info into my ECU and unplug the laptop after i complete my tuning. with the LM1 kit. does this burn my BIN into my ECU...?
again thanx for answering my questions, im looking to order the software hardware i will need within the next couple of weeks and there seem to be alot of options and alot of different ways to do this.
would hondate S200 be an option for a noob to computers like me??
It's not that hard really to get started, it seems overwhelming at first, but once you know how to do it then it's a piece of cake. Here are the steps you'll want to take to getting started on tuning. This is assuming you already have the ECU setup for datalogging like I mentioned above, and that you have the datalogging cables.
-make sure WB setup is installed properly and the controller is calibrated properly. follow instructions on engine start up and how/when you turn on the wideband. dont start the car yet
-For both burner and Ostrich setups make sure that in Crome you: remove checksum, add quickdatalog +RTP and disable knock sensor (I dont think the P06 supports a KS)
-complete making your basemap in Crome and save it. dont forget to name it
filename.bin
-if you are using a chip burner set it up and burn your basemap chip and install the chip in the ECU
-if you are using an Ostrich plug it into your laptop and set it up so Crome recognizes it. send the basemap to the ostrich
-plug in the wideband cable into the ECU and to your laptop
-start the car up. if you had to install larger injectors and rescale them in Crome hopefully the idle wont be too bad
-setup the datalogging cable in the device manager and also set it up in Crome
-open up the Lamdba View in Crome and start datalogging go back to your fuel low and fuel high to adjust fuel- actual AFR's are recorded in the Lambda View
Basically that's how the process works. If you think it's too much then you can order a Hondata and have a dealer do it all for you. But I think with Hondata moving on to the S300, it will be hard to get support on the S200. If you do decide to use Crome, then my suggestion is to first to practice making basemaps and messing with the fuel and timing tables, and options. Once you know how to do all that then later on you can focus more on how to setup the Ostrich and datalogging cable in the device manager and Crome.
First you start using Crome, once you know where all the options are then you move onto how to burn chips (if you get the burner). Once you know how to do that then you can practice connecting the Ostrich (if you have an ostrich). With the Ostrich you plug it in, set the COM ports in windows device manager, and then you set the same settings in Crome. Once you know how to use the ostrich you can move on. There is a way to verify the ostrich is working correctly by using your flash and burn software read and verify functions. If you want more info on that you I can tell you about it. Once you know how to use the ostrich then you have to setup the datalogging cable which you can only do with the car on. In order for the datalogging cable to be detected by your tuning laptop the ECU has to have power (car has to be running).
If you haven't already done so you can download CromeFREE and just start playing with it. Open up a stock file (JDM P30 would be good) and start messing with it. Go to file and save-as and name it and put a .bin at the end, this is important. You can name it whatever your want, but make sure you put a .bin at the end. The other important thing to do is remove checksum and add quickdatalog+RTP before you save it. Removing checksum will keep the CEL from coming on when you start it up with this .bin (which BTW is short for binary). Adding QD+RTP allows you to datalog with this .bin file. You also need to make sure that before you save the .bin you go into the options and uncheck/check the applicable options. For example P28's and I think P06's dont support knock sensors, because the cars these originally ran didn't have a KS. The ECU's are now modified to run your B16 which does have a knock sensor. You need to make sure you disable the knock sensor in Crome otherwise the presence of the KS in your B16 will set off a CEL in your ECU which cant support a KS.