AE Class II - Troubleshooting
#31
Yeah had a fellow FTE member stop by yesterday from one of the Carolina's so I could run AE on his truck. Hat was a long way just for a scan tool but hey what do I know. L we took his truck out, he has 140/0 SS an stock turbo with TS tunes. His truck was cutting out every now and then . Said h replaced CPS with one from the Irish store. I am letting him try my good black spare...he said it did he trick. He didn't know the others weren't good.
Any who, he was able to keep traction on his WOT runs. We then took mine out so I could show him how smooth and quiet mine runs with the in tank mods and FRX. He also as high perdels on 2of his stick WHICH I ave had plenty of experience with. So like you guessed no could not get the rubber to stick. I eventually put it in 4 hi. Then I told him about your TCLU dual stripes which I cannot do. Not sure if it because m tranny slips, II have bigger tires, you have more fuel, more air or a combo of all of it.
Needless to say he said he will be doing some mods while he is here in OCK for 6 weeks of training.
Any who, he was able to keep traction on his WOT runs. We then took mine out so I could show him how smooth and quiet mine runs with the in tank mods and FRX. He also as high perdels on 2of his stick WHICH I ave had plenty of experience with. So like you guessed no could not get the rubber to stick. I eventually put it in 4 hi. Then I told him about your TCLU dual stripes which I cannot do. Not sure if it because m tranny slips, II have bigger tires, you have more fuel, more air or a combo of all of it.
Needless to say he said he will be doing some mods while he is here in OCK for 6 weeks of training.
#32
I'm pretty sure the added oomph of my bigger nozzles, the HD4R100, and a 90 degree day gave me an edge on the long burn. Believe me, that is one of those one-offs... but it was cool to learn Stinky could do that (and I had the camera ready). I don't take aim at the tires with the Buck$Zooka more than I have to.
#33
TEST FAILED
G'day Rich,
I tried using my AE today. It connected ok.
I checked DTCs and then I tried the KOEO self test.
I got: TEST FAILED: The device is busy. Try running the self test again.
It came up on all three occassions I tried this test???
What would be causing this to come up.
I didn't trust doing anything else so disconnected.
Cheers,
Reg
I tried using my AE today. It connected ok.
I checked DTCs and then I tried the KOEO self test.
I got: TEST FAILED: The device is busy. Try running the self test again.
It came up on all three occassions I tried this test???
What would be causing this to come up.
I didn't trust doing anything else so disconnected.
Cheers,
Reg
#34
"Device is busy"
I put giant text up there to make sure it gets spotted as future readers breeze through the page.
When your KOEO test failed, "Device is busy" is the clue here. When I referred to the Auto Enginuity manual (in PDF), I did a search for the term "device". Every instance of device referred to the computing device that AE is installed on. I have a "carputer", which means it sits in a bag until I drive Stinky (my only Ford). If I boot my carputer up within range of a wireless network, it could do a Windows Update without my knowledge. The only clue I have this is going on is the carputer starts to get sluggish, then that stupid "Windows will restart in X minutes" box. I don't know how many times that little yellow message popped up in the lower-right corner (or is that on the left side in Austrailia? ) while I was driving. I have stop to tell it to postpone rebooting for 4 hours, because using a touchpad and aiming an arrow on a tiny netbook gets tricky while driving... it can bend, break, and burst valuable stuff. This act is accompanied by a sailor-speak soundtrack. I'm seriously thinking of shutting off the wireless on the unit until I need it.
I put giant text up there to make sure it gets spotted as future readers breeze through the page.
When your KOEO test failed, "Device is busy" is the clue here. When I referred to the Auto Enginuity manual (in PDF), I did a search for the term "device". Every instance of device referred to the computing device that AE is installed on. I have a "carputer", which means it sits in a bag until I drive Stinky (my only Ford). If I boot my carputer up within range of a wireless network, it could do a Windows Update without my knowledge. The only clue I have this is going on is the carputer starts to get sluggish, then that stupid "Windows will restart in X minutes" box. I don't know how many times that little yellow message popped up in the lower-right corner (or is that on the left side in Austrailia? ) while I was driving. I have stop to tell it to postpone rebooting for 4 hours, because using a touchpad and aiming an arrow on a tiny netbook gets tricky while driving... it can bend, break, and burst valuable stuff. This act is accompanied by a sailor-speak soundtrack. I'm seriously thinking of shutting off the wireless on the unit until I need it.
#35
#36
#37
#38
That is one of the most bizarre things I've seen on in AE data. Mass Duel Desired is essentially throttle... but it can be influenced by other factors. MFD is telling the IPR to back off, the IPR is telling the ICP to back off, the ICP is backing off. For WOT, it's not very WOT. I would start by looking at your Throttle Position Sensor Volts (scale from 0-4V) with KOEO and slowly exercise the throttle. Look at the graph screen (or log the data), and make sure you hold it to the floor for about 10 seconds.
#39
That is one of the most bizarre things I've seen on in AE data. Mass Duel Desired is essentially throttle... but it can be influenced by other factors. MFD is telling the IPR to back off, the IPR is telling the ICP to back off, the ICP is backing off. For WOT, it's not very WOT. I would start by looking at your Throttle Position Sensor Volts (scale from 0-4V) with KOEO and slowly exercise the throttle. Look at the graph screen (or log the data), and make sure you hold it to the floor for about 10 seconds.
#40
Software Version 11.1.4 for AE
I got a new AutoEnginuity ProLine VCI USB (w/o the security dongle) back in May, hooked it up once or twice to get some data and play along in class, and all was fine. Today I tried to use it (becuase I need to!) and it would never connect, not to my F250 nor the better half's Chevy.
Called tech support, and they're sending me a new one. The reason for the post however is the Tech guy mentioned a new software version that specifically addresses some issues with Fords. It's a simple thing to contact them and have them send you a link, in case anyone's had issues with using AE.
From the AutoEnginuity Release Notes for Version 11.1.4:
ScanTool Version 11.1.4
-----------------------
Ford-family
• Fixed retrieving "All" DTCs losing the protocol for the current controller so live data and bidirectional controls fail to work after the DTC retrieval.
I got a new AutoEnginuity ProLine VCI USB (w/o the security dongle) back in May, hooked it up once or twice to get some data and play along in class, and all was fine. Today I tried to use it (becuase I need to!) and it would never connect, not to my F250 nor the better half's Chevy.
Called tech support, and they're sending me a new one. The reason for the post however is the Tech guy mentioned a new software version that specifically addresses some issues with Fords. It's a simple thing to contact them and have them send you a link, in case anyone's had issues with using AE.
From the AutoEnginuity Release Notes for Version 11.1.4:
ScanTool Version 11.1.4
-----------------------
Ford-family
• Fixed retrieving "All" DTCs losing the protocol for the current controller so live data and bidirectional controls fail to work after the DTC retrieval.
#41
What PIDs should I record?
I get this question so often now, that I thought it best to have the answer pre-fabbed. I always suggest to set your minimums and maximums so you can at least see the sensor reading on a graph at playback. If a maximum is set to 356, but the reading never goes higher than 3... then that would be a very useless graph. The list below covers the basics when monitoring the health of the 7.3L. If something calls your attention to it, then other tests and more forum searching may be in order... but this list addresses key components. If you record these in the driveway, the data will likely be very predictable - nothing to see here. If you tow and/or get on the freeway while recording, then you document how the system behaves when it matters. Any student of Murphy's Law know that this is the time when things go wrong... and wouldn't it be nice to record what went wrong? Of course... if you're a Murphy's Law purist, you know nothing will go wrong while recording - adding to the importance of recording.
These limits are for the majority of members - those with stock injectors and turbos (many tuned). If you carry big sticks, some of the limits will need dialing.
I get this question so often now, that I thought it best to have the answer pre-fabbed. I always suggest to set your minimums and maximums so you can at least see the sensor reading on a graph at playback. If a maximum is set to 356, but the reading never goes higher than 3... then that would be a very useless graph. The list below covers the basics when monitoring the health of the 7.3L. If something calls your attention to it, then other tests and more forum searching may be in order... but this list addresses key components. If you record these in the driveway, the data will likely be very predictable - nothing to see here. If you tow and/or get on the freeway while recording, then you document how the system behaves when it matters. Any student of Murphy's Law know that this is the time when things go wrong... and wouldn't it be nice to record what went wrong? Of course... if you're a Murphy's Law purist, you know nothing will go wrong while recording - adding to the importance of recording.
These limits are for the majority of members - those with stock injectors and turbos (many tuned). If you carry big sticks, some of the limits will need dialing.
#42