VDHx is pissing me off - hidden pulsewidth multiplier

[Pocket]

Somewhere in the VDHx calibration there is a hidden pulsewidth multiplier that I cannot find. When my engine is fully warm (was playing around yesterday with EOT's at 190 degrees), something is adding nearly a full ms of pulsewidth at WOT. I've been kinda tuning around it for a while, but I'm getting new injectors (bigger injectors) soon, and I'm tired of my pulsewidth not being exactly what I'm asking it to do.

For example, playing around yesterday I'm in a tune that calls for a max 3.3 ms of pulsewidth. Instead, I was getting 4.2 ms of pulsewidth, and it hit that the instant I went from a throttle position holding 3ms of pulsewidth at 2800 psi ICP with duty cycle well under 40%, to full throttle. Of course, holding 4.2 ms I watched my ICP plummet and duty cycle go sky high. The thing is, pulsewidth went sky high first, THEN the ICP started to drop. So something is tell my injectors to stay open much longer than I'm wanting them to, rather than my tuning adding pulsewidth because ICP is falling.

Problem is, I have the EXACT same values on PMT1 pulsewidth multipliers and adder maps and functions (all the pulsewidth multiplier and adder tables that I know of are exactly identical), yet whatever I set for pulsewidth in the PMT1 tune, that's exactly what I get. No if's, and's, or but's.

So there's some undefined table in my VDHx definitions that's multiplying my fuel injection pulsewidth, and I don't know where it is.

Any ideas?

[907DAVE]

Could it be the Multiplier to Pulsewidth Adder in the functions menu?

This should not make a difference after 72*....... but I am not sure what temp this is based on.

Compare this to the PMT1 and there is a pretty significant difference.


:hmmm:

[Pocket]

Could it be the Multiplier to Pulsewidth Adder in the functions menu?

This should not make a difference after 72*....... but I am not sure what temp this is based on.

Compare this to the PMT1 and there is a pretty significant difference.


:hmmm:

Yeah I saw that table too, but after 17* C, there's no difference between VDH5 and PMT1. So I'm not sure how that would make any change. Could change it for gits and shiggles.

[Shaw]

Ive been fighting the same thing with PMT1. With all adders and multipliers zeroed out I still get a little over 1ms of PW at full throttle. Ive tried everything I can think of to no avail.

[cleatus12r]

It's not a problem with any hidden multipliers. It's a definition divisor error in the base pulse width map that will be fixed with the new definitions when they are available (obviously, current MDFs that you have would be replaced at no charge).

[Pocket]

So Cody, is this currently available for the VDHx definitions?

A few months ago Bill sent me an updated PMT1 definition, and I don't have the same issue as I do with the VDH5. Also the scaling is different on the PMT1 than it is with my current VDHx definitions. I much prefer the PMT1 style.

[Shaw]

So Cody, is this currently available for the VDHx definitions?

A few months ago Bill sent me an updated PMT1 definition, and I don't have the same issue as I do with the VDH5. Also the scaling is different on the PMT1 than it is with my current VDHx definitions. I much prefer the PMT1 style.

Hmm, wonder how I would go about getting the updated PMT1 definition?

[cleatus12r]

The latest is not available yet.

[Pocket]

The latest is not available yet.

Okey dokey. I guess I'll just continue to tune around it.

[Shaw]

The latest is not available yet.


Any word on this yet Cody?

[cleatus12r]

No. Don't expect anything for a few months.

[Pocket]

Matt gave me the idea to edit my pulsewidth map in PMT1, then transfer it over to VDH5. It worked, and I'm not tuning completely blind anymore.

Now I have a chance at getting these brand new sticks under control.

[cleatus12r]

Yep. The nice thing about certain definitions is that you can do that..... I had to learn the hard way with my Sniper software since some of the maps were all jacked up.


Do you still need this other tune? I got the order for it yesterday and I should have it ready by Friday.

[Pocket]

Do you still need this other tune? I got the order for it yesterday and I should have it ready by Friday.

Yes.

As of yesterday I probably don't need it, since I got a majority of stuff dialed in that I was having trouble with before I tried the PMT1 trick. But it wouldn't hurt to go ahead and have it so I can have a reference point and baseline. So yeah, I'll still take it. I'm sure it will help me fine tune a last few bits that I'm still working with, and save me some time since I don't have an emulator right now.

I still have a lot of tuning left to do with these injectors, so every little bit helps.

Thanks Cody! You da' man! Tell Bill you need a pay raise.

[cleatus12r]

What if I don't think I'm worth it?

:sigh:

[cleatus12r]

I have altered the stock file to hopefully take care of idle issues. It should give you a good starting point (but it may be a little "stronger" than stock).

If you need anything done to it, just PM me and I'll make some tweaks. It should be a good start though.

You will have mail in a few minutes.

[Pocket]

What if I don't think I'm worth it?

:sigh:

I tell you what.... you're earning it today. LOL

[Shaw]

Matt gave me the idea to edit my pulsewidth map in PMT1, then transfer it over to VDH5. It worked, and I'm not tuning completely blind anymore.

Now I have a chance at getting these brand new sticks under control.

I wish my PMT1 would work, must be nice to actually put the PW down that you want instead of having to guess all the time. :sigh:

[cleatus12r]

Don't get too upset.

I don't get to work with the right values either.

[Shaw]

I don't get upset at all, just get frustrated some times. I still am very happy with Minotaur and wouldn't trade being able to do my own tunes for anything!!!

[cleatus12r]

Here's a little hint to get the actual PW values.

Take the value you have in the map and multiply it by 256 then divide by 188.

[Pocket]

Here's a little hint to get the actual PW values.

Take the value you have in the map and multiply it by 256 then divide by 188.

It works :thumbs up yellow:

I tested it between VDH5 and PMT1 to verify.

[Shaw]

It works for me too, thanks!