QElectroTech doesn't natively support animation. But it does support dynamic text and conditional formatting.
Result: When a bass drum hits, your schematic wire literally fills with >>> arrows moving in real-time. g force qelectrotech tutorial
For a G-Force panel, your BOM should include: QElectroTech doesn't natively support animation
| Tip | Why it matters |
|------|----------------|
| Be consistent – 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. | Result: When a bass drum hits, your schematic
| Problem | Solution | |---------------------------------------|--------------------------------------------------------------------------| | Cannot find accelerometer symbol | Use a generic IC symbol and rename pins manually. | | Wires don’t snap to component pins | Zoom in and ensure you click exactly on the terminal cross. | | BOM missing some parts | Assign a “Reference” and “Value” to each element (right-click → Edit). | | I2C lines need pull-up resistors | Add two 4.7kΩ resistors from SDA/SCL to +3.3V in your schematic. |