I have an Xtreme Hulog and I've been trying to do some datalogging. I've tried Freelog (PGMFI's datalogger) and Bre's built in data logger. I'm still OBD0 right now. Anyways, I can't get Bre to datalog at all. It says 'Logger has timed out.' When I use Freelog, the numbers are INSANE. The Tach jumps from 2k to 9k on the screen, the MPH goes from 0 to 180. Temps are flying, the list goes on. The datalogging is just jumping every which way.

Could my datalogging header that I soldered in be upside down?

Here's the datalogger:
1 2 3 4 5 (Datalogger header is on 1-4)
B B R O
L R E R
A O D A
C W
K N

If that makes sense, I can't get a photo right now. Pin 1 has the black wire, pin 2 brown, pin 3 red, pin 4 orange. Should my pins be the other way around for the hulog wire colors? Or does it not matter at all which way it goes? I'm just trying to get my datalogging to work so I can keep track of certain things obviously, and I want to give the vitrual dyno software a shot.

 

Googling doesn't offer a lot of visual reference on datalogging headers. And there aren't a lot of write ups on this, that I've found. Maybe I overlooked it in the FAQs.

Read the FAQs. I think mine is a hardware issue though. I will continue to try and get this to work. Maybe I'll get a different version of the software.

 

The wires are correct. I think you should focus on googling other operations. Virtually every Honda datalogging problem and solution is already documented in the PGMFI.org forums.
I assume you're using either a PW0 or PR3 ECU. If not, I'm not sure why you're trying to datalog with BRE. Most likely your ROM is not programmed with the correct plugin. Or, you may be using the wrong port settings/driver.

 

The wires are right? Okay! I thought I soldered in the connection upside down. That's all. I will check out the forums and find my solution. I run into this sometimes. I get worried I messed something up and don't want to continue my software search if I have a hardware issue.

 

I had way too many problems with OBD0 (Ecu not working after changing out the Rom chip, not wanting to log, not wanting to even start period). In the end I just ditched it and focused on OBD1.

 

Yea man, If I were you I would just go OBDI man. There seems to be a lot more support for it.

 

I am going OBD1 for my turbo set up, don't get me wrong. But I am just testing a couple easy things and I wanted to get some datalogging on the completely stock motor with a stock ECU. I was going to try and get a couple decent pulls in and use the virtual dyno to compare.

I'm just having fun with the OBD0 stuff.

 

Originally thats what I thought too since I had 4 OBD0 ecus laying around. After a while of zero success with chipping 2 Pm6 and 2 PR4. I just gave up. Even after re-installing the stock rom, the ECU would not fire. They all just died and acted as if they were not getting any signals from the motor, Didn't even get a solid light on the ECU.

 

Well, I have definitely had success haha. But thanks for that bit of information.