This is the message, when the file is broken!

QET saves it's data in XML-files and (like many others!) does not show where the problem might be, when loading fails.
Try to open a copy of that file (renamed to *.xml) with firefox: It shows the first problematic part, that you have to fix. This might have to be repeated several times, before the XML is valid.

In a CMD-Window you can also use the most recent version of QET_ElementScaler, where the first problematic part of the file will be shown:
usage:

QET_ElementScaler SchematicFile.qet

It might show something like this:

$ QET_ElementScaler filtre-à-bande.qet 
File "filtre-à-bande.qet" could not be loaded: Error parsing element attribute
Check file up to byte-offset: 1196545 -- content partly shown here:
(...)rmula="" y="-130" numsize="7" condsize="1" conductor_colo" condsize="1" freezeLabel="false" bus="" dash-size="2" y="(...)
$

You mean something like a Bus or a cable like in the attachment?

As far as I know a bus cannot be defined but sometimes I read something like "define a cable" in the forum what might be similar...
Try forum search.

278

(193 replies, posted in Import DXF)

This part really does a lot of work...

Thanks for the link to the data sheet! At least now we have specific values to discuss.

But perhaps we should move away from this specific part to find something generally valid.

The primary aim is to obtain a “respectable” QET element that we can scale in a second step if necessary. The prerequisite for an element that requires little reworking is, of course, that circles from the dxf also look like circles in the element. To achieve this, the element size must be appropriate.

Do we have the chance to determine during import whether the numerical values in the unitless dxf are so small that scaling would be necessary? Something similar to: “Values are all smaller than xx, so will be enlarged by a factor of 10 or 100!

279

(193 replies, posted in Import DXF)

Maybe it is necessary also to take the tag $MEASUREMENT into account?
In the file “05DI-AD16DIX-10.dxf” one can find this:

$MEASUREMENT
 70
     0
  0

When imported in current FreeCAD dev-version you can measure the terminal-width: 18,19 mm (see screenshot)

@scorpio810:
Do you know the manufacturer and name of that part to get the real dimensions, Laurent?

280

(193 replies, posted in Import DXF)

I have noticed that there are differences in the unitless dxf files.
The test file for 1-point polygons does not contain “INSUNITS” and the file “05DI-AD16DIX-10.dxf” (see here https://qelectrotech.org/forum/viewtopi … 379#p20379) contains the tag “INSUNITS”, but no entry “70” for the unit, but this:

INSUNITS
350
99E
  3

and so the resulting element is very small. I tried a few factors and found a suitable value, I think. An “educational guess” results in a factor of 99.0508158778 for this file - then the individual terminals have a distance of 5.08mm = 10.4px. This is a commonly used dimension for terminals.
I couldn't find out what the values in the tag stand for.

For the tests I used the current source code from January 10 2025

Neben der Frage, ob ich Dir helfen kann...
Das habe ich in einem anderen Thread so geschrieben:

Many unanswered questions before you can be helped:
Which system are you using?
Which QElectroTech version are you using? (Help -> About QElectroTech -> ‘Version’ tab)
Are there any helpful entries in the log file? (Help -> About QElectroTech -> ‘log’ tab)

... und der angesprochene Anhang fehlt auch!

You mean the overlapping texts?
Try forum-search with keyword "overlap" or read here:
https://qelectrotech.org/forum/viewtopic.php?id=2418

It's the combobox under the one for user-collection in QET-Settings.
I use Debian GNU/Linux and most recent dev-version, so the paths look different from those, you use!

Maybe the path to user-titleblocks is not writable?
Did you try to set another path to user-titleblocks?

Kurze Antwort: Nö!

Etwas längere Antwort:
Gerade bei Relais hast Du doch den Kontaktspiegel, der Dir anzeigt, welche Kontakte wo verbunden sind.

Mir sind nur zwei Möglichkeiten bekannt, wie man Kontakte miteinander verbindet:
Entweder man verbindet sie mit einer mechanischen Verbindung (gestrichelte Linie) oder man verknüpft sie als "Master-Slave".
Dein Vorgehen ist aus meiner Sicht also völlig o.k.!

Tip: Move the mouse pointer slowly over the icons in the toolbar and read the hint texts!

jns wrote:

Was ich erreichen möchte ist, ein Drucktaster mit einem Öffner und einem Schliesser, welche ich individuell platzieren kann. Gibt es da eine elegante/standart Lösung?

Wer oder was hindert Dich daran, den zweiten Kontakt frei auf einem beliebigen Folio zu plazieren und die beiden dann zu verknüpfen?

Die Einstellungen wirken natürlich nur für die Elemente, die man auch passend eingestellt hat:
Man kann das in den Einstellungen für Spule, Schutzeinrichtung, Schalter unterschiedlich machen.
Dann klappt's auch mit den Schaltern und Hilfskontakten...

Hallo Foriever,

Deine Beobachtung stimmt!

Da ich das Verhalten auch nicht toll finde, habe ich mich im Quellcode auf die Suche nach der passenden Stelle gemacht und glaube, das Verhalten auch so geändert zu haben, sodass nur gescrollt wird, wenn der Text den sichtbaren Folio-Ausschnitt verlässt.
Werde bei GitHub einen PR erstellen.

online-translator:

Salut Foriever !

Ton observation est juste !

Comme je n'aime pas non plus ce comportement, j'ai cherché l'endroit approprié dans le code source et je pense avoir modifié le comportement de sorte que le texte ne défile que lorsqu'il quitte la partie visible du folio.
Je vais créer un PR sur GitHub.

Kellermorph wrote:

Jetzt fehlt mir nur noch die Variable für die höchste selbst eingetragene Seitenzahl.

Ich kann noch nicht so ganz nachvollziehen, welchen Nutzen Dir diese Angabe bringen soll!
Im Inhaltsverzeichnis stehen doch alle Folios mit den neu benannten "Seitenzahlen" in der richtigen Reihenfolge drin!

Wenn ich einen Schaltplan bekomme und sehe auf der letzten Seite eine Angabe wie "Seite 57 von 57", dann erwarte ich einen Stapel von 57 Blättern. Und wenn ich die Blätter dann durchzähle und finde nur 38 Blätter, dann gebe ich den sofort zurück und fordere einen kompletten Plan!
Wenn zwischendurch einige Seitenzahlen übersprungen werden für Reserve oder so, dann erwarte ich dort leere Folios. Oder entsprechende erklärende Trennblätter. Dann will ich aber irgendwo nachsehen können, wieviele Blätter ich in diesem Schaltplan zu erwarten habe. Deswegen wäre eine Angabe

Seite 57 (gesamt: 38 Blatt)

meiner Meinung nach vielleicht sogar richtiger bzw. praktischer!

Your file contains garbage!

At the end there are many lines behind the last closing tag "</project>" (see screenshot) and at line 12315 there are additional (fragments) of tags!

It seems that you once had some problems with your system? Did you switch off your system without closing all programs? Just guessing...

alexandra wrote:

la version utilisé est :
QElectroTech V 0.80c+87c957a06d79751d3
(...)

With which version was the QET-file created?

Do you have a special reason why you use such an old version?
Please try more recent version 0.9 or even the current dev-version from QET Download-page:
https://qelectrotech.org/download.php

The log file was not as informative as hoped:
Apart from two warnings, I don't see anything unusual.

alexandra wrote:
(...)
11:43:28.526 Warning: QString::split: invalid QRegularExpression object (:0, )
11:43:33.920 Warning: QString::split: invalid QRegularExpression object (:0, )
(...)
alexandra wrote:

comment puis je vous envoyer mon fichier ? Sur quelle adresse mail ?

Please attach the qet-file to a post here in the forum. Unless there are any legal concerns regarding patents or company secrets!

Hello Alexandra!

Many unanswered questions before you can be helped:
Which system are you using?
Which QElectroTech version are you using? (Help -> About QElectroTech -> ‘Version’ tab)
Are there any helpful entries in the log file? (Help -> About QElectroTech -> ‘log’ tab)
What have you done with the file in the meantime? (edited it with an editor or something?)
Can you make the file available for checking?

Kellermorph wrote:

If im doing it, it doesnt change the Number. In this example from 6 to 8.

Streiche doch mal das "-id" aus dem Schriftfeld und schreibe nur "%(folio)" da rein!

297

(193 replies, posted in Import DXF)

Addendum:
In the thread Scripts / QET-Element to SVG you find some posts with comments from Laurent, Joshua and me about texts, fonts and font-sizes in qt / QET. There are also some links to docs for further reading.
https://qelectrotech.org/forum/viewtopic.php?id=2637

8A wrote:

What is the correct way to create a new element from a DXF?

Did you notice the menu-entry just below "Import scaled element"? (see attachment!)
AND: Use the conversion-tool dxf2elmt! The other tool is VERY outdated!
You find the download-link for win64 in this post: https://qelectrotech.org/forum/viewtopi … 520#p20520

8A wrote:

(...) I exported a DXF (...)

What do you want to do?
QET works with own file-formats for elements and schematics!

I think, many of your questions about scale and dxf-import will be answered, if you read in the other thread and follow the links there:
https://qelectrotech.org/forum/viewtopi … 684#p20684

299

(193 replies, posted in Import DXF)

Hello Vadoola!
Salut Laurent !

vadoola wrote:

Another question is if I have a dxf that is "unit less" should I do any scaling at all or just assume it's in pixels. I don't recall which drawing it was ...

It would of course be a great help to see such a unitless file in order to be able to judge how we should deal with it.

But if there are no units, there is nothing you can do but assume pixels as the unit. Perhaps a factor of 10, 100, etc. would make sense if it turns out that the structures would otherwise be too small? You can only estimate the factor if you have seen a few examples...

8A wrote:

(...) but I need to scale a DXF  (...)

As the name QET_ElementScaler might suggest, only QET-Elements can be scaled by that software!
You need to convert your dxf to a QET-Element before using QET_ElementScaler!