How to View Wire and Cable Routes and lock, unlock, pull and issue cables
After running route optimisation you will need to check that your cables and wires are in the appropriate trays, ducts etc. and that the optimal routes, which Paneldes has assigned, are the routes that you had planned for your conductors.
Paneldes provides a diagnostic tool for you to view each cable / wire, in its route, for the purpose of checking your route optimisation results. The viewing functions allow you to visualise the routes that have been calculated by Paneldes.
If you need further information about the routing process that has occured, to assist in diagnosing issues that you have observed, Paneldes optionally provides the diagnostic output data files: RLIST.TXT and SegToPanelConnections.txt. These files can tell you how Paneldes connected trays together for routing and other details. The files are described below.
During viewing, many of the Paneldes layers are automatically turned "off" for visual clarity. Use the Clear Routes button inside Cable Manager to return to a normal model view.
During viewing, cable and wire routes are drawn on the Paneldes "routedisp" layer.
During viewing, the "Construction" layers for raceway envelope are left visible so you can view the raceway that the conductor is routed through.
Labels are attached to the lines of the viewed route to identify the conductor.
The line for the conductor route is drawn with a non-zero lineweight to enhance visibility.
You can query a conductor after you have used this tool to view its route.
Raceway segments from locked routes that are missing from the model will be skipped when viewing the route. The straight line across the gap vacated by the missing segment will be used in its place.
If you have not modified your model, you can load cached data to reduce the time required to load the route segment connections and panel and device lists.
For wire viewing function, a list of wire and their routes is displayed, as shown in the following dialog:
For cable viewing function, a list of cables and their routes is displayed, as shown in the following dialog:
The conductor list can be sorted by any column of data displayed in the list. This is done by clicking on the headings of the columns. The order of the columns can also be rearranged to allow easy sorting and identification of conductors of interest. This is done by dragging the column headings.
Select the routes you wish to view by clicking on the entries in the list.
You can use the selection buttons along the top of the dialog to select groups of routes.
Once you have selected the routes you wish to draw, clickto view them. The conductor will be drawn on the drawing. If you are using the cable route diagram, terminating devices or panels will be drawn even if there is no route found for the cable.
You can display the guidance for the wire by clicking wire route dialog.on the
To remove the drawn routes click Cable Manager.in
RLIST.TXT Diagnostic Data
If you need further information about the routing process that has occured, to assist in diagnosing issues that you have observed, Paneldes optionally provides a diagnostic output data file. The file is RLIST.TXT. This can tell you how Paneldes has connected trays together for routing and also provides other connection details. This file will often be used to explain why a cable seems to route in a path that was not expected, for example, 2 trays that appear to join however did not form a junction.
The first part of the file describes the raceway connection preferences, specifically the preferences that influence the connection behavior of the raceway.
Each following section of the file describes one raceway segment (tray, conduit or similar) and its connections. All segments are included in the file.
A section of this file would appear as follows:
>Seg 1344 of 5585: GZ899-4808#2
CLASS: CABTRAY PWR [ 400,230 ] CF [ 0.00 ] Length [ 0.3740m ]
Major end positions: ( 69448.1508,218174.7532,-500.0000 ) - ( 69448.1508,218548.7533,-500.0000 ) Raceway network: 1
Seg 1343 - GZ899-4808#1 Snug tray 0 at end 0. PWR [ 400,230 ] CF [ 0.00 ]
Seg 1345 - GZ899-4820#1 Connection 1 at end 0. PWR [ 400,230 ] CF [ 0.00 ]
Seg 4698 - UG496C.1 Connection 2 at end 0. PWR [ 400,230 ] CF [ 9490.00 ]
Seg 1250 - GZ599-4811 Snug tray 0 at end 1. PWR [ 400,230 ] CF [ 0.00 ]
The first line in each section contains the segment number (e.g. 1344) and tagname (e.g GZ899-4808#2 ). The segment number is often used in other parts of this file when referencing back to connections from other raceway segments.
The second line describes the CLASS (type of raceway component) and the POWER level number for that segment of raceway. The length of the raceway is also included on this line. When POWER levels do not match the raceway segments will not join.
The third line describes the end points in 3D space of the raceway segment. With this data you can check to see if two segments are close enough to each other to form a connection. The network number is also displayed. Raceway on the same network is theoretically joined and should be, at least, indirectly connected.
The list of "RouteConnections" that follows the third line describes each raceway segment that connects to segment 1344. The other segments have some of their properties listed and the type of connection formed. This list will quickly establish if your two trays have formed a junction/connection.
All connections are listed including REAL connections, DUMMY connections and BRIDGING connections. Dummy connections are created when a route is LOCKED and segments that were saved in that route are somehow lost or deleted. Paneldes forms a new connection which jumps the missing segment. BRIDGING connections are formed when bottleneck passes allow separated networks to artificially bridge (connect) to find a route when no route was found (due to network disconnection).
SegToPanelConnections.txt Diagnostic Data
You can enable a logging option so that Paneldes will create a text file listing the names of the route segments that are considered to be connected to each device or panel for each wire or cable route.
Paneldes will create a text file with the name <project>SegToPanelConnections.txt.
A section of this file would appear as follows:
Pass: Initial, Main trace
3 connections to panel/device 'CRPF1'.
'TRAY102x' on network 47 at distance 0.8016m with power '0' and cablefactor 40.00.
'TRAY001' on network 47 at distance 1.5307m with power '0' and cablefactor 4.00.
'TRAY217#1' on network 1 at distance 1.5761m with power '4' and cablefactor 4.00.
1 connections to panel/device 'FP1'.
'TRAY103' on network 47 at distance 0.6486m with power '0' and cablefactor 0.00.
The first line specifies the name of the cable.
The second line specifies which routing pass the section applies to. There are at least two preliminary passes and one main pass for each route. There may be more passes if bottleneck passes are enabled.
The third and forth lines specify the power and cable factor of the cable.
The following lines list the route segment connections that are considered valid or useable to the device or panel at each end of the cable. For each segment the distance between the segment and the device or panel, the power value for the segment and the cable factor of the segment are listed.
You can change the lineweight for viewed conductors, the spacing between the conductor labels and whether layers are turned off during route viewing. For more information see How to Configure the General Settings.