TRIFLEX® Windows Version 2.3.1 Enhancements & Modifications
September 30, 2003

Modifications

1. Graphical Node Location – Previous versions of TRIFLEXâWindows used an algorithm for node location that could drastically alter the users point of view of the piping system since it rotated the camera to point at the node in question. A revised algorithm has been implemented in this release that will pan the camera to a point adjacent to the node to be found, leaving the camera rotation fixed.

2. Loading System Data File with PRV – When attempting to recall a piping system saved with a pressure relief valve, the program would exit abnormally. This error has been corrected.

3. Access2000 Database Format – In order to accommodate our Win9x customers without Microsoft Office 2000 or greater loaded, the TRIFLEXâWindows database previously defaulted to Access 97 format. While there were means available such that the Access2000 format database files could be utilized from within the program, it was not an easy task to do so. Starting with release 2.3.1, TRIFLEXâWindows will check to see if Access2000 format files can be used on the computer, and, if so, present the user with a choice of Access2000 or Access97 formats.

4. Density of B31.1 Materials – When a material is chosen from the B31.1 compatible database, the density of that material is now selected properly and displayed in the Pipe Properties tab of the Component Dialog.

5. Material Ripple – Rippling Material from the Pipe Properties tab or Temperature from the Process tab of the Component Dialog, with a B31.1 material selected, now properly sets or adjusts the physical properties on the Process tab, and the stress allowables on the Code Compliance tab for all components rippled.

6. Keyword Import of Structural Members – The keyword file used to transfer system data to the calculator, has no means of storing the type and designation of structural members as a part of a flexible joint, and therefore, when such components were imported into TRIFLEXâWindows from a keyword file, these fields were left blank. Previously the Joint Component Dialog would not allow the user to exit the dialog without having these fields populated. To populate them with other than the correct information would overwrite the cross sectional area properties, which were imported correctly. The requirement for having these fields populated is relaxed as long as there is property information available on the dialog.

7. Stress Intensification Factors for Reducers – The default stress intensification factor for reducers is properly applied to the reducer and its connecting pipe ends as a function of the particular piping code selected by the user at the time the reducer dialog is called up and the reducer is added to the piping system. As always, the user is free to override the default values at his discretion.

8. Limit Stops and Friction – An error appeared in version 2.3.0 of TRIFLEXâWindows wherein limit stops and friction restraints could not be applied to the same component. This problem has been rectified.

9. B31.1 Materials Display – With the advent of long names used for the materials derived from the B31.1 compatible database in version 2.3.0, several issues arose regarding the display. Among these are the material name shown on the output spreadsheet, on the input parameter scale when showing system materials, and on the Process tab of the component dialog where the name was truncated inappropriately. These issues have been identified and corrected.

10. Reducer Dialog Title Block – The title block on the reducer component dialog mistakenly identified the component as a ‘flange’ rather than as a ‘reducer’. This has been satisfactorily resolved.

11. Renumber and Special Reports – The renumber function as implemented from the Edit Menu or using the Ctrl+R hotkey now goes into data entered for API610, API617, Flange Loading, Rotating Equipment, and NEMA reports and modifies the node numbers for this data to correspond to the new node designations. If data has been entered through these dialogs and the user wishes to renumber the system, no longer is a manual edit necessary.