powered by CADENAS

Manual

Manual

5.8.2.1.12.  Test project / Test directory

Before projects are transferred to the directory tree of PARTdataManager or get Status 5 under SVN Administration (see Section 6.5.4.2.4, “Level 4”), new entries or changes have to be checked for any errors. You can choose from a large number of test criteria.

The call is made in PARTproject under Project selection, in the context menu of projects (Test project) or directories (Test directory).

Test project

Test project

-> The dialog box Test projects in directory is opened.

Test projects in directory

Test projects in directory

When clicking OK the dialog box QA check is opened. There, the results of this check are summarized in a protocol. This information allows you to make the required corrections in targeted manner. Using context menu command Save protocol as... you can save the protocol.

The second column shows the row number.

The options in detail:

  • Find unused files: Finds all files which are not assigned to a project. You can either allocate such files to a project or delete them.

    [Note] Note

    Please note that supposedly unused files may possibly be used in other directories. So you should only delete files where you are quite sure that they are no longer required!

    [Tip] Tip

    The test run opens the dialog box QA check. Here, on the main line Unused files, you can find the context menu command Delete files.

    The command opens the same-named dialog box.

    By default, all items are disabled and sorted by file extension. Secondary, sorting happens by using the path name.

    With Select items you can select all elements at once. If you have selected single elements with Ctrl key or a block with shift key (like in Windows) before and then check Select items, only the ones selected before are marked.

    Or use the option the other way round: First select everything, then select single elements and finally uncheck Select items again.

  • Calculate geometry: This function builds up the attributes (table rows) of all geometries (*.3db drawing files) on a trial basis. Attributes which lead to an “impossible” structure, such as a negative value for width across flats, are logged as an error. The calculation process may take a very long time (depending on catalog size).

  • Test geometry on CAD compatibility: This checks the component geometry for geometrical integrity.

    Check geometry

    Select the settings for Mechanical engineering or Architecture.

  • Test value ranges:

    • As many value range combinations as possible are gone over and it is checked whether the 3D geometry can be build correctly.

    • If Test order number for uniqueness is activated in addition, it is also checked whether there are double order number among the tested variants.

    • If there is a ReverseConfig for a project, then it is checked whether the order number can be found via the ReverseConfig.

    • If there is no ReverseConfig, as of SP5 it is checked, whether the option Index order numbers dependent on value ranges is activated.

    Determine the maximum test time in minutes.

    Details on Test value ranges can be found under Auflösen von Wertebereichen: Konfiguration und Testing.

  • Test standard part identifier: The standard part identifier, e.g. ’Hexagon nut DIN 1587 $ NENN.’(displayed in PARTdataManager, in the tab of the docking window of the 3D view), which you have entered in PARTdesigner (Identification data) may, under certain circumstances, be incomplete or incorrect. For example, if column values (representing an element of the standard part identifier) prompted in certain rows are not present.

    Standard name in PARTproject when selecting the tab file

    Standard name in PARTproject when selecting the tab file

    Standard name in PARTdataManager, in the tab of the docking window "3D view"

    Standard name in PARTdataManager, in the tab of the docking window "3D view"

  • Test standard part identifier for uniqueness: ...Compares all Standard names, which may occur as the result of the various attributes (rows). If a Standard name (NB) occurs more than once, it is not unique. --> You must adapt the Standard name (NB) in a way that it is always unique!

  • Test order number for uniqueness: The option Test order number for uniqueness also contains a test for ReverseScripts. For this the option Test value ranges has to be activated in addition. See above.

    Details on this can be found under Auflösen von Wertebereichen: Konfiguration und Testing.

  • Test short name: During the export of parts from PARTsolutions to different CAD systems, it is normal for the Standard name (NB) to be adopted as part name. As certain CAD systems have a string limit for the part name, alternatively the Short name is applied.

    PARTproject -> Edit project -> tabbed page General -> Short name (max. 16 characters)

    PARTproject -> Edit project -> tabbed page General -> Short name (max. 16 characters)

    The Short name is a "reduced" (preferably as short as possible) version of theStandard Name (NB), limited to the - maximum length (max. 16 characters according to CAD!).

    If the string of a Short name is larger than this limit, an entry is created in the log file.

  • Test short name based on uniqueness: The Short name must also be unique, as must the Standard name (NB).

  • Test name of project files for uniqueness: The name of every *.prj file must also be unique since, otherwise, an assembly may use “the wrong one” if there are two identically named *.prj files (with different content).

  • Test standard numbers for uniqueness: This excludes standard numbers occurring more than once.

  • Find unused variables in 3db files: Checks all *.3db files belonging to the selected directory in order to establish whether they contain variables which are not used. The variables found may be identified in the log and then deleted if applicable.

  • Delete unused variables in 3db files: If this option is checked, the variables found with Find unused variables in 3db files are deleted directly.

    [Important] Important

    What counts for files, also counts for variables. Please remember that possibly unused variables may be linked to assemblies. Therefore only delete variables where you are absolutely sure that they are no longer needed.

  • Test bitmaps: PARTproject sets a limit for the bitmaps used as a preview. This limit is 100 x 100 pixels and 256 colors. Images which exceed this limit are recorded in the log. The file size (and, thus, the loading time) of the bitmap can be reduced accordingly using conventional image editing programs.

  • Test already tested projects:

  • Test CAD formats:

  • Check script syntax:

  • Create protocol: The test run log may record either all project rows checked (Log file) or only the wrong project rows (Error file). Check the Create protocol option and enter the required log file location, including the extension (e.g. *.txt) in the Log file or. Error file field.

  • Create metafiles: Creates a file in PARTsolutions export format *.ps3. This file can be imported in the relevant CAD system using the corresponding menu command of the PARTsolutions interface. The Destination directory field (file location of the ps3 file) can be activated by checking the Create metafiles option.

  • Maximum time for one row: ..., that should be permitted for the buildup of a single *.3db part geometry (per model). A limit of 5 minutes is recommended. If the limit is exceeded an entry in the log file follows. Check the relevant geometries and if so, make the necessary corrections in their creation.

By clicking OK the selected test criteria will be used and the test run will be started.

[Note] Note

The test run for extensive directories may take several hours under certain circumstances. It is advisable to run the test either overnight or on a separate computer.

Once the test run is finished, the dialog box QA check is displayed. Correct the shown warnings and errors.

QA check dialog box

QA check dialog box