Hi Guys,

With the ability of Map swicthing on the horizon, I was wondering if anyone has looked into having some sort of indicator in Evoscan? I am setting up a carPC, and want to be able to see which map is in use.

Thanks!

Jason

 

you can log the ADC_0F at MUT83 to monitor voltage 0 is one map anything over voltage set point is another. This is for V5 anyway.

 

logging MUT83 (Request 83 in evoscan) will give you the input signal value. It will be a value between 0-255, with 255 equaling 5 volts. To find the input voltage, take the number value you are logging in evoscan for Request 83 and enter into this formula (5/256)*(number value in datalog). So if you are seeing a value of 221 in Evoscan, (5/256)*(221) = 4.31 volts at the ADC input.

 

Thanks!!

 

I thought MUT83 showed the RAW ADC0F value? so 3volts equals 153ish..

You can setup a new MUT request to log 0xFFFF8425, if its 0 then you are on standard maps, if its on 3 then you are on altmaps.

I am pretty sure anyways - just try and see

Cheers
D.

 

Ahh, its been a while. I know was the raw and one was the active/inactive 0/1 values. It would be good to find out exactly what it is for everyone, would make troubleshooting a LOT simpler.

 

When Tephra's and my patches are combined you'll be able to make your own "MUT tables" to log anything you like. The MUT tables will be able to be loaded into RAM in the ECU if you have space, so you won't even need to reflash to log anything you like, whenever you like

 

Just to make sure I understand...



In my case, I changed 04 (16x3f314) to 8425, Then in EVOScan, I added an entry for request 04... Does this sound right?

Thanks!

Jason

 

16x3f314 looks like a 1D table address, not a 16bit hex value to be entered into a 3D MUT table?

 

Sorry if I was confusing.. I meant that as X,Y axis on MUT Table (like how the 2-byte load/rpm/airflow is setup). Instead of using the airflow, I just used that address, which used to be 89F6 and changed it to 8425. Then I created an entry in EvoScan to read RequestID="04"

And No, its not a 3D MUT Table. I just started reading up on that. I'm sorry I should have read more before wasting everyone's time.




PS. There shoulda been a pic above. Gotta love imageshack

 

Ahh, the pic really helps,lol. Yeah that looks good but 8425 might only work for ROM 94170014. 0x8929 should be in MUT83 already and SHOULD work when datalogging Request 83 in evoscan. MUT83 is the input voltage level. It registers in bytes from 0-255 with 255 = 5.0 volts.