No Device: HD/Delphi EFI Tuning Basics
Road Master
Joined: Feb 2014
Posts: 804
Likes: 237
From: TN
Steve / Gordon61, it does show what ever the pv software has logged. Here again there are no cells that do not have at least 1 decimal, example 100.47, 100.5, 100.06 etc. There is a bizarre twist though, you can adjust the map axis to the pv map points, they also have decimal points, but the rpms you can't. Pv set rpm points are every 125 rpm from 875-3000, then every 500 from 3000-7000 and then 7000/8000. The WinPep 8 uses decimal point numbers like 2.475842, 2.649158, 2.822474 etc. When you try to scale them to the pv rpm points you lose the data, they even have a couple of extra rpm points that the pv doesn't have, after that it's a headache to remove the program, search out some hidden files for setup, and then reload the app back in. I've tried 3-4 different ways with no luck. So I don't know if the numbers shown in WP 8 can be trusted.
Thread Starter
|
HD EFI Guru
Joined: Jan 2008
Posts: 4,494
Likes: 4,779
I hate to say it but as long as PV knows what it is doing to the numbers it can work within those rules, but a third party program doesn't have a chance, unless it too knows what has been done to the data first. There are way to many things that are possible, to spend the time to figure out what they are doing, so unless one of you can get an answer from the source we would all just be guessing. This is just one of those little things that can really screw with you when your trying to look at what is really going on.
As I said before it could be some sort of running average of the raw values that are coming in. I myself prefer to work with the raw data so I do not have to worry about it.
As I said before it could be some sort of running average of the raw values that are coming in. I myself prefer to work with the raw data so I do not have to worry about it.
Thread Starter
|
HD EFI Guru
Joined: Jan 2008
Posts: 4,494
Likes: 4,779
So when you guys tell me it looks this way or that way in a third party software means nothing as what your using to start with has already been changed from what it really is.
Road Warrior
Joined: Jun 2015
Posts: 1,325
Likes: 140
From: Edinburgh UK
I get the point about one person using their tools to look at data and everyone else not necessarily knowing what they are looking at (there have been one or two examples of late on that (cough))
But PV or TTS build logs by capturing data. What they capture is maybe debatable - is it an average since last time or is it the value currently in the ECU buffer ...who cares ...we are not getting all of the data anyway so we would have to interpolate in our head (or third party piece of software) anyway
Pulse width for example, what use is capture one, lose 20, capture 1, lose 20
The log is what it is and has to be analysed with that in mind. PV logging 14 samples per second ...fair enough, all you get with that is a trend
no?
But PV or TTS build logs by capturing data. What they capture is maybe debatable - is it an average since last time or is it the value currently in the ECU buffer ...who cares ...we are not getting all of the data anyway so we would have to interpolate in our head (or third party piece of software) anyway
Pulse width for example, what use is capture one, lose 20, capture 1, lose 20
The log is what it is and has to be analysed with that in mind. PV logging 14 samples per second ...fair enough, all you get with that is a trend
no?
Thread Starter
|
HD EFI Guru
Joined: Jan 2008
Posts: 4,494
Likes: 4,779
I get the point about one person using their tools to look at data and everyone else not necessarily knowing what they are looking at (there have been one or two examples of late on that (cough))
But PV or TTS build logs by capturing data. What they capture is maybe debatable - is it an average since last time or is it the value currently in the ECU buffer ...who cares ...we are not getting all of the data anyway so we would have to interpolate in our head (or third party piece of software) anyway
Pulse width for example, what use is capture one, lose 20, capture 1, lose 20
The log is what it is and has to be analysed with that in mind. PV logging 14 samples per second ...fair enough, all you get with that is a trend
no?
But PV or TTS build logs by capturing data. What they capture is maybe debatable - is it an average since last time or is it the value currently in the ECU buffer ...who cares ...we are not getting all of the data anyway so we would have to interpolate in our head (or third party piece of software) anyway
Pulse width for example, what use is capture one, lose 20, capture 1, lose 20
The log is what it is and has to be analysed with that in mind. PV logging 14 samples per second ...fair enough, all you get with that is a trend
no?
6000 RPM needs 50 fps data rate to collect all the raw data, so whatever rate your tool is getting this should give you an idea what is being missed
1000 RPM needs 9 fps.
Last edited by Steve Cole; Aug 2, 2016 at 04:30 PM.
Road Warrior
Joined: Jun 2015
Posts: 1,325
Likes: 140
From: Edinburgh UK
HD Forum Stories
The Best of Harley-Davidson for Lifelong Riders
7 Surprising Harley-Davidson Products that Are Not Motorcycles
Verdad Gallardo
8 Best Harley-Davidson Motorcycles Ever
Pouria Savadkouei
10 Worst Harley-Davidson Motorcycles Ever
Pouria Savadkouei
Killer Custom's Jail Break Is The Breakout That Refused to Blend In
Verdad Gallardo
Crazy Bunderbike Build Looks Amazing, But Is It Impossible to Ride?
Verdad Gallardo
Harley-Davidson Reveals Super Cool Cafe Racer Concept
Verdad Gallardo
Engraved Rebellion: Inside Bundnerbike's Glam Rock II
Verdad Gallardo
10 Motorcycles You Should Never Buy
Joe Kucinski
10 Things Harley-Davidson Needs to Fix in 2026
Verdad Gallardo
Thread Starter
|
HD EFI Guru
Joined: Jan 2008
Posts: 4,494
Likes: 4,779
That said you still need to understand the limits and accuracy of the sensors! Everything is based from the sensors so if you know it can and does move around, then seeing that movement becomes easier to understand. What becomes harder is to pick out when the movement is from the sensors or something else.
Road Warrior
Joined: Jun 2015
Posts: 1,325
Likes: 140
From: Edinburgh UK
So putting CLI and AFF and sensor latency and accuracy to good use, what are we looking for or hoping not to see
What are we looking for? FP3 doesn't show CLU/AFF yet, are they worth looking at,
Or are we not ready for examples yet
What are we looking for? FP3 doesn't show CLU/AFF yet, are they worth looking at,
Or are we not ready for examples yet