alright, i have a datalogging header and usb->serialbox, the "hulog", from moates.net installed in cn3 of my pm6 ecu. and i am running a pretty much stock ng55 bin with 1.8 stock map sensor. i plugged in my ecu last night and started up my car just to see if i could get some datalogging info, and it didnt work. it seems like every site i read, including pgmfi.org says something about j12, but it is usually mentioned in the context of an obd1 ecu. so for obd0, is there also a j12 that i need to do something with, or is that just a obd1 jumper for stock/chipped settings? i am trying to use ecucontrol standalone, not through turbo edit, but if that is wrong let me know. i have the settings matching on both ecu control and the ng55 as far as com 1 38400 data rate, etc.

 

Can't help you too much withou being at home, but I do know that the setup COM setup on the ECU boards should be the same, just they are in different locations. Also you need a TLL (TTL?) to RS232 converter, else your computer won't understand the com language.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Modern91Hatch &raquo;</TD></TR><TR><TD CLASS="quote">Can't help you too much withou being at home, but I do know that the setup COM setup on the ECU boards should be the same, just they are in different locations. Also you need a TLL (TTL?) to RS232 converter, else your computer won't understand the com language.</TD></TR></TABLE>

That's TTL Type 1 to RS232

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by sanimalp &raquo;</TD></TR><TR><TD CLASS="quote">is there also a j12 that i need to do something with, or is that just a obd1 jumper for stock/chipped settings?. </TD></TR></TABLE>

I think J1 is the jumper for running the Chip only on OBD1 though. OBD0 you just have to replace the chip on board.

 

yeah. that is what the moates.net "hulog" does. it translates the serial data and converts it to usb for the laptop i am using. and the header is already soldered in correctly, so that shouldnt be the issue.

 

When the ROM was programmed was it programed with the datalogging feature in it. I'm OBD1 with Crome and you have to add the RTP/Datalogging feature prior to burning the rom. just a thought.

 

yeah in turbo edit it is the same way. i dont recall selecting a button or anything to have it turned on. it seems it is just included in the ng55 binary i was using. but i will double check that to make sure. thanks for the idea.


Modified by sanimalp at 5:46 AM 9/3/2005

 

good luck. If that doesn't work I'm not sure. I checked an old PM5 ECU and couldn't find J12 but its late here so I may just be sleepy.

 

good luck..

 

well, i gave it another shot tonight. this time i did a single map instead of dual map cause im not turbo anyway.. and car started up and ran just fine. i drove it around a little and it ran like stock, so i tried a launch using launch control and that was freakin sweet.. so i know the ecu is using the chip and my car is running great. i just dont get what i am missing as far as datalogging. i make sure ecucontrol is set to obd0 ng55 bin and i make sure the com port and all that match on the chip and in ecucontrol, and click connect and still nothing. i am using the hulog from moates.net. i am starting to wonder if i am missing a driver or something for the hulog, because i go into the hardware profile and it shows that there is a usb serial port converter, but the driver listed doesnt seem to have anything to do with moates.net or anything. and it doesnt allow me to change the settings on com ports or anything either. i am starting to wonder if i should just do it straight serial cable, because the laptop has a serial plug on it.. and i can just rig it up to go to the right pins.. but that is going to take more work on the ecu. right now everything seems to point to the fact that the hulog doesnt work on my obd0 setup. maybe i am missing something.

maybe if i disable the stock serial port it will use the usb serial port. ill try that maybe tommorow. if that doesnt work, i am out of ideas.

 

I don't know if it makes a difference or even applies to OBD0, but on OBD1 you can remove J12 to run in Full Duplex Mode. If your hardware is setup to run in Full Duplex, you'll need to do this. Read up on PGMFI.org:

http://www.pgmfi.org/twiki/bin...D1J12

It can't hurt to remove J12. If your ECU stops working, just put it back. In any case, there is probably a jumper to remove to run in Full Duplex.

 

i forgot to update this post when i figured out what was wrong.. i forgot to make sure that the usb-&gt;serial converter hulog was set to com 1 instead of whatever my computer felt like making it. so i set the hulog to com 1 and it atleast gets the guages going. i havent been able to make a log file yet.. but i only get to mess around with this like an hour or 2 once in a while.

to set your hulog from com x to com 1, in windows xp, you go to control panel, then system, then the hardware tab, then device manager, and then go into ports (com and lpt) and in there you should see usb to serial converter or something like that. then you right click on it and select properties and then under one of the tabs is the setting for setting it to monitor a different com port.

and for the record, obd0 j12 is not the same as j12 obd1. im not sure what it does but i did not need to remove it. thanks to everyone though that offered ideas.