Search options (Page 13 of 26)

still only by QElectroTech

For the present, I think the idea of Unalcalde is not a bad thing.
But for the future it would be much better if the "element properties" widget is especially dedicated for element of type "terminal". I mean without a workaround like: "use the field annotation to enter another type of data".
This way it would be easier for the user to know how to configure each terminal.

@ Unalcalde:
are you able to create a dedicated "terminal properties" widget in C++?

@ Galexis:
to differenciate the upper from the bottom screw, we could draw the symbol like this:

where the the white arrow always show the "bottom screw", as convention.
Of course the element of type "terminal" must be extended with new functionalities so that QET knows what is the upper screw and what is the bottom screw.

@ Morganol

it's not a big issue to disable the "automatic connector creation": you're only ONE CLICK away from it ;-)
Most of the users find the functionality very usefull. And it was implemented because of requests of many users (QET v0.4 does not have it).
I personaly only disable the functionality when I'm drawing some terminal strip diagrams or when I'm changing an already done circuitry to avoid that some automatic created conductors appear at the wrong place.

@ Joshua

[mode mec pointilleux ON]

dans le nouveau widget pour établir les ref croisées maître/esclave, pourrais-tu masquer la colonne "N° de folio" quand la check box "utiiser les labels de folio à la place de leurs ID" est cochée dans la config de QET ?
Et inversement, quand la check box est inactive, masquer la colonne "Label de folio" ?

[mode mec pointilleux OFF]

to your problem:

not all elements of the QET collection are up to date. Those you choose are very old I think.
Their definition are updated and need to be actualised. If you want to make it... feel free!

Penser à corriger les fautes de grammaire :

La formule du nouveau potentiel contient des variables incompatibleS avec les reports de folio.

Les variables suivanteS sont incompatibleS :

je plusse à fond !!!
Le fait d'avoir 2 variables pour numéroter les folios est quelque chose de très déroutant. Je parle pour les newbies.
D'un point de vue purement utilisateur, la seule chose qu'on veut pouvoir configurer c'est :
est-ce que je laisse QET numéroter automatiquement les folios (cas où QET utilise %id) ou est-ce que j'attribue manuellement les numéros moi-même (cas où QET utilise %F), auquel cas je suis le seul responsable de l'ORDRE des folios.
Je l'avais déjà dit, mais les appelations "label de cartouche" et "ID de folio" sont des termes qui ont un sens pour les développeurs du logiciel, car il y a une histoire derrière ces termes, mais pour les nouveaux arrivants, c'est incompréhensible intuitivement.
Mes petites expériences de formation en milieu professionnel m'ont montré où se situent les limites de "l'utilisation intuitive" de QElectroTech.

Hello patricknogara,

some actions on a project are not taken into account in the undo/redo stack and these issues are known by the developpers.
This is not a bug, only functionalities that are not completely achieved.
Sometimes I use the same workaround as you to save changes that were not seen as changes (order of folios, etc.).

Usually, in automation, the texts of PLC input or output signals are related to the PHYSICAL state of actuators (valve, motor, lamp, heating, magnet...) or sensors (contact switch, limit switch, proximity switch...) from a PROCESS point of view, not from an electrical point of view.

The reason is that the programmer of the machine/plant has to know what PHISYCALY happens when a digital output is set from low level (=0) to high level (=1). The electrical state of circuitries is not interesting for the programmer, except when he has to debug something.

For example:

You have to control an automatic door which is CLOSED in the passive state.
This door is opened by a pneumatic cylinder, which is controlled by a pneumatic valve, which is controlled by a 230VAC solenoid, which is controlled by a 24VDC relay, which is controlled by a PLC digital output.
To describe the name of the PLC output, it does not matter to know the state of all components between the PLC output and the door (relay, solenoid, pneumatic valve and cylinder).

It means that the PLC output that controls the opening of the door has to be named:
"open automatic door"
because this text describes the high level of the digital output.
--> this way, the programmer knows that when he sets the output to high level, the door opens.

But... don't forget that electrical diagrams are ALWAYS drawn in the PASSIVE state!

a bash script