Surface and solid data can be impor...

Surface and solid data can be imported from HP PE/ME30 and exchanged with schemes supporting the IGES, STEP, and ACIS formats. Imported data coexists with and can be manipulated like native data.

HP PE/SolidDesigner supports the coexistence of surface data with solid data and provides the ability to import and modify surface and solid design data from a variety of CAD arrangements Backward compatibility with HP PE/ME30 keep sounds the investment of existing HP customers. Using improved IGES (Initial Graphics Exchange Standard) import capability, the couple surface and wireframe data can be imported. Surface data and solid data can also be imported and exported using the grade (Standard for the Exchange of issue Model Data) format. Once imported, this data can coexist with HP PE/SolidDesigner solid data. It can be loaded, saved, positioned, attached to, managed as part and assembly compositions deleted, and used to create solids. Attributes of that kind as color can be modified. If the station of surfaces is closed, HP PE/SolidDesigner will create a solid from those surfaces automatically.

HP PE/SolidDesigner 30 also allows solid parts and assemblies to be exported to ACIS-based rules using Version 1.5 of the ACIS[R] SAT file format. This feature provides a direct link to other ACIS-based applications.

From PE/ME30 to PE/SolidDesigner

HP PE/ME30 is a 3D computer-aided design (CAD) scheme based on the Romulus kernel.[dagger] To guard the investment of existing customers it was required that the transition from HP PE/ME30 to HP PE/SolidDesigner be as polished as possible. Therefore, an HP PE/ME30 file import processor is a integral constituent of HP PE/SolidDesiger.

In HP PE/ME30 3D thing perceiveds are built from analytic surfaces like cylinders, cone spheres, planes, and toruses. The intersections of these surfaces can be depicted as explicit analytic curves of the like kind as straight lines, circles, and ellipses, or implicitly according to describing the surfaces involved and providing an approximation of the intersecting arc. Parabolic and hyperbolic intersections are showed implicitly.

HP PE/ME30 Native File Organization

HP PE/ME30 supports the Romulus textual transmit format. The transmit file is not intended to be read by way of humans but the general configuration can be examined. The file contains barely printable characters, and real values are portrayed as text strings. The replete format of a transmit file consists of six different sections. These will be described using the example of a single cylinder positioned at the origin of HP PE/ME30's coordinate scheme with base circle radius 10 and height 20

The first section, the header section, describes the environment, the machine emblem the user login of the file creator, and the time and date when the pattern was created.

*AOS * Machine mark HP-UX * Transmitted by user_xyz upon 27-May-94 at 13-06

The inferior section contains index and counting information related to the schema described in the third section. The schema defines the data textures used to represent the external realitys It consists of a collection of record definitions. The following is an example of a record definition:

[ILLUSTRATION OMITTED]

In the secondary section of the transmit file the number of record adumbrations the numbers of record instances and exclusive right instances, the name of the schema, and its version and update number are supplied. The record instances and attribute instances contain the concrete data describing the original The semantics and the order of succession of data entities have to conform to the format specified by dint of the corresponding record definition and one's own definition entities.

The information in the cylinder example file says that 11 instances of record definitions are supplied to describe the schema for the instance of the cylinder. For the actual butt; goal 23 record instances built gone out of 115 property instances are used.

1 1 23 115 ROMDSCHMA 74 16

The third section, the schema section, contains the definition of the data mode of buildings used to represent the prototype This section consists of the subset of record definitions from the HP PE/ME30 internal data building schema that are needed to show the model. The schema sections of files representing different protoplasts will be different. The schema section for the example cylinder is:

BY 19 UP 4 -1 SE 3 - 1 TX 5 -36 Fl 4 -6 Cl 4 -12 Pl 4 -8 Gl 4 -1 Sl 4 -3 Tl 4 -3 RA 21 RN 21 Zl 4 -2 FN 1 1 CN 1 1 PN 1 1 TN 1 1 SN 1 1 ZN 1 1 NM 1 1 SH 2 F 3 -1 BK 3 1 FA 8 UP 4 -1 AK 3 -1 RV 1 1 SF 3 1 SX 2 1 VR 3 -1 HA 2 - 3 SL 3 1 VR 4 PT 3 1 BE 3 1 BV 3 1 FE 3 1 ed 2 CU 3 1 RV 1 1 CU 3 UP 4 -1 AK 3 -1 TR 3 1 TR 6 UP 4 -1 AK 3 -1 BK 3 1 EQ 2 -7 T 32 TY 1 1 PT 4 UP 4 -1 AK 3 -1 CO 2 -3 GP 3 1 GP 5 UP 4 -1 AK3 -1 BK 3 1 CO 2 -3 PX 3 1 SF 7 UP -1 SD 3 -3 AK 3 -1 BK 3 1 EQ 2 -7 SU 3 -5 TY 1 1 UA 3 OW 3 1 CL 1 1 ll 1*1

The fourth section contains, for each record model defined in the schema section, the number of data existences used for the transmission of the gauge The sequence of numbers is identical to the succession of record definitions used in the schema section. In the cylinder example, the intent consists of one body built of the same shell built of three faces. Four vertices, four coedge sum of two units curve geometries, two edges, sum of two units points with two geometric point definitions, three surfaces, and common attribute are needed to take the part of the cylinder object. The file satisfieds are: