Electronic Distributor Adapter

[90TurboVan]

Working with turbo.shaft on testing the non NGC stuff, but I do need a tester for NGC (SRT), if anyone is about ready to start their conversion up.

[glhs659]

Any updates?

[turbo.shaft]

Quote:

Originally Posted by glhs659 Any updates?

Parts shipment is delayed to Oct 8th. Then expect about two more weeks turnaround time for assembly, delivery and eventual in car testing.

[90TurboVan]

I have parts for NGC/Non-NGC adapters, but I'm waiting on circuit boards. I am still looking for an SRT swap tester.

[crazymadbastard]

It is weird, I can see that there was a post here today but I can't see it!!


edit after posting I could see the new posts, before I could only see up to #91

[gkcooper]

When will these be available to purchase? Do you have an agreement already with one of our retailers? The version I want is for a common-block hybrid buildup using a DOHC head and neon/PT coil pack. I am also interested in a cover to go over the HEP. I am going to use the Caravan long-runner intake manifold, but I want a clean installation without using a distrubutor cap.

[90TurboVan]

I'm waiting on circuit boards which are supposed to ship on the 8th. I'll put one together for testing and if all goes well, I should be able to have some NGC/non-NCG ones together by the end of October. If there's enough interest, I'll probably talk to Cindy or Chris to see if something can be arranged, but that'll have to wait until I have a known working version of all three types.

The hybrid (version you're asking about) adapter is designed, coded, and tested, but I'm concentrating on the 2.4 stuff because it seems like that's what most people are doing, and because I can't physically test it myself which adds a level of complexity to the process.

[Wizard]

How is the code for using turbo 2 wire HEP to run DIS and ideally to fool the TBI or carb computer? That one I do not mind etching a circuit board, done this many times.

Cheers, Wizard

[90TurboVan]

That would be a fairly minor code change from the hybrid style adapter, but would have to use the 2.4 hardware. I can look at it later tonight. If you want my board layout, I can send you the gerbers. I use 10/10 trace/clearance and small vias. Any ideas on how you'd mount the coilpack?

[Wizard]

Either in front of valve cover or around the a/c mount point of 2.2/2.5. When I go hybrid, the pack goes to usual spot on top of valve cover.

Still have to use NGC timing wheel and fool the old computer? That would be fine.

I'd love a gerber file of yours for the circuit board. PM or email.

Cheers, Wizard

[90TurboVan]

PM sent.

100th reply

Note that if you were to download the zip I posted several pages back, it has been updated such that all adapters use the same hardware. Carb/TBI to coilpack support has also been added. NGC, Hybrid, and Carb/TBI should work, I doubt that non-NGC does. Updated schematics and board layouts in the form of gerber files have been added. I used WinRAR for the zip, if it doesn't work, WinRAR archiver, a powerful tool to process RAR and ZIP files and download the free trial. Trial never expires and will open all common compression formats.

[turbo.shaft]

What is the status of the plug in adaptor for use with the 99 stratus motor?

[90TurboVan]

Just waiting on boards now. Had to change some stuff around with the code due to there not being a "hard" trigger I can use to simulate the HEP outputs. With the NGC, I could trigger outputs based on the crank sensor (10 degree/pulse), but non-NGC needs to be a time based output which requiers delta calculation and next revolution time prediction.

[turbo.shaft]

Quote:

Originally Posted by 90TurboVan Just waiting on boards now. Had to change some stuff around with the code due to there not being a "hard" trigger I can use to simulate the HEP outputs. With the NGC, I could trigger outputs based on the crank sensor (10 degree/pulse), but non-NGC needs to be a time based output which requiers delta calculation and next revolution time prediction.

In layman's terms do you mean mathematically guessing at the time to reach the proper point to trigger the HEP between the exisiting crank output signals based upon speed of the engine

[90TurboVan]

Yep, the program uses a "degrees" counter which is incremented every 10 degrees and cleared every TDC. With NGC, it just increments once every crank pulse (10 degrees/tooth), with non-NGC, it calculates what amout of time each "tooth" would take and increments it after that amount of time elapses. The HEP outputs are then generated based on crank degrees, and this way both types of code use the exact same HEP generation code.