What is the factor that prevents EvoScan from out puting a real HZ number? DSM link seems to be able to do it on a similarly sized MAF. Is it the EVO ecu or is it software related?

 

If you are talking about the 1603hz cap, that is an obd-II max value. I think the dsm link changed some code in the eco so that it would cut the value inhalf before reporting it to the obd-II interface, thent he looger would double the value to get the true reading, this allowed them to et around the 1603hz limit.

 

^ correct.

l8r)