You are currently reviewing an older revision of this page.
Our PlantSpace database does not return properly scaled elements and the settings cannot be changed within the same database. This is characterized by custom components such as hoses, nozzles and branch pipes that we use from a contractor's database that do not match the structure of the PlantSpace standard settings file. How can we implement the database with these new items? AutoIsogen generates the *.pcf file but does not return an output *.dgn file. The steps we currently use to work around this is to to generate a *.jsm file from PlantSpace, process through AutoIsogen to get the *.pcf file, and then create a *.dwg file using a third-party application.
AutoIsogen is not able to properly create the DGN file because the models include components that are not defined in the AutoIsogen interface (Iso.lib). There are bound to be issues using these type of custom components in a standard Isometrics generation environment, for example:
1) The components created with bad dimensions are apparently not using the dimensions stored in the database. It seems likely that the bad values are inserted in: PROJECT_CONFIG table and loaded using either prjcfg_m.dat (metric) or prjcfg_e.dat (imperial). The same definition must also exist in the seed file. More information can be found on page 2-14 of PlantSpace Design Series manual.
2) The contractor's database contains specific elements that are not managed in a standard PlantSpace environment, and also appear to be customized in a way that does not rely on standard PlantSpace isometrics generation. The contractor uses JSM files generated by PlantSpace and then generates a text file (as a report) to be used as an input within a custom application for material management and Iso generation. It is this custom environment that is not designed to work within a standard PlantSpace environment. The PlantSpace database and configuration may be customized to suit but this typically requires specific training.