My plan is to make the RadioBoard to be real, look also VemsFrontier/Bluetooth
I got Volvo Amazon with B20.
FuelCalc question: should TPS have anything to do with pulsewidth when using MAP based control? I have simulated V3 and noticed that TPS makes pw higher or lower while rest are the same. It should not, or should it?
Example: (warmup=100%, ego=100% (off), barom=100%, accel=0, kPA=30)
- TPS 0% => pw 1,7mS
- TPS 11% => pw 2mS, this is the right calculated value!
- TPS 45% => pw 2,6mS, more tps makes no difference, but with higher rpm tps up to 60% makes pw longer.
Have you made sure that both hybrid_rpm settings = 00 ? Yes they are. Even if they aren't, I think tuning view follow dot move when tps changes, right?
Also noticed that with megatune 2.20, at tuning view (current) VE value does not change but realtime view VE value does change!
Isn't fuelcalc pretty much like this: PW = REQ_FUEL * VE% * MAP% * E + accel + Injector_open_time
Everything else is working as they should, accel/decel works, pw changes according to fuel map, but there is just some weird tps coefficient! So pleeeease tell me what weird is going on! Anything, anyone?