Skip to main content
Engineering design automation since 2007 +91 40-4528 7403 sales@fdestech.com

Guide · PLS-POLE 21 · 5 minutes

How to Export Results XML from PLS-POLE

Every FDES tool that reads analysis results uses the XML post-processor file that PLS-POLE writes after a run. PLS documents this file as the supported way to read results from outside the program. It is switched off by default, so here is how to turn it on and where to find it.

1. Turn on the XML post-processor file

  1. Open the model in PLS-POLE and go to General > Post Processor Options.
  2. Under Post Processor Options select Write XML post processor file. Do not select the "run post processor" options; nothing needs to be launched.
  3. Under Post Processor File Name Options choose <PLS_TEMP>\<MODEL_NAME>.[csv|xml]. The file is then named after the model. If you prefer a fixed folder, choose "Name selected to right" and type a path.
  4. Under Post Processor Unit System keep the units you work in. The FDES tools read the units from the file and show them next to every value.
  5. Click OK.
PLS-POLE Post Processor Options dialog with Write XML post processor file selected, the file name option PLS_TEMP MODEL_NAME csv or xml selected, and the US unit system selected
General > Post Processor Options in PLS-POLE 21.01 with the three settings selected.

2. Run the analysis

  1. Run Model > Check first if the model changed.
  2. Run the analysis with Model > Run. The XML is written when the analysis finishes; the usual report windows open as normal.
  3. Save the model if you want the post-processor setting kept for next time. The setting is stored with the model.

3. Find the file

  1. Open File > Preferences. Row 2 of the file table, Temporary Directory, is the <PLS_TEMP> folder. On most installations it is C:\Users\<you>\AppData\Roaming\PLS\temp.
  2. Open that folder in Windows Explorer. The results file is <model name>.xml, for example spoex5.xml for the model spoex5.pol.
  3. Check the size. A file of 0 bytes means the run did not complete or the option was changed after the run; run the analysis again.
PLS-POLE Preferences file table with row 2 Temporary Directory highlighted and row 18 Steel Pole Library showing the path of the spobasic.spp library
File > Preferences: row 2 is the temporary directory where the XML is written; row 18 shows the steel pole library the current project uses.

Where the steel pole library (.spp) is

The library the model uses is shown in two places: the title bar of Components > Steel Pole, and row 18, Steel Pole Library, of the same File > Preferences table under "Setting for Project". The PLS-POLE examples use spobasic.spp in C:\Users\Public\Documents\PLS\pls_pole\examples\steel. Manufacturer libraries downloaded from Power Line Systems are usually kept in a project or company folder; the Preferences row tells you which one the open model points at.

How to save the load file (.lca)

Vector loads live in a separate .lca file referenced by the model. Open Loads > Vector Loads (LCA File); the dialog shows the file the model uses and lets you Save As a copy. If the model was loaded from PLS-CADD, the loads may come from a .lic wire load file instead; the Vector Loads dialog is then greyed out and the FDES LCA tools do not apply.

Which tools need which file

ToolRequiredOptional
Results Summaryresults .xml.pol, .spp, .lca for cross-file checks
Revision Comparetwo results .xml.pol, .spp, .lca per revision
Foundation Reactionsresults .xml
Fabrication Checkresults .xml
LCA Builder and Validator.lca to validate, or nothing to build.pol for label checks and label import
Steel Pole Library Explorernothing; built-in manufacturer librariesyour own .spp files

Same XML, finished drawings

That XML Is All FDES Needs to Draw the Pole.

FDES automation reads the same results file and produces the 3D model, fabrication drawings and BOM on Inventor, AutoCAD or SolidWorks, to your templates and part numbering.

  • PLS-POLE XML to 3D model, drawings and BOM
  • Inventor, AutoCAD, SolidWorks and more
  • Your templates, part numbers and standards
  • Free automation audit, no commitment