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.。
SMP 4.6 Release Notes说明书
SMP4.6Release NotesSMP4.6Release NotesCopyright©2012Alcatel-Lucent.All rights reserved.February2012New Features in SMP4.6 (1)RPC services (2)Workflow reporting (2)Documentation (2)Systems Requirements for SMP4.6 (2)Server runtime environment requirements (3)Configuration Manager requirements (6)Model Builder and Overlay Builder requirements (7)Motive Reporting application requirements (8)Motive Dashboard Console application requirements (8)Motive Workflows requirements (9)Known Issues in SMP4.6 (9)Customer Support for SMP4.6 (10)Support and contact information (10)Legal Notice (10)This document provides important information on SMP4.6,including its new features,systemrequirements,and known issues.New Features in SMP4.6SMP4.6,which is built on top of SMP4.4.6,provides the following new features:■RPC services■Workflow reporting1SMP4.6Release NotesRPC servicesThe RPC services feature uses XML-RPC to perform remote operations on other systems.Theseoperations are defined using an XML-RPC service definition file.This service definition file allows you to target any system that supports HTTP XML-RPC.You can define any number of XML-RPC servicefiles,add them to a configuration ZIP file,and publish them using the SMP Configuration Manager.Once published,you can use the RPC operations when building an SMP workflow.When the workflow is run,the RPC operations are sent to the intended target system.For example,the HomeView Activation template1.1uses the RPC services to perform operations on devices such as PCs and Macs.To route the operations to the specified endpoints,the EndpointCommunication System(ECS)is used.This RPC mechanism bypasses the need to create an SMP test module,model,and overlay. Workflow reportingThe workflow reporting capability is provided for multi-channel templates.Workflow reporting provides out-of-the-box workflow reports as well as the ability to create custom workflow reports using an XML report definition file.With reporting,you can perform analytics to help optimize ROI.Note:Oracle10g does not provide date range partitioning by default. DocumentationTo describe the new RPC services and workflow reporting features,the SMP Addenda:RPC Servicesand Workflow Reporting document is provided.For the remainder of the SMP documentation,please refer to the SMP4.4.1documentation. Systems Requirements for SMP4.6The Service Management Platform(SMP)is the software infrastructure that your team uses to model the hardware,software,and relationships on which specific subscriber services depend.■“Server runtime environment requirements”on page3❐“Solaris installations”on page32SMP4.6Release Notes❐“Red Hat Linux installations”on page5■“Configuration Manager requirements”on page6■“Model Builder and Overlay Builder requirements”on page7■“Motive Reporting application requirements”on page8❐“Motive Reporting server requirements”on page8❐“Motive Reporting Console requirements”on page8■“Motive Dashboard Console application requirements”on page8❐“Motive Dashboard Console server requirements”on page8❐“Motive Dashboard Console requirements”on page8■“Motive Workflows requirements”on page9❐“Motive Workflow Builder requirements”on page9❐“Motive Workflows server requirements”on page9❐“Motive Workflows runtime requirements”on page9Server runtime environment requirementsThe server runtime environment runs in an Oracle WebLogic Server domain that includes anAdministration Server and a cluster of one or more Managed Servers.Your team can opt to install the runtime environment in one of two primary ways:■In its own domain that the SMP installer creates(option1)Or■In an existing domain that may run other products in addition to SMP(option2)Either way,the server machines must comply with the applicable minimum hardware and softwarerequirements,depending on whether SMP is to run on a Solaris or Red Hat Linux operating system.Solaris installationsHostMinimum hardwareMinimum software3SMP4.6Release NotesSun Solaris 10including the latest patches Oracle VM Server for SPARC (formerly Sun Logical Domains)[/Sun SPARC Enterprise T5120Server with the following.For best practiceson scaling deployments,consult with Motive Customer Projects.Administration Server us/technologies/virtualization/oraclevm/oracle-vm-server-for-sparc-068923.html]if■1.2GHz UltraSPARC T2processor (with 8cores and 8threads per core)opting to create virtual machines on which to install SMP Sun Java Runtime Environment 1.6Oracle WebLogic Server 11gR1PS2(10.3.3)for SolarisThe applicable binary is provided on the SMPCD (wls1033_solaris32.bin ).Oracle Database Client (Enterprise Edition)10.2.0.3or 11.2The client version must match the server version running on the corresponding OLTP Database server.■8to 32GB RAM ■36GB disk spaceSun Solaris 10including the latest patches Oracle VM Server for SPARC (formerly Sun Logical Domains)[/Sun SPARC Enterprise T5120Server with the following.For best practices on scaling deployments,consult with Motive Customer Projects.Managed Serverus/technologies/virtualization/oraclevm/oracle-vm-server-for-sparc-068923.html]if■1.2GHz UltraSPARC T2processor (with 8cores and 8threads per core)opting to create virtual machines on which to install SMP Oracle WebLogic Server 11gR1PS2(10.3.3)for SolarisThe applicable binary is provided on the SMPCD (wls1033_solaris32.bin ).■8to 32GB RAM ■36GB disk spaceSun Solaris 10including the latest patches Oracle Database Server (Enterprise Edition)10.2.0.3or 11.2Middle-end to high-end systems with two to four system processors Note Depending on the expected size,load,and growth of the database,see OLTP Database Server Oracle system requirements or work with your Oracle consultant.Oracle Data Service Integrator (ODSI)10gR3(10.3)(formerly named AquaLogic Data Service Platform)See the Oracle Data Service Integrator 10gR3(10.3)[/docs/cd/Optional Integration ServerE13162_01/odsi/docs10gr3/index.html]documentation.See Using Web Server Plug-Ins with Oracle WebLogic Server [http://See the documentation for the applicable web server.Optional Web Server ProxySMP 4.6Release Notes4/docs/cd/E14571_01/web.1111/e14395/overview.htm#BABEJFHI].Red Hat Linux installationsMinimum softwareMinimum hardwareHostRed Hat Enterprise Linux 5.5Server 64-bit versionSun Java Runtime Environment 1.632-bit versionOracle WebLogic Server 11gR1PS2(10.3.3)for Linux 32-bit versionThe applicable binary is provided on the SMP CD (wls1033_linux32.bin ).Oracle Database Client (Enterprise Edition)10.2.0.3or 11.2The client version must match the server version running on the corresponding OLTP Database server.HP ProLiant DL360with the following.For best practices on scalingdeployments,consult with Motive Customer Projects.Administration Server ■Intel(R)Xeon(R)CPU E55062.13GHz1.2GHz (with 2CPUs and 4cores per CPU)■23.5GB RAM ■300GB disk spaceRed Hat Enterprise Linux 5.5Server 64-bit versionOracle WebLogic Server 11gR1PS2(10.3.3)for Linux 32-bit versionThe applicable binary is provided on the SMP CD (wls1033_linux32.bin ).HP ProLiant DL360with the following.For best practices on scalingdeployments,consult with Motive Customer Projects.Managed Server■Intel(R)Xeon(R)CPU E55062.13GHz1.2GHz (with 2CPUs and 4cores per CPU)■23.5GB RAM ■300GB disk spaceRed Hat Enterprise Linux 5.5Server 64-bit versionOracle Database Server (Enterprise Edition)10.2.0.3or 11.2Middle-end to high-end systems with two to four system processorsNoteDepending on the expected size,load,and growth of the database,see Oracle OLTP Database Server system requirements or work with your Oracle consultant.Oracle Data Service Integrator (ODSI)10gR3(10.3)(formerly named AquaLogic Data Service Platform)See the Oracle Data Service Integrator 10gR3(10.3)[http:///docs/cd/Optional Integration Server5SMP 4.6Release NotesE13162_01/odsi/docs10gr3/index.html]documentation.See Using Web Server Plug-Ins with Oracle WebLogic Server [http://See the documentation for the applicable web server.Optional Web Server Proxy/docs/cd/E14571_01/web.1111/e14395/overview.htm#BABEJFHI].Configuration Manager requirementsThe Configuration Manager is a browser-based interface in which your team defines the application and environment configurations for SMP deployments.■Application configuration .A versioned configuration that defines the settings and content instructions the server is to apply in the runtime environment,including its application properties and any role-based properties;user input definitions;result analyses;test modules;endpoint operations;workflow modules;test groups;startup test groups;and service policies.The active version of the application configuration is in effect.■Environment configuration .The configuration that defines the following:datasource connections;environment properties;execution auditing settings;licenses for SMP and SMP-based products;policies for southbound throttling,northbound throttling,and test module throttling;and system alerts.Related product documentation■Configuration Manager Help■In the following sections of the SMP Deployment Guide :❐"Managing the application configuration"❐"Managing the environment configuration"Minimum SoftwareMinimum HardwareSun Java Runtime Environment 6One of the following browser configurations:See documentation for the applicable operating system and web browser.■Microsoft Internet Explorer 7.0on Windows Vista or Windows XP with Service Pack 2■Microsoft Internet Explorer 8.0on Windows Vista or Windows 7SMP 4.6Release Notes6Model Builder and Overlay Builder requirementsThe Builders are desktop applications for creating service models and overlays.■A model is an abstract representation that defines an application configuration,which is the IT infrastructure (including hardware and software components,relationships and dependencies)of a mission-critical application or business process.Models establish general information about an application configuration and provide a reusable structure on which many business operations can be performed.■An overlay is built on top of an application model to evaluate a snapshot,which is a representation of the state of an application environment at a given time.The overlay is configured with a set of checks (conditions about a business issue)that determine the cause of problems and configuration issues.Each check is associated with one or more actions configured to address the issue.Minimum SoftwareMinimum HardwareHost One of the following operating systems:A PC with the following minimum specifications:Client■Microsoft Windows XP Professional with Service Pack 2■800MHz CPU clock speed■Microsoft Windows Vista HomeEnterprise Edition 32-bit with Service Pack 1(run in Administrator mode)■Intel or AMD compatible for applicable operating system ■512MB RAM■Sun Java Runtime Environment 1.6■1.5GB available hard-disk space■Oracle Database Client (Enterprise Edition)10.2.0.1or 11gThe client version must match the version running the Database.■Super VGA (800x600pixels)or higher resolution video adapter and monitor ■CD-ROM or DVD drive The Motive Product Group recommends using a system with a 1GHz CPU,1GB RAM ,and a 1024x768display.Oracle Database Server (Enterprise Edition)10.2.0.1or 11.2See the documentation for the applicableoperating system.Database 7SMP 4.6Release NotesMotive Reporting application requirementsMotive Reporting server requirementsMotive Reporting is an optional application for deployment on one or more of the Managed Servers in the server runtime environment.The reporting data is stored in the modeling schema on the OLTP database server.To ensure compliance with minimum server hardware and software,see Server runtime environment requirements on page 3.Motive Reporting Console requirementsThe Motive Reporting Console is web-based user interface for viewing and managing reports.The reports are generated against SMP data.Minimum SoftwareMinimum HardwareInternet Explorer 6.0or 7.0Note:JavaScript must be enabledSee documentation for the applicable operating system and web browser.Motive Dashboard Console application requirementsMotive Dashboard Console server requirementsMotive Dashboard Console is an additional feature application for deployment on one or more of the Managed Servers in the server runtime environment.The data is stored in the modeling schema on the OLTP database server.To ensure compliance with minimum server hardware and software,see Server runtime environment requirements on page 3.Motive Dashboard Console requirementsThe Motive Dashboard Console is web-based user interface for viewing system operation metrics.Minimum SoftwareMinimum HardwareInternet Explorer 6.0or 7.0Note:JavaScript must be enabledSee documentation for the applicable operating system and web browser.SMP 4.6Release Notes8Motive Workflows requirementsMotive Workflows is an additional feature including two main components,an engine and builder.Motive Workflow Builder requirementsThe Workflow Builder is web-based user interface for managing and authoring workflows.Minimum Software Minimum HardwareMozilla Firefox 3.6or laterSee documentation for the applicable operating system and web browser.Motive Workflows server requirementsMotive Workflow Engine and Workflow Builder are server applications for deployment on one or more of the Managed Servers in the server runtime environment.The workflow data is stored in the modeling schema on the OLTP database server.To ensure compliance with minimum server hardware and software,see Server runtime environment requirements on page 3.Motive Workflows runtime requirementsMinimum SoftwareMinimum HardwareContextInternet Explorer 7or 8See documentation for the applicable operating system and web browser.SMP-based web application such as the Customer Service Console iOS 4.0or Android 2.2See documentation for device.On a mobile deviceMozilla Firefox 3.6See documentation for the applicable operating system and web browser.In Motive WorkflowBuilder on page 9,the Motive Workflow Launcher (provided for testing workflows)Known Issues in SMP 4.6There are currently no known issues in this release.9SMP 4.6Release NotesCustomer Support for SMP4.6Support and contact informationIf you encounter issues with this product,visit the Online Customer Support(OLCS)[https://]website.After registering and logging on,you can access troubleshooting resources.In addition,you can contact Alcatel-Lucent Support as follows:Toll-free phone(within U.S.)1-866-582-3688,option1Outside U.S.+16137846100(United States)Alcatel-Lucent is interested in feedback about your experience with this product and its documentation.If you have comments or suggestions,send email to<***************>.Legal NoticeAlcatel,Lucent,Alcatel-Lucent,the Alcatel-Lucent logo,Motive,and the Motive logo are trademarksof Alcatel-Lucent.All other trademarks are the property of their respective owners.The informationpresented is subject to change without notice.Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.10SMP4.6Release Notes。
nextpad release note
各位，大家下午好。
欢迎各位百忙之中来现场参加这次在线的产品发布会活动，虽然这里说的是一个“产品”的发布会，但是按照产品的定义而言，下面要公布的也不能算是一个产品，因为它是没有价格的，也就是终生免费的一个产品（360？……）。
首先为了防止有人还不知道我是谁，我先自我介绍一下，我的GSDzone ID ， sataco ，目前担任 GSDzone 网站的主要负责人以及泛华测控院校产品部的负责人。
因此，从今年开始，我会在试图在中国工程教育这个领域做一些事情，希望能够真正实质性地助力培养更多未来的卓越工程师。
在本次产品发布会期间，你都可以回帖进行提问或者单纯的顶或踩，在发布会结束时会进行最后的抽奖活动，大奖将是一个以前从来没有发过的奖品，而且不是 GSDzone 的奖品，而是 next 的奖品，尽请期待。
下面，我将用类似意识流的方式给大家阐述一下这个产品 nextpad 的概念是如何形成的。
为了真正助力中国工程教育，我思考了很久，之后想到了有三个方向也许是我以后会奋斗的目标：一个就是在教学方面，目前在工程知识的教学上尚存在着很大的提升空间，很多概念和知识，现在还是通过老一套的纯公式推导或者板书的形式来进行教授，这种方式不利于学生能够真正理解透彻知识点，而且不生动，引不起学生的兴趣和求学欲望；第二个方向就是实验，图腾中那条白色的线指的是理论中所得到的结果，而黄色的线代表的是在实际情况中所得到的结果，你可以明显看出两条线是不一样的，这也代表着也许你理论学得很好，但是作为一个优秀的工程师，你必不可少地要和实际的系统或环境打交道，所以掌握你的理论知识的同时，你更需要的是通过实验来将理论与实践联系在一起，真正做到工程。
第三个方向就是创新，这个图腾也很好理解，每一个框代表的是一门学科，那么在这个方向，是要求同学们能够灵活地将各个学科的知识综合起来解决实际问题，例如你在大一大二可能学习了电工电子、机械原理等基础课程，那么在大三大四甚至研究生时就应该能够将这些基础学科综合起来，从而解决真正的问题。
ReleaseNote_EB8000V4.42
Version 4.4.2 2011/04/20新增功能功能][新增1. 支援TK6102i机型通讯串口只支持COM 1与COM 3, 且COM 3只支持RS485 2W通讯模式2. 新增系统保留地址LW-10750~10753用来修改HMI的Ethernet Mask地址在SetData与GetData等函式中, 在应使用array变量型态的参数使用一般变量时, 在编译时将出现警示讯息。
上图的例子因一次设定10 words的数据, 所以变量a应宣告为a[10], 且正确的语法应为：SetData(a[0], “Local HMI”, LW, 0, 10)3. Ethernet UDP通讯模式支持广播工能(PLC IP地址需设定为255:255:255:255)4. 选择使用MODBUS RTU驱动程序时, 用户可以设定[命令重送次数]。
当HMI对PLC发送命令后, 无法得到正常的响应时, HMI会尝试将此时的命令重新发送给PLC, 直至接收到正确的回复, 或重送次数等于设定值为止。
5. 提供[显示公共窗口上的元件在基本窗口]选项。
勾选此项功能后, 在使用EB8000的编辑模式时, 可以让公共窗口上的对象显示在一般窗口上。
6. 选择使用SIEMENS S7/300系列PLC时, 若数据选用32-bit 格式(例如32-bit BCD, 32-bitUnsigned/Signed, 32-bit Float)时, 若未选用DBDn地址类型(Device Type), 在编译工程档案时将出现警示讯息。
以上图为例, 此时选用32-bit Unsigned格式, 但地址类型选用的是DB0, 因此在编译工程档案后, 将出现如下图的警示讯息。
7. 新增支援BRIGHTTEK WH-E19打印机功能][修正修正功能1. 修正宏指令中的GetData与SetData等函数无法解译地址格式为16进制(例如HHH )的地址类型(Device Type), 例如：SetData(a[0], “Provisor TC200”, P, ffa, 2)其中”P”地址类型的地址格式为HHH, 参考下图：2. 修正宏指令中的GetData与SetData等函数在地址参数字段中无法辨识变量a (也就是将变量a误认为是16进制的数值)以上图的例子而言, 此时a应等于数值5, 而不是16 (= 0x0a)。
ReleaseNote_cn
E a s y B u i l d e r8000R e l e a s e N o t e[EB8000 版本命名规则]例如:EB8000 V.2.0.0第一位数 : 表示此版本所建立或开启过的工程档案,无法再使用旧版本开启第二位数 : 表示有新功能或新Driver开发第三位数 : 表示有修正BugsVersion 3.4.5 2010/4/28[新增功能]1. 更换PLC类型时, 对象会自动选择相同名称的装置类型(device type)2. 下载对话窗提供自动下载功能, EB8000在储存工程档案,并直接按下”下载”按键后,可以使用上一次的下载位置自动下载档案[修正功能]1. 修正MACRO中的函数若与GetData与SetData函数共享变量, 可能无法正常执行。
例如下面的使用例子：GetData(a, “PLC”, X, 0, 1)HIBYTE(a, b)此时变量b可能无法得到正确的运算结果2. 修正系统保留地址LB11960~11967无法在系统接收到干扰讯号时, 禁止”PLC NoResponse”窗口的出现3. 修正当某一站号的PLC无法通讯时, 会导致使用站号变量的对象也无法通讯4. 修正MACRO的sub function无法正确传送变量类型的参数, 例如在使用sub int func(char a, short b, short c), a得直无法被正确传递5. 修正MACRO的select case语法, 无法连续使用case-case, 例如下面例子的case 1与case2连续使用select case acase1case2b = 20breakcase3b = 30breakcase elseb = 50end select6. 修正MACR的INPORT函数INPORT(data[0], “Free Protocol”, 10, return_value)当发生timeout时, return_value将记录实际读取的byte数目, data也将存放读取的内容7. 修正在使用“Find”功能时若点击搜寻结果, 无法开启页面编号超过255的页面8. 修正使用备份对象时, 若备份动作尚未完成即拔除USD碟, 可能导致下一次无法进行备份动作9. 修正XY Plot的标示(Maker)无法使用绘点模式(Point)10. 修正 Direct Window的触发模式当选择使用”OFF”时, 在换页时可能无法消除已出现的Direct Window11. 修正当数据取样(Data Log)的清除功能(Clear)与趋势图的暂停功能(Hold)同时被触发使用时,可能造成趋势图不正常显示[新增驱动程序]1. 新增MITSUBISHI AJ 71 (Format 4)驱动程序2. 新增MODBUS RTU (0x/1x Range Adjustable) 驱动程序, 可以设定0x/1x的地址范围, 避免读写命令超出PLC允许读写的地址[驱动程序修改]1. 修正GE Fanuc 90-30驱动程序无法读取超过255的Bit地址2. PANASONIC FP 驱动程序新增FL, DT地址类型3. LS GLOFA Cnet驱动程序的IX, QX的bit地址范围修正为0~63Version 3.4.4a 2010/4/11[修正功能]12. 新增MITSUBISHI AJ 71 (Format 4)驱动程序13. 新增MODBUS RTU (0x/1x Range Adjustable) 驱动程序, 可以设定0x/1x的地址范围, 避免读写命令超出PLC允许读写的地址14. 修正GE Fanuc 90-30驱动程序无法读取超过255的Bit地址15. 修正系统保留地址LB11960~11967无法在系统接收到干扰讯号时, 禁止”PLC NoResponse”窗口的出现16. 修正当某一站号的PLC无法通讯时, 会导致使用站号变量的对象也无法通讯17. 修正MACR的INPORT函数INPORT(data[0], “Free Protocol”, 10, return_value)当发生timeout时, return_value将记录实际读取的byte数目, data也将存放读取的内容Version 3.4.4 2010/4/7[修正功能]1. 修正宏指令的数值运算无法正确操作属于char型态的变量2. 修正宏指令的浮点数运算3. 修正使用Master-Slave模式时, Master端在与PLC断线并重新连结时, Slave端无法与Master端恢复通讯4. 修正当宏指令中使用过多非ASCII字符的注释时, 有时无法正确执行反编译功能5. 修正使用Office 2007所产生的EXCEL档案无法汇入到文字库(Label Library)与Event Log中[驱动程序修改]3. 修正YASKAWA SMC 3010(Ethernet)驱动程序, 新增D_array, R_array, D_arr_bit地址类型4. 修正YASKAWA SMC 3010驱动程序, 新增D_array, R_array, D_arr_bit地址类型Version 3.4.3 2010/3/30[修正功能]6.修正宏指令的SetData函数无法一次传送超过256 words的数据7.修正宏指令的数学运算功能无法计算超过20000000的数值8.修正Memory Map协议无法同时处理master与slave模式9.修正PLC控制对象的打印功能无法使用远程备份/打印服务器10.修正数据传输(Data Transfer)无法传送数据到远程HMI11.使用S7-300 MPI driver 时, 无法同时使用CP343 Ethernet 装置12.宏指令有时使用中文注释会造成内容混亂13.三菱FX 3U 驱动程序加上噪声过濾功能14.修正EasyConverter.exe 无法正确转换超过99999 的數值[新增功能]1.宏指令新增select命令的通讯速度支持1200与2400 baud rate[驱动程序修改]5.修正OMRON_CJ1驱动程序无法读取EM地址6.修正HITACHI Series驱动程序无法读写Y地址Version 3.4.2 2010/3/18[修正功能]1.HMI长时间的运作可能出现的黑屏问题2.Data transfer对象如果传递远程PLC上的数据到本地HMI上, 可能出现黑屏的问题3.修正PLC Control的hardcopy无法使用的问题4.修正在向量图库的圆形无法完整显示的问题[新增驱动程序]1. Panasonic FP2 (Ethernet)FP2+ET1网络模块Version 3.4.1 2010/3/4[新增功能]3. 宏指令支持select-case语法, 下面为简单的使用范例select case acase1b = 10breakcase2b = 20breakcase elseb = 50end selectselect-case的用法必须使用 select case作为起始, 接着连接一个变量, 用来判断哪个条件式成立, 最后使用end select作为结尾, 如下：select case [variable][条件式 1][条件式 2]…..[条件式 n]case else…. // 当所有的条件式皆不成立时, 将执行此处的内容breakend select[条件式]使用case当起始, 接着连接一个常数, 最后使用case当结尾, 如下：case [constant][执行内容]break当[variable]等于[constant]时, 将执行该[条件式]下的[执行内容]当[variable]不等于所有的[constant]时, 将执行case else中的[执行内容]以上面的例子而言, 当a等于1时, b将等于10；当a等于2时, b将等于20；当a既不等于1也不等于2时, 将执行case else中的内容, 也就是b将等于504. 宏指令的HIIBYTE, LOBYTE, HIWORD, LOWORD, SQRT等数学运算函数支持使用array变量, 例如：for i = 0 to 10HIBYTE(a[i], b[i])next[修正功能]15. 修正当装置断线并重连后, 宏指令的INPORT函数无法正常使用16. 修正在某些情况下因装置断线而导致HMI的运行不正常17. 修正SIEMENS S7/300 MPI驱动程序无法支持主从协议[驱动程序修改]7. MITSUBISHI_FX3U驱动程序新增Z地址类型8. 修正恢复MITSUBISHI_FX3U驱动和X系列人机通讯9. 修改SCHLEICHER XCS 20C的地址类型排列顺序10. 修正OMRON CJ1 Ethernet驱动无法连接多台人机11. 修正KOYO CLICK 无法正确读写DD与DF地址12. 修正Panasonic FP (Ethernet) AFPX_COM5无法通讯13. MITSUBISHI AJ71 driver配合A CPU修正protocol.Version 3.4.0 2010/2/10[新增功能]1. 宏指令新增PURGE命令, 用来清除 COM端口中的数据2. 新增LW9576, 用来累积MODBUS TCP/IP Server收到的资料数目3. MODBUS Server可以设定使用[Turn around delay]4. [文字卷标库]提供排序功能5. 用户可以选择工程档案所需使用的语言数目当语言数目小于8时, 对象的文字卷标如果选用多国语言功能时, 对象的状态数可以设定超过32 (在 EB8000中, 对象所使用的语言数目乘上状态个数不得超过256)6. 对象的文字卷标提供[Bitmap font]选项, 可以用来显示波斯文等特殊字体, 或是改善小字型文字的显示效果, 或是显示原来HMI不支持显示的字型7. [事件登录]对话窗提供”插入”(insert), “复制”(copy), “贴上”(paste)等功能, 也提供排序功能和右键功能选单8. 对象若勾选使用系统缓存器, 如果使用多重复制功能时，地址将自动自动累加9. Trend Display对象可以自由选择要显示的信道(channel)10. 在[系统设定]的[密码](Security)设定页中, 新增工程档案密码保护功能当工程档案设定使用此功能时, 在开启档案前需先输入正确的密码, 档案才能被开启。
Git ReleaseNotes
Git Release Notes (Git-1.7.4-preview20110204)Last update: 4 February 2011IntroductionThese release notes describe issues specific to the Git for Windows release.General release notes covering the history of the core git commands are included in the subdirectory doc/git/html of the installation directory. Look for files starting with RelNotes.See / for further details about Git including ports to other operating systems. Git for Windows is hosted at /.Known issues∙Some commands are not yet supported on Windows and excluded from the installation;namely: git archimport, git cvsexportcommit, git cvsimport, git cvsserver, git instaweb, git shell.∙The Logitec QuickCam software can cause spurious crashes. See "Why does make often crash creating a sh.exe.stackdump file when I try to compile my source code?" on theMinGW Wiki (/wiki/Environment_issues)∙The Quick Launch icon will only be installed for the user running setup (typically the Administrator). This is a technical restriction and will not change.∙curl uses $HOME/_netrc instead of $HOME/.netrc.∙If you want to specify a different location for --upload-pack, you have to start the absolute path with two slashes. Otherwise MSys will mangle the path.∙git and bash have serious problems with non-ASCII file names (Issue 80, 159).∙If configured to use plink, you will have to connect with putty first and accept the host key.∙As merge tools are executed using the MSys bash, options starting with "/" need to be handled specially: MSys would interpret that as a POSIX path, so you need to double the slash (Issue 226). Example: instead of "/base", say "//base". Also, extra care has to be paid to pass Windows programs Windows paths, as they have no clue about MSys style POSIX paths -- You can use something like $(cmd //c echo "$POSIXPATH").Changes since Git-1.7.3.2-preview20101025New Features∙Comes with Git 1.7.4 plus patches.∙Includes antiword to enable viewing diffs of .doc files∙Includes poppler to enable viewing diffs of .pdf files∙Removes cygwin paths from the bash shell PATHBugfixes∙Please refer to the release notes for official Git 1.7.4Changes since Git-1.7.3.1-preview20101002New Features∙Comes with Git 1.7.3.2 plus patches.Changes since Git-1.7.2.3-preview20100911New Features∙Comes with Git 1.7.3.1 plus patches.∙Updated to Vim 7.3, file-5.04 and InnoSetup 5.3.11Bugfixes∙Issue 528 (remove uninstaller from Start Menu) was fixed∙Issue 527 (failing to find the certificate authority bundle) was fixed∙Issue 524 (remove broken and unused sdl-config file) was fixed∙Issue 523 (crash pushing to WebDAV remote) was fixedChanges since Git-1.7.1-preview20100612New Features∙Comes with Git 1.7.2.3 plus patches.Bugfixes∙Issue 519 (build problem with compat/regex/regexec.c) was fixed∙Issue 430 (size of panes not preserved in git-gui) was fixed∙Issue 411 (git init failing to work with CIFS paths) was fixed∙Issue 501 (failing to clone repo from root dir using relative path) was fixedChanges since Git-1.7.0.2-preview20100309New Features∙Comes with Git 1.7.1 plus patches.Bugfixes∙Issue 27 (git-send-mail not working properly) was fixed again∙Issue 433 (error while running git svn fetch) was fixed∙Issue 427 (Gitk reports error: "couldn't compile regular expression pattern: invalid repetition count(s)") was fixed∙Issue 192 (output truncated) was fixed again∙Issue 365 (Out of memory? mmap failed) was fixed∙Issue 387 (gitk reports "error: couldn't execute "git:" file name too long") was fixed∙Issue 409 (checkout of large files to network drive fails on XP) was fixed∙Issue 428 (The return value of git.cmd is not the same as git.exe) was fixed∙Issue 444 (Git Bash Here returns a "File not found error" in Windows 7 Professional - 64 bits) was fixed∙Issue 445 (git help does nothing) was fixed∙Issue 450 ("git --bare init" shouldn't set the directory to hidden.) was fixed∙Issue 456 (git script fails with error code 1) was fixed∙Issue 469 (error launch wordpad in last netinstall) was fixed∙Issue 474 (git update-index --index-info silently does nothing) was fixed∙Issue 482 (Add documentation to avoid "fatal: $HOME not set" error) was fixed∙Issue 489 (git.cmd issues warning if %COMSPEC% has spaces in it) was fixed∙Issue 436 ("mkdir : No such file or directory" error while using git-svn to fetch or rebase) was fixed∙Issue 440 (Uninstall does not remove cheetah.) was fixed∙Issue 441 (Git-1.7.0.2-preview20100309.exe installer fails with unwritable msys-1.0.dll when ssh-agent is running) was fixedChanges since Git-1.6.5.1-preview20091022New Features∙Comes with official Git 1.7.0.2.∙Comes with Git-Cheetah (on 32-bit Windows only, for now).∙Comes with connect.exe, a SOCKS proxy.∙Tons of improvements in the installer, thanks to Sebastian Schuberth.∙On Vista, if possible, symlinks are used for the built-ins.∙Features Hany's dos2unix tool, thanks to Sebastian Schuberth.∙Updated Tcl/Tk to version 8.5.8 (thanks Pat Thoyts!).∙By default, only .git/ is hidden, to work around a bug in Eclipse (thanks to Erik Faye-Lund). Bugfixes∙Fixed threaded grep (thanks to Heiko Voigt).∙git gui was fixed for all kinds of worktree-related failures (thanks Pat Thoyts).∙git gui now fully supports themed widgets (thanks Pat Thoyts and Heiko Voigt).∙Git no longer complains about an unset RUNTIME_PREFIX (thanks Johannes Sixt).∙git gui can Explore Working Copy on Windows again (thanks Markus Heidelberg).∙git gui can create shortcuts again (fixes issue 425, thanks Heiko Voigt).∙When "git checkout" cannot overwrite files because they are in use, it will offer to try again, giving the user a chance to release the file (thanks Heiko Voigt).∙Ctrl+W will close gitk (thanks Jens Lehmann).∙git gui no longer binds Ctrl+C, which caused problems when trying to use said shortcut for the clipboard operation "Copy" (fixes issue 423, thanks Pat Thoyts).∙gitk does not give up when the command line length limit is reached (issue 387).∙The exit code is fixed when Git.cmd is called from cmd.exe (thanks Alexey Borzenkov).∙When launched via the (non-Cheetah) shell extension, the window icon is now correct (thanks Sebastian Schuberth).∙Uses a TrueType font for the console, to be able to render UTF-8 correctly.∙Clarified the installer's line ending options (issue 370).∙Substantially speeded up startup time from cmd unless NO_FSTAB_THREAD is set (thanks Johannes Sixt).∙Update msys-1.0.dll yet again, to handle quoted parameters better (thanks Heiko Voigt).∙Updated cURL to a version that supports SSPI.∙Updated tar to handle the pax headers generated by git archive.∙Updated sed to a version that can handle the filter-branch examples.∙.git* files can be associated with the default text editor (issue 397).Changes since Git-1.6.4-preview20090729New Features∙Comes with official git 1.6.5.1.∙Thanks to Johan 't Hart, files and directories starting with a single dot (such as '.git') will now be marked hidden (you can disable this setting with core.hideDotFiles=false in your config) (Issue 288).∙Thanks to Thorvald Natvig, Git on Windows can simulate symbolic links by using reparse points when available. For technical reasons, this only works for symbolic links pointing to files, not directories.∙ A lot of work has been put into making it possible to compile Git's source code (the part written in C, of course, not the scripts) with Microsoft Visual Studio. This work is ongoing. ∙Thanks to Sebastian Schuberth, we only offer the (Tortoise)Plink option in the installer if the presence of Plink was detected and at least one Putty session was found..∙Thanks to Sebastian Schuberth, the installer has a nicer icon now.∙Some more work by Sebastian Schuberth was done on better integration of Plink (Issues 305 & 319).Bugfixes∙Thanks to Sebastian Schuberth, git svn picks up the SSH setting specified with the installer (Issue 305).Changes since Git-1.6.3.2-preview20090608New Features∙Comes with official git 1.6.4.∙Supports https:// URLs, thanks to Erik Faye-Lund.∙Supports send-email, thanks to Erik Faye-Lund (Issue 27).∙Updated Tcl/Tk to version 8.5.7, thanks to Pat Thoyts.Bugfixes∙The home directory is now discovered properly (Issues 108 & 259).∙IPv6 is supported now, thanks to Martin Martin Storsjö (Issue 182).Changes since Git-1.6.3-preview20090507New Features∙Comes with official git 1.6.3.2.∙Uses TortoisePlink instead of Plink if available.Bugfixes∙Plink errors out rather than hanging when the user needs to accept a host key first (Issue96).∙The user home directory is inferred from $HOMEDRIVE\$HOMEPATH instead of $HOME (Issue 108).∙The environment setting $CYGWIN=tty is ignored (Issues 138, 248 and 251).∙The "ls" command shows non-ASCII filenames correctly now (Issue 188).∙Adds more syntax files for vi (Issue 250).∙$HOME/.bashrc is included last from /etc/profile, allowing .bashrc to override all settings in /etc/profile (Issue 255).∙Completion is case-insensitive again (Issue 256).∙The "start" command can handle arguments with spaces now (Issue 258).∙For some Git commands (such as "git commit"), vi no longer "restores" the cursor position. Changes since Git-1.6.2.2-preview20090408New Features∙Comes with official git 1.6.3.∙Thanks to Marius Storm-Olsen, Git has a substantially faster readdir() implementation now. ∙Marius Storm-Olsen also contributed a patch to include nedmalloc, again speeding up Git noticably.∙Compiled with GCC 4.4.0Bugfixes∙Portable Git contains a README.portable.∙Portable Git now actually includes the builtins.∙Portable Git includes git-cmd.bat and git-bash.bat.∙Portable Git is now shipped as a .7z; it still is a self-extracting archive if you rename it to .exe.∙Git includes the Perl Encode module now.∙Git now includes the filter-branch tool.∙There is a workaround for a Windows 7 regression triggering a crash in the progress reporting (e.g. during a clone). This fixes issues 236 and 247.∙gitk tries not to crash when it is closed while reading references (Issue 125, thanks Pat Thoyts).∙In some setups, hard-linking is not as reliable as it should be, so we have a workaround which avoids hard links in some situations (Issues 222 and 229).∙git-svn sets core.autocrlf to false now, hopefully shutting up most of the git-svn reports. Changes since Git-1.6.2.1-preview20090322New Features∙Comes with official git 1.6.2.2.∙Upgraded Tcl/Tk to 8.5.5.∙TortoiseMerge is supported by mergetool now.∙Uses pthreads (faster garbage collection on multi-core machines).∙The test suite passes!Bugfixes∙Renaming was made more robust (due to Explorer or some virus scanners, files could not be renamed at the first try, so we have to try multiple times).∙Johannes Sixt made lots of changes to the test-suite to identify properly which tests should pass, and which ones cannot pass due to limitations of the platform.∙Support PAGERs with spaces in their filename.∙Quite a few changes were undone which we needed in the olden days of msysGit.∙Fall back to / when HOME cannot be set to the real home directory due to locale issues (works around Issue 108 for the moment).Changes since Git-1.6.2-preview20090308New Features∙Comes with official git 1.6.2.1.∙ A portable application is shipped in addition to the installer (Issue 195).∙Comes with a Windows-specific mmap() implementation (Issue 198).Bugfixes∙ANSI control characters are no longer shown verbatim (Issue 124).∙Temporary files are created respecting core.autocrlf (Issue 177).∙The Git Bash prompt is colorful again (Issue 199).∙Fixed crash when hardlinking during a clone failed (Issue 204).∙An infinite loop was fixed in git-gui (Issue 205).∙The ssh protocol is always used with plink.exe (Issue 209).∙More vim files are shipped now, so that syntax highlighting works.Changes since Git-1.6.1-preview20081225New Features∙Comes with official git 1.6.2.∙Comes with upgraded vim 7.2.∙Compiled with GCC 4.3.3.∙The user can choose the preferred CR/LF behavior in the installer now.∙Peter Kodl contributed support for hardlinks on Windows.∙The bash prompt shows information about the current repository.Bugfixes∙If supported by the file system, pack files can grow larger than 2gb.∙Comes with updated msys-1.0.dll (should fix some Vista issues).∙Assorted fixes to support the new libexec/git-core/ layout better.∙Read-only files can be properly replaced now.∙git-svn is included again (original caveats still apply).∙Obsolete programs from previous installations are cleaned up.Changes since Git-1.6.0.2-preview20080923New Features∙Comes with official git 1.6.1.∙Avoid useless console windows.∙Installer remembers how to handle PATH.Changes since Git-1.6.0.2-preview20080921Bugfixes∙ssh works again.∙'git add -p' works again.∙Various programs that aborted with 'Assertion failed: argv0_path' are fixed. Changes since Git-1.5.6.1-preview20080701Removed Features∙git svn is excluded from the end-user installer (see Known Issues).New Features∙Comes with official git 1.6.0.2.Bugfixes∙No Windows-specific bugfixes.Changes since Git-1.5.6-preview20080622New Features∙Comes with official git 1.5.6.1.Bugfixes∙Includes fixed msys-1.0.dll that supports Vista and Windows Server 2008 (Issue 122). ∙cmd wrappers do no longer switch off echo.Changes since Git-1.5.5-preview20080413New Features∙Comes with official git 1.5.6.∙Installer supports configuring a user provided plink (PuTTY).Bugfixes∙Comes with tweaked msys-1.0.dll to solve some command line mangling issues.∙cmd wrapper does no longer close the command window.∙Programs in the system PATH, for example editors, can be launched from Git without specifying their full path.∙"git stash apply stash@{1}" works.∙Comes with basic ANSI control code emulation for the Windows console to avoid wrapping of pull/merge's diffstats.∙Git correctly passes port numbers to PuTTY's plinkChanges since Git-1.5.4-preview20080202New Features∙Comes with official git 1.5.5.∙core.autocrlf is enabled (true) by default. This means git converts to Windows line endings (CRLF) during checkout and converts to Unix line endings (LF) during commit. This is the right choice for cross-platform projects. If the conversion is not reversible, git warns the user.The installer warns about the new default before the installation starts.∙The user does no longer have to "accept" the GPL but only needs to press "continue".∙Installer deletes shell scripts that have been replaced by builtins. Upgrading should be safer. ∙Supports "git svn". Note that the performance might be below your expectation.Bugfixes∙Newer ssh fixes connection failures (issue 74).∙Comes with MSys-1.0.11-20071204. This should solve some "fork: resource unavailable"issues.∙All DLLs are rebased to avoid problems with "fork" on Vista.Changes since Git-1.5.3.6-preview20071126New Features∙Comes with official git 1.5.4.∙Some commands that are not yet suppoted on Windows are no longer included (see Known Issues above).∙Release notes are displayed in separate window.∙Includes qsort replacement to improve performance on Windows 2000.Bugfixes∙Fixes invalid error message that setup.ini cannot be deleted on uninstall.∙Setup tries harder to finish the installation and reports more detailed errors.∙Vim's syntax highlighting is suitable for dark background.Changes since Git-1.5.3.5-preview20071114New Features∙Git is included in version 1.5.3.6.∙Setup displays release notes.Bugfixes∙pull/fetch/push in git-gui works. Note, there is no way for ssh to ask for a passphrase or for confirmation if you connect to an unknown host. So, you must have ssh set up to workwithout passphrase. Either you have a key without passphrase, or you started ssh-agent.You may also consider using PuTTY by pointing GIT_SSH to plink.exe and handle your ssh。
ACS6000 LXEB Release Note
ABB Switzerland Ltd.ACS 6000MainINT FirmwareRelease NotesAuthor:18.12.13 / M. Studer approved:18.12.13 / O. ScheussDepartement:ATDD Based on:-Language Rev.PagesNOTICEThe information in this document is subject to change without notice and should not be construed, as a commitment by ABB Switzerland Ltd. ABB Switzerland Ltd assumes no responsibility for any errors that may appear in this document. In no event shall ABB Switzerland Ltd be liable for direct, indirect, special, incidental, or consequential damages of any nature or kind arising from the use of this document, nor shall ABB Switzerland Ltd be liable for incidental or consequential damages arising from use of any software or hardware described in this document.This document and parts thereof must not be reproduced or copied without ABB Switzerland Ltd’s written permission, and the contents thereof must not be imparted to a third party nor be used for any unauthorized purpose.NOTICE (2)CHAPTER 1INTRODUCTION (5)1.1Purpose of this document (5)CHAPTER 2SUMMARIZED RELEASE INFORMATION (6)2.1Changes from Release LXEB4300 Build 6 to LXEB4310 Build 0 (6)2.1.1Changed Features (6)2.1.2New Features (6)2.1.3Bug Fixes (6)2.2Changes from Release Version LXEB4210 Build 0 to LXEB4300Build 6 (6)2.2.1Changed Features (6)2.2.2New Features (6)2.2.3Bug Fixes (6)2.3Changes from Release Version LXEB4200 Build 0 to LXEB4210Build 0 (7)2.3.1Changed Features (7)2.3.2New Features (7)2.3.3Bug Fixes (7)2.4Changes from Release Version LXEB4100 Build 0 to LXEB4200Build 0 (7)2.4.1Changed Features (7)2.4.2New Features (7)2.4.3Bug Fixes (7)2.5Changes from Release Version LXEB4000 Build 1 to LXEB4100Build 0 (8)2.5.1Changed Features (8)2.5.2New Features (8)2.5.3Bug Fixes (8)2.6Changes from Release Version LXEB3xxx to LXEB4000 Build 1 (8)CHAPTER 3DETAILED RELEASE INFORMATION (9)3.1Changes from Release LXEB4300 Build 6 to LXEB4310 Build 0 (9)3.1.1Changed Features (9)3.1.2New Features (9)3.1.3Bug Fixes (9)3.2Changes from Release Version LXEB4210 Build 0 to LXEB4300Build 4 (9)3.2.1Changed Features (9)3.2.2New Features (9)3.2.3Bug Fixes (10)3.3Changes from Version LXEB4200 Build 0 to LXEB4210 Build 0 (10)3.3.1Changed Features (10)3.3.2New Features (10)3.3.3Bug Fixes (10)3.4Changes from Version LXEB4100 Build 0 to LXEB4200 Build 0 (11)3.4.1Changed Features (11)3.4.2New Features (11)3.4.3Bug Fixes (11)3.5Changes from Version LXEB4000 Build 1 to LXEB4100 Build 0 (11)3.5.1Changed Features (11)3.5.2New Features (11)3.5.3Bug Fixes (11)3.6Changes from Version LXEB3xxx to LXEB4000 Build 1 (12)CHAPTER 4COMPATIBILITY (13)4.1Version LXEB4300 Build 6 (13)CHAPTER 5REFERENCES (14)CHAPTER 6GENERAL COMMISSIONINGINFORMATION (15)6.1How to Program the Firmware (15)6.1.1Requirements (15)6.1.2Downloading (15)CHAPTER 7BUILD INFORMATION (16)7.1Implementation/Synthesis Tool Versions (16)7.2Xilinx ISE 12.4 Build Design Summary (16)7.3Flash File Checksums (18)Chapter 1 Introduction1.1 Purpose of this documentThis document describes the changes included in the new ACS 6000 MainINT(previously PUBPFF) firmware.Chapter 2 Summarized Release Information2.1 Changes from Release LXEB4300 Build 6 to LXEB4310Build 02.1.1Changed FeaturesChanged FeaturesSSI encoder interface extension to 16 bits2.1.2New FeaturesNew Featuresnone2.1.3Bug FixesBug Fixesnone2.2 Changes from Release Version LXEB4210 Build 0 toLXEB4300 Build 62.2.1Changed FeaturesChanged FeaturesSwitch position comparison for quadruple configurations2.2.2New FeaturesNew FeaturesPUB_parallel mode2.2.3Bug FixesBug FixesLink Fault in Case of Load Balancing2.3 Changes from Release Version LXEB4200 Build 0 toLXEB4210 Build 02.3.1Changed FeaturesChanged FeaturesNone2.3.2New FeaturesNew FeaturesNone2.3.3Bug FixesBug FixesPPCC_RXFailed Timing Constraints2.4 Changes from Release Version LXEB4100 Build 0 toLXEB4200 Build 02.4.1Changed FeaturesChanged FeaturesNone2.4.2New FeaturesNew FeaturesPPCC Link AD Data of all INT boards available to AMC2.4.3Bug FixesBug FixesNone2.5 Changes from Release Version LXEB4000 Build 1 toLXEB4100 Build 02.5.1Changed FeaturesChanged FeaturesNone2.5.2New FeaturesNew FeaturesArc Detection via EOI Board2.5.3Bug FixesBug FixesNone2.6 Changes from Release Version LXEB3xxx to LXEB4000Build 1New MainINT concept (including new PFF link)Chapter 3 Detailed Release Information3.1 Changes from Release LXEB4300 Build 6 to LXEB4310Build 03.1.1Changed FeaturesChanged FeaturesThe SSI-clock frequency used to be set to 187.5kHz which allowed a data transmission rate of 13bits per 100µs. In order to increase the transmission rate to 16bits per 100µs, the SSI-clock is now set to 220kHz.3.1.2New FeaturesNew Featuresnone3.1.3Bug FixesBug Fixesnone3.2 Changes from Release Version LXEB4210 Build 0 toLXEB4300 Build 43.2.1Changed FeaturesSwitch position comparison for quadruple configurationsIn case of a quadruple INU configuration (applicable for DBC configurations), the switch position comparison is no longer made over all four INUs. Now only the switch positions of INU0 and INU1 as well as the switch positions of INU2 and INU3 are compared. This is necessary for the Semi Master+ and Semi Slave+ with DCB_QUAD configurations, since all four INT boards (and their links) are enabled but only the slave respectively the master side is modulating.Work Item [#]None3.2.2New FeaturesPUB_parallel modeThe PUB_parallel module acts as a bridge between the AMC3 board and up to 4 INT boards using a mixture of parallel interface (copper cable, direction AMC) and PPCC (serial, direction ARU/INU INT board) communication links. Please refer to the respecting technical documentation [2] in order to adjust the system with the required copper cable / fiber optic connections.Communications between the AMC34 board and the PUB_parallel module are carried by a parallel (copper cable) interface. This allows very fast communication (up to ~400 Mbit/s) and therefore removes some of the communication challenges faced by the PUB_serial module. The PUB_parallel module is disabled by default and can be enabled by setting the PUB_PAR_EN bit.Work Item [#]114233.2.3Bug FixesLink Fault in Case of Load BalancingIn case of active load balancing (used for hard parallel operation) the PPCC reset command to INU-INT boards was not forwarded correctly and thus ignored.This resulted in a tripped state of the AMC which could never be reset.Work Item [#]176483.3 Changes from Version LXEB4200 Build 0 to LXEB4210Build 03.3.1Changed FeaturesNone3.3.2New FeaturesNone3.3.3Bug FixesPPCC_RXA bug in the PPCC communication handling has been fixed. Before a communication fault could have been indicated without real fault.Work Item [#]13216Failed Timing ConstraintsFixed failed timing constraints in SSI Encoder instance.Manually added clock buffer for generated SSI encoder instance clock.Work Item[#]150533.4 Changes from Version LXEB4100 Build 0 to LXEB4200Build 03.4.1Changed FeaturesNone3.4.2New FeaturesPPCC Link AD Data of all INT boards available to AMCAll AD data coming via the PPCC Links A/B from the INU-/ARU-INT boards 1-4 has been put into the parallel link interface. This make it possible that the AMC can access all information of all INU-/ARU-INT boards at any time.Work Item [#]3.4.3Bug FixesNone3.5 Changes from Version LXEB4000 Build 1 to LXEB4100Build 03.5.1Changed FeaturesNone3.5.2New FeaturesArc Detection via EOI BoardIt is now possible to connect an arc detection device via the EOI board (UF C912 A, for details please refer to 3BHS359873 E02) to the optical input A530 on the MainINT (previously PUBPFF). When an arc is detected, the MainINT initiates (provided that the corresponding parameter in the Ctrl. SW is activated) a firing through. The communication to the EOI board provides link fault detection to prevent unwanted firing throughs in case of link problems. Note: This feature is only supported in SD Ctrl. SW versions above LSOI600D and AD Ctrl. SW versions above LAOI600C.Work Item [#]74253.5.3Bug FixesNone3.6 Changes from Version LXEB3xxx to LXEB4000 Build 1New MainINT2concept·Includes new PFF concept·Requires parallel link (X1200) to be connected to AMC·Only compatible with (INU/ARU) INT2 Boards and Ctrl. SW versions starting from LSOI600x and LAOI600x.Note: See also [1] for more information on the new MainINT/PFF concept.Work Item [#]1134.1 Version LXEB4300 Build 6Target Version ment AMC34SD SW Version AD SW Version >=LSOI600x Note: Arc Detection functionality not yetsupported in LSOI600D>=LAOI600x Note: Arc Detection functionality not yetsupported in LAOI600CChapter 4 CompatibilityChapter 5 References[1]ACS 6000 INT2 new PFF Specification.docx [$/ACS 6000/Documents/ACS6000 Common/Concepts/ACS 6000 INT2 new PFF Specification.docx]P.Bohren, ATDD2, 2011-01-05[2]ACS 6000 INT2 MainINT Technical Description[$/ACS6000/Documents/ACS 6000 Common/Concepts/ACS6000 INT2 MainINTTechnical Description LXEB.docx]ATDD, rev. 272406.1 How to Program the Firmware6.1.1RequirementsA PC with ‘Xilinx ISE Design Suite' installed.Xilinx JTAG Programmer.Programming files: int2pubpff_0.mcs, int2pubpff_1.mcsScript files: LXEBxxxx.cmd and PROG_LXEB.batAlways switch off the gate units to guarantee that no IGCT canswitch during the programming of the EPCs.Never operate the drive with invalid FPGA configuration, e.g.-Failed verification after downloading-Downloading of not matching int2pubpff_0.mcs andint2pubpff_1.mcs6.1.2DownloadingRun the PROG_LXEB.bat batch file to flash the firmware to the board. Chapter 6 General Commissioning Information7.1 Implementation/Synthesis Tool VersionsTool VersionSynplify8.6.2Xilinx ISE12.47.2 Xilinx ISE 12.4 Build Design Summaryint2_gpp_int Project Status (10/17/2014 - 14:20:56) Project File:int2pubpff.xise Parser Errors:No ErrorsModule Name:int2_gpp_int Implementation State:Programming File GeneratedTarget Device:xc3s1600e-4fg320·Errors:No ErrorsProduct Version:ISE 12.4·Warnings:674 Warnings (0new, 322 filtered)Design Goal:TimingPerformance·RoutingResults:All SignalsCompletely RoutedDesign Strategy:SmartXplorer -mapuseioreg·TimingConstraints:All ConstraintsMetEnvironment:System Settings·Final TimingScore:0(Timing Report)Device Utilization Summary[-] Logic Utilization Used Available Utilization Note(s)Number of Slice Flip Flops10,34729,50435%Number of 4 input LUTs17,35729,50458%Number of occupied Slices11,69714,75279%Number of Slices containing onlyrelated logic11,69711,697100% Number of Slices containingunrelated logic011,6970% Total Number of 4 input LUTs17,49529,50459%Number used as logic16,247Chapter 7 Build InformationNumber used as a route-thru138Number used as 16x1 ROMs672Number used for Dual Port RAMs352Number used as Shift registers86Number of bonded IOBs15825063%IOB Flip Flops1Number of RAMB16s203655%Number of BUFGMUXs52420%Number of DCMs3837%Number of MULT18X18SIOs83622%Average Fanout of Non-Clock Nets 3.60Performance Summary[-]Final Timing Score:0 (Setup: 0, Hold: 0, ComponentSwitching Limit: 0)PinoutData:Pinout ReportRouting Results:All Signals Completely Routed ClockData:Clock ReportTimingConstraints:All Constraints MetDetailed Reports[-] Report Name Status Generated Errors Warnings Infos Synthesis ReportTranslation Report CurrentFr 17. Okt12:56:46 20141 Warning (0new, 0 filtered)8 Infos (2 new,0 filtered)Map Report Current Fr 17. Okt13:28:08 2014322 Warnings (0new, 0 filtered)11 Infos (0 new,0 filtered)Place and Route Report CurrentFr 17. Okt13:35:43 201429 Warnings (0new, 0 filtered)1 Info (0 new, 0filtered)Power ReportPost-PAR Static Timing Report CurrentFr 17. Okt13:36:28 2014005 Infos (0 new,0 filtered)Bitgen Report Current Fr 17. Okt14:20:50 2014322 Warnings (0new, 322filtered)3 Infos (0 new,0 filtered) Secondary Reports[-]Report Name Status Generated SmartXplorer Report Current Fr 17. Okt 13:37:30 2014WebTalk Report Current Fr 17. Okt 14:20:51 2014 WebTalk Log File Current Fr 17. Okt 14:20:56 2014Date Generated: 10/17/2014 - 14:20:567.3 Flash File ChecksumsFlash File Checksumint2pubpff_0.mcs0x01307085int2pubpff_1.mcs0x04DBEC24。
发布说明(ReleaseNote)
[内容]
列出用户需求中所描述的系统运行环境，描述清楚哪些是全部测试过的环境，哪些是部分测试过的环境（例如只做过安装部署），哪些是没有测试过的环境。
[裁剪原则]
关于此项若没有特殊说明，此部分内容不允许裁剪掉。
4
[内容]
相对于前一个版本，增加了哪些新的功能。
[裁剪原则]
关于此项若没有特殊说明，此部分内容允许裁剪掉。
产品、文档的未解决的bug，不包含建议bug；
文档评审的未解决的问题；
[裁剪原则]
关于此项若没有特殊说明，此部分内容不允许裁剪掉。
8
附图目录
表格目录
某企业全称user full name
发布说明
企业全称
2020年8月22日
文档属性
属性
内容
客户名称
某企业全称user full name
项目名称
项目全称project full name
文档主题
发布说明
文档副标题
文档版本
0.1
文档日期
文档状态
草案
作者
文档变更
版本
修订日期
修订人
描述
文档送呈
姓名
目的
1
产品名称
中文
运行平台
英文
发布日期
发布版本
产品经理
开发经理
发布版本在FTP服务器的目录
产品依赖
本产品正常运行依赖的产品及版本号；
例如：UltraPASM 2.0.8以上，UIP 1.0.1以上等。
2
[内容]
对本产品的功能做简单介绍，并描述产品包括的模块，说明各模块的功能。
[裁剪原则]
关于此项若没有特殊说明，此部分内容不允许裁剪掉。
Original ReleaseNote(Dr_ABE_BendV34018P7)
process data are not read.
Release Note (Dr.ABE_Bend)-Version: 3.30-60.18P7
Precautions and restrictions on use #02 * About [AMNC Ver.5.0] If your using NC is AMNC-Ver.5.0.0000.0058sp4 or later, please register a machine by selecting [AMNC Ver.5.0] in [NC Type] in [new create] in [Machine Registration] in [Parameter]. It is possible to output CAM data for AMNC Ver.5.0. *1: The production with this version at FUJINOMIYA factory is October or later in 2007. *2: The version upgrade CD for serviceman was already distributed on August 24 in 2007. Besides, the bend data, which was created by [AMNC Ver.5.0] format, cannot be read and operated by NT-bender (AMNCVer3.0/4.0 series).
Created on: Jun. 9, 2008
Release Note (Dr.ABE_Bend)-Version: 3.30-60.18P7
Introduction This document is the release not regarding Dr.ABE_Bend Version 3.30-60.18 P7. It describes precautions and restrictions on use, installation, addition and improvement of features, and support of technical report. Besides, please refer to the [Operation Guideline] and operation manual for detailed handling about Dr.ABE_Bend. * Regarding [Bend Model File 5.0] In [Bend Model File 5.0] that is created based on the unfolded drawing, which is created by AP100, it became possible to express forming shape and special bend such as Z-bend, but features haven't been supported yet by AMNC. We're developing new features using [Bend Model File 5.0]. * Regarding [AMNC Ver.5.0] It is possible to output CAM data for AMNC Ver.5.0. If your using NC is AMNC Ver.5.0, please select [AMNC Ver.5.0] at [NC type]-[new create] in [Machine Registration][Parameter], and register a machine. The NT-bender(AMNC-Ver.3.0,Ver.4.0) can not use the bending data made by Dr.ABE_Bend ([NC type]=[AMNC Ver.5.0]). And you have to used this Dr. ABE_Bend (Version 3.30-60.18 P7),if Dr.ABE_Bend-Manual uses the bending data made by the NT-bender (AMNC-Ver.5.0.000.0058.sp3b,Ver.5.0.000.0058.sp3).
- 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.