DFH - Defacto FreeEMS Hardware in KICAD

Jared's unmaintained and never-used TA based "Defacto FreeEMS Hardware" design.
User avatar
jharvey
1N4001 - Signed up
Posts: 1607
Joined: Tue Jun 10, 2008 5:17 pm

Re: freeEMS_1.0 rev A KICAD

Post by jharvey »

Brian wrote:For those who etch their own PCB's, they are still going to have to drill at least 150+ holes, 100 for the two headers alone. Might be easier/better to pay the $15 (plus postage) and get a solder mask, screen print and all holes drilled and plated.
I've seen some folks simply put the connector on thier board and solder it with no holes. Seems to work well enough. So they would really have less then 50 holes to drill. Also eventually we will have an option to put the CPU on our own board. We are using the TA board for simplicity now, and will probably keep it for future designs as well. I also feel your right, that purchasing the PCB's are better then making your own.

On a different note, I bought a ham radio known as the Kenwood TS2000. Dubbed by many as a "shack in a box" because it covers all ham bands up to 1.2 ghz and does what most people do with an entire shack of equipment. This very versatile radio, cost me a pretty penny when I got it. I know a guy that just finished building a radio with almost the same capabilities (better in many regards), and he did it with his own PCB's. He didn't even use purchased iron on PCB kit's. He made his own by using inkjet glossy photo paper, run through his wife's laser printer, then ironed on to the PCB. The stack of paper cost him a $1 at the local dollar store.

It's because of talented people like this guy AI2Q that I try to keep the doors open for them. How ever, I still prefer to buy it myself.

Wow this post of mine is fragmented. Sorry about that, hope it's understandable.
User avatar
jharvey
1N4001 - Signed up
Posts: 1607
Joined: Tue Jun 10, 2008 5:17 pm

Re: freeEMS_1.0 rev A KICAD

Post by jharvey »

freeEMS 1.0 A.11 has been uploaded, it can be found here

https://sourceforge.net/project/showfil ... _id=620372

Big changes in this one are mostly back-end stuff. I've been ironing out field properties and adding them. This makes it so that when we take out netlist to the PCB it will bring in the footprints. Much easier than finding every foot print by hand.

Remaining footprints to iron out include the ignition MOSFET, caps, and connectors.

Take a look at the freeEMS_1.lst file either in a spread sheet with tab separation, or you can try a text editor of your choice. Seems to work OK for that.
User avatar
AbeFM
Post Whore!
Posts: 629
Joined: Sat Feb 16, 2008 12:11 am
Location: Sunny San Diego
Contact:

Re: freeEMS_1.0 rev A KICAD

Post by AbeFM »

Probably doesn't go here, but... I finally found (someone who found) a lead on how to use a engine position windowing knock sensing chip. I'll have to cross post this in the knock thread as well. But while laying out the board, it would be awesome to include this.
yertnamreg on http://www.MiataTurbo.net : After doing some more research, that IC that Joe mentioned is the same as another made by Intersil HPIC9011 (same as TI TPIC8101). I can't find any other ASICs on the market other than these.

We can do windowed knock detection with this chip, but we need an external uProc to talk to it and to do knock window calculations. It wouldn't be that hard, but I am lazy. Some guy in Sweden basically did what we want to do with this chip for his masters.
http://db.s2.chalmers.se/download/masters/master_062_2004.pdf

I'm down with throwing something like this together, but I wish I could get a Masters for it. This hardly seems difficult enough to deserve a Masters.
He's working on a MS-MX-5 adapter board, which I'd a big fan of.


______________
Oh! That's exciting! Seems like the board is coming along. Perhaps it's too late to add this knock sensing in. I have to read up on it, find out how much space it takes up. I agree, I'd buy a board just for the fit and finish, unless I really only needed one.

Good argument for surface mount, though. :-)
User avatar
jharvey
1N4001 - Signed up
Posts: 1607
Joined: Tue Jun 10, 2008 5:17 pm

Re: freeEMS_1.0 rev A KICAD

Post by jharvey »

As noted in the ignition thread, I'm currently 1 footprint away from moving from schematic capture to PCB layout. Some of the above recommended features have been added to the TODO list found in the zip file from sourceforge, and aren't currently implemented.

I know we have to draw a line in the sand at some point, and some things will remain on the TODO (or in the wish list thread) for the moment. If there's something that should be included in 1.0 pipe up please. If it's not currently there, I haven't been planning for it at this stage.

Oh I just remembered the LED's on the driving circuits. I'll go add them now. Any how, really close to PCB layout, so pipe up now, or it might not make the cut.

Also I don't plan on starting the PCB until we talk about the knock sensor stuff. I'm still learning so it will be a bit before I can reply on that topic. Are there any other items we should have included?

[edit] just a note, looks like we are currently at about 400 components.
User avatar
Fred
Moderator
Posts: 15433
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Re: freeEMS_1.0 rev A KICAD

Post by Fred »

jharvey wrote:As noted in the ignition thread, I'm currently 1 footprint away from moving from schematic capture to PCB layout. Some of the above recommended features have been added to the TODO list found in the zip file from sourceforge, and aren't currently implemented.

I know we have to draw a line in the sand at some point, and some things will remain on the TODO (or in the wish list thread) for the moment. If there's something that should be included in 1.0 pipe up please. If it's not currently there, I haven't been planning for it at this stage.

Oh I just remembered the LED's on the driving circuits. I'll go add them now. Any how, really close to PCB layout, so pipe up now, or it might not make the cut.
I feel we should try to nail down what the schematics should look like a little more firmly before spending PCB time on it. There are still a few things up in the air. Perhaps I need to do a post summarising the decisions and discussions from the other threads?
[edit] just a note, looks like we are currently at about 400 components.
Are we really at 400 components? And if so, how? Perhaps we need to do a "do we REALLY need this" cull? Things such as protection on the on board outputs are not required. Can we fit that much on the board reasonably inside say 100 x 160 ?

As for knock, this is a get up and running board isn't it? Knock is a you have a perfect tune and you want a safety net feature. Much like closed loop AFR control. There is no functional ignition code yet, so knock control is pretty far away... There is a thread on it here with that link already posted : http://www.diyefi.org/forum/viewtopic.php?f=9&t=354

Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
User avatar
jharvey
1N4001 - Signed up
Posts: 1607
Joined: Tue Jun 10, 2008 5:17 pm

Re: freeEMS_1.0 rev A KICAD

Post by jharvey »

about the 400 components approx thing,

top schematic has 19
vreg has 11 so X2 is 22
injector driver has 7 required and 8 optional so X6 is 42 to 90
RPM has 15 so X2 is 30
general fet drives has 7 so X3 is 21
ignition driver has 7 so X6 is 42
an protect has 20 so X4 is 80
digi protect has 5 so X11 is 55

So this tells me it's about 311 min and with all the extra options, 359.

When I noted the 400 ish, I simply went to the KICAD BOM, scrolled down to 422, then said well there is some extra stuff, so I'll call it 400. Not far from the 359.

I'd say the an protect, and digi protect are some of the larger items. If we buffer with the NAND or what have you, do you think we can get by without the digi protect's for those circuits?
User avatar
Fred
Moderator
Posts: 15433
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Re: freeEMS_1.0 rev A KICAD

Post by Fred »

digiprotects are only really required on inputs. digi protect for an output should only consist of either a resistor or a buffer of some sort if implemented. I think we can drop the protection on outputs that are built into the board such as injectors. The ign ones will be protected by the buffer we choose. I need to read up and post some more on that.

Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
GrowlingandBiffo
QFP80 - Contributor
Posts: 56
Joined: Sat Apr 26, 2008 7:42 am

Re: freeEMS_1.0 rev A KICAD

Post by GrowlingandBiffo »

400 components seem a tremendous amount, for a new and indeed modern design...

The Megaquirt V3 AVR (VEMS) is the same footprint and has about 400 and this has built in Wide Band..
User avatar
Fred
Moderator
Posts: 15433
Joined: Tue Jan 15, 2008 2:31 pm
Location: Home sweet home!
Contact:

Re: freeEMS_1.0 rev A KICAD

Post by Fred »

As much as it does sound a lot, I doubt the vems system has a bunch of protection on all pins. That would cut it considerably, as would a single power supply and various other small changes etc.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
GrowlingandBiffo
QFP80 - Contributor
Posts: 56
Joined: Sat Apr 26, 2008 7:42 am

Re: freeEMS_1.0 rev A KICAD

Post by GrowlingandBiffo »

Just giving you the component count of a comparable product.

The AVR may not have this and it may not have that, but it has the same number of components, which way is too many...
Post Reply