> Hi Joerg, I'm not quite following you. Examples?
>Hello Jim,
>
[quoted text clipped - 29 lines]
>
>http://www.analogconsultants.com
Why don't you just write your documentation _after_ you have a final
schematic?
I think OrCAD has management tools built-in??
...Jim Thompson
| James E.Thompson, P.E. | mens |
| Analog Innovations, Inc. | et |
| Analog/Mixed-Signal ASIC's and Discrete Systems | manus |
| Phoenix, Arizona Voice:(480)460-2350 | |
| E-mail Address at Website Fax:(480)460-2142 | Brass Rat |
| http://www.analog-innovations.com | 1962 |
I love to cook with wine. Sometimes I even put it in the food.
Joerg - 25 Jul 2005 00:03 GMT
Hello Jim,
> Why don't you just write your documentation _after_ you have a final
> schematic?
Writing in parallel helps a lot in making sure it is complete and all
thoughts are in there. The thoughts might not all stay but I won't
forget any. Too often I have seen engineers design a complicated board
the size of a baking pan and then scratch their head later. What was I
thinking? Why did I do that over here? What's L3 doing in there?
I grew up in med electronics and we are all used to this. In the med
world parallel documenting is actually regulated into the process, at
least for sensitive gear. You have to create a design history file. And
when the FDA inspector cometh that file better be there.
> I think OrCAD has management tools built-in??
Mine didn't but it's old. I am not aware of anything in there until
version 9 that would do document back annotation.
BTW, Cadsoft Eagle does a nice job in design history. I print every
intermediate step and stamp the date and time on it. But this CAD
program also keeps these files as running backups. So I could always
show the version I had, say, Monday last week.
Regards, Joerg
http://www.analogconsultants.com
Joerg - 25 Jul 2005 00:06 GMT
Hello Jim,
> Why don't you just write your documentation _after_ you have a final
> schematic?
Writing in parallel helps a lot in making sure it is complete and all
thoughts are in there. The thoughts might not all stay but I won't
forget any. Too often I have seen engineers design a complicated board
the size of a baking pan and then scratch their head later. What was I
thinking? Why did I do that over here? What's L3 doing in there?
I grew up in med electronics and we are all used to this. In the med
world parallel documenting is actually regulated into the process, at
least for sensitive gear. You have to create a design history file. And
when the FDA inspector cometh that file better be there.
BTW, when a client's engineer crashed his motorcycle the fact that he
kept his spec current saved their bacon. I could jump right in.
> I think OrCAD has management tools built-in??
Mine didn't but it's old. I am not aware of anything in there until
version 9 that would do document back annotation.
BTW, Cadsoft Eagle does a nice job in design history. I print every
intermediate step and stamp the date and time on it. But this CAD
program also keeps these files as running backups. So I could always
show the version I had, say, Monday last week.
Regards, Joerg
http://www.analogconsultants.com
Jim Thompson - 25 Jul 2005 00:19 GMT
>Hello Jim,
>
[quoted text clipped - 28 lines]
>
>http://www.analogconsultants.com
I use Macro Express. One of many macros I've written adds a time and
date stamp. And, anytime I make a change, I simply "Save As" to keep
track of the REV's. PSpice also has "Checkpoints", storing
intermediate steps in building a schematic, but I always forget to use
it ;-)
...Jim Thompson
| James E.Thompson, P.E. | mens |
| Analog Innovations, Inc. | et |
| Analog/Mixed-Signal ASIC's and Discrete Systems | manus |
| Phoenix, Arizona Voice:(480)460-2350 | |
| E-mail Address at Website Fax:(480)460-2142 | Brass Rat |
| http://www.analog-innovations.com | 1962 |
I love to cook with wine. Sometimes I even put it in the food.