Release Note
标杆的神器 V1.0.5 ReleaseNote
【2014】034号-关于H3C SR8800-X(-S)CR16000-F SR8800-F系列路由器内存泄露导致PPPOE拨号失败问题公告
3、修复其他问题（共计10个）。
********************************************************************
2015-1-12 发布V1.0.4版本
==========================================
新增功能
----------------------
1.新增需求
（1）【标杆的神器】可以进行蓝小翔皮肤的切换。
（2）【工具宝箱】支持对H3C命令行的模糊查询。
（3）【工具宝箱】常用协议查询，调整为常用协议号查询。
（4）【控制台】支持V7设备及用户名缺省情况下设备的自动登录。
（5）【控制台】支持设备管理员权限的自动登录。
【2014】044号-关于H3C S6300-42QT加载R2311到R2311P03版本会反复升级逻辑无法启动的公告
【2014】045号-关于H3C S5820V2-52QF-U从R2307版本升级到R2311P04导致设备无法启动问题的公告
【2014】046号-关于MSR使用3G模块导致内存泄露的公告
（8）【维护大全】支持对V7设备的安全配置审查（支持对debug开关的检查）。
2、新增故障排查脚本：
01公共协议-1.5 BGP MPLS问题排查流程
修正缺陷
ReleaseNotes_EnterpriseHomeScreen_v3.1_chinese说明书
发行说明 - Enterprise Home Screen v3.1目录·重要新闻·以前的公告·简介·说明·设备兼容性·安装要求·安装说明·使用说明·已知问题·部件号和发布日期重要新闻Android 支持：EHS 3.1 现在支持Android 8.1.0 (Oreo) 和 Android 7.1.2 (Nougat)。
针对运行 Android 6.0.1 (Marshmallow) 的设备的 EHS 支持结束了 - EHS v3.1 仅支持Nougat 和 Oreo 设备。
EHS v3.0 是支持 Android Marshmallow 设备的最后一个版本。
支持门户上仍然提供 EHS v3.0 及更早版本，供在 Marshmallow 设备上使用。
以前的公告从Android Nougat/Marshmallow 升级到Oreo：将设备从Android Nougat/Marshmallow 升级到 Oreo 之后，必须卸载现有 EHS 版本，并且必须在原处安装EHS_03XXXX_B.apk。
来自以前 EHS 安装的配置会保留下来并自动应用。
这不适用于现有版本为类型 B 的 EHS 3.X (EHS_03XXXX_B.apk) 的设备绕过锁屏功能已弃用。
安全模式功能已弃用。
已终止针对所有 Lollipop (Android 5.x) 设备的 EHS 支持 - 从 EHS v3.0 开始，仅支持Marshmallow 及更高版本设备。
EHS v2.8 是支持 Android Lollipop 设备的最后一个版本。
支持门户上仍然提供 EHS v2.8 及更早版本，供在 Lollipop 设备上使用。
从版本 2.8 开始，简体中文语言支持在 EHS 中可用从 EHS 版本 2.7 开始，在支持门户中提供两个独立的 APK（EHS_XXXXXX_A.apk 和EHS_XXXXXX_B.apk），供用户根据所使用的 Zebra 设备进行选择。
ReleaseNote
*** Topaz Adjust™ for Windows V4.1 Release Notes ***Contents1. Installation2. Running Topaz Adjust3. Registration4. System requirements5. Program Features6. More information1. InstallationTopaz Adjust 4.1™ is a plug-in for Adobe Photoshop and other photo-editing / imaging software programs (called host programs) that support Photoshop plug-ins. It has been tested with:Adobe Photoshop 7/CS/CS2/CS3/CS4/CS5Adobe Photoshop Elements 1-9Paint Shop ProPainter X/11 (preview zoom is not supported)PhotoImpactIrfanview (freeware)The installer will automatically detect and install the plug-in for Adobe Photoshop7/CSx and Elements users. However, if you are using another host program, you will need to take some additional steps.In Paint Shop Pro / PhotoImpact: You will need to specify the Topaz Adjust 4 Plug-ins folder as an additional plug-ins folder to using menu File \ Preference \ Folder and then add Topaz Adjust “Plug-ins” folder, usually located at “C:\Program Files \ Topaz Labs \ Topaz Adjust \ Plugins”In Irfanview, Make sure you’ve downloaded and installed the 8BF plug-in add-on, available on the Irfanview webpage. Go to menu \ Image \ Effects \Adobe 8BF filters and add Topaz Adjust 4 “Plug-ins” folder.For other host programs, you may need to copy “Topaz Adjust 4” “Plug-in”folder to the required location of that host program. Make sure you do notmove the “Presets” folder, however.2. Running Topaz AdjustTopaz Adjust is a Photoshop plug-in, not a stand alone program, which means that you are not able to run it directly. To use Topaz Adjust, open up an image in Photoshop (or your other compatible image-editing software). Topaz Adjust will be located in the “Filters -> Topaz Labs” menu. (You will need to open or create a new image in order to access the filters menu).3. RegistrationWhen you first install the plug-ins, Topaz Adjust will be in demo mode. All functions are available except the ability to save the processed image. In order to save your processed image, you will need to enter either a purchased license key or a 30-day fully functional trial key, which you can obtain here:/downloadsYou may purchase the product online through our secure ordering system at:/storeTo enter your key, open Topaz Adjust, click the Menu… button and then select Enter Key…. You can then copy & paste or type your key in.4. System RequirementsIt is recommended that you have at least 1 GB of RAM. Topaz Adjust is very computationally intensive and you'll need a fast computer to run it at acceptable speeds. Topaz Adjust supports multi-core CPUs, which increases rendering speed substantially.This installer is for Windows only. For the Mac version please visit our website at: /downloads5. Program FeaturesTopaz Adjust has many valuable tools to help make your photos pop.New Adjust V4 Features:•Auto Updater. Get software updates instantly.•New user interface. Includes the ability to easily expand and collapseside panelsand parameter tabs for an adjustable workspace.•Snap / Recall buttons. Save up to 99 snapshot settings for comparison.•Preset enable / disable option. Option to enable or disable the presetpreview processing at program startup.•New presets layout. The new preset format features its own preview。
RELEASE_NOTES
and SystemC.
This release includes a new dongle driver installer for Windows.
No one is permitted to use these Marks without the prior written consent
of Mentor Graphics or the respective third-party owner. The use herein
Installation and Licensing Guide under the section Supported Platforms.
* PRODUCT SUPPORT
The profiling feature is now supported on the linux_x86_64 platform.
The new dongle driver versions that will be installed are as follows:
+ Aladdin (FLEXID=9-) driver version 4.96
+ Dallas (FLEXID=8-) driver version 3.2.1.11
* PLATFORM AND COMPILER SUPPORT
SystemC has dependencies on C++ compiler versions. In release 6.5, the
Solaris and Windows MinGW versions of gcc 3 compilers will be replaced
ReleaseNotes
Mapmatrix部分1.目前断面编辑只是提供显示、查看断面效果，不提供编辑功能，其程序总是默认将断面显示模型的最左侧，可以使用键盘中的<和>进行操作，即逗号和句点键。
2.dom修补中修补效果和生成效果偶有不一致的现象，主要是由于修补的区域是采用双线型插值生成影像，而生成的dom时使用的双三次卷积方式生成的，只要在生成的时候将双三次修改为双线型插值即可。
3.重启系统后，启动液晶立体勾选且进程也已经开启了，但是开启立体时依然会黑屏，通常只需手工关闭StereoBuddyWnd进程，再重新将启动液晶立体勾选即可。
4.英文系统下安装的英文版本程序，“启动液晶立体”功能暂无法正常启动。
5.多模型进行实时核线编辑DEM，出现立体来回切换,立体上有时有块区域被其它方块区域覆盖显示,无法刷新，只需要将立体缩小到025倍时即可。
6.使用工具中的DEM格式转换，如果线将一nsdtf格式的DEM转换为tif格式（32位），再将该32位tifDEM转换为nsdtf格式，发现坐标发生了大概半个格网距离的偏移。
这个是由于DEM与TIFF起点不同导致，TIFF格式起点的在像素中心，如果可能的话也可以手工将转换后的DEM起点坐标进行修改。
7.DEM编辑中实时核线立体使用"切换立体"功能时,有的数据切换立体显示不对，通常是自动切换是正常的,用标记定位到其它立体也正常，建议实时核线不要使用手动切换。
8.南半球数据支持，由于手中无相关数据验证，所以如果有问题希望及时反馈。
9.数码相机校正功能扩展支持jpg等常用格式目前该功能输出格式只支持tif，没有提供输出jpg的功能，如果一定要输出jpg文件的话，需要手工在影像列表中双击影像，在弹出的界面中将文件后缀手工修改为jpg即可，所有的影像都需要一个个手工进行修改。
10.ADS40模型裁切里“合并ads”, “合并并且裁切”，“可视化选模型”三个按钮不要使用。
i2 Analyst's Workstation TCA 2 Release Notes.pdf
i2 Analyst's Workstation TCA 2 Release NotesVersion 2.0.1June 2007Part Number: 1264Issue No. 1.0i2 Analyst’s Workstation TCA 2 (Telephone Call Analysis) is part of i2’s suite of analysis software. It delivers an environment for managing and analyzing telephone-oriented investigations. It is availableas part of i2 Analyst’s Workstation 3, for the UK only.Please read these release notes before installing TCA.You do not need to uninstall your existing TCA software before installing Analyst’s Workstation 3. Existing security files and databases must be upgraded for use with Analyst’s Workstation 3.ContentsRelease Contents 2 System Requirements 2 Authorization Information 2 Documentation and Examples 2 Installation 3 Importing Telephone Codes 3 Enhancements and Bug Fixes 6 Known Limitations 7 Contacting i2 9Warning and Disclaimeri2 provides this document "as is", without representation or warranty of any kind, express or implied, including without limitation any warranty concerning the accuracy, adequacy, or completeness of such information contained herein. i2 does not assume responsibility for the use orinability to use the software product as a result of providing this information.The data presented in this document is fictitious and for illustration purposes only with no connection to, without limitation, past or present persons, organizations, identifying numbers, or circumstances, except by coincidence.Addresses:i2 Limited, The Visual Space, Capital Park, Fulbourn, Cambridge CB21 5XH, UKTel: +44 (0)1223 728600 Fax: +44 (0)1223 728601i2 Inc., 1430 Spring Hill Road, Suite 600, McLean, Virginia 22102, USATel: +1 703 921 0195 Fax: +1 703 842 4685© 2007 i2 Limited or its licensors. All rights reserved.Release ContentsAnalyst’s Workstation TCA 2.0.1 is provided as part of Analyst's Workstation 3. Fordetails, see the i2 Analyst's Workstation 3 Release Notes.What's New in This Release?The following table summarizes the Analyst’s Workstation TCA 2 releases:DateVersion Releasei2 Analyst’s Workstation TCA 2.0.1 June 2007System RequirementsThe recommended system requirements are described in the i2 Analyst’s Workstation 3Release Notes.Authorization InformationTCA is a licensed product and requires a dongle containing a valid permit in order to run.It can be licensed using local or network dongles. See the i2 Analyst’s Workstation 3Release Notes for further details.Documentation and ExamplesInformation specifically for TCA administrators is provided in the Administration Centerdocument Setting Up Analyst's Workstation TCA. See the i2 Analyst’s Workstation 3Release Notes for details.Information for users is provided by the i2 Analyst’s Workstation TCA 2 User Guide:Manual Title Part Numberi2 Analyst’s Workstation TCA 2 User Guide 1259This user guide is example based and is designed to help users learn how to use thesoftware. An example Telecoms database, security file, and other supporting data areprovided on the CD. You should install these so that users can work through theexamples. For details, see Installing the example Telecoms database on the serverbelow.Release notes and white papersThe following white papers are available for TCA, from your supplier.Number Title Parti2 Analyst’s Workstation TCA Product Overview1522What's New in i2 Analyst's Workstation TCA 2 1521For details of other release notes and white papers, see the i2 Analyst's Workstation 3Release Notes.2 i2 Analyst's Workstation TCA 2 Release Notes Issue No. 1.0InstallationTCA is installed as part of Analyst's Workstation 3. For details, see the i2 Analyst’sWorkstation 3 Release Notes.Installing the example Telecoms database on the serverThe example Telecoms database, which has its own security file, contains all the dataneeded to follow the exercises in the i2 Analyst’s Workstation TCA 2 User Guide.However, each user requires their own copy of the Telecoms database, installed on theserver, in order to complete these exercises.The following instructions assume that you have a working installation of TCA prior toinstalling the example databases, and that you have permission to create a database onyour SQL Server machine. See the Administration Center for information on how to dothis and for further details about the steps described below.To install a Telecoms database for each TCA user:1. On your SQL Server machine, create a database folder for each user.2. Copy the file Telecoms.ids and the Data folder from this folder on the CD:Examples\i2 Analyst’s Workstation TCA 2\TCA Databaseinto each of the database folders.3. Run the self-extracting Telecoms.exe file to extract the backup file.4. In iBase Designer, on your SQL Server machine, create a new database for eachuser. You must create the database from the i2 Telephone Call Analysis template(file name i2 Telephone Call Analysis.idt). This creates a case-controlleddatabase with the correct database schema.5. Close iBase Designer.6. In SQL Server, restore into each empty database from the extracted backup files.7. In iBase Designer:•For each Telecoms database, log on using the security file in the database folder,and open the new database.•Close the database, log off, and repeat for the next Telecoms database.• Close iBase Designer.8. If required, initialize each database for use with Data Miner. For details of this step,see the Administration Center document, Setting Up Data Miner.Importing Telephone CodesBefore you can use the Populate Number Information feature in TCA, you need to importthe UK numbering plan, UK geographic areas, and international country codes into yourTCA database. With the exception of the international country codes, this informationmust be obtained from Ofcom, and consists of Microsoft Excel spreadsheets and textfiles. The import files should be copied to the same folder.By default, on Windows XP, this is:C:\Documents and Settings\All Users\Application Data\i2\i2 Analyst’s Workstation TCA 2\Telephone CodesIssue No. 1.0 i2 Analyst's Workstation TCA 2 Release Notes 3By default, on Windows Vista, this is:C:\ProgramData\i2\i2 Analyst’s Workstation TCA 2\Telephone CodesYou import the telephone codes using the Populate Number Information task in theTelephone Task Manager. Do not import them by running the import batch specification:TCA_PNI_Number Lookups. Detailed information on how to verify the data and import itusing the Populate Number Information task is given in the Administration Centerdocument Setting Up Analyst's Workstation TCA.Note: Ofcom periodically updates its spreadsheets, changing the names ofindividual worksheets, and this may affect how the import runs. To avoid anyproblems, which may not be identified until later, open the individual importspecifications referenced by the Ofcom import batch specification(TCA_PNI_Number Lookups), reselect the displayed Excel worksheet, andthen step through the remaining pages of the dialog. Save the importspecification.The import specifications referenced by the Ofcom import batch specification(TCA_PNI_Number Lookups) were correct at the time of release. However,you may need to update these yourself in order to accommodate changes tothe structure of the Ofcom spreadsheets, or to add new Ofcom spreadsheets.Existing users of TCA will need to upgrade the import specifications used by the PopulateNumber Information task. See below for details.New usersInternational country codesThis release includes a spreadsheet of international country codes. The spreadsheet,Country Codes.xls, contains a single worksheet of two columns: country code andcountry name. The reference data for this spreadsheet can be found in the ITUdocuments at http://www.itu.int/itudoc/itu-t/ob-lists/icc/e164_763.html.The spreadsheet is installed to the Telephone codes folder given above. It must bestored in the same folder as the Ofcom files.UK numbering planThe following Ofcom files are required in order to import the UK Numbering plan into aTCA database:sabcde1.xlssabcde2.xlssabcde3.xlscps.xlss3.xlss5.xlss7.xlss8.xlss9.xlss10.xlsYou can obtain these files from the following page on the Ofcom web site:/telecoms/ioi/numbers/numbers_administered/These Ofcom files must be stored in the same folder as Country Codes.xls.4 i2 Analyst's Workstation TCA 2 Release Notes Issue No. 1.0UK geographic areasThe Ofcom file, sabc.txt, is required in order to import UK geographic dialling codesinto a TCA database. You can obtain this file from the following page on the Ofcom website:/telecoms/ioi/numbers/numbers_administered/downloadThis Ofcom file must be stored in the same folder as Country Codes.xls.Special service numbersSpecial service numbers are optional and do not need to be imported. If you do not wantto import special service numbers, remove the Ofcom_S10 import specification from theTCA_PNI_Number Lookups import batch specification. For details of this step, see theAdministration Center document Setting Up Analyst's Workstation TCA.Note: Because these numbers are optional, there will be no warning to users if theyare missing.Protecting the telephone code dataIt is important to protect the telephone code data from users who might add duplicaterecords, or modify and delete existing ones. You can do this by setting read-only accessto the Number [Area], Number [Country], Number [Service Provider], and Number[Special] tables in the Data Access Control dialog. For further details, see theAdministration Center document Setting Up Analyst's Workstation TCA.Existing usersThe predefined import specifications supplied with earlier versions of TCA have changedat this release because of changes made by Ofcom to its spreadsheets. You will need todownload the updated spreadsheets from Ofcom.Once you have obtained the updated spreadsheet, a TCA administrator (such asTCAADMIN) must delete or modify the following import specifications in the TelephoneAnalysis folder.Import specification Upgrade stepOfcom_S1F DeleteOfcom_S8F DeleteOfcom_SABCDE1 Modify (see steps below)Ofcom_SABCDE2 Modify (see steps below)Ofcom_SABCDE3 Modify (see steps below)To modify Ofcom_SABCDE1, Ofcom_SABCDE2 and Ofcom_SABCDE3:1. Download the updated spreadsheets from Ofcom. See UK numbering plan above.2. Log on to iBase as a TCA administrator and open the database.3. Open the first import specification, for example Ofcom_SABCDE1. It will be in theTelephone Analysis folder.4. On the Step 1 page, click Next—there is nothing to change on the Step 1 page.5. On the Step 2 page, browse to the location of the new Ofcom spreadsheet. The sheetname will be updated. Click Next.Issue No. 1.0 i2 Analyst's Workstation TCA 2 Release Notes 56. On the Step 3 page, click Data Transformations and, in the Transform Types area,select Merge. In the Field Indexes column, change 0,1 to 0,1,2.7. In the Clear Field Assignments message box, click Yes.8. Reassign the fields Communications Provider and SABC to the correct field in theiBase Field column:- Assign Communications Provider to Service Provider.- Assign SABC to Number.Click Next to go to the Step 4 page.9. On the Step 4 page, click Next—there is nothing to change on the Step 4 page.10. O n the Step 5 page, click Save.11. R epeat these changes for Ofcom_SABCDE2 and Ofcom_SABCDE3.Once you have made these changes, update the batch specification that is run by thePopulate Numbers task:1. Open the import batch specification called TCA_PNI_Number Lookups. It will be in theTelephone Analysis folder.2. You will see a message warning you that an import specification has been deleted. Ifyou do not see this message, go back and delete Ofcom_S1F and Ofcom_S8F.3. Click Save.4. Run the Populate Numbers task to test that it is working correctly. The import maytake some time to run.5. If you are likely to create new TCA databases, save a new template from thisdatabase.Enhancements and Bug FixesEnhancements in this releaseThe query for mobiles now supports 071–075 numbers for mobile phones.The Security Design report now includes information on cases and who has access tothem.6 i2 Analyst's Workstation TCA 2 Release Notes Issue No. 1.0Bugs fixed in this releaseThe following bugs are fixed in this release of Analyst’s Workstation TCA.Importing and exporting•An error will no longer occur in the statistics when importing from an import filethat contains one row of data.•When verifying an import, a detailed (and potentially misleading) statisticalbreakdown is no longer provided. Instead statistics are reported under theheadings Not Found, Different and Same.TextChartWhen you load a visualization created in i2 TextChart 3, that contains markups for sourcerecords that exist in the current database but are not in the current case, a warning is nowdisplayed: The source record for document <name> has either beendeleted or it is in a different case. No link will be createdbetween the source document and the source record.Known LimitationsThe following limitations apply to Analyst's Workstation TCA.Analyst's Workstation TCACasesWhen working in multi-case analysis mode, drop-down lists of cases will only list cases atOpen status.Using datasheetsWhen you select an existing entity before entering any data (such as a telephone) into anew record, you see the message: "Using this record will discard changesto the previous record. Are you sure you want to continue?". ClickYes – the record is blank so you have not made any changes that you need to keep.ImportingOn the Import Data page of the Telephone Task Manager:•When importing workbooks containing multiple worksheets from Microsoft Excel,the first worksheet may appear twice on the Sheet drop-down list. You should onlyselect the first instance of the sheet; selecting the duplicate worksheet and clickingNext will prevent you from continuing with the import.•The error file facility is only provided if the data source is identical for all imports—different worksheets of the same file are handled as different data sources.•You cannot run import batch specifications that contain data transformations.•You can only verify an import batch specification that contains importspecifications which share the same import file.Issue No. 1.0 i2 Analyst's Workstation TCA 2 Release Notes 7•When verifying the import of links between entities, you may end up withmisleading results if you do not turn on the option to Check for matching linksusing identifiers and link ends in the relevant step of the Import Wizard for all ofthe import specifications in the batch. (This only applies when you are editingindividual import specifications within a quick-start batch, or creating newspecifications, which import links.) If you do not turn on this option, any linkbetween existing entities will be considered as a new link and reported as new tothe current case.iTel import•You cannot use Pattern Search and import data from an iTel database in thesame iBase session.• If an iTel case is currently open in iTel and the same iTel database is thenselected to be opened on the Import iTel Data page of the Telephone TaskManager then the iTel Password dialog is displayed. The dialog is repeatedlydisplayed if the correct password is entered.• When iTel is open and the same iTel database is selected twice in a row on the Import iTel Data page of the Telephone Task Manager, then the followingmessage is displayed: Could not lock file. Error #3050.Telephone code data•Telephone administrators cannot import the telephone number information (on the Populate Number Information page) when the database is opened in multi-caseanalysis mode. To import the data, you must select a single case—the telephonenumber data will still be available to all cases in the database.•You must prevent analysts from adding, modifying, or deleting the telephone code data. For details, see Special service numbers on page 5. Telephoneadministrators can update the telephone code data by modifying the import filesand then re-importing them using the Populate Number Information task in theTelephone Task Manager.iBase DesignerThe Valid End Types dialog filters out the fixed link types defined in the TCA templatebecause these cannot be modified in any way. Therefore, when there are no user-definedlink types in the database, it displays the message “There are no link types in thedatabase” and the dialog does not appear.iBase GIS Interfacesblue 8 world installs entity/link icons to be represented on maps as tif files. There are onlythe following to choose from: Car, crime, house, incident, alcohol and bomb. So theTelephone Mast used in a case on the TCA template to represent the entity Cell will resultin no data being plotted. The workaround is to use, for example, a Star selected from thePlot Style dialog in the Mapping Configuration dialog.Microsoft Vista Known LimitationsFor details of Microsoft Vista known limitations, see the i2 Analyst's Workstation 3Release Notes.8 i2 Analyst's Workstation TCA 2 Release Notes Issue No. 1.0Contacting i2Technical support is available to anyone whose organization has opted for our annualsupport program. If you have a question and cannot find a solution in these release notes,in the Administration Center, or in the online help, you can send an e-mail to the i2Technical Support team. You must have an up-to-date i2 Support and MaintenanceAgreement and your dongle number as a reference when contacting Support.•For customers in North and South America, e-mail support@.•For customers in the UK or the Rest of the World, e-mail support@.Note:If your i2 software was purchased from one of our distributors, please contactyour supplier for technical support.i2 International and ChoicePoint Government Services Professional Consulting serviceswork with customers to understand specific requirements and then determine the bestmethods to get these requirements met through custom development, on-site training, oralignment with the right system integrator or product vendor.For further information, contact your i2 supplier, or visit the i2 Web site at:.Issue No. 1.0 i2 Analyst's Workstation TCA 2 Release Notes 9。
Release_Notes_CN
VirtuoZo V3.6 Release Notes简介本文叙述的是全数字摄影测量软件系统 VirtuoZo V3.6的系统配置要求、安装简介以及在推出之际已知的缺陷和部分规避的方法。
系统要求1.运行环境：y Windows NT4.0 WorkStation（Service Pack5或更高版本、IE5.0或更高版本）。
y Windows2000 Professional（Service Pack1）。
y Windows XP（Service Pack1）。
2.CPU：Pentium IV 1GHz或以上。
3.内存：512MB或以上。
4.硬盘：40GB或更大容量。
5.推荐使用双屏。
6.显示器在1024×768的分辨率下，刷新频率要达到100赫兹或以上。
7.显卡要求：y操作系统为 Windows NT，请选用支持4 buffer OpenGL 立体的显卡。
¾单屏：3Dlabs GVX1 显卡（Pentium III 处理器），3Dlabs GVX1 Pro 显卡（Pentium IV处理器），Diamond Fire GL 1000 PRO 显卡（Pentium III处理器）。
¾双屏（单卡双屏）：3Dlabs GVX210 显卡（Pentium III 处理器），3DlabsGVX420 显卡（Pentium III处理器）。
y操作系统为 Windows2000，请选用支持4 buffer OpenGL 立体的显卡。
¾单屏：不推荐使用单屏。
¾双屏：有“单卡双屏”和“双卡双屏”两种选择：单卡双屏：GVX210 显卡或GVX420 显卡均可实现一块显卡对双屏的支持。
即3Dlabs GVX210（Pentium III 处理器）或3Dlabs GVX420（PentiumIII 处理器）。
目前新推出的显卡3Dlabs VP 870、Quadro4 750 或XGLQuadro4 900 XGL（Pentium IV处理器）也可实现双屏。
SESAM Release Note SIMA V4.1.0说明书
SESAM RELEASE NOTESIMASima is a simulation and analysis tool for marine operations and floating systems — from modelling to post-processing of results.Valid from program version 4.1.0SAFER, SMARTER, GREENERSesam Release NoteSimaDate: 19 Apr 2021Valid from Sima version 4.1.0Prepared by DNV GL – Digital SolutionsE-mail sales: *****************© DNV GL AS. All rights reservedThis publication or parts thereof may not be reproduced or transmitted in any form or by any means, including copying or recording, without the prior written consent of DNV GL AS.DOCUMENTATIONInstallation instructionsRequired:•64 bit Windows 7/8/10•4 GB RAM available for SIMA (e.g. 8 GB RAM total in total on the computer)•1 GB free disk space•Updated drivers for graphics cardNote that Windows Server (all versions), Windows XP, Windows Vista, and any 32-bit Windows are not supported.Recommended:•64-bit Windows 10•16 GB RAM•Fast quad core processor (e.g. Intel i7)•High-resolution screen (1920 × 1200 / 1080p)•Graphics card: DirectX 10.1 or 11.X compatible; 512 MB or higher•F ast SSD disk, as large as possible (capacity requirements depends heavily on simulation settings, e.g. 500 GB is a good start)•3-button mouseHigh disk speed is important if running more than 2 simultaneous simulations in parallel. Example: If the user has enough SIMO-licenses and has configured SIMA to run 4 SIMO-calculations in parallel, then the simulations will probably be disk-speed-bound, and not CPU bound (with the above recommended hardware). Note that this is heavily dependent on the simulation parameters, so the result may vary. The default license type should now allow for unlimited parallel runs on one PC, workstation of cluster.Updated Drivers for Graphics CardThe driver of the graphics card should be upgraded to the latest version. This is especially important if you experience problems with the 3D graphics. Note that the version provided by Windows update is not necessarily up to date – download directly from your hardware vendors web-site.Installing graphics drivers may require elevated access privileges. Your IT support staff should be able to help you with this.SIMA should work with at least one graphics-mode (OpenGL, OpenGL2, DirectX 9 or DirectX 11) for all graphics cards that can run Windows 7 or 8. However, graphics cards can contain defects in their lower-level drivers, firmware and/or hardware. SIMA use the software “HOOPS” from the vendor “Tech Soft 3D” to draw 3D-graphics. For advanced users that would like more information on what graphics cards and drivers that does not work with SIMA (and an indication on what probably will work), please see the web page /hoops/hoops-visualize/graphics- cards/ .Before reading the compatibility table you may want to figure out which version of HOOPS SIMAis using. To do this open Help > About > Installation Details, locate the Plug-ins tab and look for the plug-in provider TechSoft 3D (click the Provider column title twice for a more suitable sort order). The version number is listed in the Version column. Also remember that all modes (OpenGL, OpenGL2, DirectX 9, DirextX 11) are available in SIMA.Upgrading from Earlier VersionsAfter upgrading to a newer version of SIMA, your workspaces may also require an update. This will be done automatically as soon as you open a workspace not created with the new version. You may not be able to open this workspace again using an older version of SIMA.Preference settings should normally be retained after upgrading, however you may want to open the preference dialog ( Window > Preferences ) in order to verify this.Verify Correct InstallationTo verify a correct installation of SIMA, perform the following steps:1.Start SIMA (by the shortcut created when installing, or by running the SIMA executable)a.If you are prompted for a valid license, specify a license file or license server. (If you needadvanced information on license options, see “License configuration”).b.SIMA auto-validates upon startup: A successful installation should not display any errorsor warnings when SIMA is started.2.Create a new, empty workspace:a.You will be prompted to Open SIMA Workspace: Create a new workspace by clicking New,select a different folder/filename if you wish, and click Finish.3.Import a SIMO example, run a SIMO simulation, and show 3D graphics:a.Click the menu Help > Examples > SIMO > Heavy lifting operationb.Expand the node Condition in the Navigator in the upper left cornerc.Right-click Initial, and select Run dynamic analysis. After a few seconds, you will see themessage Dynamic calculation done. No errors should occur.d.Right-click HeavyLifting in the Navigator in the upper left corner, and select Open 3DView. 3D-graphics should be displayed, showing a platform and a crane.4.If there were no errors when doing the above steps, then SIMA can be assumed to becorrectly installed.Changing Default Workspace Path ConfigurationWhen creating a new workspace SIMA will normally propose a folder named Workspace_xx where xx is an incrementing number; placed in the users home directory under SIMA Workspaces.The proposed root folder can be changed by creating a file named .simarc and place it in the users home directory or in the application installation directory (next to the SIMA executable). The file must contain a property sima.workspace.root and a value. For example:sima.workspace.root=c:/SIMA Workspaces/A special case is when you want the workspace root folder to be sibling of the SIMA executable. This can be achieved by setting the property as follows:sima.workspace.root=.License ConfigurationSIMA will attempt to automatically use the license files it finds in this order:e path specified in the file “.simarc” if present. See details below.e the path specified in the license wizard.e the system property SIMA_LICENSE_FILE.e the environment variable SIMA_LICENSE_FILE.e all “*.lic” files found in C:/flexlm/ if on Windows.e all “*.lic” files found in the user home directory.If any of the above matches, the search for more license files will not continue. If there are no matches, SIMA will present a license configuration dialog.The license path can consist of several segments separated by an ampersand character. Note that a license segment value does not have to point to a particular file – it could also point to a license server. For example:c:/licenses/sima.lic&1234@my.license.server&@another.license.serverIn this case the path is composed on one absolute reference to a file. F ollowed by the license server at port 1234 and another license server using the default port number.RIFLEX and SIMO LicenseWhen starting SIMO and RI F LEX from SIMA the environment variable MARINTEK_LICENSE_F ILE will be set to the home directory of the user. This means that a license file can be placed in this directory and automatically picked up.Specifying a License pathWhen starting SIMA without a license the dialog below will pop up before the workbench is shown. If you have a license file; you can simply drag an drop it into the dialog and the path to this file will be used. You may also use the browse button if you want to locate the file by means of the file navigator. If you want to use a license server; use the radio button and select License server then continue to fill in the details. The port number is optional. A host must be specified, however. Note that the host name must be in the form of a DNS or IP-address.You can now press Finish or if you want to add more path segments; you can press Next, this will bring up the second page of the license specification wizard. The page will allow you to add and remove licence path segments and rearrange their individual order.Modifying a License PathIf the license path must be modified it can be done using the dialog found in the main menu; Window >Preferences > License. This preference page works the same as the second page of the wizard.Specifying License Path in .simarcThe mechanism described here works much like specifying the environment variable, however it will also lock down the SIMA license configuration pages, thus denying the user the ability to change the license path. This is often the better choice when installing SIMA in an environment where the IT-department handles both installation and license configuration.The license path can be forced by creating a file named .simarc and place it in the users home directory or in the application installation directory (next to sima.exe). The latter is probably the better choice as the file can be owned by the system and the user can be denied write access. The license path must be specified using the sima.license.path key and a path in the F LEXlm Java format. The license path can consist of several segments separated by an ampersand character. For instance:sima.license.path=c:/licenses/sima.lic&1234@my.license.server&@another.license.serverNote that the version of FLEXlm used in SIMA does not support using Windows registry variables. It also requires the path to be entered in the F LEXlm Java format which is different from the normal F LEXlm format. Using this mechanism one can also specify the license path for physics engines such as SIMO and RIF LEX started from SIMA. This is done by specifying the key marintek.license.path followed by the path in normal FLEXlm format. For example:marintek.license.path=c:/licenses/ sima.lic:1234@my.license.server:@another.license.server Viewing License DetailsIf you would like to view license details, such as expiration dates and locations you will find this in the main menu Help > License.New Features - SIMONew Features - RIFLEXNew Features - OtherBUG FIXESFixed bugs - SIMOFixed bugs - RIFLEXFixed bugs - OtherREMAINING KNOWN ISSUESUnresolved Issues - SIMOUnresolved Issues - RIFLEXUnresolved Issues - OtherABOUT DNV GLDriven by our purpose of safeguarding life, property and the environment, DNV GL enables organizations to advance the safety and sustainability of their business. We provide classification and technical assurance along with software and independent expert advisory services to the maritime, oil and gas, and energy industries. We also provide certification services to customers across a wide range of industries. Operating in more than 100 countries, our 16,000 professionals are dedicated to helping our customers make the world safer, smarter and greener. DIGITAL SOLUTIONSDNV GL is a world-leading provider of digital solutions for managing risk and improving safety and asset performance for ships, pipelines, processing plants, offshore structures, electric grids, smart cities and more. Our open industry platform Veracity, cyber security and software solutions support business-critical activities across many industries, including maritime, energy and healthcare.。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Created: Last saved by: Printed:
2013-11-25 Olof Helander 2015-02-19
HMS Industrial Networks AB
RELEASE INFORMATION
Project name Project No
ABC DF1, Master, Generic
- Other changes
Exchanged upper case letters to lower case in file-names. New Make routine. One release label for all protocol from now on. Added Debug-object (removed by define).
Application + Bootloader Binary files –
Application code, formatted for ACM –
Boot loader (two file types): o o Bootloader file – BL_ABC_3_1.a37, not updated in this release. CANopen – o o o o o o o ABC_CANOPEN_V_3_17.eds ABC_CANOPEN_V_3_17_COMPACTSUB.eds 0212_Anybus_Communicator_3.03.01_en.cspp hms_anybus.ico hms_anybus.png 005A000C004C0300.EDS 005A000C003C0300.EDS ABC_ETHERCAT_V_3_03.xml 005A000C004D0300.EDS 005A000C00540300.EDS Configuration files –
Version 3.03.01_A
2014-12-02
o o
HMSB1803.gsd GSDML-V2.3-HMS-ABC_PROFINET_IO-20141127.xml GSDML-010C-0002-ABC-PRT.bmp GSDML-V2.3-HMS-ABC_PROFINET_IRT-20141127.xml GSDML-010C-0013-ABC-PIR.bmp
CC-Link IE –
ControlNet – DeviceNet – EtherCAT – EtherNet/IP 1-port – EtherNet/IP 2-port – PROFIBUS –
HMS Industrial Networks AB
Created: Last saved by: Printed:
2013-11-25 Olof Helander 2015-02-19
RELEASE INFORMATION
Project name Project No
ABC DF1, Master, Generic
Software Software version
7061
Release date
Application
Added support for Ethernet/IP 2 port.
- Improved functionality
N/A
- Bug fixes
Can't read MACID from ModbusTCP products in production – Support for reading MACID now added for ModbusTCP . Internal ID: 0007596..
Project name Project No
ABC DF1, Master, Generic
Software Software version
7061
Release date
Application
Version 3.03.01_A
2014-12-02
Updated in version 3.01: - New functionality
Software Software version
7061
Release date
Application
Version 3.03.01_A
2014-12-02
Updated in version 3.03: - New functionality
Added support for PROFINET IRT. Added support for CC-Link IE.
Software Software version
7061
Release date
Application
Version 3.03.01_A
2014-12-02
How to upgrade from previous versions:
It is very important that the following steps are performed in correct order, otherwise the module may be unusable and must be sent back to HMS for recover.
- Improved functionality
N/A
- Bug fixes
Generic mode TA1839 - Mantis ID: 0011208. Maximum length of variable consume transaction is set to 256. Greater
Profibus DeviceNet Ethernet ControlNet CANopen Profinet EtherCAT CC-Link FIPIO Interbus ModbusRTU ModbusPlus Ethernet/IP 2port
2.04 2.06 2.04 1.54 4.61 5.00 2.00 2.00 1.00 1.10 1.05 1.01 1.07.02
This document Application code – o o o o o o o o o APP_ABC_MASTER_V_3_03_01.a37 APP_ABC_GENERIC_V_3_03_01.a37 APP_ABC_DF1_V_3_03_01.a37. ABC_MASTER_V_3_03_01.bin ABC_GENERIC_V_3_03_01.bin ABC_DF1_V_3_03_01.bin APP_ABC_MASTER_V_3_03_01_stamped.a37 APP_ABC_GENERIC_V_3_03_01_stamped.a37 APP_ABC_DF1_V_3_03_01_stamped.a37.
Created: Last saved by: Printed:
2013-11-25 Olof Helander 2015-02-19
HMS Industrial Networks AB
RELEASE INFORMATION
Project name Project No
ABC DF1, Master, Generic
- Current fieldbus interface (Anybus-S) modules included in this release
Fieldbus Interface module (Anybus-S) version
Fieldbus
Configuration file version
Software Software version
7061
Release date
Application
Version 3.03.01_A
2014-12-02
Updated in version 2.03: - New functionality
N/A
- Improved functionality
1.83 2.26 2.02 1.76 3.17 2.03 3.01 No configuration file used No configuration file used No configuration file used No configuration file used No configuration file used 1.02
N/A
- Bug fixes
RS485 does not work – The receiver was not disabled during transmission and this gave local echo of all transmitted data. The software now disables receive during transmission if RS485 is used. Internal ID: 0006311.
PROFINET IO –Leabharlann PROFINET IRT –
Reason for release:
Added support for PROFINET IRT and CC-Link IE. Bug fixes.
Supported hardware:
Application Firmware can be downloaded to ABC hardware with PCBs marked 3299. Bootloader BL_ABC_3_1.a37 (to be used with Flash Memory SST39SF010).
lengths could cause memory conflicts.