I'm using CROME Pro 1.6.2, with the JDM P30 binary with the checksum disabled, and the quickdatalogger added to the binary. I have a copy of that bin in an Ostrich in the USDM P30 in the car and a copy of the bin in a PROM in a JDM P30 on the bench. I have datalogging working for the other relevant parameters, except I never see TPS voltage or a change in the TPS %. They are both at 0, regardless of what I do with the throttle posistion. (I have a 5K ohm pot on the bench to simulate the TPS sensor.)

I can't test the vehicle speed, gear or boost pressure logs since it isn't running well enough to move the car yet.

I see the correct voltage on the TPS signal pin in both ECUs with a voltmeter, but the datalogger is not seeing that voltage.

I am using QD2 as my serial protocol.

Any ideas as to what I am doing wrong?

Thanks in advance.

 

anybody figured this out? I'm having the same problem

 

Same problem with a simulator or same problem while in the car? Also, which version of CROME are you using?

 

ive been sitting in my car all day trying to get this damn thing to work. I'm using the latest version of crome 1.6.12. with 1.6.5 i couldnt datalog at all. now after the upgrade I can datalog now but it doesnt log the tps voltage and tps position is stuck at 26% and also throws a code 7. If i plug in my stock p28 I have no issue. So i know its not a faulty tps sensor. Ive reinstalled the ftdi drivers and reinstalled crome numerous times. Ive even tried the old 1.5.3 version of crome and still does the same thing. seems like the tps is not included in the data stream. Anybody have any ideas what it can be?

 

Use modern, supported EMS like Neptune or hondata

 

really? do you tell people that already spent money on there classics that they should buy the latest version of that car?

yes im fully aware that there is better programs to go with. Crome may not be better than its rivals but there are veterans that know this program inside and out and i need them to chime in.

 

You need to give the full details on what you have to datalog with and what settings you are trying. Or better yet a screen shot. We can assume a lot, but it helps to have all the details. Also, what edition of CROME are you using - as in Free, Pro, or Dealer?

 

I have crome pro, this is strange. sometimes it datalogs and sometimes it doesnt. when it does datalog it works just fine until i click "write" to my moates rtp then it stops working. It seems like a driver issue with the 4 pin serial connector to the ecu. Ive downloaded and reinstalled the moates driver several times. Honestly im exhausted and now i'll have to accept that I can no longer use this program. i wish i can pay someone to fix this issue for me because i honestly tried everything. what do you want me to take screen shots of?

 

Has nothing to do with it.

Crome has problems. Using a software known to work will fix your troubles. It's obvious you are learning. Learning properly becomes increasingly difficult when you have to understand how to lie to the computer to get it to do what you want. Starting with an operating system that does not require this makes learning more simplistic and takes learning how to lie to the computer out of the equation for the most part.

Good day.

 

While I agree with this, that's not what he asked. Posting nothing would have been just as effective. And part of practical learning for many people is doing things the hard way. So since you're not willing to invest in Neptune, here's the hard way.

First of all, the TPS voltage won't read correctly until the engine is running. It's just a Crome bug.
Second, make sure your TPS is wired correctly, grounded correctly (at the thermostat), and not switched with the MAP plug.
Third, which is where most people have issues, is when the TPS has been removed and isn't sprung correctly. If it's been removed before, 99% sure that's your problem.
If it continues to happen, then you're using the wrong (or outdated) datalog protocols. Gold uses QD3, P30 and P72 roms use QD2. You may need to start with a fresh ROM, since corruptions happen constantly in Crome.
If you're still having issues, then your FTDI drivers aren't properly installed or are outdated, or the ports themselves are not set up correctly.

 

I wish I knew how to do that.

Ive tried all of that and still didnt work. tps would still stay stuck 26% even with the car running. Its a weird issue. even called xenocron and still wasnt able to solve the issue. When i first purchased the crome pro tuning package from xenocron 3 years ago it was working great. after not running the program for 2 years i recently started it up and have all these kinds of issue. The only thing i could think about is formatting my hard drive. Thats not an option.


I remember when my cars were tuned on crome it was on an old laptop running on windows xp. I knew I needed a laptop dedicated for tuning. So i went on craiglist and bought an old windows xp laptop from 2006 for only $20. format the harddrive on this one, updated it with latest version of windows xp, reinstalled crome 1.6.12, reinstalled moates drivers, bought a new license and now I have 0 issues. will issues that I know how to work around. Not like some weird voodoo **** thats been happening to me 0 issues with that.

seems like crome cant run on my flawless windows 7 laptop. so a buggy software needs to run on a buggy os to run perfect? :p whatever, im no computer wizard but this is how i solved my issue. If i ever had issues again in the future i'll just do a system restore to this point.

 

That's not the issue. My dedicated tuning laptop with Windows 7 runs CROME just fine. You probably have some type of malware or virus. I don't use it for anything else just to avoid those issues (which is the whole point of having a dedicated PC for tuning in the first place). OR maybe I am just that lucky, which I HIGHLY doubt.

 

ahh i wish i knew what was the real fix was and i dont think i'll ever find out but I do have alot of programs installed on my personal laptop. each one of them works except crome pro. But i did read on pgmfi.org that it is advised to have a laptop dedicated just for tuning. thats what i did, just did 30 mins of logging on my slow *** windows xp laptop. But there is a huge relief that if were to drop the laptop or if it gets damaged all ill be losing is a $20 laptop.

 

some windows 7 systems dedicate bluetooth or other components to a specific port which can interfere with communication. you may want to manually change the port, and make sure the settings are correct as explained in my manual.