Build Thread Intro...
I guess this will be my build thread for the next few months. I'm going in a different direction than most; I LOVE WIRING. I'll be making alot of custom electrical components in the future. I plan to replace/rebuild all of the electrical systems in my car. My plans as of when I get my B16A engine: (Sorted by priority)
-Custom alarm system
-Modified Dizzy for coil-on-plugs
-WiFi based tuning/datalogging
-A completely rewired engine harness for maximum tuckage
-Replace a tach-less cluster's status lights with a tiny LCD panel that monitors EVERYTHING
-Wireless engine; Only connection to the engine is the power cables. Sensor wires are going to be insanely hidden.
-Custom ECU
-Homemade Dyno
This list might take me a few years, but I am DEADSET on doing these. I have nothing else to do with my life.
I am not going to half-*** any of these. i.e. NO wires showing. In fact I do not want any evidence of ANY custom electronics what so ever. Ironic... (except cluster)
Does anyone have any more ideas, I am brainstorming things all time and also throw away alot of ideas just as quickly.
Right now I'm working on a simple and effective alarm system. So far I have door/hatch sensors, hood sensor, seat sensors, battery cutoff sensor/backup, tilt sensor(from a Guitar Hero controller
) warning/feedback light in the cluster. Unfortunately, my Parallax Propeller microcontroller released some magic smoke when I did a test install... 
I have to use a Microchip PIC now. I really hate ASM.
Modified by Fuzzy Rhubarb at 8:48 PM 10/9/2007
-Custom alarm system
-Modified Dizzy for coil-on-plugs
-WiFi based tuning/datalogging
-A completely rewired engine harness for maximum tuckage

-Replace a tach-less cluster's status lights with a tiny LCD panel that monitors EVERYTHING
-Wireless engine; Only connection to the engine is the power cables. Sensor wires are going to be insanely hidden.
-Custom ECU
-Homemade Dyno
This list might take me a few years, but I am DEADSET on doing these. I have nothing else to do with my life.

I am not going to half-*** any of these. i.e. NO wires showing. In fact I do not want any evidence of ANY custom electronics what so ever. Ironic... (except cluster)
Does anyone have any more ideas, I am brainstorming things all time and also throw away alot of ideas just as quickly.
Right now I'm working on a simple and effective alarm system. So far I have door/hatch sensors, hood sensor, seat sensors, battery cutoff sensor/backup, tilt sensor(from a Guitar Hero controller
) warning/feedback light in the cluster. Unfortunately, my Parallax Propeller microcontroller released some magic smoke when I did a test install... 
I have to use a Microchip PIC now. I really hate ASM. Modified by Fuzzy Rhubarb at 8:48 PM 10/9/2007
Thought I'd stick this on here. Work in progress ECU pcb. This particular design is a few months old and just uncovered it. I think I will be using this one. I just need to work on the ADC and programming. It's on the back burner now.
Trending Topics
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by The_Undertaker »</TD></TR><TR><TD CLASS="quote">I have an idea make vtec wireless </TD></TR></TABLE>
your thread is now ruined, make a new one and hope he doesn't find it. i am sorry
your thread is now ruined, make a new one and hope he doesn't find it. i am sorry
Well, the basic plan is this: Make a tiny box that all sensors, injectors, solenoids, etc. plug into. Have a receiving box in the cabin that connects into the harness and ECU. The transmitting part is the easy one. The hard part will be to receive and transform the signals back into resistance to simulate a sensor for the ECU. It would be easy to make a varying voltage, but resistance is a biatch. Basically, the only connections to the engine are the vacuums, fuel, exhaust and battery. Thats it. Simple to disconnect. Simple to reconnect. You could even run the engine outside of the bay! That would be interesting...
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by .Grimace »</TD></TR><TR><TD CLASS="quote">your thread is now ruined</TD></TR></TABLE>
People need to give this guy a break. Think of him as a comic relief after a hard day's work.
He just needs to learn and listen a little more and to only give advice when he really can help. Damn...
People need to give this guy a break. Think of him as a comic relief after a hard day's work.
He just needs to learn and listen a little more and to only give advice when he really can help. Damn...
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Fuzzy Rhubarb »</TD></TR><TR><TD CLASS="quote">
-Modified Dizzy for coil-on-plugs
</TD></TR></TABLE>
That would be cool since Coil-on-plugs should work better than standart coils.
I once thought about removing the coil, and replace it with a regular low voltage feed that would connect to the coil circuit in the distributer. That way the distributer would be used to mechanically trigger the coils, maintaining correct ignition sequence and advance. (at least I think it would.. lol)
(To bad that it wouldn't allow for multi spark on low rpm, and spark duration control. lol)
How are you planning to do?
-Modified Dizzy for coil-on-plugs
</TD></TR></TABLE>
That would be cool since Coil-on-plugs should work better than standart coils.
I once thought about removing the coil, and replace it with a regular low voltage feed that would connect to the coil circuit in the distributer. That way the distributer would be used to mechanically trigger the coils, maintaining correct ignition sequence and advance. (at least I think it would.. lol)
(To bad that it wouldn't allow for multi spark on low rpm, and spark duration control. lol)
How are you planning to do?
[QUOTE=Fuzzy Rhubarb]The transmitting part is the easy one. QUOTE]
Is it, though? I'm no networking guru, but considering the number of sensors there are and their location, it would be quite difficult IMO.
Just imagine, if there were to be any type of electrical interference at, let's say 8k rpms, all it would need to take is one badly timed sensor to damage the engine.
I'm sure bluetooth and all that are fast, but intereference that causes milliseconds of delay are inevitable.
Now, here's and idea. Hardwire all sensors to a small processor underneath the intake manifold. From there, all you would need is one LAN cable or Optical line throught the firewallm to the ECU. One wire is still better than a dozen.
Whatever you try, it'll be interesting, that's for sure.
Is it, though? I'm no networking guru, but considering the number of sensors there are and their location, it would be quite difficult IMO.
Just imagine, if there were to be any type of electrical interference at, let's say 8k rpms, all it would need to take is one badly timed sensor to damage the engine.
I'm sure bluetooth and all that are fast, but intereference that causes milliseconds of delay are inevitable.
Now, here's and idea. Hardwire all sensors to a small processor underneath the intake manifold. From there, all you would need is one LAN cable or Optical line throught the firewallm to the ECU. One wire is still better than a dozen.
Whatever you try, it'll be interesting, that's for sure.
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by The_Undertaker »</TD></TR><TR><TD CLASS="quote">I have an idea make vtec wireless </TD></TR></TABLE>
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by The_Undertaker »</TD></TR><TR><TD CLASS="quote">I have an idea can you make grounds all wireless?</TD></TR></TABLE>
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by PaddingtonBear »</TD></TR><TR><TD CLASS="quote">If you're serious, you are a tool.</TD></TR></TABLE>
His Tool status exceeds all others.
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by The_Undertaker »</TD></TR><TR><TD CLASS="quote">I have an idea can you make grounds all wireless?</TD></TR></TABLE>
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by PaddingtonBear »</TD></TR><TR><TD CLASS="quote">If you're serious, you are a tool.</TD></TR></TABLE>
His Tool status exceeds all others.
Dude, you are a good man for having the guts to do this. I hope everything works out, it sounds like a HUGE handful. But once your done, I definitely advise that you patent the crap out of that stuff.
props to you
props to you
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by The_Undertaker »</TD></TR><TR><TD CLASS="quote">I have an idea can you make grounds all wireless?</TD></TR></TABLE>
Your idiocy knows no limits.
OP, good luck on this, I hope it's feasible and possible, should be interesting to watch.
Your idiocy knows no limits.
OP, good luck on this, I hope it's feasible and possible, should be interesting to watch.
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by The_Undertaker »</TD></TR><TR><TD CLASS="quote">I have an idea can you make grounds all wireless?</TD></TR></TABLE>

I'm not doing all of this at once. Most of it is going to surface in spring 2008. I'm just brainstorming and working on the basic principles/tech right now. But I promise you, you'll **** bricks when I'm done.
The dizzy will be almost exactly like what you said, but I've been thinking of using a microcontroller to monitor the RPMs and then just sparking the coils when it should. No dizzy, adjustable ignition timing and a hell of a lot more work. I'm don't know.
Interference will be really high because of the coils and injectors, but I don't actually have to transmit a continuous, perfect data stream. If the receiver can't read data, it can guess what the data most likely was. (Kalman filter FTW) I don't think that the TPS will change very much in less than a millisecond. That's really fast footwork.
Just use a slightly high transmission power and lots of error correction. It's digital, so the receiver will either get the correct data, or ignore it.
Basically, the data is going to be transmitted in a way where the receiver gets what is really going on. No delay. If it can't read anything, the receiver can guess the current state with HIGH accuracy. Plus, the data will be transmitted around 2000 times a second. 8000 RPMs is about 133 revs a second. Bluetooth would actually be a good standard to transmit the data. It's almost 2.1Mbits/sec. PLENTY of room to work with. It CAN be done... Someone just needs to do it.
...beatch
Modified by Fuzzy Rhubarb at 9:47 AM 10/13/2007

I'm not doing all of this at once. Most of it is going to surface in spring 2008. I'm just brainstorming and working on the basic principles/tech right now. But I promise you, you'll **** bricks when I'm done.

The dizzy will be almost exactly like what you said, but I've been thinking of using a microcontroller to monitor the RPMs and then just sparking the coils when it should. No dizzy, adjustable ignition timing and a hell of a lot more work. I'm don't know.
Interference will be really high because of the coils and injectors, but I don't actually have to transmit a continuous, perfect data stream. If the receiver can't read data, it can guess what the data most likely was. (Kalman filter FTW) I don't think that the TPS will change very much in less than a millisecond. That's really fast footwork.
Just use a slightly high transmission power and lots of error correction. It's digital, so the receiver will either get the correct data, or ignore it.Basically, the data is going to be transmitted in a way where the receiver gets what is really going on. No delay. If it can't read anything, the receiver can guess the current state with HIGH accuracy. Plus, the data will be transmitted around 2000 times a second. 8000 RPMs is about 133 revs a second. Bluetooth would actually be a good standard to transmit the data. It's almost 2.1Mbits/sec. PLENTY of room to work with. It CAN be done... Someone just needs to do it.
...beatchModified by Fuzzy Rhubarb at 9:47 AM 10/13/2007
Bluetooth is channelized. The receiver will only listen to data from the transmitter I tell it to. Bluetooth has it's own assigned frequencies. EMI from the ignition and injectors is what I'm worried about. I think that by switching 12v instead of the actual high voltage would help get rid of interference. The only high voltage is in a big metal block. There's my shielding for the ignition system. There's not much I can do about injectors though. I'll just use a really high signal strength. Even though it will be difficult, I want to stay wireless. It allows for easy external monitoring of EVERY sensor. Tuning will be a snap. You probably can just drive around, and you can make changes on the fly.
sounds cool, but also sounds like you are a freak. Wiring a flashlight is more than enough to me! Props though for having the motivation to try something like this. The tuning on the fly deal will be awesome. Nice thinking


