Wire Schedule Report
General
Panel wire optimisation requires a wire list to analyse. The wire list is generated when you compile the connection reports for your Elecdes project inside EBASE. If you are constructing only a Paneldes model and have no schematic drawings included in your Elecdes project, EBASE will produce you a blank report into which you can manually enter the wires.
The wire schedule must reside in your Elecdes project directory. The file must be named "YourElecdesProjectFromToWire.DBF". For example, if your Elecdes project is called "ProjectOne", then the wire schedule database will be named "ProjectOneFromToWire.dbf ".
Viewing / Editing
How to view wire and cable reports
Field usage in the Wire Schedule
Most of the fields in Wire Schedule can be regarded as INPUT data (wire name etc.). Only the compulsory fields are required to correctly optimise the wire routes. There are fields in the file that are only used for materials data (e.g. TYPE).
A number of fields in this file are designated as the report fields for the Paneldes routing function. i.e. They will contain REPORT data after wire route optimisation has occurred (e.g. wire length and route).
There are also optional fields in which data may be entered to provide more information to improve the routing optimisation results.
Compulsory fields
Whether you use the wire schedule generated by Elecdes, or manually perform the data entry, you must ensure the following fields have correct data:
| Field | Description |
|---|---|
| WIRE | The unique name of the wire. |
| PNLNO_A | The name of the panel containing the device or terminal strip for one end of the wire. |
| DEV_TBLK_A | Device or terminal strip tagname for one end of the wire. |
| TERM_A | Terminal tagname for one end of the wire. |
| PNLNO_B | The name of the panel containing the device or terminal strip for the other end of the wire. |
| DEV_TBLK_B | Device or terminal strip tagname for the other end of the wire. |
| TERM_B | Terminal tagname for the other end of the wire. |
Optional fields:
Data entered into the following fields will provide more information to improve the routing optimisation results.
| Field | Description |
|---|---|
| FORCE |
If this field is blank or contains "0" values, e.g. "0,0", then all segments of the wire can be "loop optimised". Ebase will write into the FORCE field any wire termination order value, from a termination block (CONX), for each termination as a comma separated pair of numbers. The value "0,0" indicates a pair of terminations with no specified termination order. The Ebase values are taken as input by Paneldes wire termination optimisation. Paneldes will write into the FORCE field temporary wire termination order values determined by the wire termination optimisation. The temporary values have a "$" prefix, for example "$3,$4" represents the optimum third and fourth terminations for a wire. The Paneldes temporary values are taken as input by Ebase to Back annotate Paneldes wire order during reporting. |
| POWER | This field should contain a number representing the power compatibility of the wire. You can define the compatibility for each number 0...32768. Sensitivity to electromagnetic interference is the usual use for the power number. Paneldes will only route wires through raceway with the appropriate power number. |
| CABLFACTR |
Filling factor for this wire. This may represent any wire attribute your local regulations require e.g. weight, cross sectional area. The duct fill percentage is calculated as follows: Summation of the cablefactor for all wires contained in a duct / The duct's cablefactor. This field should contain a number e.g. 3.6, 0.1, 2.400. You can also use the NEC code to calculate raceway fill for trays and conduits. |
| WEIGHT |
Weight of this wire. The weight fill percentage is calculated as follows: Summation of the weight for all wires contained in a raceway / The raceway's weight factor. This field should contain a number with units, e.g. "205 kg/km", "0.1 kg/m", "137 lbs/1000ft", "109.5 lbs", defaulting to /1km or /1000ft where a distance is not specified. |
| MINBNDRAD | Bend radius for this wire. If the chosen route has any segments bending at a smaller radius than this value, a warning will appear in the details field. |
| DRUMSIZE | The length of conductor available on a single drum. |
TERMSIDE_A TERMSIDE_B |
The side of a polarised terminal to which the wire is connected. These fields should contain either SIDE1 for a connection from above the terminal or SIDE2 for a connection from below the terminal. See Route Connections. |
Report fields
After routing, route data will be placed in the existing wires list database (the FromToWire Report). Paneldes will only add or overwrite data in existing records of the file in the following fields:
| Field | Description |
|---|---|
| EST_LEN |
Optimal wire length using the chosen route. For imperial users the value can be configured to report either feet + inches or only inches. See How to Configure the General Settings. |
| ROUTE |
Tagname of the Paneldes route for this conductor, chosen by the route optimisation function (if not filled in by route optimise function, then no route was found on your model, for this conductor). The details of the chosen route can be found in the Route List. |
| DETAILS |
Information about the route: alternate route used, route was overfilled, route bends too tightly. If the optimisation function placed your wire in a route other than the shortest found route OR in an overfilled, small bend radius route, you will need to alter your model. |
| WARNINGS |
Warnings about problems with finding a valid route. |
See also
From-To Wire report database in more detail.