Scan tool ?
Ok, here's a little update...
Went out and tried again using the standard connector and finally got the injector kill test to work! I was killing them one after the other in numerical order and noticed #3 felt very different, then it actually stalled out when I killed #5. I tried again and turned the kill test off between each one and they all felt exactly the same that time. I take it this means you're not supposed to kill one after the other without turning the test off in between?
I'm glad it finally worked for me, but apparently this last guy at AE was completely wrong and was just going to waste my time and shipping costs. Another issue I'm having is the update speed. When you try to data log more than 1 or 2 sensors simultaneously the updates occur so slow the data isn't even usable. The logs are showing 2+ seconds between sensor readings during the same update, so if you're logging RP and RP setpoint the RP updates first and then 2+ seconds later the RP setpoint updates. By that time the RP has changed so the two readings really have no correlation to each other. Do you guys have this problem when data logging with the enhanced version (it does fine for me in the standard version)?
I really wish it did the contribution test too.
Went out and tried again using the standard connector and finally got the injector kill test to work! I was killing them one after the other in numerical order and noticed #3 felt very different, then it actually stalled out when I killed #5. I tried again and turned the kill test off between each one and they all felt exactly the same that time. I take it this means you're not supposed to kill one after the other without turning the test off in between?
I'm glad it finally worked for me, but apparently this last guy at AE was completely wrong and was just going to waste my time and shipping costs. Another issue I'm having is the update speed. When you try to data log more than 1 or 2 sensors simultaneously the updates occur so slow the data isn't even usable. The logs are showing 2+ seconds between sensor readings during the same update, so if you're logging RP and RP setpoint the RP updates first and then 2+ seconds later the RP setpoint updates. By that time the RP has changed so the two readings really have no correlation to each other. Do you guys have this problem when data logging with the enhanced version (it does fine for me in the standard version)?
I really wish it did the contribution test too.
I too noticed the slow readings on the RP....it does suck that it is slow I dont know why it is this way.
whats the contribution test???
they said they should have the same test's as the starscan....he said they get their list from Chrysler.....
I have had pretty good customer service from them...I don't know why they are giving you the run around...
Another issue I'm having is the update speed. When you try to data log more than 1 or 2 sensors simultaneously the updates occur so slow the data isn't even usable.... Do you guys have this problem when data logging with the enhanced version (it does fine for me in the standard version)?
I guess I also need to try my standard connector again and see if I can get it to work...
buy the tool on ebay...from autoenginuity(cheaper on ebay) and the software from autoenginuity.com
http://www.autoenginuity.com/
http://www.autoenginuity.com/
Temperature readings?
I just started playing with it. You can see just about every sensor and component on the truck. It is almost too much information, it will take a while to sort through the software. I got the full expansion, so there is everything under the sun in there.
It shows you the range of operation for each component. Some do show a setpoint, but I haven't messed with it enough to give a lot of specifics off the top of my head.
From what I have experimented with, you can actuate the different component tests such as the injector kill, ramp up idle speed, etc. With the full expansion I can even actuate stuff like door locks, dome lamps, radio volume, lift pump relay, HVAC controls, pretty much anything that is electrically controlled.
One thing I wish it did was allow you to enable factory options such as accessory delay, high idle, change tire size, etc. I was thinking about talking to AE to see if they would come out with an update that allowed you to program the factory-optional settings. But they might be hesitant to allow any programming with their software.
It shows you the range of operation for each component. Some do show a setpoint, but I haven't messed with it enough to give a lot of specifics off the top of my head.
From what I have experimented with, you can actuate the different component tests such as the injector kill, ramp up idle speed, etc. With the full expansion I can even actuate stuff like door locks, dome lamps, radio volume, lift pump relay, HVAC controls, pretty much anything that is electrically controlled.
One thing I wish it did was allow you to enable factory options such as accessory delay, high idle, change tire size, etc. I was thinking about talking to AE to see if they would come out with an update that allowed you to program the factory-optional settings. But they might be hesitant to allow any programming with their software.
Intake air temp sensor located between the air filter and turbo.
Ambient temp sensor located just behind the grill, between the driver headlight and radiator.
Intake manifold temp sensor located in the manifold (a combo MAP/temp sensor).
I think this is correct. Each injector will stay killed until you re-enable it by unchecking the box.
I noticed this also. I was trying to monitor several different things at the same time and it was very slow...even when I changed the sampling rate to as low as it would go. I was thinking it might be a RAM issue on my computer, but they do say in the User's Guide that monitoring too many sensors at once can lead to slow response.
I guess I also need to try my standard connector again and see if I can get it to work...
I noticed this also. I was trying to monitor several different things at the same time and it was very slow...even when I changed the sampling rate to as low as it would go. I was thinking it might be a RAM issue on my computer, but they do say in the User's Guide that monitoring too many sensors at once can lead to slow response.
I guess I also need to try my standard connector again and see if I can get it to work...
Maybe I should dig it out of the back room and try again…
have you guys talked to the Chrysler programmer??? I have had great CS from him(forgot his name) and Jay...they always seem like they want to make the tool better so they are glad when I call with questions.
call them back and see what you can find....don't give up on it
call them back and see what you can find....don't give up on it
Try yours again, cold case, first with the standard OBD2 connector - if that works, exit AEII, plug in the enhanced cable and interface, re-open AEII, see if it recognizes the ehanced interface
Ambient vs IAT
Yes and yes. The 3 sensors are...
Intake air temp sensor located between the air filter and turbo.
Ambient temp sensor located just behind the grill, between the driver headlight and radiator.
Intake manifold temp sensor located in the manifold (a combo MAP/temp sensor).
Intake air temp sensor located between the air filter and turbo.
Ambient temp sensor located just behind the grill, between the driver headlight and radiator.
Intake manifold temp sensor located in the manifold (a combo MAP/temp sensor).
Can you give me an example of what your readings are when accelerating hard?
Just looking as some scan info I got my Ambient temp shows to be hotter than the IAT temp. they both climb as you accelerate hard but the Ambient rises faster than the IAT. Also when I hit the jake the Ambient temp spikes. What would cause that?
Can you give me an example of what your readings are when accelerating hard?
Can you give me an example of what your readings are when accelerating hard?
I'm not sure why your ambient readings would change like that. Maybe the scan tool isn't using the correct terminology for the different sensors? The ambient reading you're seeing could actually be the IAT (sensor near air filter), and the IAT could really be the MAP/temp sensor in the manifold. I can't think of any other reason you would see ambient temp spikes?
The only time I've needed it on the truck so far was for some codes that involved a battery temperature sensor as I recall. Everything looked ok so I just cleaned all connectors in the circuit in the engine compartment, cleared the code, and the code never came back.
The Ford dealer wants about $130 to hook up a vehicle to their fancy, all knowing, all powerful scanner. I quit taking it to them for codes after taking a vehicle in a couple of times for a problem, they couldn't find it, and on a whim I replaced an O2 sensor which fixed it. I just love technology that's so fancy that no one can troubleshoot and fix it.
http://www.sears.com/shc/s/p_10153_1...ting+Equipment
Actron PocketScan™ Code Reader
Sears item# 00947049000 Mfr. model# CP9125
The Ford dealer wants about $130 to hook up a vehicle to their fancy, all knowing, all powerful scanner. I quit taking it to them for codes after taking a vehicle in a couple of times for a problem, they couldn't find it, and on a whim I replaced an O2 sensor which fixed it. I just love technology that's so fancy that no one can troubleshoot and fix it.
http://www.sears.com/shc/s/p_10153_1...ting+Equipment
Actron PocketScan™ Code Reader
Sears item# 00947049000 Mfr. model# CP9125
Thread
Thread Starter
Forum
Replies
Last Post
DSjockey
24 Valve Engine and Drivetrain
4
Nov 5, 2005 01:48 PM
SoCal-305
3rd Gen Engine and Drivetrain -> 2003-2007
17
Aug 8, 2004 11:19 AM



