Brain Fade

[Irocing]

87/ 165ecm/ 6E ads definition file and was able to datalog at 8192.
Recently would not connect anymore.

Had to D/L the 160 baud version and will connect and datalog, but info
is showing up as garbadge. 5000rpm at idle ect..

Is there some Win settings that need correcting that may have changed
as to port speed ect. ect.

Running APU1/ TP RT.

Help or suggestions appreciated

Later

[Mangus]

Are you sure it's not in limp home mode, and are you sure the connection is solid between the ECM and your OBD connector?

[Irocing]

Not in limp mode.
Car runs great on chip and mods in chip that I changed.
Com ports in OS and TPRT match, running com 3. Tried com 1 thru
5 also.
Have reloaded OS, Win 2000-600Dell Latitude-512mgs ram-no virus programs loaded or background apps running.
Tried all latency settings, 1-16 and all settings recommended on Your
and Craigs site.
Sometimes will connect at 160 baud but garbadge info.
Reloaded FTDI usb drivers several times and showing correct when I
plug in the APU1.
Using correct definition. Tried both 6E definitions 8192 and 160 files.

When hook everything up and turn key on, ses blinks once then keeps flashing code 12
and ecm controlled fan runs all the time

This combo worked for about 1 month at 8192 and able to datalog correctly, then no joy.
Won't connect in APU1 pass thru mode either.
Have tried the resistor 10K both ways also.

Its got me stumped
Have read all the boards on this problem and tried everything.
Also running the TPRT lastest version.

Help

Thanks

[Mangus]

Ah, so it's not just ALDL - you can't emulate either? The emulation stage of the APU1 could have failed. Contact Craig via the moates.net web site.

[Irocing]

Mangus, Thanks for reply.

Will contact Craig and see if he can help.
This will be the second time I would have to send it back in a year.

He's probably going to think I use it as a (Frisby) when not chip
burning or datalogging
Been treating it like an unboiled egg after first go round.

Thanks

[Mangus]

What was the problem the first time?

You're sure you're uploading a valid bin and that the checksum is either correct or disabled (disable by setting the mask ID to AA)? That could also cause the behavior you're seeing. Although, if you burned the same bin to a chip and it works, then it's probably not the issue.

[Irocing]

The first time I could'nt get it to connect to the CPU, showing not
connected no matter what we tried.
When I got it back it hooked rite up Plus he also upgraded it
to his later model at no charge.

Have tried the checksum both ways, checked and unchecked.
Keep thinking after doing alot of reading on this, could be a timing
hookup issue

When it would hook up correctly, can't exactly remember, a month or
longer- The ses lite would not keep flashing code 12 and the fan would
not run continually with the key on

Input really appreciated

[Mangus]

Don't use the "checked" setting for the checksum. Instead, disable it in the bin itself by setting the mask ID to AA.

[Irocing]

Mangus,

Okay, just checked my current file bin and it is reading 6E.

Will change it to AA and check it out in the morning.
Here's hoping
Couldn't be this simple, Could it

As I make bin changes I always get the checksum box stating an
update change made. Can you explain that to me
Hoping that this discussion will help other newbies like myself understanding this problem

Hate to bother Craig again if I don't have to

Thanks