Sorry to resurrect this thread.. but I got confused by some of the posts. The one quoted above for example.

I thought a high MIVEC value was full advance, which means valves open earlier, meaning less overlap. Let me know if I'm crazy or if the above from mrfred was incorrect.

 

full advance is more overlap, retarded is less overlap since the lobecenter tightens up. I will pull up all the math here in a bit

 

I'm a moron... for some ridiculous reason I was putting the intake and exhaust strokes next to each other in that order... lord knows why.

It just clicked and I realized duh.. it's the exhaust and intake stroke which are next to each other in that order, therefore the sooner you start the intake stroke (more advance), the more overlap there is.

Sorry for the confusion! mrfred is totally right and I was just having a brain fart.

Retard exhaust = more overlap
Advance intake = more overlap

 

So MIVEC is a true target map. If you set the intake cam off one tooth but give the MIVEC cam gear more range of motion it will still try to get to the target value. We werent sure what it was going to do when we made the mods to my car, if I was going to have to add something to the map to get the correct logged value. Doesnt appear that way for the time being.

 

"target map"... hmm, does that mean closed loop operation then?

 

It seems as though it must be. I know that everything else being equal it should be off 3.5* and yet it managed to correct and keep on track where it should be.

 

John how do you actually change the MUT request for MUT 40 and 41 (high and low bit).
Something is missing for me here.
How do I actualy find the MUT 40 and MUT41 for different ROM id`s?
Looking on the MUT table I do not see nothing.

I want to define the addresses for those bits and I do not find them or don`t know where to look for them.

For USDM 59 addresses are 3ef86 and 3ef8a.If they will change them to 0x7650 and 0x7651 they can log mivec.

How about different ROM id`s?

Thanks

 

Your MUT table should be a giant 3D map that goes something like this:

https://www.evolutionm.net/forums/ec...ic-needed.html

I would need to see a pic of your MUT table to really be any help.

 

I know what is a MUT table.
My problem is that I think that the address is not working for my rom
Here is what I have into my table for mut 40 and 41.

Thanks a lot

 

....and the requests in EvoScan are linked to 40 & 41?

hmmm, have to think about it for a sec.

 

I had a wrong formula in EvoScan John....
Thanks 4 suport mate.

I change the formula into this and I will try today...

<DataListItem DataLog="N" Color="" Display="MIVEC" LogReference="MIVEC" RequestID="40" RequestID2="41" Eval="72-0.6*x/32" Unit="deg" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0"
GaugeMax="33" ChartMin="0" ChartMax="33" ScalingFactor="1" Notes="" />

Cheers

 

I try to read mivec but I gett 72 value all the time.
Did I miss something here?

 

Depending on your version of EvoScan it depends on the formula.

For 2.4 and higher it needs to look like this: 72-(0.6*x/32)

 

Thanks JB
I will try that....

 

Seems correct but I always get 72 value when I try to log mivec.
Where is the mistake?
Request ID in Evoscan looks like this