Crazy Ferrari 308 build thread.

[Monochrome]

https://grassrootsmotorsports.com/forum ... 959/page1/

This guy takes DIY to a high level of insanity.

[DCIV]

Lol he’s so nonsolant about how he can do whatever he wants.


Coop

[mjannusch]

He's got amazing fab skills for sure. Seems odd to put so much work into a 308, but hey... A lot of people would say the same about putting a bunch into a 3000GT.

[Jeff V.]

This guy molds metal better than I can mold clay. As cool as it is, I'm sceptical about how much longevity he's going to get out of it, especially at the power levels he's aiming for. There's a bit more science to this stuff than just "move the parts where they fit". How well will those cooling jacket patches hold up after some heat and pressure cycles for instance?

[mjannusch]

Who needs longevity in a Ferrari? Those guys never drive them.

[Jeff V.]

I don't think a 'never drives it' kind of person is working on a build like this

[DCIV]

I hope it doesn’t. So he has to do some crazy other stuff. That guy is talented. I mean who makes their own camshaft and cuts into heads. Lol.


Coop

[ChargerX3]

I love one off builds. Man after my own heart.

[Jeff V.]

Hey Matt, check this out. I can't seem to link the post directly, but the timestamp was 1/18/2019 08:36am

Next let me scale back my statement a little. The ECU I'm using now is an Enginelab https://enginelab.net/products/

This is the same as the AEM infinity (my hardware if AEM, I just run the enginelab version firware/software). The enginelab version (which is what AEM starts with) gives you a toolset to setup a functioning ECU, but there is no "model" or control logic in it, you need to write that using the tools they provide:

https://enginelab.net/documentation/

I absolutely LOVE this thing. You can set it up to do most anything you can dream up...but you have to youknow, actually set it up.

I added a model that gives me the % error TB to tb to make sync easy and also use the info to trim the cylinders in between TB syncs

I've only just started to read this, but it looks like you could define customer trigger wheel patterns.

https://enginelab.net/documentation/#En ... iption_EAL

Hardware IO Interface: The user should describe the harness interface requirement to the engine position sensors. There are several harness pins that can be used for engine position sensors where the signal conditioning circuitry ranges from variable reluctance, hall effect and optically isolated inputs. The engine position sensors for the timing setup require the following:

Harness pin: This is the harness pin that the user will interface to the sensor.
Number of teeth: This specifies the number of teeth on the reluctor wheel.
Edge control: The user can have the timing trigger on the rising egde, falling edge or both edges.
Noise cancellation: This value indicates the number of 3.2 microsecond increments that must be present for the hardware to trigger the edge. A value of 10 (32 microseconds) is generally a good choice for this setting. Noisy crankshaft and camshaft sensors can be resolved with adjustment to this field.

[tabasco122]

holy shit, this project is insane.

[mjannusch]

[quote=""Jeff V.""]Hey Matt, check this out. I can't seem to link the post directly, but the timestamp was 1/18/2019 08:36am



I've only just started to read this, but it looks like you could define customer trigger wheel patterns.

https://enginelab.net/documentation/#En ... iption_EAL[/quote]

Yeah, I looked at that - but then you also have to start entirely from scratch and basically write your own engine control strategy. Lots more than I'm willing to do, at least for the time being.