SAP2000 Version

Transcription

1 SAP2000 Version Copyright Computers and Structures, Inc., 2009 Release Date: SAP2000 Version is an update to Version and is available as a full installation from DVD or from the ftp, and also from the ftp as a patch for V or V PLEASE READ THIS FILE! It contains important information that is more current than what is in the Manuals. Contents 1. Installation Instructions for SAP2000 Version Installation Instructions for License Manager File Compatibility with Older Versions 4. Updating Older Versions 12.x.x Using the Patch from the ftp 5. Significant Changes from Version New Features in SAP2000 Version Important Notes for Users of Version 11 and Earlier 1. Installation Instructions for SAP2000 Version SAP2000 Version is available as a full installation and as a patch. Installing SAP2000 Version will uninstall previous installations of SAP2000 Version 12 if present. Versions prior to (Version 11 and earlier) will not be affected. The installation instructions are available in three places: - The SAP2000 Installation Card link on the SAP2000 DVD browser. - A printed document included with the program package. - In the file SAP_Install_Instructions.pdf in the root folder of the DVD. The instructions include information about the software protection system used and installation options and instructions. You can choose between a Standalone or Network installation. When installing the Workstation version on a Vista system with UAC (User Access Controls) enabled, you should expect to be prompted three times to allow the installation of the following components: SAP WS, Sap2000TrialLicense, and Caspol.exe. Please allow these to continue so that the installation can complete.

2 2. Installation Instructions for License Manager The information in this section does not apply if you are using standalone licenses. For new Network installations, see the System Administrator's Help for more detailed information about the License Manager and the License Manager Administration program WlmAdmin.exe. This installation contains Sentinel RMS License Manager If you are currently running Version or higher of SentinelLM you do not need to reinstall License Manager. If you are currently running a version that is older than then you must install version Uninstall the older version prior to installing this version. IMPORTANT! All commuter licenses should be checked in before uninstalling the old version. Note that Sentinel RMS License Manager will recognize older licenses for Computers and Structures products. Please refer to the SAP2000 Installation Card or the SAP2000_Install_Instructions file for information on how to do this. If you are serving licenses on a Windows Vista system, you will need to use Sentinel RMS License Manager 8.1.1, which is available from Computers and Structures, Licensing Department, upon request. This version cannot be locked to a disk ID, but instead requires a computer ID key. Note that version is only required when the license server is running on Vista. It does not matter what operating system is used to run SAP2000. To speed up finding a network license when SAP2000 is launched, you can do either or both of the following: Create a text file, LEVEL.TXT, and enter the ProgramLevel in a single line. The ProgramLevel should be one of the following: BASIC/PLUS/ADVANCED/BASICC/PLUSC/ADVANCEDC/ADVANCEDI Save this file to the folder where SAP2000 is installed. This file will cause the program to find the license faster. Note that this file will be included when a new license is sent. Create a text file, LMHOST.INI, and enter the network name or IP address of the machine that is running the License Manager. If you are serving licenses on more than one machine, enter each name or IP address on a separate line of text. Save this file to the folder where SAP2000 is installed. If you experience problems with the license please refer to the appropriate License Trouble Shooting Guide... located in the SAP2000 program folder. 3. File Compatibility with Older Versions SAP2000 Version can open model files (*.SDB) from older versions of SAP2000, as well as import older SAP2000 database files (*.S2K, *.$2K, *.XLS, and *.MDB.) Note that once you save or run these models in Version , they will not be usable by older versions of the program, so you may want to save them under a new name after opening or importing them in V

3 4. Updating Older Versions 12.x.x Using the Patch from the ftp SAP2000 Version is available as a patch for V or V However, most users with V would benefit from the full installation, since it corrects some problems with the V installation dealing with access rights. When applying the patch, only updated files are included in the zipped patch file. These should be extracted in the folder where the current program is, and allowed to overwrite existing files. Workstation installations being served from a file server that do not allow.chm files to be opened on the network may need the file SAP2000_API_Documentation.chm to be updated on the workstation for V If the program will not run after patching, please do the following: In Windows Explorer or My Computer, go to the folder where SAP2000 is installed. Right-click on SAP2000.exe, and choose Run As, and run as an administrative user. This will re-register the program. You should only need to do this once. If you do not have administrative rights, please contact your IT department. 5. Significant Changes from Version Most changes do not affect most users. We have listed significant changes here. For a complete list of changes, please see the separate file ReleaseNotes.PDF in the SAP2000 folder and available by using the Help > Documentation command in SAP2000. Changes from Version to Version (issued 01/28/2009) Enhancements Implemented Incident (Bridge Modeler): The definition of the haunch height has been changed for steel girder deck sections in the Bridge Modeler: o Previously the haunch was measured from the bottom of the slab to the top of steel. It has been changed to be measured from the bottom of the slab to the bottom of the top steel flange, which is more consistent with construction practice. Now the top and bottom of the webs will be a continuous line, rather than being offset when the top flange changes thickness. o For area models with girders as frames, the insertion point has been changed from the top of steel to the top of steel minus the thickness of the flange. o For area models with girders as areas, the girder joints now located at the top and bottom of the web rather than at the top and bottom of the entire section, and the shell offsets adjusted accordingly. This latter change eliminates the need for using body constraints at the flanges; edge constraints are used as needed. This change simplifies the model and improves the stress modeling of the flange. o Models from previous versions will not be translated for this change, since the resulting models would be too complicated. This change will affect analysis results slightly by reducing the moment of inertia until you re-adjust the haunch values. o Only steel girders are affected by these changes. The haunch definition for concrete girders has not been changed. Other minor enhancements as detailed in ReleaseNotes.pdf.

4 Incidents Resolved Incident (Analysis): An Incident was resolved in which the undeformed length of catenary cable elements was incorrectly calculated for multi-segmented cable objects. For slack cables, this caused the cable to be too taut. This did not affect cables modeled as frame elements, initially taut cables, or single-segment cable objects. Incidents 16340, 16424, (Modeling): Several Incidents were resolved in which userdefined hinges could not be assigned to frame members having concrete or Section Designer sections. Automatic and fiber hinges were (and still are) able to be assigned. This has been resolved so that now user-defined hinges of types P, V2, V3, M2, M3, M2-M3, P- M2, P-M3, and P-M2-M3 can be assigned to rectangular, circular, and Section-Designer concrete sections. The deformation/rotation scale cannot be calculated automatically, but must be specified by the user or else the assignment will fail. If you request that the force or moment scale is to be calculated by the program, the ACI code with phi=1 will be used for rectangular and circular sections, and the currently selected concrete frame design code with phi=1 will be used for Section-Designer sections. Incident (Design): An Incident was resolved in which automatic and code-generated load combinations were not being properly created for notional and other lateral loads using code AISC /IBC2006. Incident (Section Designer and Design): An Incident was resolved in which the interaction surface calculated by Section Designer for the Chinese concrete code did not properly account for rebar, resulting in no tension capacity. This could affect Chinese concrete frame design results, tending to be over-conservative. Incident (Section Designer and Design): An Incident was resolved in which the interaction surface calculated by Section Designer for the Italian concrete code did not properly account for the sign of moment, resulting in a distorted surface. This could affect Italian concrete frame design results. Other minor Incidents as detailed in ReleaseNotes.pdf. Changes from Version to Version (issued 10/17/2008) Incidents Resolved Incident (Installation): An Incident was resolved in which starting SAP2000 would trigger the setup process for some installations. This occurred when the user did not have access rights to the local settings folder created during the installation by a user with administrative rights. You must uninstall V and install V to correct this problem. If you were not having this problem, you have the option to patch from V to V instead. Incidents and (Modeling): Incidents were resolved in which the automatic notional loads were not being generated, i.e., the values were always zero. This could affect analysis or design results, and you may want to use V to re-verify models with automatic notional loads that were run in V This issue affects V only, not any previous versions. Incident (Modeling): An Incident was resolved in which user-defined wind load patterns were not being assigned to diaphragms. Automated wind loads were not affected. Incidents and (Analysis): Incidents were resolved in which the mass was sometimes doubled during the second automatic seismic analysis that is performed when

5 analysis determines that auto-seismic loads have changed. This could affect dynamic analysis results, and you may want to use V to re-verify models with auto-seismic load that were run in V This issue affects V only, not any previous versions. Incident (Analysis): An Incident was resolved in which temperature, strain, or deformation load assigned to a cable object in one load pattern sometimes acted in another load pattern to which it was not assigned. This rare behavior could affect analysis results, and you may want to use V to re-verify models with these types of cable loads that were run in previous versions. Incidents and (Analysis): Incidents were resolved in which mass source from loads did not account for forces assigned to points. This could affect dynamic analysis results. Mass source from line, area, solid, and link objects was and still is properly accounted for. You may want to use V to re-verify models using mass source from load patterns with point forces that were run in V This issue affects V only, not any previous versions. Incidents 15855, 15966, 16011, and (Analysis): Incidents were resolved in which acceleration loads on point masses were sometimes corrupted when linear static load cases were solved in the same run. This could affect Ritz (not eigen) modal cases, responsespectrum, and modal time-history results. Models without point masses are not affected. You may want to use V to re-verify models with point masses and response-spectrum or modal time-history cases that were run in V This issue affects V only, not any previous versions. Incident (Analysis): An Incident was resolved in which the cable response was not always correctly calculated for a linear load case that is based on the stiffness from a nonlinear load case, possibly leading to different results depending upon the order in which cases were run. This primarily affected linear buckling cases, but could affect other linear cable response as well. Nonlinear behavior was not affected. Incident (Analysis): An Incident was resolved in which P-M2, P-M3, and P-M2-M3 frame hinges did not always follow the moment-curvature backbone curve when there was significant axial deformation, i.e., further away from the balance point. The ductility was too small and the strength was too large. Incident (Analysis): An Incident was resolved in which the link object-element relationship may be incorrect when using panel zones. This may cause the analysis to not run, or to reference the incorrect link element when displaying analysis results. Incident (Analysis): An Incident was resolved in which the sign of the R2 stiffness and damping coupling terms for the linear 6x6 link element was reversed for linear analyses, including modal and modal time-history. It was correct for nonlinear static and nonlinear direct-integration, and the frequency-dependent stiffness matrix was also correct. As stated in the CSI Analysis Reference Manual, the link internal R2 degree of freedom is based on the frame element design convention, and therefore is of opposite sign from the corresponding external degree of freedom. This is now correctly implemented for all analyses. Incident (Analysis): An Incident was resolved in which shell joint offsets were not being accounted for in generating the joint loads for contained tendon objects modeled as loads. Tendons modeled as elements were correct. You may want to use V to reverify models with these types of tendons that were run in previous version. Such models

6 may include BrIM models that have tendons modeled as loads, although the practical effect is usually small. Incident (Design): An Incident was resolved in which some numerical output items were missing or incorrectly located in the detailed design report for ASCE even though there was a heading for them. Incident (Design): An Incident was resolved in which the design iteration for optimizing steel sections was permitting PMM interaction ratios very slightly greater than one to be accepted. This was very slightly unconservative. Incident (Bridge Design): An Incident was resolved in which bridge design results could be somewhat incorrect when considering load combinations that include live load with vehicles that need to consider vehicle response components for differentiating moment response, namely the HS20-44L and the HL-93S vehicles. You may want to use V to re-verify models with bridge design requests using these types of vehicles that were designed in V Incident (Bridge Design): An Incident was resolved in which bridge design results were sometimes affected by the order in which design requests were run. In particular, stress-check results could be adversely affected if a flexure check was performed first in the same run. You may want to use V to re-verify bridge design requests run in V if multiple checks were performed in the same run. Incident (OpenAPI): All 18 API functions that have optional arguments that were not explicitly specified as being ByRef or ByVal have been changed to pass these arguments explicitly ByVal. The default behavior was ByRef. This change was necessary for use with MATLAB, and is generally a desirable improvement. However, this breaks compatibility with V Programs and Plug-Ins that use SAP2000 V may need to be recompiled to use V Other minor Incidents as detailed in ReleaseNotes.pdf.

7 6. New Features in SAP2000 Version 12 SAP2000 Version is a major new version. Significant new features added since Version include the following: MODEL-ALIVE Option True to our tradition, we are once again advancing the state-of-the-art of numerical analysis with the introduction of the Model-Alive feature in SAPFIRE ~ CSI's Analytical Engine. Taking advantage of current advances in numerical methods and hardware technology, this option provides instantaneous re-analysis and updating of the displays following any change the user makes to the model. Multi-Processor / Multi-Threading Analysis Solvers Fast, fast, fast analysis times and unmatched solution capacity New 64 bit multi-processing/multi-threading algorithms BrIM (Bridge Information Modeler) Enhancements Design for AASHTO LRFD 2007 added for concrete box girder bridges o Checks include, shear, flexure and principal-stress Additional AASHTO, Caltrans and JTG vehicles are now available BrIM allows temperature loading including nonlinear thermal gradients Enhanced BrIM wizard with more detail and guidance Templates now have a quick BrIM option for instantaneous bridge model generation Enhanced and simplified span definitions Improved abutments with separate bearings, abutment seat and soil properties Improved bents, allowing single or dual sets of bearings Superstructure may be continuous or discontinuous over bents Enhanced control of location, alignment, and properties of bearings Enhanced control over restrainers at abutments, bents, and hinges Staged Construction Enhancements Automatic generation of staged-construction stages using standard Gantt charts Stage construction groups may now be defined as part of the bridge object Control is by individual objects as well as by groups Frame end release assignments can be changed Property modifiers for frames, tendons and shells can be changed Section properties for frames, tendons and shells can be changed Section Designer Enhancements Moment curvature curve and PMM interaction surface for arbitrary fiber sections Enhanced control over material properties, including Mander model for all sections Graphical User Interface allows for overlapping shapes and improved Boolean operations Properties for concrete-only sections, steel encased sections and steel-only sections Properties for CalTrans bridge sections, with or without prestressing tendons

8 Enhanced performance and efficiency New Analysis and Design Code Related Enhancements Hyperstatic analysis for secondary effects of prestressing forces Soil (area) springs can now be tension-only or compression-only springs AISC /IBC2006 steel-frame design code, with seismic provisions Direct Analysis Method of AISC code: o Includes small P-delta effect o Automated inclusion of stiffness modification factors, with user control o Design-decision guidance on when Direct Analysis Method is needed CAN/CSA-S16-01 steel-frame design code, including seismic provisions Enhanced design of eccentrically braced frames for AISC /IBC 2006 Canadian NBCC 2005 wind loads, seismic loads, and response-spectrum functions Load combinations can be converted to nonlinear load cases for advanced design Improved automated load combinations for design Enhanced display of failure modes for steel-frame design Open structure wind loading for the API 4F 2000 code Automated, Predefined and Customized Report Generation Quick and easy generation of final printed reports with complete user control Cover sheet identifying project, user and company Formatted tables of model definition, analysis and design results Typical graphical displays of the model Output sheets of detailed design information Other Enhancements to the Graphical User Interface (GUI) User created documents now can be accessed through the SAP2000 Help menu Export of geometry and element connectivity to CSI Perform-3D Enhanced import of input files from STAAD.Pro, GTSTRUDL, NASTRAN, etc. DXF export for finite element stress contour arrows for 2D and 3D views Export structural model data for use with soil-structure interaction product, SASSI Faster graphical user interface and enhanced OpenGL graphics Enhanced Open Application Programming Interface (OAPI) The OAPI for SAP2000 provides developers of products for CADD and 3D modeling seamless and efficient access to all of the sophisticated analysis and design technology of SAP2000. The OAPI can now be used in two different ways. First, OAPI tools developed by third parties can be accessed by the SAP2000 GUI as external plug-ins. Second, using the OAPI, third-party developers can transfer model information to and from SAP2000, trigger the SAP2000 execution and extract analysis and design information from SAP2000, all from within their application. The OAPI feature is now free with every SAP2000 license. Documentation Help updated

9 Analysis manual updated Tutorials updated Design manuals updated Verification Manual updated Automated lateral loads manual updated Watch & Learn Movies updated API manual updated 7. Important Notes for Users of Version 11 and Earlier If you are upgrading from a previous version of SAP2000 (V11 or earlier), you should be aware that there has been a significant change in nomenclature regarding loading: o The term load pattern replaces load case of previous versions o The term load case replaces analysis case of previous versions o The term load combination has not changed These changes are being made consistently in all future releases of CSi products. These are simply changes in terminology; the concepts and behavior remain the same, and models from previous versions will open in V12 without any action required by you. The choice of additional solvers, changes in the default behavior of hinges with strength loss and the change in how cover to reinforcement is specified may cause some analysis or design results to change slightly from earlier versions of SAP2000 to SAP2000 Version 12. These changes are described in more detail in the ReleaseNotes.pdf. Settings files that used to be stored in the Windows folder have been moved to the local application folder \Computers and Structures under Documents and Settings for each user. These files include the SAP0000.INI file, the.tb3 files that store changes to the menus and toolbars, and the default database table format files.