DIY PROMDo It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.
Welcome to ThirdGen.org!
Welcome to ThirdGen.org.
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, join the ThirdGen.org community today!
Ok fellas, I got my com port and 10k resistor issues resolved. WinALDL will link up and receive data although it is broken. The little box at top is flashing red and i'm getting 1-7 not full data.
My cable was made by customefis.com but since I have no serial I'm using a serial to usb converter.
Its a 165 ecm I have used A B and M, A B and E with same results.
Any ideas I can make on the computer side that may resovle these problems. Currently I am using com4 port and have searched to find others that have had success with WinXP while using an identical serial usb converter.
Yes, I have tried moates software but i haven't messed with it a whole lot. Whenever I use moates' ware it keeps freezing after you press 1 to start logging in diagnostic mode.
Anyway on the WinALDL deal, there site states it supports ECM 1227165 Engine1986-89 5.7 V8 PFI '8' L98
Oops, I overlooked that you're using XP. We gotta convince Craig to look into making it work with XP. =)
M and E are tied together, so it makes sense you'd see the same results with either.
There is some discussion on the DIY-EFI mailing list thats a seems related to this (incomplete data with winALDL), and I believe the issue came down to the cable itself. However, using the USB->Serial converter might also be throwing some chaos into the mix. Do you have a friend with a laptop (with serial port) you could try? How 'bout a friend with a different cable?
If I had to guess (and it would only be that - an educated guess), I'd say its the cable.
Well I don't have a friend with a laptop BUT my mother has an old IBM desktop that I'm going to try with tommorow it has Win 98 that I'm sure has a serial port. I tried running moates' ware in Win98 compatility mode to no avail.
I have dual hardrives and might load one of them with Win2k since it works with moates' ware but I will still have the problem with using the usb interface.
But like you said I'm going to take some of these "moving parts" out of the loop and see what I can get. I'll be back tommorow with my results.
Ok Mangus, I finally got some good data using a desktop with Win95 and serial. The cable worked perfectly so I it must have been the usb adapter. Now all I need is a Laptop so I can make a real log.
My main reason for doing this intial test was just to look at some sensor values so I can make some adjustments the hardware of the motor.
Thanks for the help I'm positive I will have more questions when I start tuning the software side.