Well with the graph and just knowing its an 01 camaro doesnt let me know if it should be making 450hp ... does it have any mods?
How much did your car make on a dyno?
Printable View
Well with the graph and just knowing its an 01 camaro doesnt let me know if it should be making 450hp ... does it have any mods?
How much did your car make on a dyno?
err, sorry:doh:
its a cam only car: 232/234 .595/.598 113
Ported FAST 92 opened to 95mm
100mm maf
102 FTRA lid
headers, etc etc etc
no u/d pulley yet
stock weight car.
never got it on the dyno. just what i know of the setup.. 440 seems about 20hp high of the highest torquer 2 cam only car.
Weight could have been a little off. Or the "flat" pavement could have been a touch down hill.
my csv files aren't detecting any wot data.. :(
i uploaded the log, wont let me upload csv..
I cant open the hpl files. I dont have HP Tuners as I would have to have every logger I support installed which would be a nightmare :)
How are the other guys uploading CSV files?
If you're using the beta, there is a bug in the latest release which messes up the data in the CSV. PID data is strewn across other columns. I have a number of the betas but I'm not going through them to figure out which have the bug.
the betas auto update also ... be specific and post me some logs to show me how you get your error to show up. Are these logs pristine or have they been edited?
Here is an exported log file, unmodified after export. As an example, scroll down the RPM column and se where there are some cells which are '1', and the RPM sems to shift to to other columns. Same issue occurs with data in the other columns.
Feh, file's too big, let me create a smaller one. OK, here's a smaller sample. Need to change the extension from txt to csv. Not the data your tool needs, but an example of the corruption. Look in columns K-Q, scrolling down you'll see that the data is shifting to the right.
yeah it seems like Ive seen this before in an HP Tuner log. This is definitely a bug in HP Tuners. Has anyone reported this to them so they can fix it? Otherwise their logger is useless
They seem to know about it because it was reported in another thread and they said to contact support. I also e-mailed them separately before I found the thread and they said it was a known issue and they'd send me an updated beta when resolved.
So they dont have it fixed yet :( boooooooo that was reported months ago.
how would i manually fix this?
I would create a new log and capture the bare minimum amount of data and export it. Then open the CSV in an editor such as Excel and manually move the data to the correct columns... it'll be tedious. Not knowing if all the data is there or whether there is duplicate data is a challenge, in addition to determining the correct column based upon the values. Perhaps you can email support to provide you with the latest build without this bug.
I cant believe they let this bug continue to be out there. It pretty much makes exporting non-existant/useless.
How often do they release a version? Every year? Heck ... mine is free and I have about the best customer service on the planet.
2.22 was released in 2008. They've only had beta versions since then... basically you deal with the bugs or you only get the vehicle support offered in 2008.
lol yeah, every year would be awesome! ^_^
You are serious about the last update in 2008?!?!? That sounds like a dead piece of software!!!
That was the last non-beta release, and they seem to be releasing updated betas fairly regularly - but you have to ask for them and you're not supposed to discuss beta problems in the forums, instead dealing with support directly.
The previous production versions (I have most of them) had been released every couple of weeks to every couple of months. Very irritating, and I'd jump ship if I didn't already have so much invested in their solution.