Nouveautés de la version de développement 0.9> 0.200.1 (Page 17 of 18)

ispyisail
yesterday
Collaborator
Author
No terminal? SpaceMouse Check now exists for all three systems. Download, double-click, press Start, then attach the file it saves here:
https://github.com/ispyisail/qelectrote … e-check-v1

Mac: SpaceMouseCheck.zip
Windows: SpaceMouseCheck-Windows.exe (if Windows warns, click More info → Run anyway)
Linux: SpaceMouseCheck-Linux-x86_64.tar.gz (it asks for your password to read the device)
The page has the steps for each system.

https://github.com/qelectrotech/qelectr … ssues/1112

Unfortunately, no – all that’s needed is for someone to have some spare time to sort it out and send me the videos; I’d be happy to upload them to the channel.

50 new features on master, April 2022 – July 2026
https://github.com/qelectrotech/qelectr … sions/1196

50 new features on master, 1 August – 19 September 2026
https://github.com/qelectrotech/qelectr … sions/1195

50 new features on master, 19–30 September 2026
https://github.com/qelectrotech/qelectr … sions/1193

IEC-Normen als Standard in QElectroTech? / Normes IEC par défaut dans QET ? / IEC standards by default in QET?

Deutsch

Hallo zusammen,

auf GitHub gibt es einen Vorschlag, QElectroTech schrittweise so auszubauen, dass Schaltpläne standardmäßig nach den IEC-Normen gezeichnet werden können (Betriebsmittelkennzeichnung nach IEC 81346, Dokumentationsregeln nach IEC 61082, Aderfarben nach IEC 60445 usw.):

https://github.com/qelectrotech/qelectr … sions/1267

Ich möchte ehrlich sein: Diese Normen betreffen vor allem Anwender und Entwickler in Deutschland und in osteuropäischen Ländern, die sie seit langem benutzen. Ich selbst wende IEC 81346 in meinen eigenen Projekten noch nicht an und kann daher die fachlichen Details nicht gut beurteilen. Ich kann nur einschätzen, was es für den Code, das Dateiformat und die Veröffentlichung bedeutet.

Deshalb brauche ich Eure Erfahrung:

• Stimmt die Übersicht in der Diskussion (was QET heute kann und was fehlt) mit Eurer täglichen Praxis überein?

• Welche Buchstabentabelle nach 81346-2 verwendet Ihr in der Praxis, die ältere oder die von 2019?

• Wer hat Zugang zu den Normtexten, damit die Regeln am echten Text überprüft werden können?

• Was würdet Ihr zuerst brauchen (zum Beispiel Aderfarben inklusive Grün-Gelb, oder die Kennzeichnungsstruktur)?

Wichtig: Es ist noch nichts entschieden, und vor der stabilen Version 0.200.2 wird dafür kein Code eingebaut. Bestehende Projekte sollen sich nicht verändern. Antworten bitte gern direkt in der GitHub-Diskussion oder hier im Forum, auf Deutsch, Französisch oder Englisch.

----------------------------------------

Français

Bonjour à tous,

il y a sur GitHub une proposition pour faire évoluer QElectroTech progressivement afin que les schémas puissent être dessinés par défaut selon les normes IEC (désignation des matériels selon IEC 81346, règles de documentation selon IEC 61082, couleurs de fils selon IEC 60445, etc.) :

https://github.com/qelectrotech/qelectr … sions/1267

Je veux être honnête : ces normes concernent surtout des utilisateurs et développeurs en Allemagne et dans des pays d'Europe de l'Est, qui les utilisent depuis longtemps. Je n'applique pas encore IEC 81346 dans mes propres projets et je ne peux donc pas bien juger les détails techniques. Je peux seulement évaluer l'impact sur le code, le format de fichier et la publication.

J'ai donc besoin de votre expérience :

• Le tableau de la discussion (ce que QET sait faire aujourd'hui et ce qui manque) correspond-il à votre pratique quotidienne ?

• Quelle table de lettres 81346-2 utilisez-vous, l'ancienne ou celle de 2019 ?

• Qui a accès aux textes des normes, afin de vérifier les règles sur le texte réel ?

• Que vous faudrait-il en premier (par exemple les couleurs de fils, vert-jaune compris, ou la structure de désignation) ?

Important : rien n'est décidé, et aucun code ne sera intégré avant la version stable 0.200.2. Les projets existants ne doivent pas changer. Vous pouvez répondre dans la discussion GitHub ou ici sur le forum, en allemand, français ou anglais.

----------------------------------------

English

Hello everyone,

there is a proposal on GitHub to gradually extend QElectroTech so that diagrams can be drawn to the IEC standards by default (device tags per IEC 81346, documentation rules per IEC 61082, wire colours per IEC 60445, etc.):

https://github.com/qelectrotech/qelectr … sions/1267

To be transparent: these standards mainly concern users and developers in Germany and in Eastern European countries, who have used them for a long time. I don't apply IEC 81346 in my own projects yet, so I'm not well placed to judge the technical details. I can only assess the impact on the code, the file format and the release process.

So I need your experience:

• Does the overview in the discussion (what QET does today and what is missing) match your daily practice?

• Which 81346-2 letter table do you actually use, the older one or the 2019 one?

• Who has access to the standards texts, so rules can be checked against the real text?

• What would you need first (for example wire colours including green-yellow, or the tag structure)?

Important: nothing is decided, and no code will be added for this before the stable 0.200.2 release. Existing projects must not change. Please reply in the GitHub discussion or here on the forum, in German, French or English.

Best regards,
Laurent

A new tool for converting DXF and DWG files to elmt format:

dwg2qet: DWG/DXF → ready-to-wire QElectroTech elements (terminals on the grid, BOM data, cabinet front views, batch libraries)
https://github.com/qelectrotech/qelectr … sions/1452

FYI, following PR #1438, the terminal block commands have been moved from the Project menu to a new ‘Lists’ menu.

The Lists menu contains the table of contents, the materials list, the terminal strip manager, the terminal generator plug-in and the new cable list.
The Numbering menu, next to the Project menu, contains terminal numbering and the new cable numbering dialogue box.
The Project menu now only retains the CSV export of the cable list, in addition to its usual entries.

52 new features on master, 1–15 October 2026 #1485
https://github.com/qelectrotech/qelectr … sions/1485

Hi Laurent,

Thank you so much for your work on the terminal manager – you have already implemented a large part of what I had planned myself: the terminal colors with the palette (green/yellow stripes included), the cross-section and manufacturer width catalog, the realistic terminal block drawing, the natural sorting, the drag & drop of free terminals, and the layout saved in the project. This is a huge step forward.

Here is what I had in mind for the remaining part, for discussion:

1. Fully automatic creation of the strips When the terminal manager is opened (or on a trigger), free terminals should be grouped automatically by their label prefix. In my projects the labels look like X1:1, X1:2 (colon as separator), so X1:1 and X1:2 belong to strip X1, X2:1 to strip X2, and so on. A strip should be created for each group, with the terminals added in natural order. Ideally the import should be idempotent: only add new terminals and never re-order or touch what the user changed manually (re-ordering, bridge colors, etc.).

2. Automatic cable assignment The cable column should be filled automatically: which cable and which core belongs to which terminal. The information is already in the project (a conductor stores the terminal name on the cable side), so the manager could resolve the core per terminal and display it in the usual notation, for example 15W1:bl (cable 15W1, core color blue). The cable type could be shown as well.

3. Automatic bridge creation An automatic bridge detection would be great. From my understanding it could work in two ways: either the two terminals are directly connected by a line in the schematic, or they share the same entry in the potential/function field of the conductors. It would need to be clarified which of the two (or which combination) is the desired procedure.

4. Stacked terminals ("Etagenklemme") and terminal Bauart A field on the terminal element for the physical type (pass-through 2/3/4-pole, stacked terminal 2/3/4 levels, measuring terminal, grounding terminal…), preferably pre-filled as a default by the symbol in the element editor and overridable per instance. With such a field, the automatic strip creation could build the levels itself instead of setting the level spinbox by hand (currently max. 4 levels in the drawing, but the spinbox allows 6 – probably worth aligning).

5. Editing color / section / width in the schematic editor Could the three new fields (color, section, width) also appear in the element properties widget in normal schematic mode, not only in the element editor and in the terminal manager? And also for free terminals in the free-terminal table? The important point for me: both directions must stay in sync – they already write to the same element data, so changing it in the schematic must show up in the terminal manager and vice versa. Having both edit points would be great to fix copy/paste mistakes wherever I notice them.

6. Small extras (low priority)

A warning when the wire section of an attached core is bigger than the rated section of the terminal.
Optionally showing the internal target as a line like the cables, with color and section, if that's not too heavy for the drawing.
No pressure at all – I just wanted to write down where I'd like to go, and I'm happy to help testing or discussing the design. If some of this is already being worked on, even better.

Thanks again for your great work!

Best regards

Hallo Thomas,

A small addition: to help you start with point 2 (automatic cable column), here is a patch on current master: terminal_strip_cable_auto.patch

The cores of your cable management (PR #1438) are already stored on the conductors, so RealTerminal::cable() / cableWire() now read them and the manager and the drawing show e.g. 15W1 / bl automatically (the core number when the cable type has no colours). Without a wired cable, the hand-typed values are kept. Cells filled from a cable are read-only and are not written into the element.

Not compiled on my side yet, and it doesn’t distinguish the cable side from the internal wiring side. Take it, change it or rewrite it as you like.

Laurent

Terminal strips: what's new in the development version

Several improvements to terminal strips have just been added to the development version (nightly builds). Here is how to use them.

1. The chosen terminal is now remembered

When you pick a terminal from the catalog (Width column of the terminal strip editor, or Width / Manufacturer in the element editor), QElectroTech now stores which terminal it is, not only its width.
Before, several terminals with the same width (for example Phoenix Contact UT 4 and ST 4, both 6.2 mm) could not be told apart: on reopening, the first one of the list was shown.

• The Width column now shows the terminal, for example: 6,2 - Phoenix Contact ST 4

• The manufacturer and manufacturer reference information of the terminal are filled automatically (useful for the bill of materials).

• A value you typed yourself in these fields is never overwritten.

• Copy / paste of the Width column keeps the chosen terminal.

2. Manufacturer filter in the terminal strip editor

In the Layout tab of the terminal strip editor, a new Manufacturer list is available in the right panel.
Choose a manufacturer, and the Width column only proposes its terminals, compatible with the section of the row.
Each terminal strip remembers its own manufacturer (saved with the project when you click Apply): X1 can use Phoenix Contact and X2 WAGO.

3. Realistic drawing: screw, spring or push-in

In the realistic styles, a terminal chosen from the catalog is now drawn with its own clamp:

• Screw: Phoenix Contact UT, Weidmüller WDU, ABB Entrelec M, Legrand Viking 3

• Spring / push-in: Phoenix Contact ST, WAGO TOPJOB S

A strip mixing screw and spring terminals is drawn as it really is. Terminals without a catalog reference keep the style of the layout.

4. Terminal strip views are refreshed immediately

The terminal strips drawn on the folios are now redrawn as soon as you click Apply in the terminal strip editor, and also on Undo / Redo. No more need to scroll or zoom to see the change.

5. Spare terminals

You can now add spare (reserved) terminals to a strip: terminals which are not drawn on any folio, but are part of the strip and of the bill of materials.

1. Open the terminal strip editor and select the terminal after which the spare terminals must be inserted (if nothing is selected, they are added at the end of the strip).

2. Click Add spare terminals...

3. Choose:
   - the number of terminals,
   - the numbering: prefix and first number are proposed from the selected terminal (after X1:12 you get X1:13, X1:14..., leading zeros are kept: X1:05 → X1:06). Untick Number the terminals to leave them without label,
   - Same terminal as...: copies type, function, LED, section, width, catalog terminal, color, manufacturer, reference, designation, plant and location of the selected terminal (not its label nor its cable).

4. Click OK.

Then:

• The labels can be changed or erased in the table, like any other cell (then click Apply).

• The Xref column shows Spare for these terminals.

• To delete spare terminals, move them to Independent terminals with the Move to button.

• They appear in the bill of materials (CSV export and nomenclature tables), after the elements of the folios. Set exclude_from_bom if you don't want them there.

• Everything can be undone (Ctrl+Z).

Compatibility note
Spare terminals are saved inside the terminal strip in the .qet file. An older version of QElectroTech ignores them, and loses them if it saves the project. Keep a backup if you share projects with users of older versions.

Feedback and bug reports are welcome here or on GitHub. Thanks!

Edit:
6. Opening the terminal block manager
On a big project, (in ‘lazzy’ mode ->.qetz – it’s worth noting, incidentally, that a large project opens in 3 seconds, compared with 35 seconds previously, but navigating through the folio can be slow and open terminal strip generator need to read all sheets) so opening the terminal block manager can take a while (the folios not loaded yet are read). A window now shows Reading folio n of N... with a progress bar, and QElectroTech stays responsive meanwhile.

Fix: a terminal strip just added to a folio is now refreshed immediately too, like the ones already saved in the project.