ION/CDI - developer info.
In fact two boards:
- one with the smarts and the sensitive electronics
- and one with the CDI and HV supplies. See CdiSupply
The combination feature:
- Internal MAP sensor.
- CLT, IAT and TPS sensors.
- CDI supply
- 4 CDI ignition outputs with ION sensing.
- 1 Plasma discharge output for use with the plasma discharge diode pack.
- 4 HighZ injector outputs. (Can be used for other applications too.)
- 1 Bosch LSU Wbo2 sensor controller
- 2 CAN busses
- 1 Knock sensor input (ARM computed, no TPIC8101).
- CRANK and CAM trigger inputs. At least the crank must have LM 1815 (VR-support).
- 4 ignition trigger inputs that emulates Bosch or MSD ignition modules. (For use with non VEMS engine management systems). They are meant to take the signal that normally trigg the stock ignition coils. (Very much like a HALL signal). We only need a total of four inputs, this can include the inputs normally used for the Crank and CAM trigger above. This feature is _very_ important. We could demux them to a CRANK+CAM signal before the ARM if needed (fortunately not).
To Store/Retreive files in the wiki:
The board for Ignition and ION sense (Standalone or in use with EFI board)
Aim: Started routing of board
Has the ARM LPC2119, CAN, RS232, one LM1815 VR interface, one hall sensor input, MAP sensor. Also has four discrete inputs that emulate an MSD DIS-4 input. The ION use one ADC channel and a MUX to choose which current mirror to sample from. -Jörgen
- 2 CAN
- 4 Igniton
- 4 ION sensing
Has the main power supply, which feed two separate CDI power supplies (needed for rotary and twin spark applications), ION power supply and plasma power supply. It has four CDI outputs and one plasma_enable output that is shared by up to four DiodeBoards?. -Jörgen
Someone would like to sum up old notes, ltspice simulations, etc... ?
Status: Non existent, dependent on initial Ionboard_r005_jk.
Possibly looking like a short thick HT wire extension. It has one HV input which is directly tied to the HV output, the cathode of the HV diode is connected to this node, the anode of the HV diode is connected to a 500v heat and abrasion resistant wire. The entire assembly is meant to sit on the plug itself. -Jörgen
I was browsing around in supply land and I cannot justify the huge cap-diode network. If you don't like self-wound transformers, a flyback type stepup (with our standard ISLV... DPAK IGBT) must be perfect. Only consumes 1 ADC input channel and 1 logic level (gatedrive) output. For prototype, safe to have both types (although the cap-diode can be soldered on a traceless carrier-board - I did it earlier for ionizator upto 20000V).
Aim: Slap 30-50 HV diodes on a board use a machined pass though for the original HV signal from the coil. Make it fit in a spark plug well.
When you make a comment, write your friggin name after it:) Like this. -Jörgen
The experimental nature of the ION project makes me feel that we should have one board with the 'smarts' and one board with the power electronics.
proposed interface between the boards
please elaborate on this...
This will enable us to make the CPU board early and try different power board configurations on proto boards. The ION current mirrors will of course be on the CPU board; they will enable those of us who already run CDI ignition to start collecting data early. -Jörgen
I'd like to see as much of our present knowledge on one board. It's better for experiments than if it was several boards. There can be optional parts on it, of course. Maybe the first boards are somewhat more work, but this would bring usable solutions faster. Remember v3 was made much faster than the small round WBO2: just because it covers more uses, so there is more interest among developers.
Valid point, but I would like to see at least a separate IONBoard for ADC/data logging, including Ion Sense, i.e. I see Ion Sensing as data logging. This is because many racing classes do not allow the use of reactive electronics i.e. data logging must be seperated from ignition/fuel control when racing. I want two boards that I can plug together when testing and tuning, during which the data logger feeds the control board and maps the ignition/fuel tables. Then when I race, I can disconnect the two boards, the engine runs off the map and the data logger runs stand-alone. Any comments? - Patrick.
This is pretty much the plan:
Both smart boards will have switches so either could control an engine by itself (one excels at ign, the other in inj). But the swithces are organized at one section so that part can be shaved off for a smaller layout "sensor-board".
Someone could put it to VemsFrontier/Boards, I made the mistake of writing to genboard-dev first, and its late now, going to bed.
Is there a problem with enabling Plasma on a global level? Plasma is basically a capacitor charged to 300-400v connected to the plug, nothing would happen until the impedance over the plug gets fairly low. That will only happen after a high voltage has ionised the gap, if we consider 4 cylinder plasma units we will have ignition events 180degrees apart. The resistance over the plug quickly increase as the cylinder pressure drop off during the work phase. The currents seen during a plasma discharge makes me want to keep the number of switches low. BTW, the HV diodes for each plug will effectively prevent the CDI re-strike that initiates the plasma from jumping to the wrong cylinder. -Jörgen
The above makes me want to have a high current plasma _arm_ switch in each 4 output CDI unit. This is connected to the common anode of the HV diodes. -Jörgen
IonSense/CicuitAndSimulation To continue the development of functional circuits that allow high energy sparks while also permitting effective protection and accurate measurement of Ion Currents
IonSense/Components Links to whats available,data sheets, how affordable and state of the art
CoilOnPlug Developing our own or finding what's available