How to Anaylse Iso Errors Revision2

How to… Analyze Isogen Drawings Error in Smart3D

[TYPE OF] Document December 3, 2015

© 2015 Intergraph Corporation. All rights reserved. The content of this document is proprietary work of Intergraph Corporation, or relevant third parties, and is protected by copyright law and international treaty. Any use, duplication, distribution or disclosure of such, other than as specified herein, is unauthorized and in violation of applicable copyright law and international treaty. All rights in content or materials bearing copyright notice or oth er attribution of third party rights are reserved to the relevant third party. United States Government license rights are limited to those mandatory rights identified in DFARS 252.227 -7015(b). Intergraph may make improvements and/or changes in the product s and/or the programs described in this publication at any time without notice. Any content or materials supplied hereunder are provided "as is ," without warranty of any kind, either expressed or implied, including, but not limited to, any implied warranties of merchantability, fitness for a particular purpose, or against infringement. In no event shall Intergraph be liable for any damages arising out of, or in connection with the downloading, viewing, use, duplication, distribution or disclosure of any content or material published by Intergraph, including but not limited to any direct, indirect, incidental, special, punitive or consequential damages, or loss or corruption of data. Some jurisdictions do not allow the exclusions or limitations set f orth above, so the above may not apply to you. The exclusions or limitations shall apply in all jurisdictions to the maximum extent allowed by law.

Intergraph Corporation 170 Graphics Drive Madison, AL 35758 Phone: +1.256.730.2000 Toll Free USA: +1.800.345.4856 Fax: +256.730.2048

Contents

Contents Introduction ................................................................................................................... 2 Getting Started .............................................................................................................. 2 Checking Setup ............................................................................................................. 3 Investigating Model errors ........................................................................................... 4 Investigating Isogen Errors .......................................................................................... 6 Common Benign Warnings .............................................................................................................. 7 Options Override..................................................................................................................................... 8 Taking it further ....................................................................................................................................... 8

Appendix: IsoDebugFiles ............................................................................................. 9 Appendix: Isogen Message File ................................................................................. 10 Appendix: Personal ISOGEN return values .............................................................. 11

December 3, 2015

Introduction

Introduction Sometimes piping isometric drawing extraction fails in Smart3D. This document should help you find where the problem lies. Drawing isometric extraction has 3 basic steps: 1. Extract data from the model and build PCF 2. Run Isogen with PCF 3. Post-processing and storage of results The majority of errors are either 1 or 2. The PCF (Piping Component File) is a text-based file that is passed to Isogen. The PCF provides a useful checkpoint between the model extraction and Isogen drawing generation. If the PCF is faulty then it is either a model extraction issue, or a problem in the PCF generation code. If the PCF is good then and the drawing fails it is a problem in Isogen which may be possible to work around by altering the style settings. If the drawing is produced ok, but there is still an error something is wrong in either the postprocessing or storing the data back into the Smart3D database.

Getting Started Use the flow chart below to decide how far the Drawing Update got before it failed.

December 3, 2015

2

ISO document size becomes 0KB because of error.

Does the message file exist? How to find it? Look in the View Extraction Data dialog. Select LOG under REPORTS\Process File, and the message file is displayed in the right-hand pane. This means Isogen started. If not something has gone wrong while preparing the PCF for the Isogen run. See Investigating Model errors. Review the message file. Did Isogen run through to produce drawings? See structure of Message File Appendix if you are not sure. If there is a failure in the Drawing generation, the next step is to look into Isogen errors. If Isogen ran open the drawings. If they look bad study the message file for clues. Is there an error or a significant warning? See where has the drawing has gone wrong, and check if there is anything unusual in the log file. If the drawings are ok but there is a failure reported, something has gone wrong after this. This could be the PipelineList Report, the Neutral File, or storing the results back into the database. See the Drawings.log for clues. You can see the Drawings log by Right clicking the drawing and selecting “View Log”. Typically this shows you the last error at the bottom of the log file. This is not normally the most important error. You should scan up the file to find the first error, as this gives a better clue as to what has gone wrong. Ignore any information items in the first analysis.

ISO document size becomes 0KB because of error. Sometimes, a strange/rare problem is observed that “though the ISO is seen generated, size was seen Zero in D&R task, and also when we saved into SHA file or in IsoDebugfiles”. This could be due to failure in blobbing of the drawing, but not reported in Log or MES files. This could be resolved by updating the drawing again or deleting the drawings and run the query.

Checking Setup Some standard checks should be made when setting Isometrics, mostly to do with the location of files. 1. All DLLs (Custom Symbols and VB labels) in symbol share and/or local paths are of latest versions and located, registered/updated into configuration file. 2. All DetailSketch files are located in UNC path (Symbol Share) instead of local path.. 3. All enabled report options are set to respective Iso options and their templates are located in UNC path (Symbol Share). 4. All enabled Auxiliary Programs, ASC files, DataFiles, ReportFiles, SummaryFile, etc are located in UNC path (Symbol Share). 5. All enabled label options are mapped to correct labels and correct data is written to PCF. 6. If you use custom Symbol KEY ASCII files the path should be correct, and these should be supplied when filing a Service Request.

December 3, 2015

3

Investigating Model errors

Investigating Model errors Listed below are a series of common model errors 1. Multiple instances modeled at the same location In some specific scenarios, even though there are no disconnections the isometrics used to fail. Upon investigating it was found that there are two components modeled at the same location. This happens with WBS isometrics.

2. Catalog updates are not in Sync with the model In some situations, the catalog is updated and some of the components are deleted. If the model is not updated it fails to update the drawing. 3. Missing labels Isometric fails to update if the configured labels pointed in the Isometric options are not available or deleted from the symbol share. Also in some situations even if the labels are present it may be customized in VB, if the corresponding dll files are not registered or mapped using the custom symbols then also the isometric fails to update. 4. Changing the ownerships of the welds In some specific configurations the default ownership has to be altered from component to pipe, then only the isometric is getting extracted. For example in the image below, the ownership of the weld was originally set to component. After altering the ownership to Pipe and changing it to field weld extracted the isometric.

December 3, 2015

4

Investigating Model errors

5. Incorrect placement of split points: In placing control points to break isometrics in specific locations on the line, if the control points of the sub type piping mfg limit point are not placed at the appropriate location(s) than it would cause the ISO failure.

6. Incorrect catalog definition for symbol. Incorrect symbol definition may result in bad geometry data in PCF which would cause double back error when creating ISOs. In the following example the center location lies outside of start and end. In this case the following parameters of the symbol should be checked. 1. Face1 to center 2. Face2 to center 3. Face3 to center

7. Placement of Taps at the same coordinates. Sometimes users accidently place Tap points at the same location which causes ISO failure. It is difficult to make out in the model but it will be clearly seen the PCF as seen below:

December 3, 2015

5

Investigating Isogen Errors

Investigating Isogen Errors The place to look if the Isogen run fails is the Message (.MES) file, and is available in the View Extraction dialog, and also in the IsoDebugFiles. To view the Message file right click the drawing and select “View Extraction Data”. Then select LOG under REPORTS\Process File, and the message file is displayed in the right-hand pane. This is Personal Isogen’s log file. There are 2 main sections. First Idfgen which translates the PCF to an IDF. This uses the coordinates of the all the components in the PCF to determine the correct order for Isogen, and also makes sure that the PCF as a whole connects together. Second there is the Isogen section where the drawing is laid out. In both sections there can be warning or errors. Most warnings are benign and can be ignored. Errors are more serious and cause the drawing to fail. Errors less than 2000 are Isogen errors; those greater than 2000 are Idfgen errors. Both errors and warnings try to identify the component that has cause the issue. They do this by using showing both the 3D coordinate and the UCI (unique component identifier) of the problem component. This can be used to identify the component in the model. Any error which identifies a 3D coordinate should be investigated. Most common error is Disconnected Segments The line is disconnected due to a missing connection. It is hard to find as there is no proper open end i.e., visible. The two possible ways to find the disconnections are explained below.

a. Isometric Trouble Shooting Utility (Automation Tool Kit): b. Using the message file which shows the coordinates of the disconnected ends as multiple START POSITIONS. Using these coordinates we can easily find out as shown in the snap below.

December 3, 2015

6

Investigating Isogen Errors

The message file also shows which groups IDFGEN has sorted the components into by printing a number such P1, P2, P3 etc. at the right side of a listing of the components. This can help find the disconnection. A list of other common errors in the message file are shown below:

Error Number

Description

Possible Resolution

2024

Serious disconnection

A genuine disconnection in the model. Try setting SortInputParts into connected sections. This should show where the issue is

1999

Drawing layout failed.

Isogen has failed to converge. This often happens if the drawing is too complicated. You can try simplifying the drawing by placing Split points, or changing the drawing boundaries. Sometime suppressing some unwatend messages from the drawing can help.

1041

User defined Fitting Spindle Key ???? not found

Check if you are using a redefined symbols (.ASC) file. There could be a problem with this file. This is listed under Supplementary.DataFiles

3102

Tee end without tee start

The main cause is Isogen trying to split the drawing in a bad location. Try making the backing sheet bigger and forcing the drawing on 1 sheet to see if this resolves the problem.

A fuller list of Personal Isogen errors is shown in the Personal Isogen Errors Appendix.

Common Benign Warnings There are some warning messages often shown in the message file from Smart3D which can often be ignored. This are: SUPPORT-TYPE not recognised. Completely benign. BOLT-ITEM-DESCRIPTION not recognised on additional items. Benign. FITTING SHAPE not found. Can be affect the drawing quality.

December 3, 2015

7

Investigating Isogen Errors

Options Override Sometimes you want to test changing the extraction options for just one line. You can do this using the Option Override mechanism, which you can access on Right Click. You need to know the name of option that you want change. When you override on option the overridden option is stored against a pipeline and used when that line is extracted again. Override options are a powerful way of working around problems on a line by line basis.

Taking it further If you still cannot determine the issue, then file a Service Request. You should always supply IsoDebugFiles, as these will often by requested to investigate an issue.

December 3, 2015

8

Appendix: IsoDebugFiles

Appendix: IsoDebugFiles You can turn on IsoDebugFiles which instructs Smart3D to leave the files used while running Isogen. Normally they are tidied up. You turn on IsoDebugFiles by setting the registry key \HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intergraph\Applications\Environment\Drawin gs\IsoDebugFiles\Save to Yes. This preserves temporary area on disk. You can find it in your temp folder under the IsoDebugFiles folder. Everything under here is useful for a Support Engineer. You a folder for each pipeline. Under here is a folder with the date/time stamp for each time that the isometric was extracted.

The full structure is shown above. The drawings log is in the folder with the data/time. Everything else under here maps into the Personal Isogen project structure. The project is the plant. The style name in this case is Iso_Pipeline. The Inputs folder contains the PCF, an also the temporary IDF. The Drawings folder contains the output drawing, and also the POD file. The Messages folder holds the Isogen log file, or message file. The Reports folder holds any Isogen Reports generated as part of the run, which could include the neutral file, or the repeatability file which is used for Change Management. The Isogen Logs folder holds a series of temporary Isogen internal log files, which are normally written to the temp folder and deleted.

December 3, 2015

9

Appendix: Isogen Message File

Appendix: Isogen Message File The Isogen message file is the Personal Isogen log file. There are 2 phases in Personal Isogen. 1. Idfgen translates the PCF in an ordered set of components in a temporary idf, called idftrans.idf. 2. Isogen itself runs on this idf. You can see this progress in the Message file. Isogen is split into ISODAT and ISOPLOT. ISODAT handles all the data issues, such dealing with option switches, deciding what text will plotted, and generating report files. ISOPLOT actually lays out the Drawing.

A sample Message file is shown above. First the Personal Isogen version is stated. Then IDFGEN runs, stating the build number. The statement “ALL COMPONENT CONNECTED” indicates successful processing. Multiple ‘passes’ made attempting to connect the components typically means a disconnection. Then Isogen version is stated:12.0.1.103 in this example. The Isogen run is split into ISODAT, followed by ISOPLOT. Finally there is a message indicating the output produced with the text “THE FOLLOWING DRAWINGS ARE IN PLOTFILE ….” followed by a list of all the sheets. Errors and warnings can occur in IDFGEN, ISODAT or ISOPLOT, and these will appear in the appropriate section of the message file. IDFGEN errors are typically some problem with connecting the components together. ISODAT errors tend to be bad data in the input file. ISOPLOT errors tend to be where Isogen struggles to lay out the drawing for some reason. Sometimes placing drawing split points can help. If any of the errors in the Message file include either 3D coordinate or a Unique Component Identifier (UCI) then you should study the relevant area in detail.

December 3, 2015

10

Appendix: Personal ISOGEN return values

Appendix: Personal ISOGEN return values Most errors Personal Isogen errors refer to reading the Isogen.fls in the style folder or accessing the temp folder. Personal Isogen has its own log file pisogen.log in the Temp folder.

Value

Issue

Possible cause/resolution

-1001

Failed to create the specified Pre/Post Processor

CreateProcess (Windows function) for the external processor has failed for some reason.

-1002

Pre/Post crashed

has

Exception raised trying to run external process. Check the programs defined as pre/post processors in Isogen.fls.

-1003

Pre/Post processor has timed out and the external process has been killed

External program exceeded the timeout and was terminated. Has it hung, or is it just taking too long?

-1004

Pre/Post processor has timed out but the external process cannot be terminated (and is therefore still running)

Check the programs defined as pre/post processors in Isogen.fls. The process is probably still running. Requires investigation of external process to determine why.

-1

Error in Isogen data.

Check message file for more details.

-2

Isogen dll failed to load

Possible installation problem, missing dependent file etc. OR crash occurred during execution, which has been trapped by the error handler.

-3

Isogen thread failed to finish

Possible execution loop which has been terminated by Personal Isogen, e.g. for exceeding a time limit.

0

Iso created successfully

1

Personal ISOGEN cannot find the isometric directory specified.

Check path exists and is writable. The isometric directory is listed in pisogen.log (on users temp area) as Pisogen Root.

2

Invalid Style for this project.

The specified Style cannot be found under the specified project. Check path of style. Under the Project folder there should be style folder, containing the isogen.fls

3

Specified Project not found.

The specified project cannot be found under the isometric directory. Check the path of the project folder. The project name is in Pisogen.log

4

IDFGEN handshake failed.

The handshake passed to the idfdll.dll has not been verified.

Processor

Note that a number of other “unexpected” failures have been found to generate this error. It could be a timing issue. 5

Could not access specified PCF in TEMFILES.

December 3, 2015

PCF is usually copied to user’s temp area, but this has failed for some reason. Check PCF exists and can be copied to temp.

11

Appendix: Personal ISOGEN return values

6

ISOGEN DLL failed to establish current directory

Windows function call _tgetcwd problem

7

ISOGEN DLL failed to change directory

Problem switching the temporary folder

8

The handshake passed to the pisodll.dll has not been verified.

A number of other “unexpected” failures have been found to generate this error. It could be a timing issue.

9

Personal ISOGEN failed to produce a valid drawing.

View message file for details as there are many possible causes

10

ISOGEN DLL failed to restore working directory

Resetting working directory failed (function _chdir)

11

IDFGEN DLL failed to establish current directory

Check access to the style and user’s temp folder.

12

IDFGEN DLL failed to change directory

Check access to the style and user’s temp folder.

13

IDFGEN did not complete successfully.

View message file for details. One common cause is that the components in the PCF do not form a connected system

14

IDFGEN DLL failed to restore working directory

Check access to the style and user’s temp folder.

15

IDFGEN could not delete PISOGEN\PROGRAMS\FO R036.DAT from a previous run.

Check for this FOR036.DAT in the user’s temp area

16

IDFGEN was unable to create ISOGEN.IDX file. Error opening isogen.idx

IDX file is obsolete under Personal Isogen (only relevant to stand-alone running of IDFGEN)

Error closing isogen.idx 17

IDFGEN was unable to copy ISOGEN.FLS to the PROGRAMS directory

Numerous causes (e.g. Error allocating memory to store a line, Zero line length encountered, Error opening source isogen.fls (in specified project\isotype), Error opening target isogen.fls (in pisogen\programs), Error closing source isogen.fls (in specified project\isotype), Error closing target isogen.fls (in pisogen\programs)) See pisogen.log for full details.

18 19

Obsolete. Personal ISOGEN handshake failed.

December 3, 2015

The handshake passed to the pisogen.dll has not been verified. A number of other “unexpected” failures have been found to generate this error. It could be a timing issue.

12

Appendix: Personal ISOGEN return values

20

Unknown Error in Personal ISOGEN.

An unexpected path through the program has occurred – a default/catch-all value which could be due to almost anything, and which is useful only in as much as it prevents a crash.

21

PISOGEN DLL could not find Current Working Directory. The current directory cannot be identified.

Windows function call _tgetcwd problem

22

PISOGEN DLL could not Change Directory to \PISOGEN\PROGRAMS.

Likely to be a problem accessing user’s temp folder

23

ISOGEN failed to write banner to message file.

May be an error opening/closing isogen.fls file; Or an error opening/closing the message file; Or the message file entry may be absent from the isogen.fls file; Or there may be a problem with the path to the message file, as specified in the Isogen.fls file.

24

PISOGEN DLL has been unable to restore current working directory.

Resetting working directory failed (function _chdir)

25

Error around accessing igen.fls or isogen.fls.

Multiple causes (Error opening i-gen.fls for reading, Error opening isogen.fls for writing, Error opening options file specified in i-gen.fls, Error closing options file specified in i-gen.fls, Error opening i-gen.opl for writing, Error closing i-gen.opl, Error closing i-gen.fls, Error closing isogen.fls I-gen was a limited-functionality mode (now obsolete). Most likely there is a problem accessing i-gen.fls in the style folder.

26

Problem with the specified isometric root directory

Check existence and access of Isometric Directory, which is the Root listed in pisogen.log.

27

Problem setting the current isometric root directory

Check existence and access of Isometric Directory, which is the Root listed in pisogen.log.

28

Invalid file extension

Check the input file is a PCF, PDF or DAT file.

29

IDFGEN called with PCF

Check input file is PCF

30

Warning occurred creating a POD (intermediate) file

Check log files (message file, pisogen.log)

31

Error occurred creating a POD (intermediate) file.

Error occurred during “pass 1” when the input IDF file is preprocessed

32

Error occurred creating a POD (intermediate) file.

Error occurred during “pass 2” when the POD file is being created from Isogen data

December 3, 2015

13

Appendix: Personal ISOGEN return values

33

Failed to load PODGRAPHICS DLL

Used in the creation of graphics output files such as DWG,IGR and SHA.

34

PODGRAPHICS process failed –

A graphics specific process has failed – e.g. user requested IGR/SHA output but SmartSketch/Shape2D is not installed

41

Cannot get path to system temp directory

Check user’s temporary path. Windows function GetTempPath failed.

42

System temp directory does not exist

Cannot find specified temp path.

43

Unable to set bore units to those specified in the input file

Often a combination of metric bores and imperial dimensions causes this. Check option switch 41.

44

Unable to perform macro substitution in style ISOGEN.FLS

Check the Isogen.fls and see what macros are defined. Macros are contained in $...$. Check user can write to Isogen.fls.

45

Unable to restore original style ISOGEN.FLS

Related to macro substitution. Check the user can edit the isogen.fls in the style folder.

50

Project disk is full – unable to create new output files

Check you have plenty of available space on the machine that you are using to create

51

File containing temp directory is full – unable to process files

Check space on the Drive containing the user’s temp folder.

52

Unable to extract the Bore Units from the incoming PCF, IDF or DAT file

Problem reading either the Option block of IDF, or header block of PCF

53

Unable to Copy a File (either PCF, IDF, DAT or FLS)

See pisogen.log (in user’s temp folder) for details of exact File Name and Path concerned

1000

Expected files missing in Style

Is the Isogen.fls present in the style folder. Are the input files present (in particular the Options file)?

1001

Requested units combination is inconsistent

Probably means a combination of metric bore and imperial co-ordinates

1002

Invalid drawing format requested

Strange value in Option Switch 71.

1003

Problem deleting an ISOGEN message file

Check whether the user can edit the message file list in Isogen.fls. Also check STDOUT.TXT in temp area. A process locking this file could cause this error.

1004

Line in the options file has invalid format

Check the .opl file in the style, listed in Isogen.fls

1005

Too many switches in the options file

Check the .opl file in the style, listed in Isogen.fls

1006

Too few switches in the options files

Check the .opl file in the style, listed in Isogen.fls

December 3, 2015

14

Appendix: Personal ISOGEN return values

1007

MicroStation design file output requested but MS_EXE environment variable is not defined

Set MS_EXE environment variable if generating DGN. You need the Microstation executable to drive creating DGN output.

1008

MicroStation design file output requested but MicroStation not installed

Currently you need Microstation to generate the DGN graphics.

1009

MS_EXE environment variable does not end with a \

Check Path of MS_EXE environment variable if generating DGN

1010

ISOGEN.FLS missing in Style

Check in style folder for Isogen.fls

1011

Options file missing specified in ISOGEN.FLS is missing

Look in Isogen.fls (location specified in Pisogen.log). Check that the .OPL file referenced is present.

Warning messages 1999

Isogen has returned a FAIL for one or more drawings in the set.

This means Isogen has been unable to layout the drawing successfully. Review failed drawing and message file for clues. Either this is bad data, bad options or too much data. Splitting the drawing can help identify the problem, as you can see where the error is occurring if you move the split points.

2001

Inconsistent units combination

Probably imperial co-ordinates and metric bores

2022

IDFGEN has detected disconnected pipeline - A “Multi-Pass” or “Hard Disconnect”

A “Multi-Pass” or “Hard Disconnect” has occurred when a gap of greater than 8mm has been encountered i.e. more than one pipeline is output in the single idf. Drawings will be created for each separate pipeline. Viewing the listing in the message file can help determine where the break is by seeing which pipeline set, P1, P2, etc. each component is assigned to.

2023

IDFGEN has detected disconnected pipeline – A “Floating Pass

A “Floating Pass” has occurred in which only out-of-line items (such as Bolts, Supports and other positional items) are “left over” from the previous pass – the rest of the pipeline is still output to the idf. This does not fail the drawing, but the “left over” items are lost.

2024

IDFGEN has detected disconnected pipeline – A “Soft Disconnect”

December 3, 2015

A “Soft Disconnect” has occurred in which gaps greater than the specified tolerance (but less than 8mm) have been encountered – a single pipeline is output to the idf, but containing positioned warning messages which can be output or suppressed on the drawing depending on switch setting. This does not fail the drawing.

15