Moates Hulog Problem on Crome PRO
Thread Starter
Honda-Tech Member
Joined: Apr 2007
Posts: 226
Likes: 0
From: VA
Moates Hulog Problem on Crome PRO
I recently purchased the Dyno Tuning Package from xenocron.com with a Crome PRO license. It came with the ostrich 2.0, the moates extreme hulog, the chip burner, annd ofcourse the crome PRO license. i installed everything correctly, following the moates guide off xenocron. My laptop connects to the ostrich just fine but when i click live tuning to connect to the hulog, it says fail to connect to ecu. i tried connecting it to different usb ports and the same thing happens. We plugged the hulog in the way the plugs matched into the header (orange,red,pink,black) We also tried plugging in the hulog plug that goes into the header the opposite way (black,pink,red,orange) What could it be?
yes, i searched. couldnt find a thing.
its 12 in the morning, i cant find a thing. My head hurts and i need answers.
please.
yes, i searched. couldnt find a thing.
its 12 in the morning, i cant find a thing. My head hurts and i need answers.
please.
Honda-Tech Member
Joined: Dec 2003
Posts: 1,391
Likes: 0
From: Somewhere in, Ca
Re: Moates Hulog Problem on Crome PRO
I found this page to be the most helpful for sorting it out. I hope it helps
http://forum.pgmfi.org/viewtopic.php?t=6116
http://forum.pgmfi.org/viewtopic.php?t=6116
ok ill give you guys step by step on what i did to get my datalogging to work...
setup/hardware im using...
USDM P30 ecu (Chipped of course w/ zif) J12 REMOVED
Moates Burner -usb cable (1.0.2154.0 port driver) be sure to update
Moates Ostrich -usb cable (1.0.2154.0 port driver) be sure to update
Moates Hulog -usb cable
Plx R-500 wideband
Ok thats the hardware im using you can find the moates stuff at http://www.moates.net very good hardware..
Ok now the procedure...first i set up my ports...
-Moates Burner port 4
-Moates Ostrich port 3
-Moates Hulog port 4 (i dont use the burner at the same time when i rtp or dl so its ok to assign same ports..)
Then i:
-open Crome
-file>new>P30 JDM (203) rom
-Plugins>Enhancements>Remove Check Sum
-Plugins>Enhancements>Quick Datalogger + RTP
-File>Save as>"whatever you want"
Now:
Using whatever burner you have...burn a chip with that bin file you saved..install the chip into your ecu (having a zif will make things 10 times easier to remove chips in and out)...turn on the car be sure it runs with no cel..then turn it off
Now: (if you dont have a romulator skip this)
Plug in your moates ostrich if you have one or whatever romulator you have...but do not plug it into the ecu, only ur laptop at this time...besdies your testing it for now..and plus u have the other chip installed in it
Then:
Plug in your datalogging hardware from your ecu to your computer, in my case i have a Hulog...the hulog if you visit the website is a small black box that connects the tx rx and ground wire from your ecu to the black box and from there a usb cable plugs into your computer..(the tx and rx lines are crossed on purpose on the hulog, so dont chang it if you purchased one..and make sure they are crossed) For anyone else using other means to connect...im not sure how the are connected..
Ok getting closer:
If you have a wideband, you should have already connected it...on the PLx R-500 theres a white wire for output...connect that to the o2 signal off the ecu wire harness ( i tapped into it using a splicer and male) and of course ground and power your wideband...
Open Crome:
-Open the same bin you burned
-File>settings>Real Time programming tab: (Skip this if you have no romulator)
-Select your Hardware type (Ostrich)
-Port setting (Com 3)
-Baud (115200)
-Data Bits 8
-Parity (None)
-Stop bits (1)
Leave the connection settings alone
TEST CONNECTION! it should say connected successfully, if not be sure your not connected to the ecu..it should load up without any connection to the ecu socket...
Moving onto the Tunner Com Tab:
-Serial Protocol (PGMFI OBD1)
-Port (Com 4)
-Baud (38400)
-Data Bits 8
-Parity (None)
-Stop bits (1)
Connection Settings leave alone
TEST CONNECTION!
-now for me while the car is off says not connected to ecu, but for some it may connect...you have to turn the car on in order for it to work...dont do it just yet..complete the rest of the settings..
-if you get a 'Bad response recieved. Check your settings' then you have the wrong port setting go back and check the right port setting.
Tunning Logging Tab:
-select the wideband you are using, if not select stock narrow-band
-dont worry about the lamda offset yet..you have to compare when you datalog with crome and the actual reading off ur wideband..
NOW push OK, should close you out of the settings window..
-Start the car, your burned chip should be in..
-Now click on the toggle tuner toolbar..its the Black RPM icon or ctrl+T
-click on live tunning at the bottom
It should now have you connected to the ecu and a box should open to the right with all the parameters mph, afr, rpm etc..
Now for ostrich: (Still should not be connected to ecu yet)
-Click the toggle rtp tool bar or ctrl+R
-On the RTP tool bar which should be above your fuel/igntion maps click 'PUT'
-Click 'Verify'..now ur ostrich is ready for rtp
Now turn off your car:
-Remove the burned chip
-Put the ostrich eprom into the ecu socket, be sure if using a zif you latch it down completely!
-turn the car back on..should run
-click live tunning agin on the bottom and now you should be all connected!
I have found for the ostrich that somtimes it wont verify or update the tables while connected to the ecu..what i have done that works is to..shut the car off...take the EPROM OUT and then load, update and verify...it usually does the trick then plug it back into the ecu...but for most of the time it works great..it just happens once in a while..also if that doesnt work...do all the above but exit crome, be sure to save if you changed anything..and reopen crome and upload or 'put' the file back and then verify..it should work and then plug it back into the ecu and you should be good to go!
Your are now ready to datalog and RTP Hopeuflly! :D
Note this is my personal experience on how to connect! so it may or may not work for you but im hoping it will!
So try it out!
setup/hardware im using...
USDM P30 ecu (Chipped of course w/ zif) J12 REMOVED
Moates Burner -usb cable (1.0.2154.0 port driver) be sure to update
Moates Ostrich -usb cable (1.0.2154.0 port driver) be sure to update
Moates Hulog -usb cable
Plx R-500 wideband
Ok thats the hardware im using you can find the moates stuff at http://www.moates.net very good hardware..
Ok now the procedure...first i set up my ports...
-Moates Burner port 4
-Moates Ostrich port 3
-Moates Hulog port 4 (i dont use the burner at the same time when i rtp or dl so its ok to assign same ports..)
Then i:
-open Crome
-file>new>P30 JDM (203) rom
-Plugins>Enhancements>Remove Check Sum
-Plugins>Enhancements>Quick Datalogger + RTP
-File>Save as>"whatever you want"
Now:
Using whatever burner you have...burn a chip with that bin file you saved..install the chip into your ecu (having a zif will make things 10 times easier to remove chips in and out)...turn on the car be sure it runs with no cel..then turn it off
Now: (if you dont have a romulator skip this)
Plug in your moates ostrich if you have one or whatever romulator you have...but do not plug it into the ecu, only ur laptop at this time...besdies your testing it for now..and plus u have the other chip installed in it
Then:
Plug in your datalogging hardware from your ecu to your computer, in my case i have a Hulog...the hulog if you visit the website is a small black box that connects the tx rx and ground wire from your ecu to the black box and from there a usb cable plugs into your computer..(the tx and rx lines are crossed on purpose on the hulog, so dont chang it if you purchased one..and make sure they are crossed) For anyone else using other means to connect...im not sure how the are connected..
Ok getting closer:
If you have a wideband, you should have already connected it...on the PLx R-500 theres a white wire for output...connect that to the o2 signal off the ecu wire harness ( i tapped into it using a splicer and male) and of course ground and power your wideband...
Open Crome:
-Open the same bin you burned
-File>settings>Real Time programming tab: (Skip this if you have no romulator)
-Select your Hardware type (Ostrich)
-Port setting (Com 3)
-Baud (115200)
-Data Bits 8
-Parity (None)
-Stop bits (1)
Leave the connection settings alone
TEST CONNECTION! it should say connected successfully, if not be sure your not connected to the ecu..it should load up without any connection to the ecu socket...
Moving onto the Tunner Com Tab:
-Serial Protocol (PGMFI OBD1)
-Port (Com 4)
-Baud (38400)
-Data Bits 8
-Parity (None)
-Stop bits (1)
Connection Settings leave alone
TEST CONNECTION!
-now for me while the car is off says not connected to ecu, but for some it may connect...you have to turn the car on in order for it to work...dont do it just yet..complete the rest of the settings..
-if you get a 'Bad response recieved. Check your settings' then you have the wrong port setting go back and check the right port setting.
Tunning Logging Tab:
-select the wideband you are using, if not select stock narrow-band
-dont worry about the lamda offset yet..you have to compare when you datalog with crome and the actual reading off ur wideband..
NOW push OK, should close you out of the settings window..
-Start the car, your burned chip should be in..
-Now click on the toggle tuner toolbar..its the Black RPM icon or ctrl+T
-click on live tunning at the bottom
It should now have you connected to the ecu and a box should open to the right with all the parameters mph, afr, rpm etc..
Now for ostrich: (Still should not be connected to ecu yet)
-Click the toggle rtp tool bar or ctrl+R
-On the RTP tool bar which should be above your fuel/igntion maps click 'PUT'
-Click 'Verify'..now ur ostrich is ready for rtp
Now turn off your car:
-Remove the burned chip
-Put the ostrich eprom into the ecu socket, be sure if using a zif you latch it down completely!
-turn the car back on..should run
-click live tunning agin on the bottom and now you should be all connected!
I have found for the ostrich that somtimes it wont verify or update the tables while connected to the ecu..what i have done that works is to..shut the car off...take the EPROM OUT and then load, update and verify...it usually does the trick then plug it back into the ecu...but for most of the time it works great..it just happens once in a while..also if that doesnt work...do all the above but exit crome, be sure to save if you changed anything..and reopen crome and upload or 'put' the file back and then verify..it should work and then plug it back into the ecu and you should be good to go!
Your are now ready to datalog and RTP Hopeuflly! :D
Note this is my personal experience on how to connect! so it may or may not work for you but im hoping it will!
So try it out!
Thread Starter
Honda-Tech Member
Joined: Apr 2007
Posts: 226
Likes: 0
From: VA
Re: Moates Hulog Problem on Crome PRO
I found this page to be the most helpful for sorting it out. I hope it helps
http://forum.pgmfi.org/viewtopic.php?t=6116
http://forum.pgmfi.org/viewtopic.php?t=6116
Trending Topics
Honda-Tech Member
Joined: Feb 2001
Posts: 908
Likes: 1
From: cc,tx, USA
Honda-Tech Member
Joined: Apr 2002
Posts: 1,351
Likes: 0
From: oakland, ca, usa
Re: Moates Hulog Problem on Crome PRO
cut the j12. i had the same problem for the longest and finally went over everything only to realize that the j12 was never cut on that ecu. once cut, connection was made, map tracing, datalogging works.
$cat /dev/urandom
Joined: Feb 2005
Posts: 3,152
Likes: 3
From: Thornton, colorado, usa
Re: Moates Hulog Problem on Crome PRO
You have to check the com port in 3 spots. First, the com port and baud defined on the burned chip in crome. Second, make sure that information matches in whatever you are datalogging in, crome or freelog or ecucontrol, whatever. Third, make sure the com port setting for the usb-serial adapter are set to match the com port settings.
second, no you will not be able to datalog if the 74hc latch is messed up. The ecu won't be able to address to the chip socket. you need to replace the 74hc chip if you think it is fried.
second, no you will not be able to datalog if the 74hc latch is messed up. The ecu won't be able to address to the chip socket. you need to replace the 74hc chip if you think it is fried.
Thread Starter
Honda-Tech Member
Joined: Apr 2007
Posts: 226
Likes: 0
From: VA
Re: Moates Hulog Problem on Crome PRO
You have to check the com port in 3 spots. First, the com port and baud defined on the burned chip in crome. Second, make sure that information matches in whatever you are datalogging in, crome or freelog or ecucontrol, whatever. Third, make sure the com port setting for the usb-serial adapter are set to match the com port settings.
second, no you will not be able to datalog if the 74hc latch is messed up. The ecu won't be able to address to the chip socket. you need to replace the 74hc chip if you think it is fried.
second, no you will not be able to datalog if the 74hc latch is messed up. The ecu won't be able to address to the chip socket. you need to replace the 74hc chip if you think it is fried.
$cat /dev/urandom
Joined: Feb 2005
Posts: 3,152
Likes: 3
From: Thornton, colorado, usa
Re: Moates Hulog Problem on Crome PRO
no, it will just revert to using the stock map that doesn't have the datalogging routine.
You can test it however, by going in to crome and setting your rev limit to 2k rpm. Then, burn the chip and insert it, and try to rev above 2k rpm. If you cant, it means it is reading from the chip.
You can test it however, by going in to crome and setting your rev limit to 2k rpm. Then, burn the chip and insert it, and try to rev above 2k rpm. If you cant, it means it is reading from the chip.
Thread Starter
Honda-Tech Member
Joined: Apr 2007
Posts: 226
Likes: 0
From: VA
Re: Moates Hulog Problem on Crome PRO
no, it will just revert to using the stock map that doesn't have the datalogging routine.
You can test it however, by going in to crome and setting your rev limit to 2k rpm. Then, burn the chip and insert it, and try to rev above 2k rpm. If you cant, it means it is reading from the chip.
You can test it however, by going in to crome and setting your rev limit to 2k rpm. Then, burn the chip and insert it, and try to rev above 2k rpm. If you cant, it means it is reading from the chip.
$cat /dev/urandom
Joined: Feb 2005
Posts: 3,152
Likes: 3
From: Thornton, colorado, usa
Re: Moates Hulog Problem on Crome PRO
Then it is reading from the chip.. Is the header soldered in wrong? Pin 1 being in the #2 slot for instance? If your datalogging header is soldered in wrong, it doesn't matter what direction you connect the cable in. Use this for reference.. http://www.moates.net/documentation....entation_id=25
Thread Starter
Honda-Tech Member
Joined: Apr 2007
Posts: 226
Likes: 0
From: VA
Re: Moates Hulog Problem on Crome PRO
im sure thats the problem, but heres the thing, im using a jdm ecu, when i was soldering in my header i looked at the usdm ecu looking at how it was soldered in (i.e. the clip was facing the numbers on CN2) maybe it was supposed to go the other way since its a jdm ecu? thanks alot for the help.
$cat /dev/urandom
Joined: Feb 2005
Posts: 3,152
Likes: 3
From: Thornton, colorado, usa
Re: Moates Hulog Problem on Crome PRO
here is another good reference just to cross check what you are doing.
http://www.scribd.com/doc/12609689/T...ith-CROME-v106
http://www.scribd.com/doc/12609689/T...ith-CROME-v106
Thread
Thread Starter
Forum
Replies
Last Post
rhd
All Motor / Naturally Aspirated
3
Nov 29, 2004 08:01 AM
