26 Reply by b.w.v.leeuwen

(288 replies, posted in Terminal block generator)

Nice indeed, but when loading terminals which have no terminal number (but do have a terminal Id) the script fails to see them. It would be nice to have a possibility when making the drawing just to enter the information to what terminal box the terminals belong (X1, X2, X3 etc). The script will insert them following the order in which they are placed (Page, Column, Row). Than a auto-numbering option might number all the separate terminals (X1:1, X1:2, X1:3 etc, X2:1, X2:2, X2:3 etc, X3:1, X3:2, X3:3 etc).
When there are pre-defined terminals (e.g. X2:5), these ones will be frozen by default (kept while numbering the terminals). An option might be to renumber the whole terminal box, or defreeze separate terminals.

Another nice option might be to use the location field. When the "location"-field is empty it is similar to the "location" of the Folio. When the "location" field of the element defers from the location of the Folio, the terminal is an external terminal. The same is true for elements that are connected with. A terminal might be connected internal with a relay contact. Both the location filed of the terminal and the location field of the relay-contact are empty. This means that it is an internal connection. At the other side of the terminal we have a motor connected. The location field of the motor is "+Roof" and thus defers from the location of the terminal. His means that this connection is an External connection.
The motor might have a Function-description, like "Ventilator 1". This field might be used to fill out a "comment" field for use in the terminal box.
When there are two or more external connections, they might be added to the string, separated by a comma (e.g. Ventilatior 1, Ventilator 2).

Go to forum: Terminal block generator

27 Topic by b.w.v.leeuwen

(8 replies, posted in EN : Help, suggestions, discussions, ...)

It seams a reference is always made up by the "page Id" and then "Row" and "Col" of the element. When using auto page numbering the reference still shows the "page Id" and not the "page number" which is quite confusing.

Go to forum: EN : Help, suggestions, discussions, ...

28 Reply by b.w.v.leeuwen

(17 replies, posted in EN : Help, suggestions, discussions, ...)

Hello,

I really like this new function of dynamic texts. When using rotation I face some problems. When I make a "Group of texts" and put into it some texts with rotation, the rotation is neutralized. Is there some way of keeping the rotation in a group text without rotating the whole group? I would like to have both vertical and horizontal texts in the same group.

Go to forum: EN : Help, suggestions, discussions, ...

29 Reply by b.w.v.leeuwen

(11 replies, posted in Scripts)

Here another example of how core symbols are used to define cables

Go to forum: Scripts

30 Reply by b.w.v.leeuwen

(11 replies, posted in Scripts)

For making things easier with selecting cable's I was thinking of making a Cable database. Here the cables and cores are defined. Something like this:

Cables:
Cable Name            | Diameter | Cable Gland | Number of Cores | Art Number | Other info
YmvK-Dca 2X1,5     |      9,1    |       M20        |         2                 |   170016     |  ....
YmvK-Dca 3X1,5     |    10,2    |       M20        |         3                 |   170026     |  ....
LIYY-JZ Dca 7G0,75|     7,3    |       M16         |         7                 |   172710     | ......
Cat6F/UTP Dca       |      7,2    |       M16         |          8                |    172402    | ......

Cores:
Cable Name            | Core Id | Pair Id | Screen | Inner screen | number | color   | cross section | AWG
YmvK-Dca 2X1,5     |      1     |            |             |                     |              |  bn     |         1,5        |
YmvK-Dca 2X1,5     |      2     |            |             |                     |              |  bl      |         1,5        |
YmvK-Dca 3X1,5     |      1     |            |             |                     |              |  bn     |         1,5        |
YmvK-Dca 3X1,5     |      2     |            |             |                     |              |  bk     |         1,5        |
YmvK-Dca 3X1,5     |      3     |            |             |                     |              |  gy     |         1,5        |
LIYY-JZ Dca 7G0,75|     1      |            |             |                     |      1      |          |         1,5        |
LIYY-JZ Dca 7G0,75|     2      |            |             |                     |      2      |          |         1,5        |
LIYY-JZ Dca 7G0,75|     3      |            |             |                     |      3      |          |         1,5        |
LIYY-JZ Dca 7G0,75|     4      |            |             |                     |      4      |          |         1,5        |
LIYY-JZ Dca 7G0,75|     5      |            |             |                     |      5      |          |         1,5        |
LIYY-JZ Dca 7G0,75|     6      |            |             |                     |      6      |          |         1,5        |
LIYY-JZ Dca 7G0,75|     7      |            |             |                     |      7      |          |         1,5        |
Cat6F/UTP Dca       |      1      |      1    |    sh     |                     |      7      | wh/bl |                     |  23
Cat6F/UTP Dca       |      2      |      1    |    sh     |                     |      7      |   bl    |                     |  23
Cat6F/UTP Dca       |      3      |      2    |    sh     |                     |      7      | wh/og|                     |  23
Cat6F/UTP Dca       |      4      |      2    |    sh     |                     |      7      |   og   |                     |  23
Cat6F/UTP Dca       |      5      |      3    |    sh     |                     |      7      | wh/gn|                     |  23
Cat6F/UTP Dca       |      6      |      3    |    sh     |                     |      7      |   gn   |                     |  23
Cat6F/UTP Dca       |      7      |      4    |    sh     |                     |      7      | wh/bn|                     |  23
Cat6F/UTP Dca       |      8      |      4    |    sh     |                     |      7      |   bn   |                     |  23


When running the script each first core with cable-label will be searched for to find all different cables. For each label (W1001, W1002 etc.) a cable can be chosen from the cable database. The connected cores to the first core symbol will be filled automatically with the correct label. The cable data will be inserted in each core symbol.

Does anyone have an available script for starting with these XML searches?

Go to forum: Scripts

31 Topic by b.w.v.leeuwen

(8 replies, posted in EN : Help, suggestions, discussions, ...)

A feature that might improve the QET for making all kind of connection descriptions like Terminal diagrams, Wiring lists etc. will be the possibility to add text to the QET-terminals within symbols.

Here follows an example of what I mean (see picture):

For now all connections are addressed to -Q1. The separate terminals within -Q1 have an ID in the XML but it isn't possible to add information to them. The texts for the connections (1/L1, 3/L2, 5/L3, 2/T1, 4/T2 and 6/T3) is just plain text. It is not connected to the terminal and thus unusable for getting information about the exact wire connection.

It would be very nice in some future day to have the possibility to add label and description information to each terminal inside a symbol. This would make it possible to derive information about the exact connection and later define them in terminal diagrams, wiring schedules etc. like -Q1:1/L1

In the XML it might look like this (added RED parts of element-xml):

        <elements>
            <element y="180" orientation="0" prefix="Q" type="embed://import/10_electric/10_allpole/200_fuses&amp;protective_gears/12_magneto_thermal_circuit_breakers/dis_mag_term_3f-1.elmt" freezeLabel="false" x="200" uuid="{3648bd06-62de-42ca-82ae-51fe2dcf01b3}">
                <terminals>
                    <terminal y="-36" orientation="0" number="_" nameHidden="0" id="0" x="-20" name="_"/>
                    <terminal y="-36" orientation="0" number="_" nameHidden="0" id="1" x="0" name="_"/>
                    <terminal y="-36" orientation="0" number="_" nameHidden="0" id="2" x="20" name="_"/>
                    <terminal y="36" orientation="2" number="_" nameHidden="0" id="3" x="20" name="_"/>
                    <terminal y="36" orientation="2" number="_" nameHidden="0" id="4" x="0" name="_"/>
                    <terminal y="36" orientation="2" number="_" nameHidden="0" id="5" x="-20" name="_"/>
                </terminals>
                <terminalInformations>
                    <terminalInformation id="0" name="label" show="1">1</elementInformation>
                    <terminalInformation id="0" name="description" show="0">L1</elementInformation>
                    <terminalInformation id="1" name="label" show="1">3</elementInformation>
                    <terminalInformation id="1" name="description" show="0">L2</elementInformation>
                    <terminalInformation id="2" name="label" show="1">5</elementInformation>
                    <terminalInformation id="2" name="description" show="0">L3</elementInformation>
                    <terminalInformation id="3" name="label" show="1">2</elementInformation>
                    <terminalInformation id="3" name="description" show="0">T1</elementInformation>
                    <terminalInformation id="4" name="label" show="1">4</elementInformation>
                    <terminalInformation id="4" name="description" show="0">T2</elementInformation>
                    <terminalInformation id="5" name="label" show="1">6</elementInformation>
                    <terminalInformation id="5" name="description" show="0">T3</elementInformation>
                </termianlInformations>
                <inputs/>
                <elementInformations>
                    <elementInformation name="label" show="1">-Q1</elementInformation>
                </elementInformations>
                <dynamic_texts>
                    <dynamic_elmt_text y="-10.5" font_size="9" text_width="-1" frame="false" rotation="0" x="50" text_from="ElementInfo" uuid="{f3e8a6b2-2fb4-46f4-bee4-f0b5d741267e}">
                        <text>-Q1</text>
                        <info_name>label</info_name>
                    </dynamic_elmt_text>
            <dynamic_elmt_text y="0.5" font_size="7" text_width="-1" frame="false" rotation="0" x="10" text_from="TermianlInfo" uuid="{....}" id="0">
                        <text>1</text>
                        <info_name>label</info_name>
                    </dynamic_elmt_text>
            <dynamic_elmt_text y="0.5" font_size="7" text_width="-1" frame="false" rotation="0" x="15" text_from="TermianlInfo" uuid="{....}" id="0">
                        <text>L1</text>
                        <info_name>description</info_name>
                    </dynamic_elmt_text>
                </dynamic_texts>
                <texts_groups/>
            </element>
        </elements>

Go to forum: EN : Help, suggestions, discussions, ...

32 Topic by b.w.v.leeuwen

(2 replies, posted in EN : Help, suggestions, discussions, ...)

Is it possible to make macro's for multiple use. In a macro will be several symbols with connections and their definitions. There will also be formula's for auto numbering in the symbols. By inserting a complete macro the symbols are numbered according to their format. This speeds up the making of schedules and gives them more consistency.

Here is an example of a macro:

Go to forum: EN : Help, suggestions, discussions, ...

33 Reply by b.w.v.leeuwen

(11 replies, posted in Scripts)

Thank you for your good explanation.

It might be workable when making wires of the type terminal. Every core of each cable has to be a separate symbol, so the potential will not be mixed-up. The same is true for all symbols in the section all-pole/connections. They share the same potential, so they have to be of the type terminal.

While making these symbols I thought, wouldn't it be nice to have a separate "element type" for wires. They have the same potential on both sides, but are in no way terminals. Making them "terminals" courses problems with the terminal block generator. In fact they are no real connections, an endpoint on witch the core is terminated, but just clarifications of the connection itself.

In the terminal-block-generator they have to be seen as "way" and not "end point". E.g. in the previous example, the first terminal is internal connected to the Motor-protection-device, point 2:T1, and at the other side to the Motor, point U1 (and not to the cable, but through the cable).

Go to forum: Scripts

34 Reply by b.w.v.leeuwen

(288 replies, posted in Terminal block generator)

It would be nice if the script would put its data form the XML-file first in a database (e.g. sqlite). From here the data could be edited in a kind of terminal-editor. Some of the actions might be inserting empty terminals. Changing positions of terminals in the terminal block and switching internal/external wiring.
Afterwards this data might be used for various outputs like terminal blocks, but also terminal or cable diagrams. It would be nice in the future for these scripts, as mentioned before, if the QET-terminals can have their own tag-information.

To visualize it a bit I'll add some pictures of what it might look like.

Go to forum: Terminal block generator

35 Topic by b.w.v.leeuwen

(11 replies, posted in Scripts)

I am facing some problems with terminals and cable symbols.
As you can see, the core colors are copied automatically for both sides of the terminals. This is not correct. The cable in my case has numbered wires. When I change them, the cores in the cabinet are changing as well. The same is true for changing them from solid line to dots.
This copying of properties of connections through the terminals is for me unwanted, but I would like to see it in the cable sign. Unfortunately here the wire is interrupted and the properties have to be added manually.

- Is it possible to remove this property copying function from the terminals?
- Is it possible to add it to the cables
- Is is possible to add information to the terminals is the element editor for automatically giving cables doted lines?

Looking forward to receive an answer on these questions.
Bastiaan

Go to forum: Scripts