Pending
- MAT ignition retard
- custom oil temp/pressure gauge with V3.3 and LCD
should check the relevant page, IIRC these are not yet implemented
thermfactor
no coolant temp measurement data was provided so far
because looks like it works properly,i dont need/want to modify this!
matfactor / airdenfactor recalibration
LCD displays -24..-26C air temp instead of -6 .. -8C
MAT - airdenfactor - solved appr 3 days after reasonable data was provided
See EasyTherm page, the precise testing was made with airdenfactor and matfactor that closely matches your MAT setup.
At 0 Celsius the displayed MAT is -16 Celsius. Therefore the ECM enriches appr. 6% (as it should, according to the gas-law), this must be fixed.
We really do not want to hack by raping the gas-law. Instead we fix it the proper way, with proper matfactor and airdenfactor tables. See EasyTherm.
- 3000, 287 is best (shows -2C where prev showed -16C). Added lately, better than the old 3300_270 recommendation (that showed appr. -9C at the same input). Also, the end-railing (at min and max ADC reading) was dropped in the new tables, like in default firmware because it's a dangerous practice (left over from ... guess where).
TODO: clean up history, only leave measurements that can be useful
When
- -16C (3F) is displayed, internal 43 (0x2B) value is read from adcread position 230.5 (actually, 230=>0x2C, 231=>0x2A)
- however, it should read 0C (32F, internal 72=0x48, which could be read from adcread 201)
This huge difference was identified, eg. appr 3000 Ohm sensor is used.
The sensor is a regular GM style airtemp sensor,like this one here:
http://www.034motorsport.com/product_info.php?cPath=23_30&products_id=58
Note that these measurements are taken in garage,not in a laboratory,i do not have a special equipment for this,80C measurement was made with boiling water.
Temp in Celsius
Real / LCD / DVM (kOhm) / DVM position / NOTE
0 / -16 / NA / NA /
5 / NA / 5.93 / @20k /
18 / 08 / 4.41 / @20k /
21 / NA / 2.92 / @20k /
35 / NA / 3.17 / @20k /My hand,real temp NA
80 *** / 77 / 0.322 / @2k /HOT water,real temp NA Real temp would be nice, but see below
100 / NA, would be nice / 0.200 / @2k /Boiling water w/ bubbles
The 100C point suggests an appr 3000 Ohm sensor: 200 / 152.75 * 2252 = 2948.60.
From this, we can have a good estimation of the 80C point: 322 Ohm * 2252/2948.6 = 245.93 Ohm for a standard 2252 Ohm sensor, which is appr 84.15 Celsius. This suggests we want +7.2C = +13F at high-temp (so 101C reading ment actual 108C which - if known - would have advantages for the coolant temp, but remember this is all for the airtemp at the moment).
2005-12-31 UPDATE:
tried bot 3000_270 and 3300_270, max MAT increase was 2C with 3300 (from -16C to -14C), but with this i was unable to use MegaTune, because it crashed, i think because firmware version problems ( i used the good one!!).
- upload your edited vems.hex (zipped)
- see IssueReports for the info needed for the report so it can be investigated
OK so here you go:
version v3.3
serialnr 312
firmware 1.0.19
Megatune R27
config,tables,vemshex zipped together(renamed,but used with normal original name!)
http://www.vems.hu/files/MembersPage/NanassyPeter/mcd_mct_hex.zip
Take care to copy-paste properly.
Messed up vems.hex version ?
Anyway the symptoms were the same,no MAT reading change after firmware change,
- and MegaTune said: "Controller code does not match"
- Expected:"0X32"
- Recieved:"0X3f"
This suggests you likely messed up the firmware and used a different one than you intended (used earlier).
OK it looks like Im unable to make this vemsdotini hack so PLEASE do it for me and i just copy it to my firmware directory and upload it!
btw did you ever tried this method?it worked in your car????
Answer: I suspect you might have accidentally changed controller code version in the firmware. As far as I know BG_EMULATION (the var where 0x32 version is stored) never has been 0x3F (63 decimal). So be careful that nothing else was ruined in the same mistake. The mod to vemsv3.ini is simple, Line 11, signature = 50 changed to 63 will fix this warning. But again, take care not to drive with a otherwise broken firmware
Ok thanks,i really tried it hard but im not a programmer,so please do this for me!!
Ego
Today i noticed a weird ego thing:
in the lambda table there is 1.00 at idle,and the engines current lambda is approx 1.00-1.04 BUT the ego correction is at -07 - -10.
With ego=+00, lambda would be appr 0.90 .. 0.97, so the direction is right. When lambda is leaner than configured, ego slowly (speed depends on config.ego_pid_kp and ego_lag) moves toward enriching (ego++). It's not the ego correction value (you can get any by configuration) is of interest. But the direction of change: eg. if it's leaner than configured BUT ego keeps climbing down (--), that's suspicious! (shouldn't happen).
Take datalogs if you'd like to evaluate. Trashgrade injector-match (regarding injector-opening : independent of flowrate) especially with big injectors might make it impossible to keep lambda within 1%.
Im not able to do the copy-paste properly,here is what i made,no success!
http://www.vems.hu/files/MembersPage/NanassyPeter/airXfactor/MCELLNEK.zip
PLEASE DO it for me,maybe something is wrong with windows edited files.
firmware 1.0.19
clt default
air 3000_287
thanks!