AE vs IDS clone
I think if you open a thread about your troubled truck, you're sure to get help here.
The sad thing about AE is the injector test can show you that a nearly dead injector is still good.
Oh and also not 100% sure why but no codes for cylinder contribution on any cylinders also have a scan gauge that I programmed in some misfire count codes into for each individual injector and all show 0 or do not count but believe me that truck is missing because sometimes when it’s really bad you can be sitting in the cab with it idling and watch your soda or whatever is in the cup holder splash from side to side to the point it starts foaming up around the edges from the rocking of the truck it’s so out of balance. Also worth mentioning that I found a DTC count code and it will show 3 codes currently active but when I use the code scan function it will pull up only 1 and it is irrelevant to the partial miss issue that I’m having, I know why that code is showing up and just haven’t had the time to take care of it yet.
Do you have fuel pressure gauge? That value helps also.
Could it be your ficm? Since you said the hotshots help, maybe it's your injectors. If you want to tinker, you can try to check few videos showing how to "clean up" the spool valve.
And it sounds like you don't yet have IDS. I suggest get one then.
Ford Trucks for Ford Truck Enthusiasts
Copy and paste the contents into notepad and save it as: IDS_Date_Time.cmd
Keep it on the desktop.
@echo off
date 07-11-19
time 21:00:00
Run it and the clock will change every time IDS gets turned on.
Who has the link to v116_01_Full?
My daughter's boyfriend came over with his Taurus so we hooked that up too...he was amazed at it and thought I was some master mechanic, lol.
It's running on an older IBM Thinkpad with 8GB and Win10 Pro. I did have to set the clock back and haven't tried the date trick listed right above yet.
Okay, guys sorry for the delay but the family came first at Christmas. So without further delay here is how to get IDS 116 to work with the J2534 diagnostic tool. A huge thank you to the suppliers at www.FLYOBD.com they were awesome to work with.
Windows 10 Pro 64 bit and IDS 116 and patch 116.02 installed
1. Go to My account ? flyobd shop and make an account if you don't have one.
2. Login to your account and go to Download or Download Center ? flyobd shop
3. For Ford IDS download the following 3 packages : IDSFord, SVCI-J2534-Ford-Quickloader, and most importantly IDS_VCI. (Files appear to all be hosted on Mega expect for IDS it comes from Fords servers)
4. Right click on each install file and Install everything "As Administrator" IDSFord (it will have you reboot after this installs), SVCI-J2534-Ford-Quickloader, and most importantly IDS_VCI (The install vidoes I watched failed to list this, without this when IDS try's to load it will fail.) I used the default option on all installs and ran everything as Administrator just in case.
5. On your Desktop there will be IDS shortcut, delete it as you will NOT use it to load IDS as it will fail due to no license.
6. Plug in your USB cable to your computer, plug your diagnostic tool into your USB cable and plug it in to your OBD 2 port on your vehicle. (Ensure the push button on the tool is in the pressed position to enable J2534, mine came in this position plus the button is recessed so you have to use something to press it. Otherwise it is a ELM327 if the switch is in the depressed position.)
7.1. Download IDSLoader***** and SVDIPT32.dll from my Google Drive, copy IDSLoader***** to "C:\Program Files (x86)\STIC\SVCI Based Software List\Ford IDS" and SVDIPT32.dll to "C:\Program Files (x86)\STIC\SVCI Passthru Driver". You can either overwrite the files or rename the old one before copying.
8. Turn your key to the run position and open the shortcut on your Desktop named "SVCI J2534".
9. You should see the IDS splash screen load up, upon first start it'll ask about "Dealer Type". Choose "Non-dealer" and select your country. IDS will load and you now have IDS!
10. You can go here to see what updates are available afterwards. Step 3 on this page will link the update package, simply download the package and run as Administrator. Now you have the updated package and just like before open with "SVCI J2534".
A couple of notes:
1. VCI program looks like it does nothing when opened because it shows VCM not connected. Leave it installed or IDS will not work!
2. Without the tool plugged in and the key in the run position if you try to run SVCI J2534 you will get error saying "VCI not plugged into car, or car battery under 8Volt."
3. If you don't install IDS_VCI you will encounter error "Load IDS software failed. TDSNetsetup error. Please reinstall IDS software."
4. I had also encountered a similar message reading "IDSLOADER Load IDS software failed. Maybe IDS has not been installed. Please install IDS at first. (I'm not sure what caused this error on the first install, perhaps I didn't run something as Administrator) But after running everything as Administrator I no longer have this issue.
5. Ford and Mazda IDS cannot be installed on same computer, if you need Mazda IDS you must uninstall Ford IDS.
6. Compatibility mode is not needed on Windows 10.
7. Updating once the main version number changes ex. 116 to 117 you will have to wait on a new crack to be posted here as the SVCI loader will realize the version does not match.
8. I've had some strange happenings at times, upon trying to do a relative compression test I follow the test holding the pedal to the floor and cranking. Randomly the truck will decide to start and IDS will give an error, but after trying it a few times it will work.
If anyone has any questions or needs any help I will do my best to help them out or need me to test a function of IDS for this tool just let me know. If you don't understand something or need help feel free to contact me, I will even hop on TeamViewer and assist you if needed. The guys at FLYOBD told me they would be updating the files so that all of the changing permissions of folders wouldn't be necessary buy they haven't update it yet so here is the work around for now. Here's a couple of shots showing it in action.
DataLogger
Power Balance












