The first step was always the same: a clean sheet. Alex created a new project in QElectroTech and set the page size to the required print dimensions. On the left, the libraries promised footprints, symbols and connectors. Alex imported a custom symbol for the IMU (inertial measurement unit) and a module symbol for the flight controller. The tutorial began with this: how to set page size, import libraries, and add custom symbols — a gentle orientation for someone opening QElectroTech for the first time.

| Tip | Why it matters | |------|----------------| | – Use names like K1-1 , K1-2 for coil/contact sets. | Avoids orphaned contacts that never simulate correctly. | | Use the "Report" function – Generate a list of all G Code pairs (Coils → Contacts). | Instant verification of your logic design. | | NC contacts need the "Slave Type: NC" – Don’t leave it as default NO. | Simulation will show opposite behavior. | | Equipotential names are global – A name like +24V on one page connects to +24V on any other page. | Creates virtual power rails without messy wires. | | Don’t mix master/slave on one component – A coil is master only; a contact is slave only. | Prevents recursive logic errors. |

Next, he needed protection. He opened the Protection > Fuses folder. He dragged a below the source.