Subpage of MembersPage/MarcellGal/PowerAndTraction
See EasyTherm, EasyTherm/SensorTable for generic notes and tables.
It's very surprising that MAT stays very low all the time, only goes above 40C when the (hot) engine is stopped. It would be interesting to verify with an NTC if that is good. We'll see MAT above 200 HP.
please DO NOT FOLLOW THESE STEPS, as the EasyTherm "How to choose tables" method is MUCH simpler and faster, with the help of airXfactors.csv !
I used PTC_aref264_420 and got appr MAT=17C when real=24C
| real C | real F | real internal | MAT C|MAT F | MAT internal | ADC | |
| 24C | 75 F | 115=0x73 | 17C | 63F | 103=0x67 | 0x8A |
- The 0x8A value is the position in airXfactorptc_aref264_420.hex where 0x67 (MAT internal) lives
- Similarly, with the easy method, in airXfactors.csv in ptc264_420 line you find +17C at ADC=138 (=0x8A) column.\n
:10028000161E252D353D454E565F677079828B953C^M :100290009EA8B2BCC6D1DCE6F1FCFFFFFFFFFFFF6A^M
- Similarly, with the easy method, in airXfactors.csv in ptc264_420 line you find +17C at ADC=138 (=0x8A) column.\n
To choose a calibration curve with 0x73 in the position where the airXfactorptc_aref264_420.hex has 0x67, I did this: grep 100280 airXfactorptc_aref2*'
In the simple method, one just examines the found "ADC=138" column and finds his new precise calibration.\n
... airXfactorptc_aref260_410.hex::10028000323A424A535B646D767F89929CA6B0BA3B^M airXfactorptc_aref260_420.hex::10028000252D353D464E575F68717A838D97A0AA1C^M airXfactorptc_aref260_425.hex::100280001F272F373F475059616A737C868F99A388^M airXfactorptc_aref260_430.hex::1002800019212931394149525B636C757F88929BF2^M airXfactorptc_aref260_435.hex::10028000131B232B333B434C545D666F78818A9458^M airXfactorptc_aref260_440.hex::100280000E151D252D353D454E565F68717A838DBF^M airXfactorptc_aref260_450.hex::10028000030A121A21293139424A525B646D767F82^M airXfactorptc_aref260_470.hex::10028000000000040C131B232B333B434B545D66CF^M airXfactorptc_aref260_490.hex::10028000000000000000060E151D252D353D464ED0^M airXfactorptc_aref260_510.hex::100280000000000000000000020911192028303988^M airXfactorptc_aref260_530.hex::100280000000000000000000000000060D151D2405^M airXfactorptc_aref264_370.hex::1002800059626A737C858F98A2ABB5BFC9D4DEE989^M airXfactorptc_aref264_390.hex::100280003C444D555E666F78818A949DA7B1BBC58D^M airXfactorptc_aref264_410.hex::10028000222A323A424A535B646C757E88919AA462^M airXfactorptc_aref264_420.hex::10028000161E252D353D454E565F677079828B953C^M airXfactorptc_aref264_425.hex::1002800010181F272F373F474F586069727B848EA5^M airXfactorptc_aref264_430.hex::100280000B1219212931394149515A626B747D860B^M airXfactorptc_aref264_435.hex::10028000050C141B232B333B434B535C656D767F6E^M airXfactorptc_aref264_440.hex::1002800000070E161D252D353D454D555E677079CD^M ...
As you see (sorry about the non-proportionate font, but the bold numbers are in same column),
- airXfactorptc_aref264_420.hex 10028000161E252D353D454E565F677079828B953C (0x67 is the 17C)
- airXfactorptc_aref260_425.hex 100280001F272F373F475059616A737C868F99A388
- airXfactorptc_aref256_440.hex 100280001D252D353E464F576069727C858F99A399
0x72 or 0x73 is much better calibration. The theoretical value would be 256_430, but 260_425 or 256_440 turned out to be best match in reality. I think I will use 260_425