How do you plan out your electronics?

It's important to me to properly document my projects. This includes schematics, BOM, mechanical design, and simulation.

kkazem OMG, did you say documentation LOL!! For each piece of gear that goes into the sim, I have one book for part numbers, description, and my part number which are <categroy><my number><manufacure><description> category and categories numbers 1 -100.

Each Modules Book has a number which is in the parts list.

Normally, there are sections like Intro/scope, design theory, user manual, repair section, and of course our friends the part number section. This list is <descrption by category><partnumber><manufacure><mypartnumer>

~~Cris

phoenixcomm  I don't think it necessarily has to be that complicated for every project. I might start a new project with a block diagram either on paper or using AutoCAD. I often do the B.O.M. using a Microsoft Access database with a single table. Then, I'll do a schematic in Altium, and simulate using LTSPICE (I do analog and mixed signal most often). After simulation of PARTS of the circuit, I'll either breadboard or layout a PCB. When testing, I use a lab notebook and this is most helpful later on. I also use Excel for many design calculations. Obviously, I'm not talking digital here as I specialize in Inverter, DC-DC Converter, and magnetics design.

Before choosing parts, I carefully inspect the datasheet. This is especially important for ALL new ICs and even for caps and resistors in certain applications to ensure reliability. For example, if I'm using a resistor for a high pulsed power application, I must be sure the part can take the pulsed power without damage. But manufacturers don't typically provide pulsed power specs for resistors, so the engineer must work with the available information.

Anyway, the documentation process for sure depends on the type of project. I document differently for a Arduino or Raspberry Pi project than for a power inverter.

We all have our own procedures for documenting a project. What's really important is that you put down enough information so that it's there when you need it in the future.

phoenixcomm  I don't think it necessarily has to be that complicated for every project. I might start a new project with a block diagram either on paper or using AutoCAD. I often do the B.O.M. using a Microsoft Access database with a single table. Then, I'll do a schematic in Altium, and simulate using LTSPICE (I do analog and mixed signal most often). After simulation of PARTS of the circuit, I'll either breadboard or layout a PCB. When testing, I use a lab notebook and this is most helpful later on. I also use Excel for many design calculations. Obviously, I'm not talking digital here as I specialize in Inverter, DC-DC Converter, and magnetics design.

Before choosing parts, I carefully inspect the datasheet. This is especially important for ALL new ICs and even for caps and resistors in certain applications to ensure reliability. For example, if I'm using a resistor for a high pulsed power application, I must be sure the part can take the pulsed power without damage. But manufacturers don't typically provide pulsed power specs for resistors, so the engineer must work with the available information.

Anyway, the documentation process for sure depends on the type of project. I document differently for a Arduino or Raspberry Pi project than for a power inverter.

We all have our own procedures for documenting a project. What's really important is that you put down enough information so that it's there when you need it in the future.

kkazem Rember this is a large flight simulator, not a small one-off.

phoenixcomm  wrote:

 

kkazem  Rember this is a large flight simulator, not a small one-off.

Cristina, I didn't know we were talking about a flight simulator. I thought this discussion was about documenting our engineering projects.

kkazem it is my project. its just verrry large.