RPM reading present with 1.0.36 but not with 1.0.73? Why?

[PeepPaadam]

I installed 160mm diameter and 4mm thick custom 60-2 trigger wheel to my Porsche 931 project car and used Ford VR sensor that is proven to behave well with small diameter trigger wheels. I've used it several times without a problem.

I tried cranking and got consistant rpm readings around 160-170rpm  with 1.0.36 (though with occasional trigger errors for some reason at the beginning of cranking) but when uploading 1.0.73 and using known working config there's no rpm. Why? What is the difference in rpm implementation between those two?

Cable is shielded 2wire quality one and ground goes separate from shield.

Any ideas?

[rob@vems.co.uk]

Do you mean you've used the trigger wheel before or the sensor before?
Custom 60-2 wheels are often problematic.

[dnb]

There were a few things to note when upgrading to 1.0.7x.  They are documented on the WIKI if you know where to find them...

Check that nothing has been set to zero in MT - specially things like the map and RPM indicees on the VE and spark tables.  I don't think there are any changes to the trigger stuff itself, although some things did change their name and move around a bit.

[PeepPaadam]

I have used BOTH sensor and trigger wheel with both firmwares, configs are both have been used number of times and work like a charm. Checked the variables also and all seem fine.

Maybe the shelded cable is not suitable? Though I've heard before that after upgrading from 1.0.36 to 1.0.73 there's no rpm reading in multitooth mode.

I use mostly 1.0.73 on all cars that doesn't require 1.1.x versions.

[rob@vems.co.uk]

I did ask and got told that there was more filtering in the trigger code between 1.0.36 and 1.0.73
Can you do a trigger log and see if that gives you any more detail?