Sorry to repost but I thought that it was easier. These runs are all from the same log files. You can see the power suddenly fall off on the first graph.

 

I will send you the logs and make a donation. Thank you for your time.

 

are you hitting the rev limiter in your log? if so try cutting that portion out of the log and see how it reacts in VD

 

I am not hitting the rev limiter. I have it set to 8000. I was putting some different logs through the program and if the log doesnt go over 6800rpm it does not seem to drop off. I had one recommendation to try revving out farther as well. I will try that once I get the new turbo on, but it seems like that should not make a difference. I don't know though and will have to try it out.

Here is an example of when I did not rev it out all the way and a few when I revved it out more. I had the methanol off and was playing with cam gear settings/timing so the power was already down but the drop off did not happen. The ones that I did rev out do not show the drop when put into other programs.

 

I do a lot of testing with VD from many different car (just like mellon) and I dont experience drop offs like those.

I would suggest trying to revving it out more.

Also, this is a prime example of why there is a RPM trimming feature.

 

I will try reving it out more once I get my car back together. Why would a RPM trimming feature be needed? I am not hitting my rev limiter. It only happens when revved out past 6800 and doesnt on Virtual Dyno Room Simulator, Dynovision, Virtual Dyno 1.06 or a dynojet.

It doesnt make sense to me but I can show it happening only on the VD 1.07/1.08 program. I do not know what I am doing wrong. Maybe I can send you my logs and you can put them in to see if it is just my computer...

 

Since these power calculation work on averages, when it gets near the end of the pull, sometimes the averages can get "screwy" just be cause the data is stopping and that affects the averaging process. VDR even has the rpm triming feature.

So when this happens, you use the RPM trimming feature to eliminate the "screwy" end part. Like so..



Next, I know for sure that 1.0.7/8 is more accurate then pre 1.0.7 versions.

You say it doesnt do it on the dynojet, do you have a current dynojet chart and that exact log ran though VD??

Also, there may be a way for Brad to fix this drop off, but for now, I recommend ...

-revving out much further then you want the dyno plot to go to ie. you want the dyno plot to go to 7200rpm, then rev out to 76-7700rpm.

-Use the RPM trimming feature.

 

I am using the rpm trim feature If I do not it looks like spagetti until about 2500rpm.

It should not be showing a 50hp drop in 400rpm that others do not.

I do have the exact log files that I entered into both 1.06 and 1.07 and got the drop only on the 1.07 runs.

I will have to dig up my dynojet run. I made 445whp. I am out of town right now and will be back on Mon. to dig it up. I will post it up for reference vs. the other graphs. I did not log the car while on the dyno but the setup had not changed until I just blew my turbo.

Why wouldn't it show up on 2 others or an older version with the same logs? Why does the run that stops short of 6800 not drop off? I would expect some consistensy btwn programs

I would love to send you my runs. Please enter them into multiple programs and let me know what you find. It does not make sense to me.

I would think if there should be a drop off it would show up in multiple programs. This happens in any log I put in at anytime of the year. I will get off my soap box and simply use another program. I do not mean to cause an issue.

 

Yea I dont know why your graph falls off like that. Mine doesnt do that. It just reads lower than the old version read.

 

Answers in bold.

Last, your not causing an issue, and we would like to see you keep using VD. Like I said, you may have a logging issue or there may be a fix that Brad can implement to fix this issue.

 

I appriciate your help. I have logs that basicaly only consist of WOT ( as close as I can) and it still happens. It just seems to me that if three other programs are giving me the same basic curve and a fourth is saying differently btwn 6800-7400rpm. It makes me think that the fourth is off.

Let me know if you find anything in those logs I sent you that would cause the drop off or if you are not getting the same drop I am seeing.

I would love to know why this is happening.

 

Okay. Me and Brad are working on this issue right now and trying to find a solution.

 

Thanks again to both of you. Since no one else seems to be experiencing this... I think I might just have to put my computer down like old yeller.

 

Something I wish your software had.

private bool hptq_MouseMoveEvent_1(ZedGraphControl sender, MouseEventArgs e)
{
// Save the mouse location
PointF mousePt = new PointF(e.X, e.Y);

// Find the Chart rect that contains the current mouse location
GraphPane pane = sender.MasterPane.FindChartRect(mousePt);

// If pane is non-null, we have a valid location. Otherwise, the mouse is not
// within any chart rect.
if (pane != null)
{
double x, y, y2;
// Convert the mouse location to X, and Y scale values
pane.ReverseTransform(mousePt, out x, out y);
pane.ReverseTransform(mousePt, false, true, 0, out x, out y2);
// Format the status label text

if (pane.Title.Text == "HP/TQ")
{
this.label2.Text = string.Empty;
this.label1.Text = String.Format("RPM: {0:0.00} HP:{1:0.00} TQ:{2:0.00}", x, y, y2);
}
else
{
this.label1.Text = string.Empty;
this.label2.Text = String.Format("RPM: {0:0.00} AFR:{1:0.00} BOOST:{2:0.00} TIMING:{2:0.00}", x, y, y2);
}
}
else
{
// If there is no valid data, then clear the status label text
this.label1.Text = string.Empty;
this.label2.Text = string.Empty;
}

// Return false to indicate we have not processed the MouseMoveEvent
// ZedGraphControl should still go ahead and handle it
return false;
}


If you place a label somewhere on the graph, you will be able to just move your mouse over the values ont he map and see what they are without having to click on the nodes. I created lables in both the HP/TQ map and the AFR/Boost one. Enjoy.

 

Here is how I did dyno jet style text results.

// Add the Text
TextObj text = new TextObj("█", 0.25F, offset, CoordType.ChartFraction, AlignH.Left, AlignV.Center);
text.FontSpec.FontColor = primaryColor;
text.FontSpec.Border.IsVisible = false;
text.FontSpec.Fill.IsVisible = false;
text.FontSpec.Size = 14;
myPane.GraphObjList.Add(text);

text = new TextObj("█", 0.26F, offset, CoordType.ChartFraction, AlignH.Left, AlignV.Center);
text.FontSpec.FontColor = secondaryColor;
text.FontSpec.Border.IsVisible = false;
text.FontSpec.Fill.IsVisible = false;
text.FontSpec.Size = 14;
myPane.GraphObjList.Add(text);

text = new TextObj(String.Format("{0} Max Power = {1:0.00} Max Torque = {2:0.00} Boost = {3:0.00}", Path.GetFileNameWithoutExtension(vi.Vehicle.LogFil eName), peekHP, peekTQ, peekBoost), 0.28F, offset, CoordType.ChartFraction, AlignH.Left, AlignV.Center);
text.FontSpec.FontColor = Color.Black;
text.FontSpec.Border.IsVisible = false;
text.FontSpec.Fill.IsVisible = false;
text.FontSpec.Size = 14;
myPane.GraphObjList.Add(text);