News & Politics
acslXtreme™ Release Notes acslXtreme Version 1.3.2a The AEgis Technologies Group, Inc. 631 Discovery Drive Huntsville, AL 35806 U.S.A. acslXtreme™ Release Notes Version 1.3.2a Page 2 of 8 1.0 Scope These release notes refer to acslXtremeTM Version 1.3.2 released February 2003. Version 1.3.2 is the First Customer Shipment (FCS) of acslXtreme, the sophisticated, next-generation tool for modeling continuous dynamic systems and processes. 2.0 Overview of Improvements over the legacy ACSL product acslXtreme™ provides a single Integrated Development Environment (IDE) through which simulation model development, execution, experimentation, and results analysis are controlled. acslXtreme includes both graphical and text-oriented modeling environments that give you full control over your models. From a functionality standpoint, acslXtreme includes the features from ACSL® 11.8 Sim, Graphical Modeller, and Math in one program. acslXtreme builds on the main strengths of ACSL - speed, advanced solution algorithms, ability to solve non-linear problems, and our physical representation approach. The following list highlights some of the new capabilities that acslXtreme has over the ACSL 11.8 software: • Comprehensive Integrated Development Environment (IDE) providing complete model design, development, execution, and analysis capability in one package • Choice of target language between C/C++ and FORTRAN • GNU C Compiler provided on distribution media • Interactive debugging in both text and graphical modeling environments • Dramatically improved Plotting Capability including 2-D, runtime, and 3-D • Improved Export capabilities for results data and plots • Advanced CSL Code Editor with context sensitive color coding • Improved support for external C, FORTRAN, and M-Files • Enhanced model API with C, .NET (C++, C#, and VB.NET) binding • ACSL v11.8 GM porting tool For detailed instructions on migrating ACSL models to acslXtreme refer to the ACSL to acslXtreme Migration Guide located in the Documentation Folder under the acslXtreme installation directory. 3.0 On-Line Help and Documentation acslXtreme incorporates an extensive On-line Help facility. Help is accessed through the Help menu or by clicking the Help toolbar icon. A self guided online tutorial is also available which provides an overview of the new acslXtreme user interface, simulation workflow, and help resources available for more detailed information. The following is a brief description of each manual included in the online help and its relevance to creating simulations using the acslXtreme software. acslXtreme™ Release Notes Version 1.3.2a Page 3 of 8 Getting Started Guide - Provides basic information on the installation and registration of the acslXtreme software. It also contains a couple of basic examples designed to verify installation and functionality of the software while introducing fundamental processes for continuous simulation such as creating Workspaces, Projects, and Block Diagrams, compiling models, and basic analysis such as plotting. acslXtreme User's Guide - Introduces the user to the acslXtreme Integrated Design Environment (IDE), presents an overview of simulation workflow using both CSL and Block Diagram modeling, describes analysis functions associated with plotting, exporting, and printing data, and introduces advanced topics such as debugging, managing block libraries of PowerBlocks, and external C and Fortran code with models. Several appendices are provided which include a variety of detailed examples, overview of the Simulation API, mathematical background, file types, error messages, and details on editing plots. acslXtreme Language Reference Manual - Provides a detailed overview of the Continuous Simulation Language (CSL), syntactical information the programming elements which comprise the CSL modeling language, the use of macros, and acslXtreme system symbols. acslXtreme Command Reference Manual - Presents a detailed syntactical information on commands for control of a simulation and analysis of simulation data using functions, M-Files, and scripts. The full text of the acslXtreme Getting Started Guide, User Guide, Language Reference Manual, and Command Reference Manual are available through online help. In addition, PDF files are available in the Documentation folder under the acslXtreme installation directory. 4.0 Installation Chapter 2 of the Getting Started Guide contains detailed instructions on the installation of both Single User Licenses (SUL) and Floating Network Licenses (FNL) of acslXtreme. The first time acslXtreme is installed a 14 day demonstration license is provided. License registration can be accomplished online using the automated web licensing procedure at http://www.acslxtreme.com/web-fulfill/login.jsp. By installing the acslXtreme program, Licensee agrees to all terms of the End User License Agreement (EULA). For installation support contact support@acslXtreme.com or to purchase the acslXtreme software contact sales@acslXtreme.com. For more information on acslXtreme and appropriate contact information go to www.acslXtreme.com. 5.0 Known issues The following sections describe known issues; TR’s = Trouble Reports; CR’s = Change Request). Please submit any additional TR and CRs to Technical Support using the following link: http://www.acslxtreme.com/acslXtremeTechQuestionForm.html. acslXtreme™ Release Notes Version 1.3.2a Page 4 of 8 5.1 Deletion of “License.lic” file during uninstall • Change Request: o When acslXtreme is uninstalled, the license file (default name is “License.lic”) is removed along with the program. • Work Around: o This will be corrected in future release. It is recommended that the license file be stored for backup purposes by Licensee. To view and save a previously generated license file go to the web licensing page on the located at http://www.acslxtreme.com/web-fulfill/login.jsp and enter your License Authorization Number (e.g. OR123-4567890) then hit View Licenses. 5.2 Line Continuation within a Macro • Trouble Report: o If a line continuation (&) is used in a Macro, the acslXtreme parser will not be able to handle the line, and a parser error message will be displayed when exiting or loading the model. • Work Around: o The maximum number of characters per line is compiler dependent. The documentation for each compiler can be checked although a length of 1024 characters is stated to function properly. There is no work around in acslXtreme for this issue with the initial release. This will be fixed in an upcoming release. 5.3 Cut, Copy and Paste in Block Diagram • Change Request: o The Block diagram Window does not currently support the ability to Cut, Copy and Paste (Ctrl-X, C, and V). • Work Around: o (1) A user defined block library can be created. The block that is desired to be copied can be drag and dropped into the Block Diagram. or o (2) A new block can be created and the CSL/GSL code can be cut and pasted from the code editor window. 5.4 Issuing a “!! Command” from the anlyz> prompt in the Command Window • Change Request: o Issuing ‘!! start’ (or any other similarly formatted simulation runtime command) from the anlyz> prompt in the Command Window executes properly but is displayed as a comment in the Command History window. • Work Around: o The command functions properly by the acslXtreme software but is displayed incorrectly in the command history window. Ignore 5.5 Using Watch Window for Array Data Types • Trouble Report: o The watch window does not support the ability to watch individual array element values. If an array variable is specified in the watch window, the value of the first element of the array is displayed. • Work Around: o Use the DISPLAY simulation control command to view array element values. 5.6 Online help for TeeChart • Trouble Report: acslXtreme™ Release Notes Version 1.3.2a Page 5 of 8 o If acslXtreme is not installed in the default installation directory, the Help button associated with the Edit Plot Properties, gives the message 'Cannot find the C;\Program Files\AEgis Technologies\acslXtreme\TeeUserX5.hlp file.' • Work Around: o Browse to the TeeUserx5l.hlp file that is located in the directory where acslXtreme was installed. Once you point to this file, the error should not occur again. 5.7 Memory Pooling Issue • Trouble Report: o acslXtreme currently has a memory pooling issue associated with the .NET framework. acslXtreme may allocate memory when a workspace is opened and does not get released when the workspace is closed. • Work Around: o Depending on available memory; users may need to exit out of acslXtreme and restart the application after multiple open/close operations. 5.8 Use of Large Fonts • Trouble Report: o On Windows 2000 Operating System if a computer has the Display Font Size set to “Large Fonts”, the user may experience screens with words that appear to be cutoff. • Work Around: o Change the “Large Fonts” setting to “Small Fonts”. This is located at Start > Settings > Control Panel > Display > Settings > Advanced. 5.9 Watch Variable Inconsistency • Change Request: o Watch window variables are displayed anytime the simulation stops. The three stop conditions that generally occur are break points set in debug mode, manual intervention (e.g. stop button pressed), or a normal termination of the simulation (e.g. TERMT condition is met). The variables values displayed in the watch window are sometimes different than the values shown using the DISPLAY command upon termination of a simulation. • Work Around: o The watch window is normally used to view variable values when a debug break point occurs. In this instance, the watch window values and the DISPLAY values are consistent and correct. If termination occurs through manual intervention or normal simulation termination, the watch window and DISPLAY values may differ. In these instances, the Watch window value is not being updated to show the final value. The DISPLAY value is correct. See DISPLAY in the Command Reference Manual for more information. 5.10 Plotting Vectors on Runtime Plots • Trouble Report: o When mapping an array variable (entry) to a plot block, the resulting output values are not displayed for runtime plots. • Work Around: o (1) Manually edit the array variable name as a scalar element so that it can be plotted using runtime plots (e.g. the plot wizard lists the array variable "foo" - manually edit it to read "foo(1)) or o (2) Create the plot in the analysis mode (after a simulation run) using any of the variety of means to create a plot (e.g. a plot block in block diagram mode, through command line, etc.) acslXtreme™ Release Notes Version 1.3.2a Page 6 of 8 5.11 RRR Files are not updated when using the “Start Debug Run” Icon • Change Request: o When running a simulation in Debug mode (e.g. using a Debug version of the compiler) using the toolbar Start Debug Run icon, the RRR file is not updated. Individual variables can be monitored using the watch and task list windows as described in the User’s Guide; runtime plots are created as the simulation runs. • Work Around: o If the compiler is set to debug, the RRR can be created by using the Run Icon (!) in the toolbar or typing start at a cntrl> prompt in the command window. 5.12 CSL Utility Routines not implemented • Trouble Report: o The following CSL utility routines are not implemented: AGET, APUT, DEBUG, LISTD, SETI, and SETR. In addition, the routine to add a customer integration algorithm has not been implemented. • Work Around: o These CSL utility routines are not implemented in this version of acslXtreme. 5.13 Direct Pass through of Data in a Compound Block • Trouble Report: o When connecting an input port directly to an output port within a compound block, the data may become inaccessible (e.g. cannot plot or list). • Work Around: o Insert a Gain PowerBlock from the Linear Operations Block Library between the input and output ports - use the default constant value of 1. 5.14 Analysis Commands that work only with Real or Complex Numbers • Trouble Report: o The following commands execute properly at the anlyz> prompt in the command window on real number values but not complex: ‘^’, ATAN2, POW2, and SCHUR. In addition, the QR command works for complex numbers but not real. • Work Around: o Will be implemented in a future release. 5.15 CSL Code Editor Window Behavior • Trouble Report: o The CSL Code Editor Window does not properly color code certain CSL keywords and intrinsic functions e.g. CONSTANT, LOGICAL, SIN, COS. In addition, the collapse (“+”) and the expand (“-“) options sometimes does not function correctly for nested sections of CSL code. • Work Around: o The CSL code will parse and execute correctly. The problems are cosmetic and will be investigated for correction in an upcoming release. 5.16 Debugging with models that INCLUDE Macros • Trouble Report: o When running in Debug Mode, breakpoints may not be recognized. • Work Around: o This is not currently implemented in this release of acslXtreme. acslXtreme™ Release Notes Version 1.3.2a Page 7 of 8 5.17 Using Unix or Linux FLEXlm License Servers • Trouble Report: o During the license registration process, you may be unable to enter the HOSTID of the Unix/Linux system. • Work Around: o The floating license manager system that acslXtreme uses expects the HOSTID to be 12 characters long. If your physical address is not 12 characters or if you are having difficulties start the licensing server, please contact the acslXtreme technical support. 5.18 Runtime Command REINIT does not set Initial Values Properly • Trouble Report: o The REINIT simulation runtime command followed by a START entered at the cntrl> prompt in the command window does not reset the initial conditions properly to the last computed value of the state variables. • Work Around: o To reinitialize the state variables to the last computed value, issue a SAVE to file, then a RESTORE simulation runtime command followed by a CONTINUE. ! For example at the cntrl> prompt: set tstp = 10 start save /f=save.txt restore /f=save.txt set tstp = 20 (or something greater than before) continue 5.19 DASSL Algorithm not supported • Trouble Report: o When setting the integration algorithm to DASSL (IALG=10), the state variables are not updated. • Work Around: o This is not currently implemented in this release of acslXtreme. 5.20 Display of Comment Lines in Code Editor • Trouble Report: o On some computers, the comment statement (green and italicized) will be hard to read. • Work Around: o The command executes correctly either as a comment or as a command (!!) accordingly. 5.21 Changing CSL block code from Embed to Link • Trouble Report: o If you use the suggested default name in the open dialog box when changing the block data properties of a PowerBlock in a Block Diagram, it will not save your work. • Work Around: o In the open dialog box, change the name to a different filename to save the code as GSL. 5.22 Running in Demo Mode requires Administrator Privileges • Trouble Report: o If running in the 14 day Demo Mode (without a “license.lic” file in the acslXtreme installation directory) and acslXtreme is started, depending on the Operating System you may encounter a CLR (Common Language Runtime) Error or it may appear that nothing happens at all. acslXtreme™ Release Notes Version 1.3.2a Page 8 of 8 • Work Around: o Use the User Accounts option in Control Panel to modify your privileges to be a part of the Administrators group. 6.0 Technical Support Information For detailed information on using acslXtreme refer to the on-line acslXtreme User’s Guide. Extensive examples are provided in the User Guide Appendix A which cover a wide variety of topics. If the problem is about using or programming with acslXtreme, or an earlier version of ACSL®, please consult the manuals provided online or in .pdf format with the installation of the software. If additional help is required, acslXtreme technical support can be contacted through the following means. Website The acslXtreme website at www.acslXtreme.com provides a variety of resources for technical support. You can go directly to the Technical Support section by using the following link: http://www.acslxtreme.com/acslXtremeTechSpt.html. E-Mail Questions can be sent directly via e-mail to the technical support and development team. Technical Support business hours are Monday through Friday, 8:00 AM to 5:00 PM, Central Time (US & Canada). For Technical Support questions and trouble reports about acslXtreme, send email to: email@example.com Telephone For telephone support, call AEgis Technologies during normal business hours Monday through Friday, 8:00 AM to 5:00 PM, Central Time (US & Canada) at: (512) 615-3575. FAX You can also fax questions directly to the acslXtreme technical support and development teams. For technical support issues, be sure to list “acslXtreme Support” as the recipient on the cover page. Fax questions to the following number: (512) 615-3574.