yes i tried that but when I unplug the sensor, the readings don't change. I only tried setting this gauge up without the car running, only in key on mode. wondering if that matters??
Printable View
well with my snap-on brick scanner I'm able to see the charge air temp and with key on only it reads fine and when unplugged there is change in reading, so still not sure why I can't get it to work in MP Scan dash layout so I can log it. But on a positive note i figured out that the charge air temp sensor is a 0-5v range and 5v is full cold while 0v is full hot and 3.14v was about 55*F and using a heat gun on the charge pipe the voltage started dropping as the temp on the scanner rose.
Worked on a new dashboard layout last night, going to try and see if I can get CHGVLT to work with MPscan today. One thing I noticed is there is no address for charged air temp value, only voltage, but don't know if it's the raw data or converted channel? Also
going to snoop around in the sbecII since they are close and see what addresses are used there and see if i can find something to help me, if so how do I change ram location addresses? Is it the same way as when you make your dashboard when you populate the ram info, just change the ram info there?
turbo joe, i looked at the t-t3_22_t3_mtx cal and rob has set up these 3 variables:
1) ChargeTemp 0x7d (125D)
2) LastChargeTemp 0x8e (142D)
3) AmbientAirTemp 0x90 (144D)
in mpscan you would need to make sure you are using the SBEC TIII ecu, correct? i would try logging all 3 gauges just to see what you get for results, but my best guess would be to use #2 above based on looking at the code which stores all ecu reads initially to address 0x8e. if that works and you want to see degrees, then go back into mpscan and open up the layout file called xref settings. scroll down to the gauge called ChargeTemp (CHRG) and in the TIII column change the -1 to the decimal number shown, e.g. 142.
let me know how this works.
I don't have my computer with me, but I'll try to help.
If you make a change to the ram setup, the point will go into the user gauge list.
You should be able to edit the settings to convert to a temperature, or you may be able to do the conversion in your gauge config when you add CHGVLT to your layout. There is a divisor setting and i'm thinking you could use that to convert to temperature if you knew the constant to convert. Or, it may be simpler, by just using different ecu min/max values in the ram setup to display the values in temperature.
When in the user gauge list, you can change name to ChgTmp or something as well.
Morris might be able to chime in to provide the correct numbers to set your gauge to read temperature.
I think this should work, as i don't see why it would be different than the analog input gauges he added. But, i may be overspeaking.
If 3.14v = 55F, what does 5v, and 0.1v =? From that i think a math geek can solve for the constant if the resistance/temperature is linear.
Its been a while since i had to do math, or think whatsoever...
You could easily check with a hairdryer and a thermometer for linearity of the tempsensor, no? In case of non-linearity we could easily figure out some approximation formula (adding some ofset or factor)
Sorry Morris, you must have been replying as i was, i hadn't seen the reply when i butt in!
Joe you can disregard most of what i said.
yes this is true, the scale is NOT linear at all.. I will try using my brick scanner since it tells me voltage and converted temp to map out the scale so maybe wowzer can figure out a way to make a conversion thing to use in MPscan or anyone else can map out a scale manually themselves with the info
TJ - mpscan already uses a non linear scale using the function sets i mentioned earlier. if you have downloaded the most current layout file for it you will see i have set 3 of them up including one for the charge temp sensor based on actual chrysler info. to get it to work you need to do what i said in post 505. however, it would be interesting to see real world feedback which you can then enter into the function set table, ie. change the values to represent what you see.
ok I'll see what i can do to help with that.. on another note I found some info that i need to verify about that scale, a volt scale and a resistance scale, I'll try to test this out today, but a family member is having a baby so I spent all of yesterday evening until 5am at the hospital, hopefully i can get something done but the arrival was delayed until today so I'll most likely not be able to do much.
Does anyone know if MPScan actuator tests are supposed to work with the vehicle running?
I swapped in a FWDP Stage 3 SBEC today and the radiator fan doesn't come on anymore. While testing, I noticed the actuator test with key on, engine off, cycles the cooling fan relay, but with the key on, engine running, it does not.
Edit: Nevermind, apparently the fan motor took a ---- between the last time I drove the car and when I installed the new stuff.
Unless you know that for sure, maybe not.
The actuator tests in MPScsn should be performing similar function tests the DRBII performs (although i have never tried with MPScan).
These tests are performed with the vehicle not running, but the ignition power needs to be on.
Try this again if you want to test your fan and fan relay. If you suspect a bad fan (hear your relay clicking but fan doesn't start ) try powering your fan with jumper wires off the battery. Thst will at least determine if it is the fan, or the relay.
That's what I did. After the actuator test showed me the calibration wasn't screwed up and it would at least cycle the relay, I started tested and determined the fan motor would not run when direct power was supplied. I replaced the motor and repeated the actuator test with success, it turns on and off. The only issue with the actuator test is you can not cancel the test without cycling the key. It will just keep cycling the relays without end. Even closing MPScan won't stop the test. But I'll gladly deal with that over not having the test in there. Thanks for everything you've done Wayne.
Just glad you got it! You did all the hard work! ;) My stuff usually stays broken way too long, so I'll always try to help others if i can. And glad to hear your fan motor was easy to remove. You got lucky!
I think Morris (wowzer) has mentioned the actuator tests might not be 100% yet. I've never tried them before since i have a drbII, but its good to know they generally work even if a bit tricky.
i think there might be a "special" way to end the actuator tests that i read about somewhere! i'll need to hook my drb2 back up and log the protocol. actually, should do ALL of them! i wrote the routines before i had the drb2 and saleae logic analyzer.