ReleaseNote
EasyBuilder8000 V4.65.11 Build 2014.01.29
新增功能
1.工具栏新增下列两项功能：
显示公共窗口的元件：可以设定是否在一般页面显示公共窗口的内容。
显示重迭窗口的元件：可以设定是否在一般页面显示所选的重迭窗口内容。
2.[定时式资料传输]元件的最小运行时间间隔缩短为0.2秒。
3.元件[安全] 属性中的[最少按键时间(秒)] 项目新增0.1秒至0.9秒选项。
4.宏指令中的[时间间隔] 项目所使用的时间单位由"秒”更改为”100ms”，以提供更
高的执行频率。
5.在[系统参数设置] 的[HMI 属性] 设定页中新增[穿透端口] 设定功能。
用户可
以依实际需要修改穿透端口的编号。
此外，也新增系统寄存器LW-9904 (穿透服务器端口号)。
用户可以在HMI上实时修改端口编号。
穿透端口的编号若被变动，则在使用穿透功能前，需一并修改Project Manager中[穿透通讯] 设定页里的[HMI埠号]。
这两者的设定必须保持一致，穿透功能才能正常运作。
6.Barcode/Keyboard (USB/COM)驱动程序支持USB RFID装置。
功能修正
1.提升ASCII Server驱动程序的命令回复速度，反应时间缩短为6ms。
2.避免因网络质量不稳定时，导致[定时式资料传输] 元件无法传送数据到远程
HMI。
3.修正当使用宏指令宣告浮点数(float) 数组时, 若一并赋予初始值(如下图所示)，
且初始值非浮点数(例如1或2等整数)，将无法正确设定初始值。
驱动程序
1.新增Siemens S7-300 (ISO Ethernet) 驱动程序。
2.修正Beckhoff Twincat 3 ADS/AMS (Ethernet), Beckhoff ADS/AMS (Ethernet) 与
Beckhoff Embedded PC驱动程序：
●可以过滤记录或警报等非必要的数据，保持通讯的畅通。
●增加AMS Net Id 设定功能格。
AMS Net ID 格式为六个字节：
xxx.xxx.xxx.xxx.xxx.xxx；默认值一般为IP 地址+.1.1。
3.修正Siemens TI505 驱动程序无法读写Remote IO 所映像的XY地址。
4.修正OMRON EtherNet/IP (NJ Series) 驱动程序无法连接NJ301 系列PLC。
5.修正Mitsubishi Q00UJ/QnU/QnUD/QnUDH/QnUDEH/L (mini USB) 驱动程序，可以
过滤异常的数据，保持通讯的畅通。
6.BACnet/IP 驱动程序支持[BACnet/IP to MS/TP] Adapter 与[BACnet/IP] Server。
标杆的神器 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问题排查流程
修正缺陷
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
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处理器）也可实现双屏。
Release_notes_v3.81[1]
![Release_notes_v3.81[1]](https://360docs-1393072327.cos.ap-beijing.myqcloud.com/5e7d5fffc8d376eeaeaa314f.webp)
Changes: GH Bladed v3.80 – v3.81dtbladed.exe v3.24Changes to Offshore Support Structure module and GH Tidal Bladed •Comprehensive modelling of multi-point non-linear foundation dynamics.•Modelling of the effects of marine growth on the submerged structure.Other changes to GH Tidal Bladed•Network licence now works with GH Tidal Bladed.Changes to Hardware Test module•Option to resample simulation outputs at fixed intervals.•New device timing options offering improved accuracy.•New channels for recording device performance.•Improved live device data view.•New time-series resampling options for easier post-processing.•New export options: Bladed and Matlab .mat binary data files.•Usability and bug fixes.Changes to Advanced Processing module•Now allows Mann model to be used for generating multiple turbulence files.Changes to Advanced Transmission Interface module•Extended to allow user-defined generator/converter/electrical system dynamics to be integrated into Bladed simulations through a DLL interface.User interface•Checks on the validity of the numbers of rotor modes selected.•Tower screen resizable for easier data input.•Channel combination screen can be expanded to help with equation editing. •Corrections to 3D graphical display of turbine.•More intuitive allocation of wind speed bins for post-processing.•Obsolete ‘Maximum generator speed’ removed from variable speed pitch regulated controller.•Various incompatibilities with European number format resolved.•Project Info Special Data now allows more characters.Turbine model•Improved modelling1of inertial coupling between rotor/tower dynamics and drive train torque, by including further Coriolis terms which may become significant in certaincircumstances, e.g. fast yawing, leading to improved prediction of the torque-related (Mx) loads.•Improved modelling1of the coupling of angular motion between rotor out of plane and tower fore-aft modes to include a term which becomes more significant with higher modes and flexible rotor blades. This has led to a significant improvement in the agreement between predicted and measured frequencies especially for the second tower fore-aft and rotor out of plane coupled mode. Computed hub and tower top bending moments, particularly nodding moments, are among the variables most affected by this change.•New electrical model for synchronous generator and full converter.•If refining of blade deflections is used, the resulting changes to deflection-dependent loads are now used consistently throughout the calculation ant not only in the output loads. Some torque-related (Mx) loads may be affected.•Correction to refining of blade deflections and tower closest approach for teetered rotors. •Teeter angle and velocity now passed to external controller.•External controller record 23 now gives actual rather than demanded generator torque. •Re-initialisation of passive pitch rate actuator following safety system trip: corrected. •Correction to interpolation of electrical losses from look-up table in steady calculations and calculation of simulation initial conditions.•Summary information file in simulation outputs now gives time from start of output; time from start of simulation is still available in the ‘Control variables’ output file.Calculations•Option to phase out stall hysteresis automatically when approaching 90º angle of attack. •Improvements to constrained wave models.•Currents now added to constrained nonlinear waves.Post-processing•Extreme load sub groups now work even if no stats are available in the header. •Rainflow calculation and Level Crossing analysis with multiple processing could crash in some instances, or give erroneous error messages: now fixed.•Peak analysis now works even if some signals are all zero.•Transient load cases: the wind regime no longer needs to be defined if it is not required. •If a problem is encountered in writing output files, the error message now identifies the file name correctly.Other•Network licences for optional modules were not always released after a calculation.Note 1: These modelling improvements represent improvements in the accuracy of the code to ensure that its capabilities continue to keep pace with developments in the size and design trends of modern wind turbines. The modal synthesis approach of GH Bladed has proved a very satisfactory basis for this, giving a good compromise between accuracy of load predictions and speed of simulation. However we are constantly reviewing the approximations used to ensure that the accuracy of predictions is maintained as turbines become larger and more flexible. Independent results from measured field data and comparisons with other models have been used to test and validate these improvements.。
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.。
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)。
Sesam Release Note PET v4.1说明书
SESAM RELEASE NOTEPET – Pipeline Engineering Tool The definitive tool for early phase pipeline designValid from program version 4.1 SAFEGUARDING LIFE, PROPERTYAND THE ENVIRONMENTSesam Release NotePET – Pipeline Engineering ToolDate: 27February 2018Valid from PET version 4.1Prepared by DNV GL – Digital SolutionsE-mail support: **************************E-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.Table of contents1DOCUMENTATION (1)2NEW FEATURES (1)3BUG FIXES (1)4OTHER (1)1DOCUMENTATIONThe purpose of this document is to inform users about new features and changes in the PET 4.1 release.The PET 4.1 release is supported by two additional documentations:-Sesam User Manual for PET-Sesam Verification Document for PETThe User Manual provides an overall introduction of the program, the established features, and step-by-step guidance on how to use it.All documentations listed above can be found at:-[Your PET Installation Path]\doc\2NEW FEATURESThe PET 4.1 release features some important enhancements. The main features are summarised below:-DNV-OS-F101 calculation module:o Updated to include DNVGL-ST-F101 released in 2017. The new version of the Submarine Pipeline Systems Standard affected the load combination check for displacement control.The references in the information cells were also updated to the 2017 version.o Releated to the new displacement control formulation, it was added input option to indicate if the material has a Lüder plateau.o The required thickness for buckle arrestors are now calculated according to DNV-OS-F101.3BUG FIXESIn addition to the new features, the following known issues are fixed:-DNV-OS-F101 calculation module:o Fixed a issue with αU factor for system pressure test condition in the Load Combination, DCC check.-Free Span calculation module:o Issue related to calculations showing N/A (Not a number).-Reel packing calculation module:o The number of layers on the reel were showing one off.4OTHERThe following minor change was performed:o Corrected typo in the DNV-OS-F101 calculation module.o Corrected typo in the DNV-OS-F101 Load Combination – Displacement Controled report.A BOUT DNV GLDNV GL is a global quality assurance and risk management company. Driven by our purpose of safeguarding life, property and the environment, we enable our customers to advance the safety and sustainability of their business. Operating in more than 100 countries, our professionals are dedicated to helping customers in the maritime, oil & gas, power and renewables and other industries to make the world safer, smarter and greener.D IGITAL S OLUTIONSDNV 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.。
Release Notes for C51单片机笔记
Release Notes for C518051 Development Tool KitsThis file contains release notes and last minute changes that are not found in theprinted m anuals.Information in this file, the accompany manuals, and soft ware isCopyright © Keil Software, Inc and Keil Elektronik GmbH.All rights reserved.Contents1What's New in C512Example Program s3Device Database™4Peripheral Simulation5Technical Support6Contact DetailsWhat's New in C51The following sections list the changes instituted in each release of the C51 toolset.C51 Version 9.00 Release[µVision4]▪This C51 release com es with the new µVision4 IDE.[New Supported Devices]▪Evatronix R8051XC(1 DPTR), R8051XC2(1 DPT R), R8051XC2(2DPT R), R8051XC2(8 DPTR), R8051XC2-A(1 DPT R), R8051XC2-A(2DPT R), R8051XC2-A(8 DPTR), R8051XC2-AF, R8051XC2-B(1 DPTR),R8051XC2-B(2 DPT R), R8051XC2-B(8 DPT R), and R8051XC2-BFdevices.▪Nordic nRFLU1P-F16and nRFLU1P-F32 devices.▪NXP P89LPC9361device.▪Silabs C8051F580, C8051F581, C8051F582, C8051F583,C8051F584, C8051F585, C8051F586, C8051F587, C8051F588,C8051F589, C8051F590, and C8051F591 devices.[Device Support]▪Corrected:device settings for Infineon XC888-6FF, XC888CM-8FF,XC888LM-6FF, XC886-6FF, XC866L-1FR, XC866L-2FR, XC866L-4FR, andXC864-1FRI devices.▪Corrected: device settings for Nordic Semiconductor nRF24E1,nRF24E2, nRF9E5, nRF24LU1, and nRF24LE1 devices.▪Added: debug support for NXP P89LPC9361 and P89LPC954 devicesin the LPC900 EPM Emulator/Programmer.▪Updated: LPC900 EPM flash programmer configuration dialog tosupport devices with 16 flash sectors.[CX51 Compiler]▪Corrected: constant folding of two negative array index values. Forexample:unsigned char arr[512];unsigned int i;i = arr[i-1-5]; // incorrect in C51 V8: arr[i-4] instead of arr[i-6]▪Corrected: when using the NOAREGS directive, complex arithmeticwith nested calls m ay create incorrect results. For exam ple:#pragma NOAREGSint result;extern char f(unsigned char idx);result = (f(1)*0x100+f(0)) - (f(3)*0x100+f(2)); // incorrect result. POP destroys value in ACCLX51 Linker/Locater]▪Corrected: when using OPTIMIZE(10) or above, there was a potentialthat common code blocks are called incorrectly. Therefore programs m ayhave operated incorrectly.[BL51 Linker/Locater]▪Corrected: when using RTX51 user interrupt functions wereoverlapping with RTX ISR vectors which resulted in a linker warning.▪Corrected: data overlaying may not work when the last input modulecontains an interrupt function; the linker incorrectly issues WARNING 16:main uncalled.C51 Version 8.18 Release[Device Support]▪Added: debug support for NXP P89LPC9408in the LPC900 EPMEmulator/Programmer.[New Supported Devices]▪Nuvoton W681308device.▪NXP P89LPC9201, P89LPC9211, P89LPC922A1, P89LPC9241,P89LPC9251, P89LPC9301, P89LPC931A1, P89LPC9331, P89LPC9341,and P89LPC9351 devices.▪Silabs C8051F500, C8051F501, C8051F504, C8051F505,C8051F506, C8051F507, C8051F508, C8051F509, C8051F510,C8051F511, C8051F700, C8051F701, C8051F702, C8051F703,C8051F704, C8051F705, C8051F706, C8051F707, C8051F708,C8051F709, C8051F710, C8051F711, C8051F712, C8051F713,C8051F714, and C8051F715 devices.[ULINK2 Support]▪Corrected: potential deadlock on ST uPSD targets with ULINK2solved.[Device Simulation]▪Corrected: Infineon XC800 simulation of the MDU was incorrectlyimplem ented.▪Corrected: For C8051F12x/F13x devices the EXFn and TOGnbehavior matches with latest inform ation from SiLABS.▪Added: simulation for Atmel AT89C51RE2. The second UART is nowavailable for the simulation.[CX51 Compiler]▪Corrected: initialization failed on far addresses when the object islocated with _at_. For example:#pragma VARBANKING O2unsigned char far array[65530] _at_ 0x150006;unsigned long x1 = (unsigned long)(array); // incorrect address stored in 'x1'.C51 Version 8.17a Release[Device Support]▪Added: debug support for the follow devices from Analog DevicesADE5166, ADE5169, ADE5566,ADE5569, ADE7166F16, ADE7166F8,ADE169F16, ADE7566F16, and ADE7566F8 in the ADI Monitor Driver.▪Added: debug support for NXP P89LPC9321 and P89LPC9351devices in the LPC900 EPM Emulator/Programmer.[Device Support]▪Added: Nuvoton devices in the device database.▪Corrected: Port Pin P2.2 is available (instead of P2.5) on NXPP89LPC917 devices. This is now reflected in the peripheral dialogs.▪Corrected: UART0 baudrate is now correctly displayed whenTim er2/3/4 is used as baudrate generator on SiLabs C8051F13xdevices.[Device Simulation]▪Corrected: sim ulation of Reset Source Register (RSTSRC) and SFRPage Control Register (SFRPGCN) for SiLabs C8051Fxxx devices.▪Corrected: handling of Automatic Page Control Enable (SFRPGCN)and Reset Source Register (RSTSRC) for SiLabs C8051Fxxx devices.▪Corrected: sim ulation of PLLLCK (PLL Lock Flag) for SiLabsC8051F12x/13x devices. PLLLCK is now set when PLL is configuredcorrectly and frequency is locked.▪Added: support for V: user-defined memory area for NXP 80C51MXdevices.▪Corrected: sim ulation issues with the Evatronix R8051XC peripheralsDMA and interrupt.[CX51 Compiler]Corrected: when two long operands are loaded from com plex arrays (each with object size bigger than 256 bytes), there was a potential register overwrite in register R0. The result of the long operation was in such cases incorrect.Example:struct s2 { unsigned int idx : 1; } s2;struct s { unsigned long l1; unsigned char a[256]; unsigned long l2; } xdata sarr[2];unsigned long l;void main (void) {l = sarr[s2.idx].l1 + sarr[s2.idx].l2; // incorrect result of long addition }[A X51 Macro A ssembler]▪Corrected: in NXP 80C51MX m ode, DATA, IDATA, and EDATA can beplaced to absolute addresses 0x7F0000 and above. This is now accepted.▪Added: ECRM directive that allows to expand generic CALLinstructions to ECALL for NXP 80C51MX devices.C51 Version 8.16a Release[CX51 Compiler]▪Corrected: when int num bers are multiplied and assigned to long, theresult is potential incorrect. This problem has been introduced in V8.15.▪Corrected: C51 _at_ problem with linker code packing fixed.[A X51 Macro A ssembler]▪Enhanced: for the NXP MX devices, CALL/JMP instructions areencoded to ECALL/JMP when needed..[Device Support]▪Added: ULINK and Infineon DAS (Device Access Server) support forthe XC864 device.▪Enhanced: Evatronix R8051XC XDATA Banking example optimized.▪Enhanced: Infineon XC800 startup code.▪Added: Support for Infineon XC864 including a Blinky example.▪Added: Syntek Semiconductors STK6031and STK6032devices todevice database.[Device Simulation]▪Added: for SiLABS C8051F360/1/2/3/4/5/6/7/8/9andC8051F410/1/2/3.C51 Version 8.15 Release[Cx51 Compiler]▪Corrected: interrupt functions com bined with NOINTVECTOR wherenot detected by the linker as new root and an incorrect linker warningwas reported.▪Corrected: when using Dallas 390 m ode with ROM(D512K) orROM(D16M), pdata arrays could not be located anywhere in m emory.▪Corrected: when using the XCROM directive in com bination withfunction pointers, constant initializations where omitted.▪Enhanced: long multiplication with two unsigned int/char argumentshas now a m uch higher performance.[Target Support]▪Added: support for the Infineon USCALE XC800 hardware via theInfineon DAS Client for XC800.[Device Simulation]▪Corrected: access to MACACC was not corrected simulated for SiLABSC8051F12x and C8051F13x devices.▪Added: device support and simulation for Infineon XC878.▪Added: simulation for new peripherals (Software Reset, RTC, DMA)on Evatronix R8051XC core.▪Added: xdata banking support for Evatronix R8051XC core.[LX51 Linker/Locater]▪Corrected: Linker Code Packing may com bine incorrectly blocks fromseveral code banks into common areas.[ULINK2 Support]▪Added: Debug and Flash-Programming support for NXP P89LPC952and P89LPC954.C51 Version 8.12 Release[Device Simulation]▪Added: device support and simulation for SiLABSC8051T600/1/2/3/4/5 and C8051T610/1/2/3/4/5/6/7.[Cx51 Compiler]▪Corrected: nested call with struct pointer arguments whereincorrectly processed.[LX51 Linker/Locater]▪Corrected: sfr16 definitions in assembly code and C source file maygenerate Warning L46: SFR SYMBOL HAS DIFFERENT VALUE.C51 Version 8.11a Release▪[Device Support]Added: support for Ram t ron VRS51L3072 and VRS51L3174.▪Added: support for Nordic Semiconductor nRF24LU1.[Device Simulation]▪Added: device support and simulation for SiLABS C8051F336,C8051F337, C8051F338, and C8051F339.▪Corrected: PORTx and PCA output pins on SiLABS C8051F12x d id notcorrectly update in simulation.C51 Version 8.10 Release▪[Device Support]Added: support for Megawin MPC82G516A and MPC82L54A.▪Enhanced: startup code for Infineon XC800 devices has nowselections for device variants. Infineon XC88x AC step devices requiresto set the device to VCO bypass m ode before PLL switching.▪Added: support for NXP P89V52X2.[Device Simulation]▪Corrected: simulation of MULRDY and OSCICL corrected for SiLABSC8051F3xx series.▪Enhanced: simulation of Evatronix R8051XC watchdog tim er withoptional prescaler. For details refer to Application Note 191: ToolchainExtensions for R8051XC Core.▪Corrected: DPTR simulation of Evatronix R8051XC; when 2 DPT Rwhere selected the auto-increm ent feature (DPC register) did not work.Two R8051XC devices are now in the device database: R8051XC (8DPTR) with simulation for 8 DPTR, R8051XC (2 DPTR) with simulationfor 2 DPTR.▪Corrected: SiLABS simulation for UART #1 had a problem with thetransmit interrupt bit (TI) when SFR page was set to 1.[Cx51 Compiler]▪Corrected: the MODC2 directive did not correctly save and restoremultiple DPTR registers on interrupt entry/exit.▪Corrected: Assem bler instructions inserted with #pragma ASMtrigger now register usage of all CPU registers and therefore avoidsregister clashes.▪Corrected: strcm p and strnc mp library functions changed fromsigned char to unsigned char com pare (ANSI requirement).▪Improved: detection of conflicting memory types when used incom bination with typedef's, for example:typedef char code CCHAR;typedef CCHAR xdata XCHAR; // generates now WARNING C185: different memory spaceCCHAR idata var2; // generates now WARNING C185: different memory space [LX51 Linker/Locater]▪Corrected: REMOVEDUNUSED did not correctly work with SROMsym bols and linker code packing.▪Corrected: debug sym bols of absolute bits generated in AX51 hadwrong offset.▪Corrected: segm ent locating with the LAST keyword generatedunnecessary m emory gaps when used with code banking.▪Corrected: when linker code packing is used, an address reference tofar variables with _at placem ent was wrong.[BL51 Linker/Locater]▪Corrected: segm ents with a AJMP instruction as last instructionwhere located at the end of a 2KB block which generated a linker error. [ULINK and ULINK2 Support]▪Corrected: Verify failed on µPSD devices when common segm entswhere located to code banks, but no bank 0 exists.C51 Version 8.09 Release[Device Simulation]▪Corrected: wrong timing of the Tim er 1 in the Infineon XC800devices.▪Corrected: clock cal culation of Infineon XC88x devices was incorrect.▪Corrected: Dallas D80C400 simulation did not correctly switch tocontiguous m ode.▪Added: Simulation for At m el AT89C51AC3.▪[Device Support]Corrected: when debugging Infineon XC800 Devices with the DASinterface data/idata variables where shown incorrect ly.▪[Target Debugging for A nalog Devices ADuC83x, A DuC84x, and ADE7xxx]Options - Project - Debug - Use: ADI Monitor Driver selects target driver for the Analog Devices ADuC834, ADuC84x, and ADE7xxx devices. This driver is now extended to support the 1-Pin Pod interface and the new ADE7xxx devices.[Monitor-51, Monitor-390]▪Corrected: potential communication problems with low-costUSB-COM adapters.[Cx51 Compiler]▪Corrected: a code generation problem with bit-field arrays when thearray index is a function return value.C51 Version 8.08a Release[Device Simulation]▪Corrected: the previous version had a delay when starting signalfunctions. This delay is now removed so that the startup behavior isidentical to releases before version 8.06.▪Corrected: the behavior of JBC instructions on I/O ports was not fullycorrect. JBC instructions now read the SFR register (Px) instead of theI/O port value (PORTx).[Cx51 Compiler]▪Corrected: integer promotion was m issing on com plex arithmeticwith char/unsigned char and multiplication or division.[A x51 Macro A ssembler]▪Enhanced: the _DATE2_ m acro is now defined also for the A51 andAX51 Macro Assembler.[uVision3 IDE]▪Corrected: potential crash in the project window on right mouse clickwhen no item was selected.[Device Support]▪Corrected: Peripheral display for Port 4 and Port 5 of the NXP89LPC952 device was m issing.▪Enhanced: on XC800 devices the dialog Project - Options - Debug- ULINK Settings - Disable interrupts during steps is implemented.This option disables interrupts during single-stepping and thereforeexecutes only instructions from the current function.▪Added support for Infineon TLE78xx series.▪Corrected: sim ulation for external interrupt inputs EINT0 and EINT1on Infineon XC800 devices.▪Corrected: debugger startup problem s with the Infineon DAS server.C51 Version 8.06 Release▪[Device Support]Infineon XC800 Devices: added debugging and flash programmingsupport for new Infineon XC800 devices (XC866-1FR, XC856) withULINK and Infineon DAS server.▪Enhanced: Infineon XC800 startup code START_XC.A51 V1.02 thatsupports pdata addressing (C51: USING PDATA VARIABLES ONINFINEON XC800).▪SST Sm artCards: added core features for device sim ulation.[Device Simulation]▪Corrected: interrupt vector for 2nd UART on Philips P89LPC952 wasincorrectly configured in simulator and target dialog.▪Enhanced: VTREG PPAGE is initialized to 0 on all Philips LPC900devices to allow simulation of MOVX @Ri without configuration.▪Corrected: a problem with AT89S8252 EEPROM simulation.▪Corrected: a problem with the baudrate generation on At m el deviceswith X2 feature (the baudrate was displayed incorrect).▪Corrected: a problem with code banking on Mentor M8051EW core. [Cx51 Compiler]▪Corrected: code that is not used (i.e. with m acros) is removed, evenwhen it creates other side effects.▪Corrected: unexpected error m essage for syntactical correctstatem ent.struct st2 { unsigned char uc1; unsigned char uc2; };struct st1 { struct st2 st2; unsigned char u1; unsigned char u2; };struct st1 st;void main (void) {(&st.st2)->uc1 = 0; // gives error, but should be Ok.}▪Corrected: library function toint did no flag values 0x3A - 0x40 asincorrect.[ULINK and ULINK2 Support]▪Added: support for ULINK2 for the Infineon XC800 and ST uPSDseries.▪Added: device support for Infineon XC886, XC888, and XC856.C51 Version 8.05 Release▪[Device Simulation for Infineon XC88x Series]Added device sim ulation for Infineon XC886 and Infineon XC888.▪[Device Simulation for Philips P89LPC952/954]Corrected: the two serial windows did not work for the Philips P89LPC952/954 devices.▪[Device Simulation for M8051EW]Corrected: when M8051EW features were enabled, it was not possible to debug non-banking applications.▪[Device Simulation for R8051XC]Enhanced: som e features were not covered in the first revision of the simulator.Now the simulator also takes care about peripheral timing, and write operations to code m emory.▪[LX51 Linker/Locater]Corrected: when using interbank call table optim ization (?B_RST_BANK != 0xFF), the linker was optimizing too much.▪[ULINK Driver for ST uPSD]Corrected: flash programming did not work for uPSD3422 devices.[Cx51 Compiler]▪Enhanced: C51 did issue an error when accessing struc t m emberswith s->member instead of s.member.▪Corrected: using multiple dummy assignm ents to rem ove unusedvariables m ay cause register overwrites.▪Corrected: potential code problems when increm enting far pointerswith long constants.void func (void) {unsigned int i;long far* entry;while(i) {i--; // increment missingentry += 1L; // due to 'far' pointer increment with 1L}}▪Corrected: potential problem on SmartMX, when using Optimize level8 or 9 without OBJECTADVANCED.#pragma MXPint xdata x;char xdata * xdata p;void f1 (char *);void f2 (char *);void main (void) { // uses CMPW instruction that affects 'Z' flagif (x == 0xFFFF) f1 (p); // MOVX A,Rx,@DPTR destroys 'Z' flagelse f2 (p); // and cannot be combined}C51 Version 8.04 Release[Cx51 Compiler]▪Enhanced: The Warning C259: pointer: different mspace is im provedand covers now also situations where an address value is assigned.▪New: The Warning C289: converting non-pointer to pointer is issuedwhen a integer value is assigned to a pointer.▪Corrected: A problem with the SRC file output is wrong withoptimized address values.▪Corrected: dummy read to MD3 was missing for int*int m ultiplicationwhen using the Infineon/Evatronix MDU.▪Added: Support for the SiLABS Arithmetic Accelerator (available inC8051F12x and F13x devices) in the far banking library.▪[Device Support for Evatronix/Cast R8051XC Core]Added com plete sim ulation and com piler support for the features of theR8051XC core. Detailed information is provided in Application Note 191: Toolchain Extensions for the R8051XC Core.▪[Device Support for Mentor M8051EW Core]Enhanced simulation support for the Mentor M8051EW memory extension features. It is now possible to sim ulate code banking and far m emory applications and the address of the The address of the extension corefeatures of the R8051XC core. Detailed information is provided in Application Note 171: Using M8051EW Memory Extension.▪[Device Support for Infineon XC800 Series]Added ULINK debugging support and DAS driver for new Infineon XC800 devices (XC886, XC888). Detailed information is▪[BL51 and LX51 Linker/Locater]Corrected: there might be incorrect WARNING L15: MULTIPLE CALL TO FUNCTION messages when using syntax: OVERLAY (* ! (func1, func2,func3,...)) to group more than just two functions.C51 Version 8.02 Release▪[uVision Debugger]Added peripheral simulation support and target debugging dialogs for the following devices:▪Atm el AT89C51RE2, AT89C51IE2, AT89C51CC03, AT8xC51SND1,AT89S8253, AT89LP2052, AT89LP4052▪Revised: Atm el AT89C5131/AT89C5131A(added TWI), AT8xC5132(added TWI, ADC)▪Philips P89LPC9102, P89LPC9103, P89LPC9107. P89LPC9221,P89LPC9311, P89LPC932A1, P89LPC938,▪Philips P89LPC9401/P89LPC9408 (without LCD Driver), P89LPC952,P89LPC964, P89LPC966▪Philips P89V660, P90V662, P89V664[LX51 Linker/Locater]Corrected a problem with code banking, the linker reported incorrectly error L124: BANK SWITCH MODULE INCORRECT.▪[Cx51 Compiler]Corrected a m acro expansion problem, array index calculations with negative offset, and far access to absolute m emory locations.▪[Target Debugging Support for Infineon XC800 Series]Added ULINK debugging support and DAS driver for new Infineon XC800 devices (XC886, XC888).▪[ULINK Driver for ST uPSD]Added new JTAG device ID's for ST uPSD3212, uPSD3312, and uPSD3422.C51 Version 8.01 Release▪[uVision Debugger]Added peripheral simulation support and target debugging dialogs for the following devices:▪Silicon Labs C8051F120, Silicon Labs C8051F121, Silicon LabsC8051F122, Silicon Labs C8051F123,▪Silicon Labs C8051F124, Silicon Labs C8051F125, Silicon LabsC8051F126, Silicon Labs C8051F127,▪Silicon Labs C8051F130, Silicon Labs C8051F131, Silicon LabsC8051F132, Silicon Labs C8051F133[P89LPC952 and MCB950 Board Support]Added support for Philips P89LPC95x device series.▪[A X51 Macro A ssembler]Corrected a problem with forward references in sym bols which generates an error m essage.▪[LX51 Linker/Locater - Code Packing]Corrected a potential problem with code packing when modules are translated with different optimization levels (less than 8) but the OBJECTADVANCED directive.▪[L51_BA NK.A51 - Code Banking Configuration File]Changed behavior of the ?B_RESTORE_BANK entry with ?B_MODE=0 to avoid glitches when using the RTX51 or RTX51 Tiny operating system together with code banking.▪[Cx51 Compiler]Version number changed for logistic reasons. No other changes com pared to V8.00.C51 Version 8.00 Release▪[uVision3 IDE]The µVision3 IDE contains several enhancem ents orrected: the device simulation covers now the latest timing specification for Dallas DS89C420, DS89C430, DS89C440, and DS89C450 devices. The tim er simulation was previously based on a older data book and therefore incorrect.[Device Simulation]▪Corrected: the device sim ulation c overs now the latest tim ingspecification for Dallas DS89C420, DS89C430, DS89C440, andDS89C450 devices. The tim er simulation was previously based on a olderdata book and therefore incorrect.▪[Target Debugging for A nalog Devices ADuC83x and ADuC84x]Options - Project - Debug - Use: ADI Monitor Driver selects target driver for the Analog Devices ADuC834 and ADuC84x devices. This driver directly connects via a serial COM interface to the on-chip Download/Debug Kernel of the ADuC device. No specific monitor or firmware is required. A detaileddocum entation is available in the Analog Devices ADuC83x/84x Download/Debug Driver User's Guide (..\C51\HLP\MonADI.CHM).▪[Support for Infineon XC866]Added complete support for new Infineon XC800 Device series including device simulation, ULINK driver, and MCBXC866 Evaluation Board support.▪Example projects are provided in thefolder ..\C51\Examples\Infineon XC866.▪Complete docum entation is available in the MCBXC866 User'sGuide(..\C51\HLP\MCBXC866.CHM) which also explains the ULINKdriver.▪[Support for ST uPSD34xx Series]Added com plete ULINK support for new ST uPSD34xx device series.[C Library]▪Corrected: on Dallas 390, 400, 5240, and 5250 devices tan (INF)generated a wrong return, and printf ("%f")did not print the floatingpoint value INF and NaN.▪Corrected: the return value of scanf and sscanf was just 0xFF insteadof -1 when no arguments where processed.▪Corrected: the library takes care about the changed behavior of theMem ory Accelerator on Dallas DS80C390 Rev. C.▪Corrected: on Dallas 390, 400, 5240, and 5250 devices m emmove inxdata m emory failed when source buffer is overlapping destinationbuffer.C51 Version 7.50a Release▪[LX51 Linker/Locater]Corrected: potential problem with Linker Code Packing that m ight causein-efficient operation or a MEMORY SPACE OVERLAY warning.▪Corrected: fixup error messages when using the REMOVEUNUSEDdirective.▪Corrected: when using L51_BANK.A51 the far m emory addressingused a wrong offset (-64KB). Instead of X:0x20000 the X:0x10000 wasaddressed.▪[BL51 Linker/Locater]The new BL51 Linker/Locater was by accident not included in Version 7.50.▪[C Library]Corrected a problem on Dallas 390, 400, 5240, and 5250 devices with log and log10 when const data is not in stored in segm ent 0 (C:0x0000-C:0xFFFF).C51 Version 7.50 Release▪[uVision2 Debugger]Added Extended Memory Simulation for Mentor M8051EW. Refer to Application Note 171: Using M8051EW Memory Extension in the folder \C51\EXAMPLES\M8051EW.Added peripheral simulation support and target debugging dialogs for the following devices:▪Dallas Semiconductor DS89C420,▪Dallas Semiconductor DS89C430,▪Dallas Semiconductor DS89C440,▪Dallas Semiconductor DS89C450,▪Silicon Labs C8051F000,▪Silicon Labs C8051F001,▪Silicon Labs C8051F002,▪Silicon Labs C8051F005,▪Silicon Labs C8051F006,▪Silicon Labs C8051F007,▪Silicon Labs C8051F010,▪Silicon Labs C8051F011,▪Silicon Labs C8051F012,▪Silicon Labs C8051F015,▪Silicon Labs C8051F016,▪Silicon Labs C8051F017,▪Silicon Labs C8051F350,▪Silicon LabsC8051F351,▪Silicon LabsC8051F352,▪Silicon LabsC8051F353,▪SST SST89E554RC,▪SST SST89E564RD,▪SST SST89V554RC,▪SST SST89V564RD.▪[ISD51 In-System Debugger]Added example configuration for Dallas DS89C420, DS89C430, DS89C440, and DS89C450 devices. For details refer to Application Note 177: Using ULINK with STMicroelectronics Turbo µPSD 3300/3400 Devices and the sam ple projects in the folder ..\C51\EXAMPLES\ST uPSD.[C51 Compiler]▪Corrected a code generation issue for negative array index values.For example:signed int i = v1 - v2;value = table [i + 4]; // code works for 'signed char' index// but fails with 'signed int' index▪Added MODC2 Compiler Directive: enables use of dual datapointers available on the Cast and Evatronix R80515 core. Usingadditional data pointers improves the performance of the followinglibrary functions: memcpy, memmove, memcmp, strcpy, andstrcmp.▪Added MODH2 Compiler Directive: enables use of dual datapointers available on Hynix, ST uPSD 33xx, and ST uPSD 34xx devices.Using additional data pointers improves the performance of the followinglibrary functions: memcpy, memmove, memcmp, strcpy, andstrcmp.▪[CX51 Compiler]Corrected the following problem s for the Sm artMX instruction set:▪Switch/case with long types and ROM(HUGE).▪Over optimization with CMPW instruction.▪Stack adjust m ent failure with setjmp/longjmp library routines.▪[C Library]Corrected several library problems including:▪Corrected a problem on Dallas 390, 400, 5240, and 5250 deviceswith asin, acos, and atan when const data is not in stored in segment 0(C:0x0000-C:0xFFFF).▪The labs function has been optimized and is now fully reentrant.▪Added configuration symbol ?C?DPSEL that defines DPSEL SFRaddress for MOD517(NOAU)multiple DPTR support. May be used forMentor M8051EW based devices which have the Infineon m ethod formultiple DPT R but with a different DPSEL SFR address. The ?C?DPSELdefinition shown below m ay be included in a chip-specific Startup.A51 file.Without this definition, the DPSEL register is accessed at the defaultaddress 0x92.PUBLIC ?C?DPSEL?C?DPSEL DATA 0A2H ; define DPSEL address for Mentor M8051EW▪[LX51 Linker]Added the REMOVEUNUSED(abbreviation RU) directive which removes unused program and data segm ents provided that Data Overlaying is enabled.▪[ULINK]Added instruction trace support to the STMicroelectronics uPSD ULINK Driver.For details refer to Application Note 177: Using ULINK with STMicroelectronics Turbo µPSD 3300/3400 Devices and the sam ple projects in the folder ..\C51\EXAMPLES\ST uPSD.▪[BL51/LX51 Linker]Improved the OVERLAY directive. Now, using OVERLAY (* ! (func1, func2)), you m ay com bine the segm ents of several function call trees. This is useful for interrupt functions that have overlayable data but use the sam e interrupt level.Such interrupt functions cannot interrupt each other. Therefore, data overlaying of both call trees is possible. For example:void irq0 (void) interrupt 0 {unsigned char arr[10];arr[0] = 0;}void irq1 (void) interrupt 1 {unsigned char arr[10];arr[0] = 0;}If irq0 and irq1 are set to the sam e priority level their data areas m ay be overlaid. The OVERLAY directive m ay be specified to do that as follows:BL51 ... OVERLAY (* ! (irq0, irq1))The linker map file shows the following OVERLAY MAP.SEGMENT DATA_GROUP+--> CALLED SEGMENT START LENGTH----------------------------------------------?PR?IRQ1?I 0008H 000AH*** NEW ROOT *********************************?PR?IRQ0?I 0008H 000AHNote that both functions' call trees are overlaid.C51 Version 7.20 Release▪[uVision2 Debugger]。
AirCheck G2 v2.0.0 Release Notes说明书
AirCheck G2 version 2.0.0 Release NotesOctober 2017AirCheck G2 v2.0.0 Release Notes briefly describe the Bug Fixes included in the release, along with Known Issues to be aware of. It also includes a reference to Frequently Asked Questions (FAQ).Upgrading to Version 2.0Upgrading from 1.1.1 to 2.0 is straightforward, however there are several recommended steps that you can take to further minimize the chances for problems. Following these steps will ensure important data is not lost when transitioning to the new build.e the AirCheck G2 Manager application to export and save any screen captures or session filesoff your unit prior to upgrading.2.Ensure you have saved a backup copy of all AirCheck G2 profiles, and session files you may havecreated, upgrading the unit will migrate files to a 2.0 format, and should you need 1.x versions in the future you will need to use the archived copies.3.Before upgrading your 1.x AirCheck G2 to 2.0, we recommend that you ensure you are running1.1.1. Upgrading directly from 1.0.0 is possible, but upgrading from 1.1.1 is recommended.4.After performing steps 1 – 3 as applicable, you should then update your AirCheck G2 Managersoftware to the 2.0 version.5.Finally after updating your AirCheck G2 Manager Software to 2.0, attach your 1.1.1 AirCheck G2to your computer using the USB cable and update it to the v2.0 firmware.Version 2.0 New FeaturesThe AirCheck G2 v2.0 release brings enhancements to existing AirCheck G2 features as well as new features never before seen in an AirCheck tester.New and Updated FeaturesPerformance Testing with iPerfQuickly and easily test the throughput on your network by conducting iPerf tests from an AirCheck G2 to an iPerf server. The iPerf test allows a user to validate the throughput on their network at a given location.The tester uses the industry standard performance measuring tool iPerf in either UDP or TCP mode of operation. Tests can be conducted with a customer’s iPerf server they install themselves on their own or utilizing our new Test Accessory.IPerf results are logged to your session file and can be saved and reviewed by using the AirCheck G2 Manager software.iPerf ConfigurationA new configuration area is available in the AirCheck G2 settings: iPerf Settings. Additional new iPerf thresholds are available for configuration in the Thresholds area.iPerf SettingsProtocoliPerf tests can be run for TCP traffic or UDP. Allperformance tests will be run based upon the traffictype selected here.PortConfigures the port to be used for the iPerf traffic.Test DurationConfigures the amount of time (in seconds) for the iPerftest to run. The test runs an uplink followed by adownlink test. This duration is for the total time of bothtests, so the default 20s setting will result in a 10s uplink followed by a 10s downlink test. ThresholdsThis is not a setting but instead is a link to the AirCheck G2 Thresholds configuration screen.Remote Battery TypeThis sets what battery type is present in a Test Accessory. The AirCheck will use this information to give the most accurate reading possible for the remaining battery level of your Test Accessories. Running an iPerf Performance TestAn iPerf test can be conducted by following these steps:1.Connect to a network or an AP as before2.After a successful connection, a newbutton is available at the bottom of thescreen titled “iPerf Test”. Tap thatbutton. The Select iPerf Server screenwill now display.3.You can now select what iPerf serveryou would like to use. You can tap inthe space next to “iPerf Server” tomanually enter the IP address of theiPerf server you would like to testagainst, or you can select from a list ofdetected Test Accessories at the bottomand then tap “Done”. For furtherinformation on configuring iPerf serversand managing Test Accessories pleaserefer to the User Guide.4.Tap “Start” at the bottom of the screento begin your iPerf test. The test will runfor the configured amount of time, andresults will be marked pass/fail basedupon the configured threshold.Captive Portal SupportCustomers asked and we listened, users can now conduct all their AirCheck testing even on public facing networks that feature a captive portal.A new configuration item is available in the AirCheck G2 Network Configuration screen. For a given network, you can set Captive Portal to be On or Off for that network.When attaching to a network configured as a captive portal network, the AirCheck G2 will open a web browsing screen for the user to provide any necessary interaction.Important Notes:•Some web pages contain small features (such as check boxes) that can be difficult to accurately interact with unless the page is zoomed in.•Secondary pop-up windows (such as opening a Terms and Conditions form) that open off the main Captive Portal page are not supported.Authorization ClassesOne of our popular AirCheck G1 features is now available on the AirCheck G2. Users can now mark APs as Authorized, Unauthorized, Neighboring, or Flagged. APs can be sorted by authorization class, and the updated AutoTest can now report on any APs that have been marked as Unauthorized or Flagged that are heard during the test scan. [Please note, Rogue AP for AutoTest is on by default after upgrading from 1.x to 2.0.] In addition, users can set up a ‘default’ setting to be used for any APs heard that do not already have an assigned Authorization class. If ‘None’ is selected, then no ACL will be assigned and that AP will not indicate any ACL icons in the AP listings.Interferer Detection and ClassificationSometimes the problem isn’t the Wi-Fi, it’s the other devices in your area. Get a view into what other technologies are in your airspace by detecting interferers such as Microwave ovens or wireless cameras. The AirCheck G2 will use its wi-fi radio to detect interfering technologies in the environment and attempt to identify them. Interferer events are categorized by the AirCheck G2 radio as it scans through the bands. Based upon the readings it receives during the scan, if the AirCheck G2 believes the devices is operating with enough power and regularity to interfer with your Wi-Fi Network, it will attempt to identify an interfering device and (if identified) an interferer event will be logged.Various Small EnhancementsChannel OverlapUsers have requested the ability to visualizethe channels and how they overlap witheach other. This view is now available atthe tap of a button from the Channelsscreen.Supported Rates vs. Basic RatesAnother common request was to separate the rates information the AirCheck provides on an AP into Supported vs. Basic rates, so that the user could see explicitly how the AP was configured. We’ve made this change to the AP Details screen, so both pieces of information are now available.Save a Packet CaptureNow when saving a session file, the user also has the option to save that information as a PCAP. The capture file is automatically set to slice packets at 512 length. Packet capture files can be exported from the unit via a supported USB thumb drive.Version 2.0.0 Bug FixesDE14857 Upgrading firmware via the AirCheck G2 Manager no longer causes an error message of: “Error transferring AirCheck G2 firmware file”DE15486 After disconnecting from AirCheck G2 Manager and rebooting, the AirCheck G2 no longer will occasionally show AutoTest, Ethernet Test and soft keys as disabled (greyedout).DE15659 If a Profile is created/edited in AirCheck G2 Manager with multiple security certificates and at least one Network, and that Profile is transferred to an AirCheck G2 and thatNetwork is edited within the AirCheck G2, the first certificate in the Profile’s list is nolonger automatically assigned to that Network.Version 2.0.0 Known IssuesDE14570 AirCheck G2 Manager does not apply grouping of virtual APs (BSSIDs on the same AP radio). Therefore the AP count shown in AirCheck G2 with virtual AP grouping enabledmay not match the AP count in AirCheck G2 Manager.DE14604 If AutoTest connects to a hidden network, Network Coverage will show 0 APs. This will cause the connection test to fail when using the default threshold for Network Coverage.You can adjust this threshold in Settings / Thresholds to avoid this.DE15401 If a negative signal adjustment causes the signal level to exceed the -99 dBm minimum level limit, Signal/Noise Ratio (SNR) readings may be incorrect.DE15466 Link-Live does not report channel utilization for wireless connection tests.DE15541 If the AirCheck G2 is set to scan on only one channel, it is possible that a Connect to Network test can connect to the network on a different channel. 802.11 Types reportedto Link-Live might be missing in this scenario.DE17209 After running an Ethernet or iPerf test the * will appear next to the profile name indicating a change to the profile despite the user not changing profile characteristics.This occurs due to “last used” information being saved to a profile by the unitautomatically.DE17343 If a 2.0 unit is downgraded to 1.1.1, the unit should be reset to factory defaults before upgrading again to 2.0 to prevent the first test result to fail Link-Live archiving.DE17394 Changing the Date or Time on the unit puts it into a very slow scanning state which can only be recovered by rebooting the unit.Frequently Asked Questions (FAQ)For a list of FAQ and answers, please log into your link-live account and visit https://app.link-/support. Select the AirCheck G2 article.。