First off, this is my 'tuning' setup:

Chipped P28
Ostrich 2.0
Xtreme HULOG
HP Pavilion dv9000 (2.0Ghz CPU, 2.0Gb Memory, 250Gb HDD) (Only thing installed other than what came with the computer is Crome, Freelog, and TunerProRT)
Freelog
Crome 1.5

I got Crome/Ostrich working fine now, but I cannot get my Freelog to connect to Hulog for some reason.

Baud rate/Data Bits/Comm Port/Parity/Stop Bits all properly setup in BOTH Freelog and Windows. I'm positive I have the correct Comm Port (I disconnected Ostrich to make sure). It will not pass Sanity Test, Here is what I get...

Test Port button will open port, perform loopback test & report results
Port Successfully Opened!
Transmit Event Successful!
Sanity Check failed! Cui's Datalogger code NOT detected! Please check Comm settings and Baudrate!
Port Successfully Closed!

And for Loopback:

Port Opened Successfully!
Transmit Event Successful!
Loopback failed
Port Successfully Closed!

 

Is j12 removed from the ecu ?
If not, cut it out with a small pair of snippers.

 

Ummmmm.. You did the ecu, so is it?? I'll go check.

 

Okay, that was part of the problem. Cut J12 and now its connected. But its not reading right, im idling in my garage and its says:

RPM: 0
MPH: 120
Water: 200
Air: 160
Boost: 0

 

Also a big one here, it says my o2 is 10:1, when my UEGO reads 17:1 (yes.... i know)

 

Anyone know? This **** is tripping me out, I really need to tune this!!

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Powered By Garrett &raquo;</TD></TR><TR><TD CLASS="quote">Also a big one here, it says my o2 is 10:1, when my UEGO reads 17:1 (yes.... i know)</TD></TR></TABLE>

What wire do you have your uego wired to ? The white 0-5 volt output to the primary o2 pin on the ecu ?

Did you make sure you have the latest quick datalog + rtp addon installed on the binary file you are using ?

 

UEGO goes into D14 (red/white)

Added Quick/RTP last night, after cutting J12 and it not doing anything, it wouldnt work at all with out the Quick Datalogger in the rom. I'm assuming its the latest? I just updated Crome a couple days ago to 1.5 (I had and old version from my last car)

 

Make sure freelog is setup to log the latest protocol. Details can be found on the freelog forum of pgmfi.org

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by HRTuning &raquo;</TD></TR><TR><TD CLASS="quote">Make sure freelog is setup to log the latest protocol. Details can be found on the freelog forum of pgmfi.org</TD></TR></TABLE>

X2

new version of crome & new rtp/datalog plugin+old version of freelog =
new version of crome & new rtp/datalog plugin+new version of freelog =
old version of crome & old rtp/datalog plugin+old version of freelog =

Of course you could always buy CromePro or eCtune and get it all working on one screen for under $200. If you buy CromePro get it from xenocron.com

 

Since you have the hardware already, I would suggest eCtune over Crome. For the money the software is a lot nicer.

 

I planned on getting ectune once I get all the kinks worked out of the car, lol. Just want to make sure I can learn how to tune on free Crome before I put money into ectune just to stare at the screen and be lost, like I am with crome

And thanks for the help HRTuning (and everyone else), that was the problem I had the new crome/quicklog and it didnt want that, downgraded to Crome 1.2 (as suggested in the pgmfi forums) and now it 'works'.

Still a couple issues though.. O2 stays at 17.7 no matter what (actual wideband is reading what i hope is correct a/f). MPH, RPM, etc all works on Freelog correctly now.

Also, Freelog doesnt want to 'log' it wont save any values. I drove down the road, accelerating every slowly (and no boost) through 1st and 2nd up to redline, and when I went to the temp/afr relation tab, nothing, and when i saved fuel map captures, it was just a bunch of 0's. Am I doing something wrong? Thanks

 

you are making your "learning" a lot more difficult, lol

you will have to "setup" the wideband so freelog knows how to interpret the data it is getting.

what wideband are you using?

just know that using D14 limits the wideband voltage on a scale from 0 to ~3.88. It's possible that you have the wideband setup to read on a 0-5v scale so thats another thing you need to look into.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by 98vtec &raquo;</TD></TR><TR><TD CLASS="quote">you are making your "learning" a lot more difficult, lol

you will have to "setup" the wideband so freelog knows how to interpret the data it is getting.

what wideband are you using?

just know that using D14 limits the wideband voltage on a scale from 0 to ~3.88. It's possible that you have the wideband setup to read on a 0-5v scale so thats another thing you need to look into.</TD></TR></TABLE>

Why am I making it more difficult? :D

Wideband is an AEM UEGO.

And I didn't know that about D14, I searched, and read that D14 was the place to go. Where SHOULD I do it?

 

with crome, you can only use D14 and the voltage must be scaled properly in order to read the UEGO signal correctly. Should be the same with freelog.

you are making it more difficult because its so much simpler using one program to do all the work

 

lol. true. i guess ill go search on pgmfi some more to figure out how to do the scaling

 

No problem and just noticing that you said it's stuck at 17.7, as mentioned the O2 input stops around 3.86 volts or so and with a linear scale of 0v=10 and 5v=20, that puts it at 17.7 if it's outputting 3.86 or higher. You may be able to adjust the output of the UEGO and you should be able to change the wideband scale in freelog as well.

Good luck

 

No clue how to adjust the uego, but im digging around to figure out the scaler in freelog

 

It would have software to do so. If you don't have a programmable one then using D14 is pretty useless for the scale they provide stock. You'll have to use ELD/EGR/B6 and I'm pretty sure crome's protocol doesn't allow you to log any of those.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by HRTuning &raquo;</TD></TR><TR><TD CLASS="quote">It would have software to do so. If you don't have a programmable one then using D14 is pretty useless for the scale they provide stock. You'll have to use ELD/EGR/B6 and I'm pretty sure crome's protocol doesn't allow you to log any of those.</TD></TR></TABLE>

Ah no, my wideband didnt come with any software

And I dont know what ports Freelog alows you to use. I dont think the wideband has any effect on Crome (since i dont have pro, so no datalogging, am i wrong?)

 

Well, what I meant was logging ELD/EGR/B6 aren't even an option with crome, so freelog doesn't have a way to see that info. What you're running decides what you can log, freelog is just an acquisition tool to get and display the data.

 

Ya you lost me with that one

Well I found this writeup on adjusting the o2:
http://forum.pgmfi.org/viewtop...eband

BUT, when I put o2 on voltage in freelog, it stays at 3.8v no matter what my a/f is. Am I doing something wrong?? I have the white wire (0-5v output) from the UEGO wired into pin D14 on the ECU. WTF?

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by HRTuning &raquo;</TD></TR><TR><TD CLASS="quote">It would have software to do so. If you don't have a programmable one then using D14 is pretty useless for the scale they provide stock. You'll have to use ELD/EGR/B6 and I'm pretty sure crome's protocol doesn't allow you to log any of those.</TD></TR></TABLE>

yea, i have the AEM single channel wideband and it came with no software to rescale anything and Crome does not have 5v provisions so you can use EGR/ELD, etc.

Basically, you will never get the voltage scalar right unless you A) figure out a way for crome to read 5v or B) run a different tuning program (eCtune or Neptune) which can support 5v wideband inputs.

this is the deal Garrett. You are running Crome and the only wideband input for Crome is D14 aka primary o2 sensor. This sensor can only see 0-~3.88 volts maximum (8-20AFR). Your wideband uses a range of 0-5v for the same AFR scalar. This means that freelog will never interpret the signal coming from the wideband correctly and wont display it correctly because the scalars are off.

you may want to look into the TunerTee

 

TunerTee? Is that a different tuning program??

 

just look it up on pgmfi