In VCM editor dose anyone know why the graph displays wildly different values in comparison to the chart gauges or channels? I am logging a 2021 mustang gt pp.
Printable View
In VCM editor dose anyone know why the graph displays wildly different values in comparison to the chart gauges or channels? I am logging a 2021 mustang gt pp.
Would need to see your exact example but usually the channels data is showing you the actual last value received and graphs/gauges are interpolation more between data points. Also could be using a different channel with a very similar name or could have more/less resolution than the one you're comparing to.Quote:
Originally Posted by 2021mustangGTPP
The data is delayed, and then, apparently, there is processing time in HP program. So for me, misc data can easily be a half sec off compared to other data.
When I first got HP I was getting a total engine shutdown at the 1-2 shift at full throttle. I think, oh crap, I killed it! Then it recovers a second or so later. Rpms were well below the limiter, fuel psi good, no codes, no clues... So wth is it??? Turns out it was hitting the limiter, but HP couldn't see it, it's too slow. The dash gauge was also too slow because it also gets the data digitally. It was better than HP, but still delayed and still below redline. I figured it out when I raised the limiter and the problem went away, because what else could cause that other than the limiter.
I then discovered there were two rpm channels, so I put both on the screen, plus the digital read on the far left in Channels. Well, you see how far off everything was. The colored arrows connect the PID in Channels to its gauge, so even that is fubar. In the pix the top channel (white arrow) read higher, but moments later the other channel was a good 300 higher. Basically the quicker the rpm change the further off they get from each other, and no clue which is closer to the truth. In this example I can only assume rpms were somewhere between 5000-6200?
Spark retard from ping is another good example; I made a ping retard alarm out of a gauge in HP to let me know when it happens, but when I see it I have to go fwd quite a bit from that moment before the data shows up in Channels to see which cyl and by how much. Then I wonder how do I compare that to spark, rpm and load if I have no clue where any of them actually are in that moment? So all I can do is make a spark timing adjustment and see what happens.
Attachment 145531
Did you play with polling frequency?
It's maxed. If I recall correctly, the default on RPMs was already 10ms. That tach error was a surprise, even with my low expectations. My guess is it's the best the ecu can do, but maybe it's worse because some stupid engineer tired to make the tach move more smoothly and dampened it. I've seen worse ideas so it wouldn't surprise me.