Message

http://www.digimoto.com/

I guess I = should have=20 looked before posting to this list... I'll put it on order.

but thanks = for the=20 reply!

-frank

From: David Cooley = [mailto:n5xmt at bellsouth.net]=20
Sent: Friday, October 22, 2004 11:10 PM
To:=20 diy_efi at diy-efi.org
Subject: Re: [Diy_efi] Data logging on a=20 neon

That's OBD-II... you can datalog with something like the = car-code=20 OBD-2 scanner... http://www.obd-2.com/

only about 100 bucks for a single interface and the = software

-------Original = Message-------

From: A list for Do-It-Yourself = EFI

Date: = 10/22/04=20 23:01:37

To: diy_efi at diy-efi.org

Subject: = [Diy_efi] Data=20 logging on a neon

Is there any way that I can cheaply = run data=20 logging to a PC on a 98 neon dohc? I'm mostly interested in = knock=20 sensor readings, timing changes and O2 readings.

Is their a mod I can do to the ecu = to add this=20 somehow? I'm not beyond opening it up and modifying the = components=20 on the pcb. Sorry if this has already been = covered.

Thanks.

Frank

------_=_NextPart_001_01C4B8AF.C345A348-- --===============7060092414316641== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============7060092414316641==-- From ozimmer at softhome.net Sat Oct 23 05:47:58 2004 From: ozimmer at softhome.net (Oolan Zimmer) Date: Sat, 23 Oct 2004 02:47:58 -0300 Subject: [Diy_efi] Data logging on a neon Message-ID: This is a multi-part message in MIME format. --===============72507395128339858== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0035_01C4B897.A7C38E40" This is a multi-part message in MIME format. ------=_NextPart_000_0035_01C4B897.A7C38E40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Data logging on a neonThat really depends on what you want to do. There = are data logging solutions that range from $100 or so up to Ferrari = prices. If you're trying to find mechanical problems and don't want to change = the tune of the ECU, there are inexpensive ways of reading data from the = OBDII datastream. That only gives you maybe 2 updates/second, though, = so it's not fine-grained enough to setup an engine tune. You're also = limited to the stock sensors. If all you're trying to do is give your = car enough octane to make sure it's not pulling timing, this is all you = need. =20 If you're trying to improve on-track driver performance but not set up = the engine or chassis, a 6-8 channel data logger logging at 20-40 = samples/second and a few special sensors should be enough to reveal = everything you never realized you were doing. If you can do some of the = work yourself, like putting together a harness and tapping into stock = sensors, you can probably manage to get it done with less than $1000. = If you can do a lot of the stuff yourself (like write embedded software, = design and assemble PC boards, etc.), you can probably get in under half = that for parts but with those skills the value of your time spent doing = it all would probably exceed what you'd spend for the mostly-complete = solution. You can also gather less data (but still enough to draw some = conclusions about your driving) with some cheaper solutions. If you're trying to change your fuel map and need your air to fuel = ratio, you need a wide band oxygen sensor. These days, many wide band = sensor controllers also do some data logging, and that may be all you = need. If you're trying to design a new suspension or a first-time setup of a = standalone ECU (with no base map), then the sky's the limit. Really = looking at raw knock sensor data and trying to determine if the ECU is = detecting knock correctly falls in this category. =20 Regards, Oolan Zimmer ozimmer at softhome.net ----- Original Message -----=20 From: Frank Clements=20 To: diy_efi at diy-efi.org=20 Sent: Friday, October 22, 2004 9:59 PM Subject: [Diy_efi] Data logging on a neon Is there any way that I can cheaply run data logging to a PC on a 98 = neon dohc? I'm mostly interested in knock sensor readings, timing = changes and O2 readings. =20 Is their a mod I can do to the ecu to add this somehow? I'm not = beyond opening it up and modifying the components on the pcb. Sorry if = this has already been covered. Thanks.=20 Frank=20 ------=_NextPart_000_0035_01C4B897.A7C38E40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Data logging on a neon

That really depends on what you want to = do. =20 There are data logging solutions that range from $100 or so up to = Ferrari=20 prices.

If you're trying to find mechanical = problems and=20 don't want to change the tune of the ECU, there are inexpensive ways of = reading=20 data from the OBDII datastream. That only gives you maybe 2=20 updates/second, though, so it's not fine-grained enough to setup an = engine=20 tune. You're also limited to the stock sensors. If all = you're=20 trying to do is give your car enough octane to make sure it's not = pulling=20 timing, this is all you need.

If you're trying to improve on-track = driver=20 performance but not set up the engine or chassis, a 6-8 channel data = logger=20 logging at 20-40 samples/second and a few special sensors should be = enough to=20 reveal everything you never realized you were doing. If you can do = some of=20 the work yourself, like putting together a harness and tapping into = stock=20 sensors, you can probably manage to get it done with less than = $1000. If you can do a lot of the stuff yourself (like write = embedded=20 software, design and assemble PC boards, etc.), you can probably get in = under=20 half that for parts but with those skills the value of your time spent=20 doing it all would probably exceed what you'd spend for the=20 mostly-complete solution. You can also gather less data (but still = enough=20 to draw some conclusions about your driving) with some cheaper=20 solutions.

If you're trying to change your = fuel map and=20 need your air to fuel ratio, you need a wide band oxygen sensor. = These=20 days, many wide band sensor controllers also do some data logging, and = that may=20 be all you need.

If you're trying to design a new suspension or a first-time setup = of a=20 standalone ECU (with no base map), then the sky's the limit. = Really=20 looking at raw knock sensor data and trying to determine if the ECU is = detecting=20 knock correctly falls in this category.

Regards,

Oolan Zimmer

ozimmer at softhome.net

----- Original Message -----

From:=20 Frank=20 Clements

To: diy_efi at diy-efi.org

Sent: Friday, October 22, 2004 = 9:59=20 PM

Subject: [Diy_efi] Data logging = on a=20 neon

Is there any way that I can cheaply run = data=20 logging to a PC on a 98 neon dohc? I'm mostly interested in = knock sensor=20 readings, timing changes and O2 readings.

Is their a mod I can do to the ecu to = add this=20 somehow? I'm not beyond opening it up and modifying the = components on=20 the pcb. Sorry if this has already been covered.

Thanks.

Frank =

------=_NextPart_000_0035_01C4B897.A7C38E40-- --===============72507395128339858== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============72507395128339858==-- From fastcarson at prodigy.net Mon Oct 25 05:25:33 2004 From: fastcarson at prodigy.net (Chris Carson) Date: Mon, 25 Oct 2004 02:25:33 -0300 Subject: [Diy_efi] Help, putting a 4.3 TBI on a buick 3.8L V6 Message-ID: The only G-bodies to get fuel injection were the 3.8 Turbo Buick (84-87) or the 4.3 TBI Monte Carlos. And good luck finding a TR setup without giving up your firstborn. There is a MUCH BETTER alternative. What you should be looking for is an 80's "A-body"; that is, a FWD compact car like Cutlass Ciera, Buick Century, Pontiac 6000, Celebrity. THESE CARS ARE ALL OVER THE JUNKYARDS!!! Starting in 84, these came with MPFI 3.8s, and they went to SFI in 1986. The heads and intake will definitely bolt onto any old 3.8, if not just the intake. 88 and up 3.8s are completely different and nothing interchanges with the older style, this is the "3800" that everyone knows and loves. Chris ----- Original Message ----- > Chuck, > > You want a RWD 1986 or 1987 Regal or Cutlass. You'll need to take the > entire intake setup but you'll get port injection vs. TBI. > > Jim > > Charles Woock wrote: > > I'm game. What vehicle/year would be a good donor? The donor is > > critical. I can buy whole cars/trucks from an insurance salvage pool > > (through a friends dealer ID). I'm going buy the whole thing and use as > > much off it as possible to save money. _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From gianmarco.rizzo at ericsson.com Mon Oct 25 10:16:52 2004 From: gianmarco.rizzo at ericsson.com (Gianmarco Rizzo (BE/EAS)) Date: Mon, 25 Oct 2004 07:16:52 -0300 Subject: [Diy_efi] Changing the fuel and spark on a Porsche Message-ID: Hi Brian fitting a turbocharger without EFI adaptations will end up in a blown engine very very quickly i dont' know what ECU the car uses but i'd recommend using a aftermarket programmable EFI for best (and safe) results -----Original Message----- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On Behalf Of Brian MacKay Sent: Samstag, 23. Oktober 2004 03:48 To: diy_efi at diy-efi.org Subject: [Diy_efi] Changing the fuel and spark on a Porsche I have a friend to races a Porsche and while he knows a lot about cars, he knows nothing about the guts of his EFI. He insists on making major mechanical changes to the engine and doesn't consider the fact that the computer won't necessarily make good corrections. He plans to turbo charge the car and is assuming everything will be fine without modifying the computer. My background is that I regularly modify code and look up tables in my GM ECM but I know nothing about Porsche stuff, like what processor is used, does it use EPROMS, etc. The car is a 1992 Porsche 968 therefore OBD-I. Can anyone point me to any references or websites where I can learn more and hopefully prevent him from blowing up another engine! Thanks, Brian _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From brian.mackay at sympatico.ca Tue Oct 26 00:33:19 2004 From: brian.mackay at sympatico.ca (Brian MacKay) Date: Mon, 25 Oct 2004 21:33:19 -0300 Subject: [Diy_efi] Changing the fuel and spark on a Porsche Message-ID: I agree 100%. My current car is a Grand National so I am used to tuning under boost conditions. I cannot fathom why my normally intelligent friend wants to do this. He must not value his time at all. Brian -----Original Message----- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On Behalf Of Gianmarco Rizzo (BE/EAS) Sent: October 25, 2004 6:14 AM To: 'A list for Do-It-Yourself EFI' Subject: RE: [Diy_efi] Changing the fuel and spark on a Porsche Hi Brian fitting a turbocharger without EFI adaptations will end up in a blown engine very very quickly i dont' know what ECU the car uses but i'd recommend using a aftermarket programmable EFI for best (and safe) results -----Original Message----- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On Behalf Of Brian MacKay Sent: Samstag, 23. Oktober 2004 03:48 To: diy_efi at diy-efi.org Subject: [Diy_efi] Changing the fuel and spark on a Porsche I have a friend to races a Porsche and while he knows a lot about cars, he knows nothing about the guts of his EFI. He insists on making major mechanical changes to the engine and doesn't consider the fact that the computer won't necessarily make good corrections. He plans to turbo charge the car and is assuming everything will be fine without modifying the computer. My background is that I regularly modify code and look up tables in my GM ECM but I know nothing about Porsche stuff, like what processor is used, does it use EPROMS, etc. The car is a 1992 Porsche 968 therefore OBD-I. Can anyone point me to any references or websites where I can learn more and hopefully prevent him from blowing up another engine! Thanks, Brian _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From n5xmt at bellsouth.net Tue Oct 26 03:22:43 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Tue, 26 Oct 2004 00:22:43 -0300 Subject: [Diy_efi] MOPAR PCM info available Message-ID: Hey all, I have been hacking around with the Mopar PCM's... mostly 97, but have obtained a 98 PCM, which also drove the dash via the CCD bus... They have 2 28F010 Flash proms, a 68HC16Z2 main CPU, a 68HC11K4 for ignition and a 68HC11D3 for fuel. I also have a Mopar Performance PCM for my truck, so I was able to dump it's flash as well and compare to my stock PCM... Major differences are the stocker has a 5200 RPM redline/rev limit, MP has a 6000 RPM limit, shift points with the stocker are 4800 RPM, and 5200 with the MP PCM. then better fuel and spark cal's as well for better performance. I have all the info so far up at: http://www.nancyknowshomes.com/dodge/97PCM/pcm.htm Let me know what you think! _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From gianmarco.rizzo at ericsson.com Tue Oct 26 09:48:02 2004 From: gianmarco.rizzo at ericsson.com (Gianmarco Rizzo (BE/EAS)) Date: Tue, 26 Oct 2004 06:48:02 -0300 Subject: [Diy_efi] Changing the fuel and spark on a Porsche Message-ID: i have done a short research and apparently is not possible to change any parameter at all in the 968 stock ECU. Also, the car runs high compression to start with so forget turbocharging it unless pistons are changed for lower comp type, and a different ECU is fitted http://forums.beyond.ca/showthread/t-56892.html alos check this www.986.net gm -----Original Message----- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On Behalf Of Brian MacKay Sent: Dienstag, 26. Oktober 2004 02:30 To: A list for Do-It-Yourself EFI Subject: RE: [Diy_efi] Changing the fuel and spark on a Porsche I agree 100%. My current car is a Grand National so I am used to tuning under boost conditions. I cannot fathom why my normally intelligent friend wants to do this. He must not value his time at all. Brian -----Original Message----- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On Behalf Of Gianmarco Rizzo (BE/EAS) Sent: October 25, 2004 6:14 AM To: 'A list for Do-It-Yourself EFI' Subject: RE: [Diy_efi] Changing the fuel and spark on a Porsche Hi Brian fitting a turbocharger without EFI adaptations will end up in a blown engine very very quickly i dont' know what ECU the car uses but i'd recommend using a aftermarket programmable EFI for best (and safe) results -----Original Message----- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On Behalf Of Brian MacKay Sent: Samstag, 23. Oktober 2004 03:48 To: diy_efi at diy-efi.org Subject: [Diy_efi] Changing the fuel and spark on a Porsche I have a friend to races a Porsche and while he knows a lot about cars, he knows nothing about the guts of his EFI. He insists on making major mechanical changes to the engine and doesn't consider the fact that the computer won't necessarily make good corrections. He plans to turbo charge the car and is assuming everything will be fine without modifying the computer. My background is that I regularly modify code and look up tables in my GM ECM but I know nothing about Porsche stuff, like what processor is used, does it use EPROMS, etc. The car is a 1992 Porsche 968 therefore OBD-I. Can anyone point me to any references or websites where I can learn more and hopefully prevent him from blowing up another engine! Thanks, Brian _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From brian.trulove at charter.net Tue Oct 26 12:53:29 2004 From: brian.trulove at charter.net (Brian Trulove) Date: Tue, 26 Oct 2004 09:53:29 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: How were you able to obtain the dumps? Did you have to use SCI and/or = have you made any progress in that area? I have a copy of the J2534 software = from DCX but not the pass-thru interface yet. I was hoping I could get some = help in making one ... schematics?? _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From n5xmt at bellsouth.net Tue Oct 26 13:17:02 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Tue, 26 Oct 2004 10:17:02 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: --===============23574025281681243== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_5007QL80000000000000" --------------Boundary-00=_5007QL80000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Brian,=0D I took the easy way out for the dumps LOL... removed the flash from the board and popped them into my prom burner... then socketed the PCB.=0D I've been looking for a passthru interface myself as well...=0D I also wonder if I can get a dump of the CPU's ROM's thru SCI off the chi= p.. Flash appears to be nothing but data, no code... Slowly finding out a bunch about these PCM's... they are very powerful, but Mopar has only scratched the surface of what they do with them...=0D =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/26/04 08:51:31=0D To: diy_efi at diy-efi.org=0D Subject: [Diy_efi] Mopar PCM=0D =0D How were you able to obtain the dumps? Did you have to use SCI and/or hav= e=0D you made any progress in that area? I have a copy of the J2534 software f= rom=0D DCX but not the pass-thru interface yet. I was hoping I could get some he= lp=0D in making one ... schematics??=0D =0D =0D _______________________________________________=0D diy_efi mailing list=0D diy_efi at diy-efi.org=0D http://lists.diy-efi.org/mailman/listinfo/diy_efi --------------Boundary-00=_5007QL80000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi Brian,

I took the easy way out for the dumps LOL... removed the flash from = the board and popped them into my prom burner... then socketed the PCB.

I've been looking for a passthru interface myself as well...

I also wonder if I can get a dump of the CPU's ROM's thru SCI off th= e chip... Flash appears to be nothing but data, no code... Slo= wly finding out a bunch about these PCM's... they are very powerful,= but Mopar has only scratched the surface of what they do with them...

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/26/04 08:= 51:31

To: diy_efi at diy-efi.org

Subject: [Diy_efi]= Mopar PCM

How were you able to obtain the dumps? Did you have to use SCI and/o= r have

you made any progress in that area? I have a copy of the J2534 softw= are from

DCX but not the pass-thru interface yet. I was hoping I could get so= me help

in making one ... schematics??

_______________________________________________

diy_efi mailing list

diy_efi at diy-efi.org

http:/= /lists.diy-efi.org/mailman/listinfo/diy_efi

--------------Boundary-00=_5007QL80000000000000-- --===============23574025281681243== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============23574025281681243==-- From brian.trulove at charter.net Tue Oct 26 15:15:38 2004 From: brian.trulove at charter.net (brian.trulove at charter.net) Date: Tue, 26 Oct 2004 12:15:38 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: The passthrough device supported by most mfg is the Passthru+ XS by I+ME ACTIA. The documents from Daimler specifically indicate the device must support SCI so this must be the method used. There are more and more passthrough devices being made but few that support SCI. Guess which ones are more expensive. Do you have any idea what makes these devices different (hardware wise) than the standard OBDII adapters? I know the driver makes a difference because of the J2534 API required but that should be fairly easily modified. -------Original Message------- Hi Brian, I took the easy way out for the dumps LOL... removed the flash from the board and popped them into my prom burner... then socketed the PCB. I've been looking for a passthru interface myself as well... I also wonder if I can get a dump of the CPU's ROM's thru SCI off the chip.. Flash appears to be nothing but data, no code... Slowly finding out a bunch about these PCM's... they are very powerful, but Mopar has only scratched the surface of what they do with them... _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From n5xmt at bellsouth.net Tue Oct 26 15:41:01 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Tue, 26 Oct 2004 12:41:01 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: Hmm... I bet the ones with SCI LOL... I'm not sure, because SCI is normally done with just a MAX-232 to convert to serial... Heck, even the OBD-II is simple... I have the CarCode scantool from www obd-2.com and it's basically a PIC microcontroller and a few passive components, and it does all 3 modes (PWN, VPW and ISO-9141-2) Plus now it also does CAN... I'm going to tap direct to the CPU's SCI and hook it to the adapter I built for my HC11 Eval board and see what comes across... I know the HC16 is the master and basically does menial single sensor/output tasks along with sending proper data to the fuel and ignition HC11's... Maybe there will be some insight there?? -------Original Message------- From: A list for Do-It-Yourself EFI Date: 10/26/04 11:13:08 To: diy_efi at diy-efi.org Subject: [Diy_efi] Mopar PCM The passthrough device supported by most mfg is the Passthru+ XS by I+ME ACTIA. The documents from Daimler specifically indicate the device must support SCI so this must be the method used. There are more and more passthrough devices being made but few that support SCI. Guess which ones are more expensive. Do you have any idea what makes these devices different (hardware wise) than the standard OBDII adapters? I know the driver makes a difference because of the J2534 API required but that should be fairly easily modified. -------Original Message------- Hi Brian, I took the easy way out for the dumps LOL... removed the flash from the board and popped them into my prom burner... then socketed the PCB. I've been looking for a passthru interface myself as well... I also wonder if I can get a dump of the CPU's ROM's thru SCI off the chip.. Flash appears to be nothing but data, no code... Slowly finding out a bunch about these PCM's... they are very powerful, but Mopar has only scratched the surface of what they do with them... _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From brian.trulove at charter.net Tue Oct 26 16:38:59 2004 From: brian.trulove at charter.net (brian.trulove at charter.net) Date: Tue, 26 Oct 2004 13:38:59 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: Is this the same as the Tricom? They have a SAE J2534 driver on their developement page. If you're game I can send the DCX2534 application, driver, and a 00' Durango 5.9 bin for you to try uploading. My interface works for diagnostics (BR-3) from obddiagnostics.com. I've never taken it apart so I don't know if they're similar. A schematic is posted on the site though. I don't give up easy either so I hope you're interested in pursuing this. -------Original Message------- Hmm... I bet the ones with SCI LOL... I'm not sure, because SCI is normally done with just a MAX-232 to convert to serial... Heck, even the OBD-II is simple... I have the CarCode scantool from www obd-2.com and it's basically a PIC microcontroller and a few passive components, and it does all 3 modes (PWN, VPW and ISO-9141-2) Plus now it also does CAN... I'm going to tap direct to the CPU's SCI and hook it to the adapter I built for my HC11 Eval board and see what comes across... I know the HC16 is the master and basically does menial single sensor/output tasks along with sending proper data to the fuel and ignition HC11's... Maybe there will be some insight there?? _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From n5xmt at bellsouth.net Tue Oct 26 19:32:24 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Tue, 26 Oct 2004 16:32:24 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: --===============68627020490577095== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_TYF7BHK0000000000000" --------------Boundary-00=_TYF7BHK0000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable yep... it's the new Trican unit.=0D Would love to try the J2534 driver etc and see if it works! =0D =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/26/04 12:35:38=0D To: diy_efi at diy-efi.org=0D Subject: [Diy_efi] Mopar PCM=0D =0D Is this the same as the Tricom? They have a SAE J2534 driver on their developement page. If you're game I can send the DCX2534 application, dri= ver and a 00' Durango 5.9 bin for you to try uploading. My interface works f= or diagnostics (BR-3) from obddiagnostics.com. I've never taken it apart so = I don't know if they're similar. A schematic is posted on the site though. = I don't give up easy either so I hope you're interested in pursuing this.=0D =0D -------Original Message-------=0D =0D Hmm... I bet the ones with SCI LOL...=0D I'm not sure, because SCI is normally done with just a MAX-232 to convert= to=0D serial...=0D Heck, even the OBD-II is simple... I have the CarCode scantool from www=0D obd-2.com and it's basically a PIC microcontroller and a few passive=0D components, and it does all 3 modes (PWN, VPW and ISO-9141-2) Plus now it= =0D also does CAN...=0D I'm going to tap direct to the CPU's SCI and hook it to the adapter I bui= lt=0D for my HC11 Eval board and see what comes across...=0D I know the HC16 is the master and basically does menial single sensor/out= put=0D tasks along with sending proper data to the fuel and ignition HC11's...=0D Maybe there will be some insight there??=0D =0D =0D _______________________________________________=0D diy_efi mailing list=0D diy_efi at diy-efi.org=0D http://lists.diy-efi.org/mailman/listinfo/diy_efi=0D =2E --------------Boundary-00=_TYF7BHK0000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

yep... it's the new Trican unit.

Would love to try the J2534 driver etc and see if it works!

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/26/04 12:= 35:38

To: diy_efi at diy-efi.org

Subject: [Diy_efi]= Mopar PCM

Is this the same as the Tricom? They have a SAE J2534 driver on thei= r developement page. If you're game I can send the DCX2534 application, d= river, and a 00' Durango 5.9 bin for you to try uploading. My interface w= orks for diagnostics (BR-3) from obddiagnostics.com. I've never taken it = apart so I don't know if they're similar. A schematic is posted on the si= te though. I don't give up easy either so I hope you're interested in pur= suing this.

-------Original Message-------

Hmm... I bet the ones with SCI LOL...

I'm not sure, because SCI is normally done with just a MAX-232 to co= nvert to

serial...

Heck, even the OBD-II is simple... I have the CarCode scantool from = www

obd-2.com and it's basically a PIC microcontroller and a few passive=

components, and it does all 3 modes (PWN, VPW and ISO-9141-2) Plus n= ow it

also does CAN...

I'm going to tap direct to the CPU's SCI and hook it to the adapter = I built

for my HC11 Eval board and see what comes across...

I know the HC16 is the master and basically does menial single senso= r/output

tasks along with sending proper data to the fuel and ignition HC11's= =2E..

Maybe there will be some insight there??

_______________________________________________

diy_efi mailing list

diy_efi at diy-efi.org

http:/= /lists.diy-efi.org/mailman/listinfo/diy_efi

--------------Boundary-00=_TYF7BHK0000000000000-- --===============68627020490577095== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============68627020490577095==-- From n5xmt at bellsouth.net Tue Oct 26 20:03:49 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Tue, 26 Oct 2004 17:03:49 -0300 Subject: [Diy_efi] Info on Mopar SCI was Mopar PCM Message-ID: --===============38722890333231375== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_97H7QL80000000000000" --------------Boundary-00=_97H7QL80000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable So far, My only experience is on the 96 and newer OBD-II controllers... t= hey still use the SCI (or at least they call it SCI) on the diag connector, f= or=20 the OBD-II interface... it may support multiple protocols, but it's runni= ng ISO 9141-2 for the OBD-II=0D =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/26/04 15:00:54=0D To: A list for Do-It-Yourself EFI=0D Subject: Re: [Diy_efi] Info on Mopar SCI was Mopar PCM=0D =0D At 12:19 PM 26/10/04, you wrote:=0D =0D > Hmm... I bet the ones with SCI LOL...=0D >I'm not sure, because SCI is normally done with just a MAX-232 to conver= t to=0D >serial...=0D =0D =0D Hello Everyone in the group,=0D =0D I am in the process of retrofitting a 1988 vintage 318 with=0D Throttle Body Injection into a Bombardier Tracked=0D vehicle called a " Muskeg ". We have been using this vehicle to log with=0D and up till now had been using a Holley 2bbl=0D for carburetion. The big problem is that the vehicle sometimes has to wor= k=0D at an attitude close to 45 deg and when this=0D happens, the float sticks and the vehicle stalls.=0D =0D With all of the recent discussion on Mopars, and with the ECU= =0D internals I was hoping that you folks might=0D be able to point me to where I can find info on the SCI interface /=0D protocol etc that would let one retrieve codes etc from the=0D diagnostic port.=0D I am aware that I can using the ' flashing light ' method an= d=0D I have saved this part of the wiring harness to use=0D for that purpose. But having a hobby in MicroControllers and such, I woul= d=0D like to cook up a device to read the codes=0D if I can. Up till joining this group, I have not been able to find much = in=0D the way of info on the pre-OBD controllers.=0D =0D Any pointers are greatly appreciated.=0D =0D Sincerely, Wally=0D =0D =0D =0D =20 --------------Boundary-00=_97H7QL80000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

So far, My only experience is on the 96 and newer OBD-II controllers= =2E.. they still use the SCI (or at least they call it SCI) on the diag c= onnector, for the OBD-II interface... it may support multiple proto= cols, but it's running ISO 9141-2 for the OBD-II

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/26/04 15:= 00:54

To: A list for Do-It-Yourself EFI

Subject: Re: [Diy_= efi] Info on Mopar SCI was Mopar PCM

At 12:19 PM 26/10/04, you wrote:

> Hmm... I bet the ones with SCI LOL...

>I'm not sure, because SCI is normally done with just a MAX-232 t= o convert to

>serial...

Hello Everyone in the group,

I am in the process= of retrofitting a 1988 vintage 318 with

Throttle Body Injection into a Bombardier Tracked

vehicle called a " Muskeg ". We have been using this vehicle to log = with

and up till now had been using a Holley 2bbl

for carburetion. The big problem is that the vehicle sometimes has t= o work

at an attitude close to 45 deg and when this

happens, the float sticks and the vehicle stalls.

&n= bsp;With all of the recent discussion on Mopars, and with the ECU

internals I was hoping that you folks might

be able to point me to where I can find info on the SCI i= nterface /

protocol etc that would let one retrieve codes etc from the

diagnostic port.

&n= bsp; I am aware that I can using the ' flashing light ' method and

I have saved this part of the wiring harness to use

for that purpose. But having a hobby in MicroControllers and such, I= would

like to cook up a device to read the codes

if I can. Up till joining this group, I have not been abl= e to find much in

the way of info on the pre-OBD controllers.

Any pointers are greatly appreciated.

Sincerely, Wally

--------------Boundary-00=_97H7QL80000000000000-- --===============38722890333231375== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============38722890333231375==-- From wally.daniels at ns.sympatico.ca Tue Oct 26 20:19:24 2004 From: wally.daniels at ns.sympatico.ca (Wally Daniels) Date: Tue, 26 Oct 2004 17:19:24 -0300 Subject: [Diy_efi] Info on Mopar SCI was Mopar PCM Message-ID: --=======EDC6326======= Content-Type: text/plain; x-avg-checked=avg-ok-6B0D7C55; charset=us-ascii; format=flowed Content-Transfer-Encoding: 8bit At 12:19 PM 26/10/04, you wrote: > Hmm... I bet the ones with SCI LOL... >I'm not sure, because SCI is normally done with just a MAX-232 to convert to >serial... Hello Everyone in the group, I am in the process of retrofitting a 1988 vintage 318 with Throttle Body Injection into a Bombardier Tracked vehicle called a " Muskeg ". We have been using this vehicle to log with and up till now had been using a Holley 2bbl for carburetion. The big problem is that the vehicle sometimes has to work at an attitude close to 45 deg and when this happens, the float sticks and the vehicle stalls. With all of the recent discussion on Mopars, and with the ECU internals I was hoping that you folks might be able to point me to where I can find info on the SCI interface / protocol etc that would let one retrieve codes etc from the diagnostic port. I am aware that I can using the ' flashing light ' method and I have saved this part of the wiring harness to use for that purpose. But having a hobby in MicroControllers and such, I would like to cook up a device to read the codes if I can. Up till joining this group, I have not been able to find much in the way of info on the pre-OBD controllers. Any pointers are greatly appreciated. Sincerely, Wally --=======EDC6326======= Content-Type: text/plain; charset=us-ascii; x-avg=cert; x-avg-checked=avg-ok-6B0D7C55 Content-Disposition: inline --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.778 / Virus Database: 525 - Release Date: 15/10/04 --=======EDC6326======= Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --=======EDC6326=======-- From A6intruder at adelphia.net Tue Oct 26 21:17:23 2004 From: A6intruder at adelphia.net (Daniel Nicoson) Date: Tue, 26 Oct 2004 18:17:23 -0300 Subject: [Diy_efi] Info on Mopar SCI was Mopar PCM Message-ID: This is a multi-part message in MIME format. --===============54139408423698088== Content-Type: multipart/alternative; boundary="----=_NextPart_000_002A_01C4BB7A.D3BB53D0" This is a multi-part message in MIME format. ------=_NextPart_000_002A_01C4BB7A.D3BB53D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Wally, For a project like you are describing, why not use a stand-alone controller that is made to be used for one-off projects like you have in mind? This could save time rather than having to reverse-engineer an old OEM system that may have limited support. It sounds like you would rather USE this tracked vehicle than spend time learning what Mopar engineers designed 15 years ago. I don't suggest this to discourage the spirit of this list, DIY-EFI, but as an option to get you going sooner. http://www.bgsoflex.com/megasquirt.html Megasquirt (DIY already figured out) http://www.sdsefi.com/ Simple Digital System (store bought) These are two links that could get you full control of your engine very quickly and not too expensively. You might even be able to drive the existing throttle body fuel injector you noted with these controllers. Just a couple more possibilities. Good luck with the project. Dan From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On Behalf Of David Cooley Sent: Tuesday, October 26, 2004 3:09 PM To: diy_efi at diy-efi.org Subject: Re: [Diy_efi] Info on Mopar SCI was Mopar PCM So far, My only experience is on the 96 and newer OBD-II controllers... they still use the SCI (or at least they call it SCI) on the diag connector, for the OBD-II interface... it may support multiple protocols, but it's running ISO 9141-2 for the OBD-II -------Original Message------- From: A list for Do-It-Yourself EFI Date: 10/26/04 15:00:54 To: A list for Do-It-Yourself EFI Subject: Re: [Diy_efi] Info on Mopar SCI was Mopar PCM At 12:19 PM 26/10/04, you wrote: > Hmm... I bet the ones with SCI LOL... >I'm not sure, because SCI is normally done with just a MAX-232 to convert to >serial... Hello Everyone in the group, I am in the process of retrofitting a 1988 vintage 318 with Throttle Body Injection into a Bombardier Tracked vehicle called a " Muskeg ". We have been using this vehicle to log with and up till now had been using a Holley 2bbl for carburetion. The big problem is that the vehicle sometimes has to work at an attitude close to 45 deg and when this happens, the float sticks and the vehicle stalls. With all of the recent discussion on Mopars, and with the ECU internals I was hoping that you folks might be able to point me to where I can find info on the SCI interface / protocol etc that would let one retrieve codes etc from the diagnostic port. I am aware that I can using the ' flashing light ' method and I have saved this part of the wiring harness to use for that purpose. But having a hobby in MicroControllers and such, I would like to cook up a device to read the codes if I can. Up till joining this group, I have not been able to find much in the way of info on the pre-OBD controllers. Any pointers are greatly appreciated. Sincerely, Wally ------=_NextPart_000_002A_01C4BB7A.D3BB53D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Wally,

For a project like you are = describing, why=20 not use a stand-alone controller that is made to be used for one-off = projects=20 like you have in mind? This could save time rather than having to=20 reverse-engineer an old OEM system that may have limited support. = It=20 sounds like you would rather USE this tracked vehicle than spend time = learning=20 what Mopar engineers designed 15 years ago.

I don't suggest this to discourage = the=20 spirit of this list, DIY-EFI, = but as an=20 option to get you going sooner.

http://www.bgsoflex.com/= megasquirt.html =20 Megasquirt (DIY already figured out)

http://www.sdsefi.com/ Simple = Digital=20 System (store bought)

These are two links that could get = you full=20 control of your engine very quickly and not too expensively. You = might=20 even be able to drive the existing throttle body fuel injector you noted = with=20 these controllers.

Just a couple more=20 possibilities.

Good luck with the = project.

Dan

From: diy_efi-bounces at diy-efi.org=20 [mailto:diy_efi-bounces at diy-efi.org]On Behalf Of David=20 Cooley
Sent: Tuesday, October 26, 2004 3:09 PM
To:=20 diy_efi at diy-efi.org
Subject: Re: [Diy_efi] Info on Mopar SCI = was Mopar=20 PCM

So far, My only experience is on the 96 and newer OBD-II=20 controllers... they still use the SCI (or at least they call it = SCI) on=20 the diag connector, for the OBD-II interface... it may = support=20 multiple protocols, but it's running ISO 9141-2 for the = OBD-II

-------Original=20 Message-------

From: A list for Do-It-Yourself=20 EFI

Date: = 10/26/04=20 15:00:54

To: A list for Do-It-Yourself=20 EFI

Subject: = Re:=20 [Diy_efi] Info on Mopar SCI was Mopar PCM

At 12:19 PM 26/10/04, you wrote:

>  Hmm... I bet the ones with SCI LOL...

>I'm not sure, because SCI is normally done with just a = MAX-232=20 to convert to

>serial...

Hello Everyone in the group,

         I am in = the=20 process of retrofitting a 1988 vintage 318 with

Throttle Body Injection into a Bombardier Tracked

vehicle called a " Muskeg ". We have been using this = vehicle to log=20 with

and up till now had been using a Holley 2bbl

for carburetion. The big problem is that the vehicle = sometimes has=20 to work

at an attitude close to 45 deg and when this

happens, the float sticks and the vehicle stalls.

=
           &n= bsp;With=20 all of the recent discussion on Mopars, and with the ECU

internals I was hoping that you folks might

be able to point me to where I can find  info on = the SCI=20 interface /

protocol etc that would let one retrieve codes etc from = the

diagnostic port.
=
           &n= bsp;=20 I am aware that I can using the ' flashing light ' method = and

I have saved this part of the wiring harness to use

for that purpose. But having a hobby in MicroControllers = and such,=20 I would

like to cook up a device to read the codes

if I can.  Up till joining this group, I have not = been=20 able to find much in

the way of info on the pre-OBD controllers.

Any pointers are greatly appreciated.

Sincerely, Wally

------=_NextPart_000_002A_01C4BB7A.D3BB53D0-- --===============54139408423698088== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============54139408423698088==-- From Djfreggens at aol.com Wed Oct 27 02:15:58 2004 From: Djfreggens at aol.com (Djfreggens at aol.com) Date: Tue, 26 Oct 2004 23:15:58 -0300 Subject: [Diy_efi] MOPAR PCM info available Message-ID: --===============20678615786947038== Content-Type: multipart/alternative; boundary="-----------------------------1098843162" -------------------------------1098843162 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 10/26/2004 10:01:15 PM Eastern Standard Time, n5xmt at bellsouth.net writes: http://www.nancyknowshomes.com/dodge/97PCM/pcm.htm id bet the adress lines a scrambled. -------------------------------1098843162 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

In a message dated 10/26/2004 10:01:15 PM Eastern Standard Time, n5xmt@= bellsouth.net writes:

http://www.nancyknowshomes.com/dodge/97PCM/pcm= .htm

id bet the adress lines a scrambled.
-------------------------------1098843162-- --===============20678615786947038== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============20678615786947038==-- From n5xmt at bellsouth.net Wed Oct 27 02:35:46 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Tue, 26 Oct 2004 23:35:46 -0300 Subject: [Diy_efi] MOPAR PCM info available Message-ID: --===============69914366046173226== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_AD186RO0000000000000" --------------Boundary-00=_AD186RO0000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable nope. these are off the shelf 28F010's in the PCM's.=0D so far, Ford is the only one I have seen scrambling address lines...=0D CPU's are also off the shelf and not one-off variants.=0D Received a copy of a factory flash file and it compares with what is in t= he flash PROMS=0D =0D =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/26/04 22:13:33=0D To: diy_efi at diy-efi.org=0D Subject: Re: [Diy_efi] MOPAR PCM info available=0D =0D In a message dated 10/26/2004 10:01:15 PM Eastern Standard Time, n5xmt at bellsouth.net writes:=0D http://www.nancyknowshomes.com/dodge/97PCM/pcm.htm=0D id bet the adress lines a scrambled. =0D =20 --------------Boundary-00=_AD186RO0000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

nope. these are off the shelf 28F010's in the PCM's.

so far, Ford is the only one I have seen scrambling address lines...=

CPU's are also off the shelf and not one-off variants.

Received a copy of a factory flash file and it compares with what is= in the flash PROMS

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/26/04 22:= 13:33

To: diy_efi at diy-efi.org

Subject: Re: [Diy_= efi] MOPAR PCM info available

In a message dated 10/26/2004 10:01:15 PM Eastern Standard Time, n5x= mt at bellsouth.net writes:

http://www.nancyknowshomes.com/dodg= e/97PCM/pcm.htm

id bet the adress lines a scrambled.

--------------Boundary-00=_AD186RO0000000000000-- --===============69914366046173226== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============69914366046173226==-- From Djfreggens at aol.com Wed Oct 27 02:45:11 2004 From: Djfreggens at aol.com (Djfreggens at aol.com) Date: Tue, 26 Oct 2004 23:45:11 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: --===============063568272161044437== Content-Type: multipart/alternative; boundary="-----------------------------1098844322" -------------------------------1098844322 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit again a dump wont do you any good. every piece of chyrsler code ive ever seen has a copyright in asccii test at the bottom of the rom. these do not. the only clear reasoning is that the adress line are muxed or something during programming. this is not even remotely beyond the capability of the 68hc vriants running in these ecms. -------------------------------1098844322 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable again a dump wont do you any good. every piece of chyrsler code ive ever=20= seen has a copyright in asccii test at the bottom of the rom. these do not.=20= the only clear reasoning is that the adress line are muxed or something duri= ng programming. this is not even remotely beyond the capability of the 68hc=20= vriants running in these ecms. -------------------------------1098844322-- --===============063568272161044437== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============063568272161044437==-- From Djfreggens at aol.com Wed Oct 27 02:47:48 2004 From: Djfreggens at aol.com (Djfreggens at aol.com) Date: Tue, 26 Oct 2004 23:47:48 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: --===============16279804055495473== Content-Type: multipart/alternative; boundary="-----------------------------1098844345" -------------------------------1098844345 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit i would get a dump of the rom on the actuall MCU,. that migth shed some real light on What is going on -------------------------------1098844345 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable i would get a dump of the rom on the actuall MCU,. that migth shed some r= eal light on What is going on -------------------------------1098844345-- --===============16279804055495473== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============16279804055495473==-- From Djfreggens at aol.com Wed Oct 27 03:01:06 2004 From: Djfreggens at aol.com (Djfreggens at aol.com) Date: Wed, 27 Oct 2004 00:01:06 -0300 Subject: [Diy_efi] MOPAR PCM info available Message-ID: --===============34386726056755634== Content-Type: multipart/alternative; boundary="-----------------------------1098844508" -------------------------------1098844508 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit obviously you havent been looking very hard. GM scrambeled the adress lines with muxes in the lt1 cars. they also did some back end hard coding on the internal rom of the MCU itself to support the mixed adress lines. -------------------------------1098844508 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
obviously you havent been looking very hard. GM scrambeled the adress l= ines with muxes in the lt1 cars. they also did some back end hard coding on=20= the internal rom of the MCU itself to support the mixed adress lines.

-------------------------------1098844508-- --===============34386726056755634== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============34386726056755634==-- From n5xmt at bellsouth.net Wed Oct 27 12:55:39 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Wed, 27 Oct 2004 09:55:39 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: --===============026933498167871495== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_JFU8G6G0000000000000" --------------Boundary-00=_JFU8G6G0000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable As I said, even the factory flash file looks identical to what is in the flash proms... it is both flash concatenated into a single file with a checksum so the DRB can check for file corruption before it applies the flash. The flash appears to be strictly data, and no code at all. I iha= ve to set up SCI direct to the CPU's to see if I can dump the ROM. Once I d= o that I will have a better idea what is going on... and the info I have i= s not speculation... I have received it from a person that works for a company that assembles, programs, reworks and tests the PCM's for Chrysle= r.=20 96 and newer Chrysler PCM's are a totally different animal than the 95 an= d earlier units.=0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/26/04 22:42:52=0D To: diy_efi at diy-efi.org=0D Subject: Re: [Diy_efi] Mopar PCM=0D =0D again a dump wont do you any good. every piece of chyrsler code ive ever seen has a copyright in asccii test at the bottom of the rom. these do no= t. the only clear reasoning is that the adress line are muxed or something during programming. this is not even remotely beyond the capability of th= e 68hc vriants running in these ecms. =0D =20 --------------Boundary-00=_JFU8G6G0000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

As I said, even the factory flash file looks identical to what= is in the flash proms... it is both flash concatenated into a single fil= e with a checksum so the DRB can check for file corruption before it appl= ies the flash. The flash appears to be strictly data, and no code a= t all. I ihave to set up SCI direct to the CPU's to see if I can du= mp the ROM. Once I do that I will have a better idea what is going = on... and the info I have is not speculation... I have receiv= ed it from a person that works for a company that assembles, programs, re= works and tests the PCM's for Chrysler. 96 and newer Chrysler PCM's= are a totally different animal than the 95 and earlier units.

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/26/04 22:= 42:52

To: diy_efi at diy-efi.org

Subject: Re: [Diy_= efi] Mopar PCM

again a dump wont do you any good. every piece of chyrsl= er code ive ever seen has a copyright in asccii test at the bottom of the= rom. these do not. the only clear reasoning is that the adress line are = muxed or something during programming. this is not even remotely beyond t= he capability of the 68hc vriants running in these ecms.=20

--------------Boundary-00=_JFU8G6G0000000000000-- --===============026933498167871495== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============026933498167871495==-- From n5xmt at bellsouth.net Wed Oct 27 12:58:26 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Wed, 27 Oct 2004 09:58:26 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: --===============30993204771687966== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_NGU86RO0000000000000" --------------Boundary-00=_NGU86RO0000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable That's what I am going to try next. I am hoping that I can tap into the = SCI at the CPU's themselves and dump it.=0D =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/26/04 22:46:35=0D To: diy_efi at diy-efi.org=0D Subject: Re: [Diy_efi] Mopar PCM=0D =0D i would get a dump of the rom on the actuall MCU,. that migth shed some r= eal light on What is going on =0D =20 --------------Boundary-00=_NGU86RO0000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

That's what I am going to try next. I am hoping that I can tap= into the SCI at the CPU's themselves and dump it.

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/26/04 22:= 46:35

To: diy_efi at diy-efi.org

Subject: Re: [Diy_= efi] Mopar PCM

i would get a dump of the rom on the actuall MCU,. that = migth shed some real light on What is going on=20

--------------Boundary-00=_NGU86RO0000000000000-- --===============30993204771687966== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============30993204771687966==-- From n5xmt at bellsouth.net Wed Oct 27 13:05:13 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Wed, 27 Oct 2004 10:05:13 -0300 Subject: [Diy_efi] MOPAR PCM info available Message-ID: --===============49568476195769762== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_ZHU8WCW0000000000000" --------------Boundary-00=_ZHU8WCW0000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The last GM I worked on was my 95 Buick Lesabre. and for that one I had = a copy of the official GM cal docs... almost 300 pages!=0D =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/26/04 23:02:01=0D To: diy_efi at diy-efi.org=0D Subject: Re: [Diy_efi] MOPAR PCM info available=0D =0D obviously you havent been looking very hard. GM scrambeled the adress lin= es with muxes in the lt1 cars. they also did some back end hard coding on th= e internal rom of the MCU itself to support the mixed adress lines. =0D =0D =0D =20 --------------Boundary-00=_ZHU8WCW0000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

The last GM I worked on was my 95 Buick Lesabre. and for that = one I had a copy of the official GM cal docs... almost 300 pages!

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/26/04 23:= 02:01

To: diy_efi at diy-efi.org

Subject: Re: [Diy_= efi] MOPAR PCM info available

obviously you havent been looking very hard. GM scrambeled the adres= s lines with muxes in the lt1 cars. they also did some back end hard codi= ng on the internal rom of the MCU itself to support the mixed adress line= s.

--------------Boundary-00=_ZHU8WCW0000000000000-- --===============49568476195769762== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============49568476195769762==-- From alexis.pavlov at st.com Wed Oct 27 13:18:47 2004 From: alexis.pavlov at st.com (Alexis PAVLOV) Date: Wed, 27 Oct 2004 10:18:47 -0300 Subject: [Diy_efi] Changing the fuel and spark on a Porsche Message-ID: Porsche engines use Bosch Motronic boxes. This one is probably of the M2.1 or M1.7 generation, based on the intel mcs96 controller, with knock sensors. I don't know how it's with 4cyl engines, but flat6 engines run very high compression ratio (above 11:1), so of course everything must be modified to use a charger. Bosch ECU are not really simple to program, there is not a lot of informations. In any case the stock ECU would not be able to control the pierburg valve for boost control, so an aftermarket ECU seems mandatory. Except if you completely re-program the box. Sell the original box and buy a race one, they are not so expensive now. May be it would be less expensive to sell your engine and buy a turbo one. "Gianmarco Rizzo (BE/EAS)" wrote: > > i have done a short research and apparently is not possible to change any parameter at all in the 968 stock ECU. Also, the car runs high compression to start with so forget turbocharging it unless pistons are changed for lower comp type, and a different ECU is fitted > > http://forums.beyond.ca/showthread/t-56892.html > > alos check this > www.986.net > > gm > > -----Original Message----- > From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On > Behalf Of Brian MacKay > Sent: Dienstag, 26. Oktober 2004 02:30 > To: A list for Do-It-Yourself EFI > Subject: RE: [Diy_efi] Changing the fuel and spark on a Porsche > > I agree 100%. My current car is a Grand National so I am used to tuning > under boost conditions. I cannot fathom why my normally intelligent friend > wants to do this. He must not value his time at all. > > Brian > > -----Original Message----- > From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On > Behalf Of Gianmarco Rizzo (BE/EAS) > Sent: October 25, 2004 6:14 AM > To: 'A list for Do-It-Yourself EFI' > Subject: RE: [Diy_efi] Changing the fuel and spark on a Porsche > > Hi Brian > > fitting a turbocharger without EFI adaptations will end up in a blown engine > very very quickly > > i dont' know what ECU the car uses but i'd recommend using a aftermarket > programmable EFI for best (and safe) results > > -----Original Message----- > From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org]On > Behalf Of Brian MacKay > Sent: Samstag, 23. Oktober 2004 03:48 > To: diy_efi at diy-efi.org > Subject: [Diy_efi] Changing the fuel and spark on a Porsche > > I have a friend to races a Porsche and while he knows a lot about cars, he > knows nothing about the guts of his EFI. He insists on making major > mechanical changes to the engine and doesn't consider the fact that the > computer won't necessarily make good corrections. He plans to turbo charge > the car and is assuming everything will be fine without modifying the > computer. > > My background is that I regularly modify code and look up tables in my GM > ECM but I know nothing about Porsche stuff, like what processor is used, > does it use EPROMS, etc. The car is a 1992 Porsche 968 therefore OBD-I. > Can anyone point me to any references or websites where I can learn more and > hopefully prevent him from blowing up another engine! > > Thanks, > > Brian > > _______________________________________________ > diy_efi mailing list > diy_efi at diy-efi.org > http://lists.diy-efi.org/mailman/listinfo/diy_efi > _______________________________________________ > diy_efi mailing list > diy_efi at diy-efi.org > http://lists.diy-efi.org/mailman/listinfo/diy_efi > > _______________________________________________ > diy_efi mailing list > diy_efi at diy-efi.org > http://lists.diy-efi.org/mailman/listinfo/diy_efi > _______________________________________________ > diy_efi mailing list > diy_efi at diy-efi.org > http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From pwilson22000 at yahoo.com Wed Oct 27 17:54:11 2004 From: pwilson22000 at yahoo.com (Paul Wilson) Date: Wed, 27 Oct 2004 14:54:11 -0300 Subject: [Diy_efi] GM OBD 2 Message-ID: --===============37331682783913189== Content-Type: multipart/alternative; boundary="0-1761607006-1098899439=:81453" --0-1761607006-1098899439=:81453 Content-Type: text/plain; charset=us-ascii Has any worked with any of the OBD 2 ECM's? I'm interested specifically in grand prix or other 3800 powered cars hardward and software used. Any help will be greatly appreciated. --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. --0-1761607006-1098899439=:81453 Content-Type: text/html; charset=us-ascii
Has any worked with any of the OBD 2 ECM's? I'm interested specifically in grand prix or other 3800 powered cars hardward and software used. Any help will be greatly appreciated.

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish. --0-1761607006-1098899439=:81453-- --===============37331682783913189== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============37331682783913189==-- From Steve.Ravet at arm.com Wed Oct 27 19:10:59 2004 From: Steve.Ravet at arm.com (Steve Ravet) Date: Wed, 27 Oct 2004 16:10:59 -0300 Subject: [Diy_efi] GM OBD 2 Message-ID: This is a multi-part message in MIME format. --===============46203807704310229== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4BC58.2ECDB591" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4BC58.2ECDB591 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Take a look at the OBD2 page on the gmecm page (click ECM info, then = OBD2). There's a project listed for '96/'97 V6 cars that allows you to = dump the flash. =20 --steve ________________________________ From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] = On Behalf Of Paul Wilson Sent: Wednesday, October 27, 2004 12:51 PM To: diy_efi at diy-efi.org Subject: [Diy_efi] GM OBD 2=20 =09 =09 Has any worked with any of the OBD 2 ECM's? I'm interested = specifically in grand prix or other 3800 powered cars hardward and = software used. Any help will be greatly appreciated. =09 ________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete = - You start. We finish. ------_=_NextPart_001_01C4BC58.2ECDB591 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Take a look at the OBD2 page on the gmecm = page (click=20 ECM info, then OBD2). There's a project listed for '96/'97 V6 cars = that=20 allows you to dump the flash.

--steve

From: = diy_efi-bounces at diy-efi.org=20 [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of Paul=20 Wilson
Sent: Wednesday, October 27, 2004 12:51 = PM
To:=20 diy_efi at diy-efi.org
Subject: [Diy_efi] GM OBD 2 =

Has any worked with any of the OBD 2 ECM's? I'm interested=20 specifically in grand prix or other 3800 powered cars hardward and = software=20 used. Any help will be greatly appreciated.

Do you Yahoo!?
Yahoo!=20 Mail Address AutoComplete - You start. We = finish. ------_=_NextPart_001_01C4BC58.2ECDB591-- --===============46203807704310229== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============46203807704310229==-- From brian.trulove at charter.net Wed Oct 27 20:04:40 2004 From: brian.trulove at charter.net (brian.trulove at charter.net) Date: Wed, 27 Oct 2004 17:04:40 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: This is a multi-part message in MIME format. ------=____1098907296757_K'EcWgY-3O Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Anyway to reverse engineer the application I sent you to see how Chrysler accesses the flash via SCI? Data logger maybe? > > From: "David Cooley" > Date: 2004/10/27 Wed PM 12:52:31 GMT > To: > Subject: Re: [Diy_efi] Mopar PCM > > As I said, even the factory flash file looks identical to what is in the > flash proms... it is both flash concatenated into a single file with a > checksum so the DRB can check for file corruption before it applies the > flash. The flash appears to be strictly data, and no code at all. I ihave > to set up SCI direct to the CPU's to see if I can dump the ROM. Once I do > that I will have a better idea what is going on... and the info I have is > not speculation... I have received it from a person that works for a > company that assembles, programs, reworks and tests the PCM's for Chrysler. > 96 and newer Chrysler PCM's are a totally different animal than the 95 and > earlier units. > > > > -------Original Message------- > > > > From: A list for Do-It-Yourself EFI > > Date: 10/26/04 22:42:52 > > To: diy_efi at diy-efi.org > > Subject: Re: [Diy_efi] Mopar PCM > > > > again a dump wont do you any good. every piece of chyrsler code ive ever > seen has a copyright in asccii test at the bottom of the rom. these do not. > the only clear reasoning is that the adress line are muxed or something > during programming. this is not even remotely beyond the capability of the > 68hc vriants running in these ecms. > > > ------=____1098907296757_K'EcWgY-3O Content-Type: text/plain; charset="us-ascii"; name="reply" Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi ------=____1098907296757_K'EcWgY-3O Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi ------=____1098907296757_K'EcWgY-3O-- From espresso_doppio at yahoo.com Wed Oct 27 20:31:44 2004 From: espresso_doppio at yahoo.com (Adam Wade) Date: Wed, 27 Oct 2004 17:31:44 -0300 Subject: [Diy_efi] Factory turbo motorcycle reverse engineering project Message-ID: Well, I am working on developing chips for the Honda CX500 Turbo and hopefully the CX650 Turbo as well. Here's what I have so far: "As I surmised in an earlier post, the CX500T unit had a 8xxx MPU of some sort as the box used the 8253 PIT, which is used with the 8xxx family. Futher investigation of the pinouts leads me to believe the MCU is in the 8035/39/40 sub-family. Nipondenso is large enought to fab their own chips, but I think they only "branded" the available chip with their number...ND079753-0021. I tried to read on-board ROM as an 8048/49, but got nothing in the read buffer. The 8035 units are CPU only with no memory on-board. All these chips use the same pinout. The companion chip is a 8755. The 2716 eeprom is standard." I have hex dumps of both the 2716 and the 8755. I am trying to sort out which maps are where, and to disassemble the machine code, as there is an overboost fuel cut-off I wish to eliminate. If I can't get it sorted to where I can burn my own chip, I may just build a Megasquirt. But since I can socket the EPROM, it makes more sense to me to just do tabletop work and save my money and testing effort. :) I have access to a step-testing eddy current dyno, as well as an attached four-gas analyzer and an emulator, so once I get the code and the maps sussed, tuning and burning a replacement chip will be simple and easy. Old-tech wizards, I'm looking forward to hearing from you. :) ===== | 82 Honda CX500 Turbo (Cassandra) 90 Kwak Zephyr 550 (Daphne) | | "It was like an emergency ward after a great catastrophe; it | | didn't matter what race or class the victims belonged to. | | They were all given the same miracle drug, which was coffee. | | The catastrophe in this case, of course, was that the sun | | had come up again." -Kurt Vonnegut | | Buy my M/C Fuel Inj. Handbook - http://tinyurl.com/2e8eu | __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From n5xmt at bellsouth.net Wed Oct 27 21:15:26 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Wed, 27 Oct 2004 18:15:26 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: --===============30937039691171808== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_7IH9QL80000000000000" --------------Boundary-00=_7IH9QL80000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hmm... I do have a disassembler for windows programs! =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/27/04 16:02:24=0D To: A list for Do-It-Yourself EFI=0D Subject: Re: Re: [Diy_efi] Mopar PCM=0D =0D Anyway to reverse engineer the application I sent you to see how Chrysler accesses the flash via SCI? Data logger maybe?=0D >=0D > From: "David Cooley" =0D > Date: 2004/10/27 Wed PM 12:52:31 GMT=0D > To: =0D > Subject: Re: [Diy_efi] Mopar PCM=0D >=0D > As I said, even the factory flash file looks identical to what is in t= he=0D > flash proms... it is both flash concatenated into a single file with a=0D > checksum so the DRB can check for file corruption before it applies the= =0D > flash. The flash appears to be strictly data, and no code at all. I ihave=0D > to set up SCI direct to the CPU's to see if I can dump the ROM. Once I= do=0D > that I will have a better idea what is going on... and the info I have= is=0D > not speculation... I have received it from a person that works for a=0D > company that assembles, programs, reworks and tests the PCM's for Chrys= ler =0D > 96 and newer Chrysler PCM's are a totally different animal than the 95 = and=0D > earlier units.=0D >=0D >=0D >=0D > -------Original Message-------=0D >=0D >=0D >=0D > From: A list for Do-It-Yourself EFI=0D >=0D > Date: 10/26/04 22:42:52=0D >=0D > To: diy_efi at diy-efi.org=0D >=0D > Subject: Re: [Diy_efi] Mopar PCM=0D >=0D >=0D >=0D > again a dump wont do you any good. every piece of chyrsler code ive eve= r=0D > seen has a copyright in asccii test at the bottom of the rom. these do = not =0D > the only clear reasoning is that the adress line are muxed or something= =0D > during programming. this is not even remotely beyond the capability of = the=0D > 68hc vriants running in these ecms.=0D >=0D >=0D >=0D =0D =20 --------------Boundary-00=_7IH9QL80000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hmm... I do have a disassembler for windows programs!

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/27/04 16:= 02:24

To: A list for Do-It-Yourself EFI

Subject: Re: Re: [= Diy_efi] Mopar PCM

Anyway to reverse engineer the application I sent you to see how Chr= ysler accesses the flash via SCI? Data logger maybe?

>

> From: "David Cooley" <n5xmt at bellsouth.net>

> Date: 2004/10/27 Wed PM 12:52:31 GMT

> To: <diy_efi at diy-efi.= org>

> Subject: Re: [Diy_efi] Mopar PCM

>

>  As I said, even the factory flash file looks identic= al to what is in the

> flash proms... it is both flash concatenated into a single file= with a

> checksum so the DRB can check for file corruption before it app= lies the

> flash.  The flash appears to be strictly data, and no= code at all.  I ihave

> to set up SCI direct to the CPU's to see if I can dump the ROM.=   Once I do

> that I will have a better idea what is going on...  a= nd the info I have is

> not speculation...  I have received it from a person = that works for a

> company that assembles, programs, reworks and tests the PCM's f= or Chrysler.

> 96 and newer Chrysler PCM's are a totally different animal than= the 95 and

> earlier units.

>

>

>

> -------Original Message-------

>

>

>

> From: A list for Do-It-Yourself EFI

>

> Date: 10/26/04 22:42:52

>

> To: diy_efi at diy-efi.org<= /A>

>

> Subject: Re: [Diy_efi] Mopar PCM

>

>

>

> again a dump wont do you any good. every piece of chyrsler code= ive ever

> seen has a copyright in asccii test at the bottom of the rom. t= hese do not.

> the only clear reasoning is that the adress line are muxed or s= omething

> during programming. this is not even remotely beyond the capabi= lity of the

> 68hc vriants running in these ecms.

>

>

>

--------------Boundary-00=_7IH9QL80000000000000-- --===============30937039691171808== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============30937039691171808==-- From pwilson22000 at yahoo.com Thu Oct 28 00:06:44 2004 From: pwilson22000 at yahoo.com (Paul Wilson) Date: Wed, 27 Oct 2004 21:06:44 -0300 Subject: [Diy_efi] GM OBD 2 Message-ID: --===============47995375661766726== Content-Type: multipart/alternative; boundary="0-319594777-1098921855=:15923" --0-319594777-1098921855=:15923 Content-Type: text/plain; charset=us-ascii Is this the link you were referring too? www.diy-efi.org/gmecm/ecm_info/ I didn't see any info for the 96/97 cars. Steve Ravet wrote:Take a look at the OBD2 page on the gmecm page (click ECM info, then OBD2). There's a project listed for '96/'97 V6 cars that allows you to dump the flash. --steve --------------------------------- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of Paul Wilson Sent: Wednesday, October 27, 2004 12:51 PM To: diy_efi at diy-efi.org Subject: [Diy_efi] GM OBD 2 Has any worked with any of the OBD 2 ECM's? I'm interested specifically in grand prix or other 3800 powered cars hardward and software used. Any help will be greatly appreciated. --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish._______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --------------------------------- Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. --0-319594777-1098921855=:15923 Content-Type: text/html; charset=us-ascii
Is this the link you were referring too? www.diy-efi.org/gmecm/ecm_info/ I didn't see any info for the 96/97 cars.

Steve Ravet <Steve.Ravet at arm.com> wrote:

Take a look at the OBD2 page on the gmecm page (click ECM info, then OBD2). There's a project listed for '96/'97 V6 cars that allows you to dump the flash.

--steve

From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of Paul Wilson
Sent: Wednesday, October 27, 2004 12:51 PM
To: diy_efi at diy-efi.org
Subject: [Diy_efi] GM OBD 2

Has any worked with any of the OBD 2 ECM's? I'm interested specifically in grand prix or other 3800 powered cars hardward and software used. Any help will be greatly appreciated.

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
_______________________________________________
diy_efi mailing list
diy_efi at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/diy_efi

Do you Yahoo!?
Y! Messenger - Communicate in real time. Download now. --0-319594777-1098921855=:15923-- --===============47995375661766726== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============47995375661766726==-- From enlight22 at hotmail.com Thu Oct 28 00:46:57 2004 From: enlight22 at hotmail.com (biob dobbs) Date: Wed, 27 Oct 2004 21:46:57 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: What program is this you are looking at disassembling, that j(some number) program from daimler chrysler? >From: "David Cooley" >Reply-To: A list for Do-It-Yourself EFI >To: >Subject: Re: Re: [Diy_efi] Mopar PCM >Date: Wed, 27 Oct 2004 17:10:55 -0400 (Eastern Daylight Time) > >Hmm... I do have a disassembler for windows programs! > >-------Original Message------- > >From: A list for Do-It-Yourself EFI >Date: 10/27/04 16:02:24 >To: A list for Do-It-Yourself EFI >Subject: Re: Re: [Diy_efi] Mopar PCM > >Anyway to reverse engineer the application I sent you to see how Chrysler >accesses the flash via SCI? Data logger maybe? > > > > From: "David Cooley" > > Date: 2004/10/27 Wed PM 12:52:31 GMT > > To: > > Subject: Re: [Diy_efi] Mopar PCM > > > > As I said, even the factory flash file looks identical to what is in >the > > flash proms... it is both flash concatenated into a single file with a > > checksum so the DRB can check for file corruption before it applies the > > flash. The flash appears to be strictly data, and no code at all. I >ihave > > to set up SCI direct to the CPU's to see if I can dump the ROM. Once I >do > > that I will have a better idea what is going on... and the info I have >is > > not speculation... I have received it from a person that works for a > > company that assembles, programs, reworks and tests the PCM's for >Chrysler > > > 96 and newer Chrysler PCM's are a totally different animal than the 95 >and > > earlier units. > > > > > > > > -------Original Message------- > > > > > > > > From: A list for Do-It-Yourself EFI > > > > Date: 10/26/04 22:42:52 > > > > To: diy_efi at diy-efi.org > > > > Subject: Re: [Diy_efi] Mopar PCM > > > > > > > > again a dump wont do you any good. every piece of chyrsler code ive ever > > seen has a copyright in asccii test at the bottom of the rom. these do >not > > > the only clear reasoning is that the adress line are muxed or something > > during programming. this is not even remotely beyond the capability of >the > > 68hc vriants running in these ecms. > > > > > > > > >_______________________________________________ >diy_efi mailing list >diy_efi at diy-efi.org >http://lists.diy-efi.org/mailman/listinfo/diy_efi _________________________________________________________________ Check out Election 2004 for up-to-date election news, plus voter tools and more! http://special.msn.com/msn/election2004.armx _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From brian.trulove at charter.net Thu Oct 28 01:07:25 2004 From: brian.trulove at charter.net (Brian Trulove) Date: Wed, 27 Oct 2004 22:07:25 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: That is correct. It is an application by which flash upgrades are loaded = to the pcm by other than DRBIII interfaces. -----Original Message----- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] = On Behalf Of biob dobbs Sent: Wednesday, October 27, 2004 7:45 PM To: diy_efi at diy-efi.org Subject: Re: Re: [Diy_efi] Mopar PCM What program is this you are looking at disassembling, that j(some = number)=20 program from daimler chrysler? >From: "David Cooley" >Reply-To: A list for Do-It-Yourself EFI >To: >Subject: Re: Re: [Diy_efi] Mopar PCM >Date: Wed, 27 Oct 2004 17:10:55 -0400 (Eastern Daylight Time) > >Hmm... I do have a disassembler for windows programs! > >-------Original Message------- > >From: A list for Do-It-Yourself EFI >Date: 10/27/04 16:02:24 >To: A list for Do-It-Yourself EFI >Subject: Re: Re: [Diy_efi] Mopar PCM > >Anyway to reverse engineer the application I sent you to see how = Chrysler >accesses the flash via SCI? Data logger maybe? > > > > From: "David Cooley" > > Date: 2004/10/27 Wed PM 12:52:31 GMT > > To: > > Subject: Re: [Diy_efi] Mopar PCM > > > > As I said, even the factory flash file looks identical to what is = in=20 >the > > flash proms... it is both flash concatenated into a single file with = a > > checksum so the DRB can check for file corruption before it applies = the > > flash. The flash appears to be strictly data, and no code at all. = I >ihave > > to set up SCI direct to the CPU's to see if I can dump the ROM. = Once I=20 >do > > that I will have a better idea what is going on... and the info I = have=20 >is > > not speculation... I have received it from a person that works for = a > > company that assembles, programs, reworks and tests the PCM's for=20 >Chrysler > > > 96 and newer Chrysler PCM's are a totally different animal than the = 95=20 >and > > earlier units. > > > > > > > > -------Original Message------- > > > > > > > > From: A list for Do-It-Yourself EFI > > > > Date: 10/26/04 22:42:52 > > > > To: diy_efi at diy-efi.org > > > > Subject: Re: [Diy_efi] Mopar PCM > > > > > > > > again a dump wont do you any good. every piece of chyrsler code ive = ever > > seen has a copyright in asccii test at the bottom of the rom. these = do=20 >not > > > the only clear reasoning is that the adress line are muxed or = something > > during programming. this is not even remotely beyond the capability = of=20 >the > > 68hc vriants running in these ecms. > > > > > > > > >_______________________________________________ >diy_efi mailing list >diy_efi at diy-efi.org >http://lists.diy-efi.org/mailman/listinfo/diy_efi _________________________________________________________________ Check out Election 2004 for up-to-date election news, plus voter tools = and=20 more! http://special.msn.com/msn/election2004.armx _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From n5xmt at bellsouth.net Thu Oct 28 01:22:17 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Wed, 27 Oct 2004 22:22:17 -0300 Subject: [Diy_efi] GM OBD 2 Message-ID: yep... under a bit of info about OBD2, there is a link on that page at the bottom... -------Original Message------- From: A list for Do-It-Yourself EFI Date: 10/27/04 20:04:34 To: A list for Do-It-Yourself EFI Subject: RE: [Diy_efi] GM OBD 2 Is this the link you were referring too? www.diy-efi.org/gmecm/ecm_info/ I didn't see any info for the 96/97 cars. Steve Ravet wrote: Take a look at the OBD2 page on the gmecm page (click ECM info, then OBD2). There's a project listed for '96/'97 V6 cars that allows you to dump the flash. --steve From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of Paul Wilson Sent: Wednesday, October 27, 2004 12:51 PM To: diy_efi at diy-efi.org Subject: [Diy_efi] GM OBD 2 Has any worked with any of the OBD 2 ECM's? I'm interested specifically in grand prix or other 3800 powered cars hardward and software used. Any help will be greatly appreciated. Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From n5xmt at bellsouth.net Thu Oct 28 01:25:45 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Wed, 27 Oct 2004 22:25:45 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: --===============6084396008842905== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_GTS9G6G0000000000000" --------------Boundary-00=_GTS9G6G0000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Interactive Disassembler Pro =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/27/04 20:49:14=0D To: diy_efi at diy-efi.org=0D Subject: Re: Re: [Diy_efi] Mopar PCM=0D =0D What program is this you are looking at disassembling, that j(some number= )=0D program from daimler chrysler?=0D =0D =0D >From: "David Cooley" =0D >Reply-To: A list for Do-It-Yourself EFI =0D >To: =0D >Subject: Re: Re: [Diy_efi] Mopar PCM=0D >Date: Wed, 27 Oct 2004 17:10:55 -0400 (Eastern Daylight Time)=0D >=0D >Hmm... I do have a disassembler for windows programs!=0D >=0D >-------Original Message-------=0D >=0D >From: A list for Do-It-Yourself EFI=0D >Date: 10/27/04 16:02:24=0D >To: A list for Do-It-Yourself EFI=0D >Subject: Re: Re: [Diy_efi] Mopar PCM=0D >=0D >Anyway to reverse engineer the application I sent you to see how Chrysle= r=0D >accesses the flash via SCI? Data logger maybe?=0D > >=0D > > From: "David Cooley" =0D > > Date: 2004/10/27 Wed PM 12:52:31 GMT=0D > > To: =0D > > Subject: Re: [Diy_efi] Mopar PCM=0D > >=0D > > As I said, even the factory flash file looks identical to what is in= =0D >the=0D > > flash proms... it is both flash concatenated into a single file with = a=0D > > checksum so the DRB can check for file corruption before it applies t= he=0D > > flash. The flash appears to be strictly data, and no code at all. I= =0D >ihave=0D > > to set up SCI direct to the CPU's to see if I can dump the ROM. Once= I=0D >do=0D > > that I will have a better idea what is going on... and the info I ha= ve=0D >is=0D > > not speculation... I have received it from a person that works for a= =0D > > company that assembles, programs, reworks and tests the PCM's for=0D >Chrysler=0D >=0D > > 96 and newer Chrysler PCM's are a totally different animal than the 9= 5=0D >and=0D > > earlier units.=0D > >=0D > >=0D > >=0D > > -------Original Message-------=0D > >=0D > >=0D > >=0D > > From: A list for Do-It-Yourself EFI=0D > >=0D > > Date: 10/26/04 22:42:52=0D > >=0D > > To: diy_efi at diy-efi.org=0D > >=0D > > Subject: Re: [Diy_efi] Mopar PCM=0D > >=0D > >=0D > >=0D > > again a dump wont do you any good. every piece of chyrsler code ive e= ver=0D > > seen has a copyright in asccii test at the bottom of the rom. these d= o=0D >not=0D >=0D > > the only clear reasoning is that the adress line are muxed or somethi= ng=0D > > during programming. this is not even remotely beyond the capability o= f=0D >the=0D > > 68hc vriants running in these ecms.=0D > >=0D > >=0D > >=0D >=0D >=0D >_______________________________________________=0D >diy_efi mailing list=0D >diy_efi at diy-efi.org=0D >http://lists.diy-efi.org/mailman/listinfo/diy_efi=0D =0D _________________________________________________________________=0D Check out Election 2004 for up-to-date election news, plus voter tools an= d=0D more! http://special.msn.com/msn/election2004.armx=0D =0D _______________________________________________=0D diy_efi mailing list=0D diy_efi at diy-efi.org=0D http://lists.diy-efi.org/mailman/listinfo/diy_efi=0D =20 --------------Boundary-00=_GTS9G6G0000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Interactive Disassembler Pro

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/27/04 20:= 49:14

To: diy_efi at diy-efi.org

Subject: Re: Re: [= Diy_efi] Mopar PCM

What program is this you are looking at disassembling, that j(some n= umber)

program from daimler chrysler?

>From: "David Cooley" <= n5xmt at bellsouth.net>

>Reply-To: A list for Do-It-Yourself EFI <diy_efi at diy-efi.org>

>To: <diy_efi at diy-efi.o= rg>

>Subject: Re: Re: [Diy_efi] Mopar PCM

>Date: Wed, 27 Oct 2004 17:10:55 -0400 (Eastern Daylight Time)
>

>Hmm... I do have a disassembler for windows programs!

>

>-------Original Message-------

>

>From: A list for Do-It-Yourself EFI

>Date: 10/27/04 16:02:24

>To: A list for Do-It-Yourself EFI

>Subject: Re: Re: [Diy_efi] Mopar PCM

>

>Anyway to reverse engineer the application I sent you to see how= Chrysler

>accesses the flash via SCI? Data logger maybe?

> >

> > From: "David Cooley" <n5xmt at bellsouth.net>

> > Date: 2004/10/27 Wed PM 12:52:31 GMT

> > To: <diy_efi at diy= -efi.org>

> > Subject: Re: [Diy_efi] Mopar PCM

> >

> >  As I said, even the factory flash file looks id= entical to what is in

>the

> > flash proms... it is both flash concatenated into a single= file with a

> > checksum so the DRB can check for file corruption before i= t applies the

> > flash.  The flash appears to be strictly data, a= nd no code at all.  I

>ihave

> > to set up SCI direct to the CPU's to see if I can dump the= ROM.  Once I

>do

> > that I will have a better idea what is going on... &n= bsp;and the info I have

>is

> > not speculation...  I have received it from a pe= rson that works for a

> > company that assembles, programs, reworks and tests the PC= M's for

>Chrysler

>

> > 96 and newer Chrysler PCM's are a totally different animal= than the 95

>and

> > earlier units.

> >

> >

> >

> > -------Original Message-------

> >

> >

> >

> > From: A list for Do-It-Yourself EFI

> >

> > Date: 10/26/04 22:42:52

> >

> > To: diy_efi at diy-efi= =2Eorg

> >

> > Subject: Re: [Diy_efi] Mopar PCM

> >

> >

> >

> > again a dump wont do you any good. every piece of chyrsler= code ive ever

> > seen has a copyright in asccii test at the bottom of the r= om. these do

>not

>

> > the only clear reasoning is that the adress line are muxed= or something

> > during programming. this is not even remotely beyond the c= apability of

>the

> > 68hc vriants running in these ecms.

> >

> >

> >

>

>

>_______________________________________________

>diy_efi mailing list

>diy_efi at diy-efi.or= g

>ht= tp://lists.diy-efi.org/mailman/listinfo/diy_efi

_________________________________________________________________
Check out Election 2004 for up-to-date election news, plus voter too= ls and

more! http:= //special.msn.com/msn/election2004.armx

_______________________________________________

diy_efi mailing list

diy_efi at diy-efi.org

http:/= /lists.diy-efi.org/mailman/listinfo/diy_efi

--------------Boundary-00=_GTS9G6G0000000000000-- --===============6084396008842905== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============6084396008842905==-- From Steve.Ravet at arm.com Thu Oct 28 02:01:29 2004 From: Steve.Ravet at arm.com (Steve Ravet) Date: Wed, 27 Oct 2004 23:01:29 -0300 Subject: [Diy_efi] GM OBD 2 Message-ID: This is a multi-part message in MIME format. --===============95423770144421782== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4BC91.A825CE1F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4BC91.A825CE1F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable whoops. Before the crash there was some info on the 96/97 on that page. = The reflash article is still there, click "Using BDM" to get it. =20 --steve ________________________________ From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] = On Behalf Of Paul Wilson Sent: Wednesday, October 27, 2004 7:04 PM To: A list for Do-It-Yourself EFI Subject: RE: [Diy_efi] GM OBD 2=20 =09 =09 Is this the link you were referring too? = www.diy-efi.org/gmecm/ecm_info/ I didn't see any info for the 96/97 = cars. =09 Steve Ravet wrote:=20 Take a look at the OBD2 page on the gmecm page (click ECM info, then = OBD2). There's a project listed for '96/'97 V6 cars that allows you to = dump the flash. =20 --steve ________________________________ From: diy_efi-bounces at diy-efi.org = [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of Paul Wilson Sent: Wednesday, October 27, 2004 12:51 PM To: diy_efi at diy-efi.org Subject: [Diy_efi] GM OBD 2=20 =09 =09 Has any worked with any of the OBD 2 ECM's? I'm interested = specifically in grand prix or other 3800 powered cars hardward and = software used. Any help will be greatly appreciated. =09 ________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete = - You start. We finish. _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi =09 =09 ________________________________ Do you Yahoo!? Y! Messenger = - Communicate in real time. Download now. ------_=_NextPart_001_01C4BC91.A825CE1F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
whoops. Before the crash there was some = info on=20 the 96/97 on that page. The reflash article is still there, click = "Using=20 BDM" to get it.

--steve

From: = diy_efi-bounces at diy-efi.org=20 [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of Paul=20 Wilson
Sent: Wednesday, October 27, 2004 7:04 = PM
To: A=20 list for Do-It-Yourself EFI
Subject: RE: [Diy_efi] GM OBD 2=20

Is this the link you were referring too? www.diy-efi.org/gmecm/ecm= _info/ =20 I didn't see any info for the 96/97 cars.

Steve Ravet=20 <Steve.Ravet at arm.com> wrote:=20

Take a look at the OBD2 page on the gmecm = page=20 (click ECM info, then OBD2). There's a project listed for = '96/'97 V6=20 cars that allows you to dump the flash.

--steve

From: = diy_efi-bounces at diy-efi.org=20 [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of Paul=20 Wilson
Sent: Wednesday, October 27, 2004 12:51 = PM
To:=20 diy_efi at diy-efi.org
Subject: [Diy_efi] GM OBD 2 =

Has any worked with any of the OBD 2 ECM's? I'm = interested=20 specifically in grand prix or other 3800 powered cars hardward and = software used. Any help will be greatly appreciated.

Do you Yahoo!?
Yahoo!=20 Mail Address AutoComplete - You start. We=20 = finish.
_______________________________________________
di= y_efi=20 mailing=20 = list
diy_efi at diy-efi.org
http://lists.diy-efi.org/mailman/listinfo/= diy_efi

Do you Yahoo!?
Y!=20 Messenger - Communicate in real time. Download=20 now. ------_=_NextPart_001_01C4BC91.A825CE1F-- --===============95423770144421782== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============95423770144421782==-- From instigatr at merkurboys.com Thu Oct 28 02:32:22 2004 From: instigatr at merkurboys.com (Aaron) Date: Wed, 27 Oct 2004 23:32:22 -0300 Subject: [Diy_efi] anyone doing GM TBI ECU's? Message-ID: This is a multi-part message in MIME format. --===============91439929487467131== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C4BC5B.7AA84370" This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C4BC5B.7AA84370 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello New guy here. I have no experience reprogramming, but my little brother = has done so extensively on mopar computers. What I=92m wondering is, can the = gm TBI system be reprogrammed? If so, what mods need to be done, and where = can the modification program and such be found? Two vehicles I=92m primarily interested in =96 (1) =96 GM 454 system. This would be adapted to fit on a caddy 500, = with twin turbo=92s (2) - I have a 94 GMC that I would to get more power out of to pull = my trailer. any help would be appreciated. Thanks Aaron =20 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004 =20 ------=_NextPart_000_0007_01C4BC5B.7AA84370 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hello

New guy here. I have no experience reprogramming, but = my little brother has done so extensively on mopar computers. What I=92m wondering is, can the gm TBI system be reprogrammed? If so, what mods = need to be done, and where can the modification program and such be = found?

Two vehicles I=92m primarily interested in = =96

(1)     =96 GM 454 system. This would be adapted to = fit on a caddy 500, with twin turbo=92s

(2)     =A0- I have a 94 GMC that I would to get more = power out of to pull my trailer.

any help would be appreciated.

Thanks

Aaron

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004

------=_NextPart_000_0007_01C4BC5B.7AA84370-- --===============91439929487467131== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============91439929487467131==-- From Steve.Ravet at arm.com Thu Oct 28 04:43:28 2004 From: Steve.Ravet at arm.com (Steve Ravet) Date: Thu, 28 Oct 2004 01:43:28 -0300 Subject: [Diy_efi] anyone doing GM TBI ECU's? Message-ID: The GM TBI systems are about the most well understood computers out = there. Be prepared to spend some time reading, you'll be able to find = out as much as you want to about it. Start with the programming 101 = article which describes the truck TBI computer. Go to tunercat.com and = download the demo, and you can see the tables and get a feel for how = they work. --steve=20 ________________________________ From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] = On Behalf Of Aaron Sent: Wednesday, October 27, 2004 9:31 PM To: diy_efi at diy-efi.org Subject: [Diy_efi] anyone doing GM TBI ECU's? =09 =09 Hello New guy here. I have no experience reprogramming, but my little brother = has done so extensively on mopar computers. What I=92m wondering is, can = the gm TBI system be reprogrammed? If so, what mods need to be done, and = where can the modification program and such be found? Two vehicles I=92m primarily interested in =96 (1) =96 GM 454 system. This would be adapted to fit on a caddy 500, = with twin turbo=92s (2) - I have a 94 GMC that I would to get more power out of to = pull my trailer. any help would be appreciated. Thanks Aaron =20 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004 =09 _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From enlight22 at hotmail.com Thu Oct 28 07:03:35 2004 From: enlight22 at hotmail.com (biob dobbs) Date: Thu, 28 Oct 2004 04:03:35 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: would anyone be willing to post this program, or send it to me? >From: "Brian Trulove" >Reply-To: A list for Do-It-Yourself EFI >To: "'A list for Do-It-Yourself EFI'" >Subject: RE: Re: [Diy_efi] Mopar PCM >Date: Wed, 27 Oct 2004 19:57:10 -0500 > >That is correct. It is an application by which flash upgrades are loaded to >the pcm by other than DRBIII interfaces. > >-----Original Message----- >From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] On >Behalf Of biob dobbs >Sent: Wednesday, October 27, 2004 7:45 PM >To: diy_efi at diy-efi.org >Subject: Re: Re: [Diy_efi] Mopar PCM > >What program is this you are looking at disassembling, that j(some number) >program from daimler chrysler? > > > >From: "David Cooley" > >Reply-To: A list for Do-It-Yourself EFI > >To: > >Subject: Re: Re: [Diy_efi] Mopar PCM > >Date: Wed, 27 Oct 2004 17:10:55 -0400 (Eastern Daylight Time) > > > >Hmm... I do have a disassembler for windows programs! > > > >-------Original Message------- > > > >From: A list for Do-It-Yourself EFI > >Date: 10/27/04 16:02:24 > >To: A list for Do-It-Yourself EFI > >Subject: Re: Re: [Diy_efi] Mopar PCM > > > >Anyway to reverse engineer the application I sent you to see how Chrysler > >accesses the flash via SCI? Data logger maybe? > > > > > > From: "David Cooley" > > > Date: 2004/10/27 Wed PM 12:52:31 GMT > > > To: > > > Subject: Re: [Diy_efi] Mopar PCM > > > > > > As I said, even the factory flash file looks identical to what is in > >the > > > flash proms... it is both flash concatenated into a single file with a > > > checksum so the DRB can check for file corruption before it applies >the > > > flash. The flash appears to be strictly data, and no code at all. I > >ihave > > > to set up SCI direct to the CPU's to see if I can dump the ROM. Once >I > >do > > > that I will have a better idea what is going on... and the info I >have > >is > > > not speculation... I have received it from a person that works for a > > > company that assembles, programs, reworks and tests the PCM's for > >Chrysler > > > > > 96 and newer Chrysler PCM's are a totally different animal than the 95 > >and > > > earlier units. > > > > > > > > > > > > -------Original Message------- > > > > > > > > > > > > From: A list for Do-It-Yourself EFI > > > > > > Date: 10/26/04 22:42:52 > > > > > > To: diy_efi at diy-efi.org > > > > > > Subject: Re: [Diy_efi] Mopar PCM > > > > > > > > > > > > again a dump wont do you any good. every piece of chyrsler code ive >ever > > > seen has a copyright in asccii test at the bottom of the rom. these do > >not > > > > > the only clear reasoning is that the adress line are muxed or >something > > > during programming. this is not even remotely beyond the capability of > >the > > > 68hc vriants running in these ecms. > > > > > > > > > > > > > > >_______________________________________________ > >diy_efi mailing list > >diy_efi at diy-efi.org > >http://lists.diy-efi.org/mailman/listinfo/diy_efi > >_________________________________________________________________ >Check out Election 2004 for up-to-date election news, plus voter tools and >more! http://special.msn.com/msn/election2004.armx > >_______________________________________________ >diy_efi mailing list >diy_efi at diy-efi.org >http://lists.diy-efi.org/mailman/listinfo/diy_efi > > >_______________________________________________ >diy_efi mailing list >diy_efi at diy-efi.org >http://lists.diy-efi.org/mailman/listinfo/diy_efi _________________________________________________________________ Is your PC infected? Get a FREE online computer virus scan from McAfee? Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From enlight22 at hotmail.com Thu Oct 28 07:05:09 2004 From: enlight22 at hotmail.com (biob dobbs) Date: Thu, 28 Oct 2004 04:05:09 -0300 Subject: [Diy_efi] Mopar PCM Message-ID: no, not that, what PC program are you talking about dissassembling with it >From: "David Cooley" >Reply-To: A list for Do-It-Yourself EFI >To: >Subject: Re: Re: [Diy_efi] Mopar PCM >Date: Wed, 27 Oct 2004 21:15:16 -0400 (Eastern Daylight Time) > >Interactive Disassembler Pro > >-------Original Message------- > >From: A list for Do-It-Yourself EFI >Date: 10/27/04 20:49:14 >To: diy_efi at diy-efi.org >Subject: Re: Re: [Diy_efi] Mopar PCM > >What program is this you are looking at disassembling, that j(some number) >program from daimler chrysler? > > > >From: "David Cooley" > >Reply-To: A list for Do-It-Yourself EFI > >To: > >Subject: Re: Re: [Diy_efi] Mopar PCM > >Date: Wed, 27 Oct 2004 17:10:55 -0400 (Eastern Daylight Time) > > > >Hmm... I do have a disassembler for windows programs! > > > >-------Original Message------- > > > >From: A list for Do-It-Yourself EFI > >Date: 10/27/04 16:02:24 > >To: A list for Do-It-Yourself EFI > >Subject: Re: Re: [Diy_efi] Mopar PCM > > > >Anyway to reverse engineer the application I sent you to see how Chrysler > >accesses the flash via SCI? Data logger maybe? > > > > > > From: "David Cooley" > > > Date: 2004/10/27 Wed PM 12:52:31 GMT > > > To: > > > Subject: Re: [Diy_efi] Mopar PCM > > > > > > As I said, even the factory flash file looks identical to what is in > >the > > > flash proms... it is both flash concatenated into a single file with a > > > checksum so the DRB can check for file corruption before it applies >the > > > flash. The flash appears to be strictly data, and no code at all. I > >ihave > > > to set up SCI direct to the CPU's to see if I can dump the ROM. Once >I > >do > > > that I will have a better idea what is going on... and the info I >have > >is > > > not speculation... I have received it from a person that works for a > > > company that assembles, programs, reworks and tests the PCM's for > >Chrysler > > > > > 96 and newer Chrysler PCM's are a totally different animal than the 95 > >and > > > earlier units. > > > > > > > > > > > > -------Original Message------- > > > > > > > > > > > > From: A list for Do-It-Yourself EFI > > > > > > Date: 10/26/04 22:42:52 > > > > > > To: diy_efi at diy-efi.org > > > > > > Subject: Re: [Diy_efi] Mopar PCM > > > > > > > > > > > > again a dump wont do you any good. every piece of chyrsler code ive >ever > > > seen has a copyright in asccii test at the bottom of the rom. these do > >not > > > > > the only clear reasoning is that the adress line are muxed or >something > > > during programming. this is not even remotely beyond the capability of > >the > > > 68hc vriants running in these ecms. > > > > > > > > > > > > > > >_______________________________________________ > >diy_efi mailing list >>diy_efi at diy-efi.org > >http://lists.diy-efi.org/mailman/listinfo/diy_efi > >_________________________________________________________________ >Check out Election 2004 for up-to-date election news, plus voter tools and >more! http://special.msn.com/msn/election2004.armx > >_______________________________________________ >diy_efi mailing list >diy_efi at diy-efi.org >http://lists.diy-efi.org/mailman/listinfo/diy_efi > >_______________________________________________ >diy_efi mailing list >diy_efi at diy-efi.org >http://lists.diy-efi.org/mailman/listinfo/diy_efi _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar ? get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From n5xmt at bellsouth.net Thu Oct 28 09:30:21 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Thu, 28 Oct 2004 06:30:21 -0300 Subject: [Diy_efi] anyone doing GM TBI ECU's? Message-ID: --===============59674193602823156== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_7NFAQL80000000000000" --------------Boundary-00=_7NFAQL80000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/27/04 22:30:57=0D To: diy_efi at diy-efi.org=0D Subject: [Diy_efi] anyone doing GM TBI ECU's?=0D =0D Hello=0D New guy here. I have no experience reprogramming, but my little brother h= as done so extensively on mopar computers. What I=92m wondering is, can the = gm TBI system be reprogrammed? If so, what mods need to be done, and where c= an the modification program and such be found?=0D Two vehicles I=92m primarily interested in =96=0D (1) =96 GM 454 system. This would be adapted to fit on a caddy 500, w= ith twin turbo=92s=0D (2) - I have a 94 GMC that I would to get more power out of to pull = my trailer.=0D any help would be appreciated.=0D Thanks=0D Aaron=0D =0D =20 --------------Boundary-00=_7NFAQL80000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/27/04 22:= 30:57

To: diy_efi at diy-efi.org

Subject: [Diy_efi]= anyone doing GM TBI ECU's?

Hello

New guy here. I have no experience reprogramm= ing, but my little brother has done so extensively on mopar computers. Wh= at I=92m wondering is, can the gm TBI system be reprogrammed? If so, what= mods need to be done, and where can the modification program and such be= found?

Two vehicles I=92m primarily interested in =96=

(1)     =96 GM 454 system. This would be adapted to fit on a caddy 500,= with twin turbo=92s

(2)     - I have a 94 GMC that I would to get more power out of t= o pull my trailer.

any help would be appreciated.<= /P>
Thanks

Aaron

--------------Boundary-00=_7NFAQL80000000000000-- --===============59674193602823156== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============59674193602823156==-- From n5xmt at bellsouth.net Thu Oct 28 09:31:25 2004 From: n5xmt at bellsouth.net (David Cooley) Date: Thu, 28 Oct 2004 06:31:25 -0300 Subject: [Diy_efi] anyone doing GM TBI ECU's? Message-ID: --===============050419218735260785== Content-Type: Multipart/Alternative; boundary="------------Boundary-00=_NPFAG6G0000000000000" --------------Boundary-00=_NPFAG6G0000000000000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Aaron,=0D What mopar computers has your little brother worked on?=0D I'm currently trying to hack the 96 and up PCM's...=0D have a website of my progress at:=0D http://www.nancyknowshomes.com/dodge/97PCM/pcm.htm=0D Could use some pointers =0D =0D -------Original Message-------=0D =0D From: A list for Do-It-Yourself EFI=0D Date: 10/27/04 22:30:57=0D To: diy_efi at diy-efi.org=0D Subject: [Diy_efi] anyone doing GM TBI ECU's?=0D =0D Hello=0D New guy here. I have no experience reprogramming, but my little brother h= as done so extensively on mopar computers. What I=92m wondering is, can the = gm TBI system be reprogrammed? If so, what mods need to be done, and where c= an the modification program and such be found?=0D Two vehicles I=92m primarily interested in =96=0D (1) =96 GM 454 system. This would be adapted to fit on a caddy 500, w= ith twin turbo=92s=0D (2) - I have a 94 GMC that I would to get more power out of to pull = my trailer.=0D any help would be appreciated.=0D Thanks=0D Aaron=0D =0D =20 --------------Boundary-00=_NPFAG6G0000000000000 Content-Type: Text/HTML; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Aaron,

What mopar computers has your little brother worked on?

I'm currently trying to hack the 96 and up PCM's...

have a website of my progress at:

http:= //www.nancyknowshomes.com/dodge/97PCM/pcm.htm

Could use some pointers

-------Original Message-------

From: A list for Do-It-Yourself EFI

Date: 10/27/04 22:= 30:57

To: diy_efi at diy-efi.org

Subject: [Diy_efi]= anyone doing GM TBI ECU's?

Hello

New guy here. I have no experience reprogramm= ing, but my little brother has done so extensively on mopar computers. Wh= at I=92m wondering is, can the gm TBI system be reprogrammed? If so, what= mods need to be done, and where can the modification program and such be= found?

Two vehicles I=92m primarily interested in =96=

(1)     =96 GM 454 system. This would be adapted to fit on a caddy 500,= with twin turbo=92s

(2)     - I have a 94 GMC that I would to get more power out of t= o pull my trailer.

any help would be appreciated.<= /P>
Thanks

Aaron

--------------Boundary-00=_NPFAG6G0000000000000-- --===============050419218735260785== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============050419218735260785==-- From mrcad472 at iowatelecom.net Thu Oct 28 13:56:54 2004 From: mrcad472 at iowatelecom.net (Scott Pearson) Date: Thu, 28 Oct 2004 10:56:54 -0300 Subject: [Diy_efi] SFI/COP Message-ID: Just ran across this message, hopefully you're still around and interested. I'm running SFI and coil near plug on a 3800 V6 using a GM 1228253 and a FAST eDist. Don't see why that wouldn't work for you. Scott ----- Original Message ----- From: "TomQ" To: "Diy Efi" Sent: Saturday, March 27, 2004 12:51 PM Subject: [Diy_efi] SFI/COP > Hi all, > > I am interested in maybe installing a Sequential system with Coil on Plug > on > a I6 motor (1-5-3-6-2-4). I have searched the internet to see if I could > find some information on using the MPU out of a donor vehicle and then > reprogram it for my set up but I have come up short. Does anyone know of a > particular model that might work, or maybe a book/internet site that might > provide me with more information. If not what would the recommendation for > a > off the shelf MPU. This would be used in a low rpm truck motor. I would be > most interested in ease of installation/programming and reliability. Why > don't I just go TBI? I already did that but now would like to see if I can > do something else. Thanks. > > > _______________________________________________ > diy_efi mailing list > diy_efi at diy-efi.org > http://lists.diy-efi.org/mailman/listinfo/diy_efi > _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From instigatr at merkurboys.com Thu Oct 28 14:07:52 2004 From: instigatr at merkurboys.com (Aaron) Date: Thu, 28 Oct 2004 11:07:52 -0300 Subject: [Diy_efi] anyone doing GM TBI ECU's? Message-ID: This is a multi-part message in MIME format. --===============14477826625218171== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C4BCBC.55806D50" This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C4BCBC.55806D50 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello He=92s primarily working on the late 80=92s caravans and such that had = the turbo engine. He built one to fit in his Merkur. I dunno if that info will = apply or not. You could ask him, his website is HYPERLINK "http://www.merkurboys.com/"www.merkurboys.com. Good luck Aaron=20 =20 -----Original Message----- From: diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] = On Behalf Of David Cooley Sent: Thursday, October 28, 2004 2:30 AM To: diy_efi at diy-efi.org Subject: Re: [Diy_efi] anyone doing GM TBI ECU's? =20 Aaron, What mopar computers has your little brother worked on? I'm currently trying to hack the 96 and up PCM's... have a website of my progress at: HYPERLINK "http://www.nancyknowshomes.com/dodge/97PCM/pcm.htm"http://www.nancyknows= hom es.com/dodge/97PCM/pcm.htm Could use some pointers=20 =20 -------Original Message------- =20 From: HYPERLINK "mailto:diy_efi at diy-efi.org"A list for Do-It-Yourself = EFI Date: 10/27/04 22:30:57 To: HYPERLINK "mailto:diy_efi at diy-efi.org"diy_efi at diy-efi.org Subject: [Diy_efi] anyone doing GM TBI ECU's? =20 Hello New guy here. I have no experience reprogramming, but my little brother = has done so extensively on mopar computers. What I=92m wondering is, can the = gm TBI system be reprogrammed? If so, what mods need to be done, and where = can the modification program and such be found? Two vehicles I=92m primarily interested in =96 (1) =96 GM 454 system. This would be adapted to fit on a caddy 500, = with twin turbo=92s (2) - I have a 94 GMC that I would to get more power out of to pull = my trailer. any help would be appreciated. Thanks Aaron =20 =20 =20 =20 =20 =20 --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004 =20 ------=_NextPart_000_000B_01C4BCBC.55806D50 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hello

He=92s primarily working on the = late 80=92s caravans and such that had the turbo engine. He built one to fit = in his Merkur. I dunno if that info will apply or not. You could ask him, = his website is www.merkurboys.com.=

Good luck

Aaron

-----Original = Message-----
From: = diy_efi-bounces at diy-efi.org [mailto:diy_efi-bounces at diy-efi.org] On Behalf Of David Cooley
Sent: Thursday, October = 28, 2004 2:30 AM
To: = diy_efi at diy-efi.org
Subject: Re: [Diy_efi] = anyone doing GM TBI ECU's?

Aaron,

What mopar computers has your little brother worked = on?

I'm currently trying to hack the 96 and up = PCM's...

have a website of my progress at:

http://www.na= ncyknowshomes.com/dodge/97PCM/pcm.htm

Could use some pointers

-------Original = Message-------

From:= A list for Do-It-Yourself = EFI

Date:= 10/27/04 22:30:57

To: diy_efi at diy-efi.org=

Subject: [Diy_efi] anyone doing GM TBI ECU's?

Hello

New guy here. I have no experience reprogramming, = but my little brother has done so extensively on mopar computers. What I=92m wondering is, can the gm TBI system be reprogrammed? If so, what mods = need to be done, and where can the modification program and such be = found?

Two vehicles I=92m primarily interested in = =96

(1)     = =96 GM 454 system. This would be adapted to fit on a caddy 500, with twin turbo=92s

(2)     = - I have a 94 GMC that I would to get more power out of to pull my = trailer.

any help would be appreciated.

Thanks

Aaron

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.784 / Virus Database: 530 - Release Date: 10/27/2004

------=_NextPart_000_000B_01C4BCBC.55806D50-- --===============14477826625218171== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============14477826625218171==-- From christopher.k.kete at Cummins.com Thu Oct 28 17:34:55 2004 From: christopher.k.kete at Cummins.com (christopher.k.kete at Cummins.com) Date: Thu, 28 Oct 2004 14:34:55 -0300 Subject: [Diy_efi] Christopher K Kete/Corp/Cummins is out of the office. Message-ID: I will be out of the office starting 10/28/2004 and will not return until 11/05/2004. Out on vacation 10/28 through 11/6. Please contact the following people for assistance: A-Series: Funmi Ige-Wright B3.3: Suzanne Tatman Best Value 4B: Priscilla Rishi NMHG: Scott Files Terex: Damon Chandler All other inquires: Scott Files Emergencies: 812-344-0474 Thank-you! _____________ This e-mail transmission and any attachments to it are intended solely for the use of the individual or entity to whom it is addressed and may contain confidential and privileged information. If you are not the intended recipient, your use, forwarding, printing, storing, disseminating, distribution, or copying of this communication is prohibited. If you received this communication in error, please notify the sender immediately by replying to this message and delete it from your computer. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From alexis.pavlov at st.com Fri Oct 29 09:38:03 2004 From: alexis.pavlov at st.com (Alexis PAVLOV) Date: Fri, 29 Oct 2004 06:38:03 -0300 Subject: [Diy_efi] Factory turbo motorcycle reverse engineering project Message-ID: I know nothing about these ECU, but would assume the 8755 is for knock signal processing. Just like on early Bosch M2.1 Motronics. Adam Wade wrote: > > Well, I am working on developing chips for the Honda > CX500 Turbo and hopefully the CX650 Turbo as well. > > Here's what I have so far: > > "As I surmised in an earlier post, the CX500T unit had > a 8xxx MPU of some sort as the box used the 8253 PIT, > which is used with the 8xxx family. Futher > investigation of the pinouts leads me to believe the > MCU is in the 8035/39/40 sub-family. Nipondenso is > large enought to fab their own chips, but I think they > only "branded" the available chip with their > number...ND079753-0021. I tried to read on-board ROM > as an 8048/49, but got nothing in the read buffer. The > 8035 units are CPU only with no memory on-board. All > these chips use the same pinout. The companion chip > is a 8755. The 2716 eeprom is standard." > > I have hex dumps of both the 2716 and the 8755. I am > trying to sort out which maps are where, and to > disassemble the machine code, as there is an overboost > fuel cut-off I wish to eliminate. > > If I can't get it sorted to where I can burn my own > chip, I may just build a Megasquirt. But since I can > socket the EPROM, it makes more sense to me to just do > tabletop work and save my money and testing effort. > :) I have access to a step-testing eddy current dyno, > as well as an attached four-gas analyzer and an > emulator, so once I get the code and the maps sussed, > tuning and burning a replacement chip will be simple > and easy. > > Old-tech wizards, I'm looking forward to hearing from > you. :) > > ===== > | 82 Honda CX500 Turbo (Cassandra) 90 Kwak Zephyr 550 (Daphne) | > | "It was like an emergency ward after a great catastrophe; it | > | didn't matter what race or class the victims belonged to. | > | They were all given the same miracle drug, which was coffee. | > | The catastrophe in this case, of course, was that the sun | > | had come up again." -Kurt Vonnegut | > | Buy my M/C Fuel Inj. Handbook - http://tinyurl.com/2e8eu | > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - You care about security. So do we. > http://promotions.yahoo.com/new_mail > _______________________________________________ > diy_efi mailing list > diy_efi at diy-efi.org > http://lists.diy-efi.org/mailman/listinfo/diy_efi _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From espresso_doppio at yahoo.com Fri Oct 29 11:29:31 2004 From: espresso_doppio at yahoo.com (Adam Wade) Date: Fri, 29 Oct 2004 08:29:31 -0300 Subject: [Diy_efi] Factory turbo motorcycle reverse engineering project Message-ID: --- Alexis PAVLOV wrote: > I know nothing about these ECU, but would assume the > 8755 is for knock signal processing. There is no knock sensor on this engine. Also, only fuel is controlled by the ECU; there is a separate box for analog spark control (CDI). ===== | 82 Honda CX500 Turbo (Cassandra) 90 Kwak Zephyr 550 (Daphne) | | "It was like an emergency ward after a great catastrophe; it | | didn't matter what race or class the victims belonged to. | | They were all given the same miracle drug, which was coffee. | | The catastrophe in this case, of course, was that the sun | | had come up again." -Kurt Vonnegut | | Buy my M/C Fuel Inj. Handbook - http://tinyurl.com/2e8eu | __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From christopher.k.kete at Cummins.com Fri Oct 29 17:11:52 2004 From: christopher.k.kete at Cummins.com (christopher.k.kete at Cummins.com) Date: Fri, 29 Oct 2004 14:11:52 -0300 Subject: [Diy_efi] Christopher K Kete/Corp/Cummins is out of the office. Message-ID: I will be out of the office starting 10/28/2004 and will not return until 11/05/2004. Out on vacation 10/28 through 11/6. Please contact the following people for assistance: A-Series: Funmi Ige-Wright B3.3: Suzanne Tatman Best Value 4B: Priscilla Rishi NMHG: Scott Files Terex: Damon Chandler All other inquires: Scott Files Emergencies: 812-344-0474 Thank-you! _____________ This e-mail transmission and any attachments to it are intended solely for the use of the individual or entity to whom it is addressed and may contain confidential and privileged information. If you are not the intended recipient, your use, forwarding, printing, storing, disseminating, distribution, or copying of this communication is prohibited. If you received this communication in error, please notify the sender immediately by replying to this message and delete it from your computer. _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From fastcarson at prodigy.net Fri Oct 29 23:24:30 2004 From: fastcarson at prodigy.net (Chris Carson) Date: Fri, 29 Oct 2004 20:24:30 -0300 Subject: [Diy_efi] Fuel delivery top mounts Message-ID: Hi y'all, I have a set of 8 standard GM fuel injectors that I'm trying to build a fuel rail for. I've already botched one length of fuel rail extrusion and I want to try a different route. MSD sells these "fuel delivery top mounts" for flex-line installations. I have a few questions: 1. Is there a place that sells these things with two holes instead of one, so as to avoid having to use a junction block? 2. Does 1/8" NPT convert to some AN size? Or am I stuck with NPT? 3. Is it an option to just remove the o-ring from the tops of the injectors and clamp a hose on to the end, which then would be clamped to a hose barb that's attached to a bunch of Ts? 4. Is there a source for cheaper, small lengths of fuel hose with fittings on the end? I'm concerned that my injectors may not be perfectly lined up as I was not capable of perfectly lining up things when I was using the old drill press on the intake. So, I'm worried that if I try solid fuel rail again, the o-rings will not seat in the bores straight and that they will leak. Is this a valid concern? Chris _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From liberty1 at gmail.com Sat Oct 30 06:32:59 2004 From: liberty1 at gmail.com (Bobby Yates Emory) Date: Sat, 30 Oct 2004 03:32:59 -0300 Subject: [Diy_efi] Fuel delivery top mounts Message-ID: Chris, There was a discussion of this about two months ago. Basically - forget trying to make a fuel rail. You have to ream or broach to get a round enough hole - a drill does not produce a perfectly round hole. Plus there is the alignment problem you were discussing. I think they said MSD sells bungs that are accurate enough to seal up. I would be very careful - barbs could let go the hose and you would be spraying gasoline on a hot engine. Good luck On Fri, 29 Oct 2004 19:25:01 -0400, Chris Carson wrote: > Hi y'all, > I have a set of 8 standard GM fuel injectors that I'm trying to build a fuel > rail for. I've already botched one length of fuel rail extrusion and I want > to try a different route. MSD sells these "fuel delivery top mounts" for > flex-line installations. I have a few questions: > 1. Is there a place that sells these things with two holes instead of one, > so as to avoid having to use a junction block? > 2. Does 1/8" NPT convert to some AN size? Or am I stuck with NPT? > 3. Is it an option to just remove the o-ring from the tops of the injectors > and clamp a hose on to the end, which then would be clamped to a hose barb > that's attached to a bunch of Ts? > 4. Is there a source for cheaper, small lengths of fuel hose with fittings > on the end? > > I'm concerned that my injectors may not be perfectly lined up as I was not > capable of perfectly lining up things when I was using the old drill press > on the intake. So, I'm worried that if I try solid fuel rail again, the > o-rings will not seat in the bores straight and that they will leak. Is this > a valid concern? > > Chris > > _______________________________________________ > diy_efi mailing list > diy_efi at diy-efi.org > http://lists.diy-efi.org/mailman/listinfo/diy_efi > -- Toward freedom, Bobby Yates Emory _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From lorcan at 750turbo.com Sat Oct 30 07:26:50 2004 From: lorcan at 750turbo.com (Lorcan Parnell) Date: Sat, 30 Oct 2004 04:26:50 -0300 Subject: [Diy_efi] Fuel delivery top mounts Message-ID: RC adapts o-ring injectors to top hose mounting by removing the o-ring mounts and machining grooves on the outside of the injector inlet. They did this for my Kawasaki which has a tubular fuel rail and hose mounted injectors like this one http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&rd=1&item=7930094713&ssPageName=STRK:MESE:IT If you need a clearer pic let me know. Lorcan _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi From kml_daniel at yahoo.com Sat Oct 30 12:53:14 2004 From: kml_daniel at yahoo.com (K DANIEL) Date: Sat, 30 Oct 2004 09:53:14 -0300 Subject: [Diy_efi] ECU Tester Message-ID: --===============38970640228286646== Content-Type: multipart/alternative; boundary="0-1949956014-1099140561=:67506" --0-1949956014-1099140561=:67506 Content-Type: text/plain; charset=us-ascii Hello I'm new member to DIY-EFI .. I'm engineer I have designed an engine simulator for testing engine ECU's the simulator generate all the sensors signals required operate the ECU under test I'm using LABview software to monitor and control the ECU operation By now most of the BOSCH MOTRONIC ECU?s can be tested...I'm now preparing the simulator For testing SIMTEC and GM ecru?s but the information on SIMTEC and GM ECU is very rare... any one can help with the pinout or schematics of SIMTEC and GM ECU's K Daniel --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. --0-1949956014-1099140561=:67506 Content-Type: text/html; charset=us-ascii

Hello

I'm new member to DIY-EFI .. I'm engineer I have designed an engine simulator for testing engine

ECU's the simulator generate all the sensors signals required operate the ECU under test

I'm using LABview software to monitor and control the ECU operation

By now most of the BOSCH MOTRONIC ECU?s can be tested...I'm now preparing the simulator

For testing SIMTEC and GM ecru?s but the information on SIMTEC and GM ECU is very rare... any one can help with

the pinout or schematics of SIMTEC and GM ECU's

                                                                                                        K Daniel

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish. --0-1949956014-1099140561=:67506-- --===============38970640228286646== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ diy_efi mailing list diy_efi at diy-efi.org http://lists.diy-efi.org/mailman/listinfo/diy_efi --===============38970640228286646==--