Professional Documents
Culture Documents
Solidworksrouting-Guidetosetupandbestpractises 3 PDF
Solidworksrouting-Guidetosetupandbestpractises 3 PDF
Over time files may get moved, for example to a networked location. This
document details how to change the settings in SolidWorks to match changes
in file locations and also describes the key routing options and what affect
they have on using the Routing application.
Throughout this document we will refer to different rules for Piping and
Electrical Routing. For Tubing the methods and processes are the same
methods as for Piping.
\\data\design library
Tip: when using Network drives the folders should be read-only for safety and
improved performance.
For simplicity all users should map to this directory using the same drive letter
‘X’ in this example and it is important that the relative path for each mapped
drive is the same.
Machine1- mapped drive should be:
x:\data\design library
Following these simple rules ensures that all downstream operations can be
performed easily and Routing is easily maintained. Note: If you are using
PDMWorks do NOT use mapped network drives, use UNC paths.
x:\data\design library\Routing\Electrical
After deciding on the actual location for the common Design Library and
subsequent Routing libraries we need to set the appropriate paths for the
Design Library, Routing and finally general SolidWorks.
C. Go to Routing>Electrical>Route by Drag/Drop of
Connector
The recommended location is the same folder as the route assembly it is used
with.
Once the From-To list has been imported all of its data is held in the assembly
so the original file isn’t needed. When the route assembly is saved a new
copy of the From-To file is created named <assemblyName>-fromtolist.xml.
This contains the data from the original From-To list plus some additional data
such as wire lengths. This file can be used to transfer the wire lengths back
to the schematic design system – if supported by the design system being
used. Beyond this purpose the XML file is not important to the design
process.
If the electrical design changes, the From-To list is likely to change and the
revised Excel file can be re-imported into the route assembly to help drive the
modification of the 3D route.
The part number of the standard cable, end fitting part numbers, cable OD
and length are all stored in a Microsoft Excel file. This file is best kept in the
Routing folder. It is here not in the Electrical folder because it contains both
electrical and tubing data and it holds references to both.
This file also holds relative path names, so if the Routing Folder and child
folders are moved the cable and tube definitions will still work. The same
applies for all the Standard Tubes file.
We recommend that these files are kept in this harnessing folder under the
Electrical folder at all times. If you move the Electrical folder to a new
location, move the harnessing folder too.
This greatly improves workflow and usability. However the user loses the
ability to control the naming of the files. NOTE: There are API notifications
that can be used to automatically name the files using user defined names.
These are used primarily for PDM but can be used by other applications.
Note: Workflow is smoother with this dialog not displayed. To do this enable
Auto Naming and Use default templates options.
Take great care to also use the same paths in the general SolidWorks search
paths – External references, Design Library etc. If, you do not see preview
graphics when dragging a component from the Design Library, it is almost
certainly because the assembly already references a component of the same
name but located in a different folder. You will also get a message on drop
‘…do you want to use the existing component’. If you see this, look for the
existing component in the assembly, find its path change the settings or
component location such that there is only one copy of the component
available.
Essentially, for Electrical Routing the location of the component library also
performs the same function as the Routing Library folder setting for piping &
tubing.
For electrical conduit components the same methods are used as for piping
so for these components the piping setup should be followed.
The first element of this only needs to be done once (except for an eccentric
reducer in the piping environment). Once add-to-route has been used, the
route knows about that component so it doesn’t need to be added again. If
the component has additional CPoints you can simply draw a line
Note, when creating a route if you want to use a different elbow for a
particular bend change the radius of the arc to use a different elbow.
This process allows users to choose whichever package is best suited to their
needs. It should also be noted that electrical design is typically a separate
process performed by a separate department. More direct links from
electrical to mechanical can desirable but not always preferred in a company.
This preference will vary from company to company.
NOTE: Flattened ‘harness’ drawings can not be created for Conduit routes.
Route the conduit using lines and arcs, use autoroute, route through clips etc.
Add Tee’s, pull elbows, crosses, etc the same way you would for piping.
Route the conduit using lines and arcs, use autoroute, route through clips etc.
Add Tee’s, pull elbows, crosses, etc the same way you would for piping.
Flexible type conduit segments can be routed using spline-type auto routes.
Drag/drop tees, crosses, pull elbows and additional adaptors etc, as required.
To model the wires from the open end of each adaptor use Add to route on
the other CPoint of the adaptor, or just create a line from the end of the
existing line (at the adaptors RPoint) such that it passes straight out through
the CPoint. From the end of this line, use splines or autoroute to connect to
the electrical connectors or terminals.
3.9 Harnessing
With the exception of conduit routes, all routes are considered to be
harnesses.
NOTE: Route type = Cable/wire. This type is obsolete but has been retained
for consistency to earlier releases. When creating routes/CPoints, use the
harness sub-type.
Answer: There were numerous reasons for this the primary cause if there
are no wires terminating at a connector.
Also in sw2006 the harnessing application looks in the Design Library folders
for all of its files. It looks for the file ‘terminals.xml’ under the design library. It
then looks for all of the block files in the same folder. To ensure that the files
are found add the folder …\data\design library\routing\electrical\harnessing to
your design library.
In 2007 reliance on the Design Library folders has been removed. Block files
are now located in the same folder (Electrical Folder) as the 3D connector
models and have a name based on the name of the 3D model. So, for a
connector called db9-male.sldprt the block file would be in the same folder
and would be named db9-male-hblock.slddrw.
Answer: There is no problem with this as long as the initial setup is done
correctly. Use the same process as detailed in Section1.
…\data\design library\routing
The default Pipe & Elbow files to use under this folder are:
…\data\design library\routing\piping\pipes\Pipe.sldprt.
…\data\design library\routing\piping\elbows\Elbow.sldprt.
What is stored with the assembly is the relative name of this file:
\\piping\pipes\Pipe.sldprt
\\piping\ elbows\Elbow.sldprt
You want to move the library to a network drive. Let us use the example we
have already used in Section1:
x:\data\design library
Important NOTE: Change the other Piping and SolidWorks paths too as
described in section1 including the Design Library folder and external
references paths to also use the new location.
When opening existing assemblies they will find the files in the new Design
Library not in the original design library.
Remember that you need to update the Location of the default Pipe and
Elbow files in the Route Properties PM (See Section 1.3.3) before creating
new Route assemblies.
Now, when you open a route part it will look for a pipe part using the changed
library path and the relative path to the pipe.
x:\data\design library\data\routing\piping\pipes\pipe.sldprt
It may be worth archiving the original files as it is a good idea to only have one
copy of any file available. Having multiple copies of files is a regular source of
problems.
Use File>Find references with the assembly open to check all references
have been updated.
Electrical.
The overall process is the same but with one difference. The electrical
application makes use of a component library file as described in section
1.6.3. This file contains additional information about the components and is
also used to map a given part number to a SolidWorks document. The
document names are stored in this folder as relative names so all components
should be in the same folder as the library file or a sub-folder of it
4.4 Question: If I see issues when using Routing what should I do?
Use File>Find References on an assembly and ensure all paths are correct.
Answer: If the user drops a multi-CPoint component it will drop into the active
assembly and will not start a route. To start routing RMB on a CPoint and
select Start route (select in FM or graphics window). This will create a route
assembly and start routing but the original component will remain in the
parent assembly. Carry on creating the route as normal. After exiting the
route sketch select the component in the feature manager and drag it into the
route assembly.
Answer: With the route assembly open in context of its parent. Assuming
that this relates to electrical routes and harness drawings.
Answer: If you are using PDM works with a Routing Project all users must
use a central Design Library and respective Routing folder. Using local copies
of the Routing files will not work. If users are having problems this should be
the first check that is made.
\\DesignLibraryServer\design library
This is all you need to do on the SolidWorks side. To set-up PDM works
launch the PDMWorks Workgroup 2007 VaultAdmin tool.
Note: If this is not carried out then PDMWorks will not be synchronized with
respect to the Routing Library. This will cause all the design library parts to be
revision managed.