question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: Aspen Cim-IO may stop functioning if IO_TAGNAME or IO_VALUE_RECORD&FLD are empty. | Solution: During routine maintenance or record creation it's possible that some fields in Aspen Cim-IO transfer record occurrences may be left empty. Leaving the IO_TAGNAME or IO_VALUE_RECORD&FLD fields empty may cause Aspen Cim-IO to stop functioning as expected.
To ensure that this situation does not occur delete any occurrences in Aspen Cim-IO transfer records the have an empty IO_TAGNAME or IO_VALUE_RECORD&FLD.
Keywords: tags, fields, setup
References: None |
Problem Statement: The Aspen Cim-IO diagnostics feature has the ability to log a very large amount of information (beyond what is logged in the cimio_msg.log) regarding data transfer between the Cim-IO server and Cim-IO client. However, all of this information is not required if only troubleshooting problems with Put transfers. This Knowledge Base article describes how to set the Cim-IO diagnostics to only log information regarding Put transfers. | Solution: For versions prior to v2004, all parameters which control the Cim-IO diagnostics configuration are located in the cimio_diag.cfg file. This file is located in the following folder:
Program Files\AspenTech\CIM-IO\etc
Note: Items in cimio_diag.cfg are not case sensitive.
In order to set the Cim-IO diagnostics to log only Put information, turn off (or comment out) all of the lines toward the end in the 'Category' section. To comment out a line in the cimio_diag.cfg file, place an exclamation mark (!) in the first space of the row. For example,
!Category, Logic = ON
To turn a category off simply change ON to OFF as illustrated below:
Category, Logic = OFF
After all of the 'Category' lines are commented out or turned off, enter the following:
Category, Message-*-*-PUT = On
The wildcard parameters (*) above mean that all message logging options will be enabled for the Put requests.
As of version 2004, the Cim-IO diagnostics configuration information can be controlled either though the cimio_diag.cfg file (as outlined above) or through CimioProperties.exe. The following procedure describes how to use CimioProperties.exe to configure the diagnostic logging to only log information regarding Put transfers.
1. Open
Program Files\AspenTech\CIM-IO\code\CimioProperties.exe
2. Click Add/Update
3. On the Message tab click the New button. This will enable checkboxes under Detail, Message Type and Transaction Type. Select the appropriate items under each heading or check the Select All checkbox to select all items. Under Transaction Type select Put then select ON. Click Add. Click OK.
In the main window expand the Category node. There will now be an entry which shows
Category, Message-*-*-PUT = On
Keywords: Get
Transfer
Write
Send
Debug
References: None |
Problem Statement: How to solve Range invalid for dependent property error which is encountered during model execution.
The starting range 1e+030 is invalid for dependent property SPG in property calculator SPV. Setting both range values to EMPTY. | Solution: This error occurs when range specified for a dependent property in property calculation formula is incorrect.
The starting and ending range for the dependent property must be mentioned correctly.
Keywords: Property calculation formula, Range, Dependent property
References: None |
Problem Statement: What are the different types of matrix files generated in XLP? | Solution: XMps.mps - Holds initial activities for variable
XMps.Xlp - Holds final activities of variables
XMps_New101.Mps - Holds activities of inputSolution
Keywords: XLP matrix files
Xmps.Mps
Xmps.Xlp
Matrix files
References: None |
Problem Statement: What is the impact of selecting/unselecting the check box of Input/Output Mapping in XNLP setting | Solution: Input/Output Mapping feature for external models in XNLP is not checked by default in Aspen PIMS-AO. Whether this option is selected or not, does not affect how non-linear equations are evaluated. In both situations, the non-linear equations provided in the external modes are evaluated at each XSLP iteration.
However, Input/Output Mapping is essential depends on whether user wants to have derivatives for all terms in the external model or just terms that are mapped. Without checking it, the solver will be slower by having all terms, but have better ability to avoid localSolutions. This is useful if user have a large number of unmapped variables in the external model.
Keywords: None
References: None |
Problem Statement: How to I import / export COMThermo packages for use in DISTIL and HYSYS? | Solution: It is possible to import and export COMThermo property packages for use in both DISTIL and HYSYS.
In DISTIL:
To export the package, highlight the fluid package you want to export in the Fluid Package manager and click the Export button. A file navigator view will appear allowing you to name the exported file (*.cdf) and will default to the directory defined in the Preferences (Tools-->Preferences-->Files tab-->Locations page).
To import a fluid package, click the Import button in the Fluid Package Manager view. Navigate to the saved *.cdf file and select it.
In HYSYS:
To import the package, you must first create a new Fluid Package and select COMThermo. To do this, move to the Fluid Package tab and click the Add button. Turn on the COMThermo checkbox and then click the Import button. Navigate to the saved *.cdf file.
To export the property package, it must be a COMThermo package. Move to the Fluid Package and make sure that the COMThermo checkbox is activated. To export from HYSYS, property packages for both phases must be defined.
It is important to note that if you change the location of the *.cdf file, you must also move the *CC.xml and *PM.xml to the same location. Failure to do so may result in incorrect binary coefficients being imported.
Keywords: COMThermo, HYSYS, DISTIL, import, export
References: None |
Problem Statement: If the Cim-IO Interface Manager is not needed, execution at startup can be disabled by clearing the check box Invoke this application automatically at Login ? at the bottom of the user interface:
However, this option will not be available if Aspen Cim-IO failed to load for some reason, leaving no option to disable this tool to be executed after every restart.
This | Solution: provides other methods to disable the Cim-IO interface manager.Solution
The Windows Task Scheduler activates Cim-IO Interface Manager on every reboot for every user. You can disable the Cim-IO Interface Manager from automatically using the Windows Task Manager tool:
You can also disable the Cim-IO Interface Manager by changing the file “Cim-IO Interface Manager” (without extension) located in C:\Windows\System32\Tasks by changing the highlighted text to false.
You can then copy this file to other computers to keep the Cim-IO Interface Manager from automatically starting on them.
Keywords: CIM-IO Interface Manager
References: None |
Problem Statement: What happens when I use the I/O Device Wizard from the Aspen InfoPlus.21 Administrator to delete a CIM-IO logical device? | Solution: When deleting a CIM-IO logical device, the I/O Device Wizard performs the following steps:
Deletes the file disk:\Program Files\AspenTech\CIM-IO\management\iodevicename,csd on the CIM-IO server, where iodevicename is name of the logical device being deleted
Optionally removes iodevicename related services from the Windows services file on both the Aspen CIM-IO and InfoPlus.21 servers
Takes out the reference to the logical device from the file disk:\Program Files\AspenTech\CIM-IO\etc\cimio_logical_devices.def on both the Aspen CIM-IO and InfoPlus.21 servers
Note: After the I/O device wizard modifies cimio_logical_devices.def on the Aspen InfoPlus.21 server, InfoPlus.21 will not be able to access points from the device. The I/O device wizard does not verify if there are I/O transfer records in InfoPlus.21 reading points from or writing data to the device. Be sure that readings are no longer needed from the device before using the I/O device wizard to delete the logical device.
Keywords: I/O Device Wizard
Delete logical device
Remove logical device
logical device
References: None |
Problem Statement: Aspen Cim-IO redundancy may fail to cleanup properly if the letter case does not match for the Logical Device and External task names. | Solution: If using Aspen Cim-IO redundancy then create all Logical Device, and External tasks names using upper case lettering. In addition use upper case lettering when cross referencing Logical Device, External tasks, and in the Changeover task record.
Aspen Cim-IO configurations include the cross linking of Logical Device's (IoDeviceRecDef), External tasks (IoExternalTskDef), and Transfer records (IoGetDef, IoPutDef, etc). If redundancy is configured the Logical Device is also a linked to the Changeover task (IoExternalFTDef).
If the Logical Device is created and configured via the I/O configuration in the InfoPlus.21Administrator then all the records are linked with the correct case. The I/O configuration creates the records and links them using upper case lettering. If the logical Device and associated tasks are configured manually there is a possibility they will not be linked properly if the case does not match.
Keywords: tsk_detect
io_device
io_main_task
io_unsol_task
io_async_task
References: None |
Problem Statement: CIM-IO generates an error message indicating that redundant CIM-IO servers have a different configuration.
The complete message is as follows.
The CIM-IO server for logical device <logical device> on node <node> has a different configuration than the CIM-IO server on <another node> Please make sure your primary and secondary logical devices are an exact mirror of each other. For further assistance, please contact Aspentech Support.
The message indicates that differences exist between the logical devices on the two nodes. When using CIM-IO redundancy, both CIM-IO servers must run the exact same processes.
Some potential sources of the error are:
Differences in Store and Forward configuration
Differences in DIOP configuration (e.g., one node has an unsolicited DIOP, the other does not)
You can verify the problem by looking at the <logical device>.csd file in the %CIMIOROOT%\management folder on each CIM-IO server. The two files should be identical. Sample contents of the file are below.
CIM-IO Redundant Simulation,CIMIOSIMUL,CIMIOSIMUL
DontRun,,
0
StoreForward,Default
4
CIMIO SIMULATION DLGP,CIMIOSIMUL,C:\Program Files\AspenTech\CIM-IO\io\simulation\cimio_x_dlgp.exe, CIMIO SIMULATION READ DIOP,CIMIOSIMULREAD,C:\Program Files\AspenTech\CIM-IO\io\simulation\cimio_x_diop_read.exe, CIMIO SIMULATION WRITE DIOP,CIMIOSIMULWRITE,C:\Program Files\AspenTech\CIM-IO\io\simulation\cimio_x_diop_write.exe, CIMIO SIMULATION UNSOL DIOP,CIMIOSIMULUNSOL,C:\Program Files\AspenTech\CIM-IO\io\simulation\cimio_x_diop_unsol.exe, | Solution: Two methods can be used to address this problem.
Method 1
Use the InfoPlus.21 Administrator to make the necessary changes. Simply right click on the logical device that generated the error, and select 'Properties'. This should bring up the '<logical device> properties' dialog. Remove any inconsistencies between the servers. This includes:
Differences in Store and Forward
Differences in configured processes
The only difference allowed between servers is the path to the executable. All other configurable parameters must be identical.
Example 1: Node 1 has store and forward enabled, Node 2 has store and forward disabled.
Solution
1: Bring up the properties for the logical device and click on the processes tab. The initial state of the 'store & forward enabled' checkbox can be ignored. Click once, and then again to its desired behavior. The two CIM-IO servers should pick up the change and be mirrored.
Example 2: One node has extra processes (not found on the other node).
Solution
2: On the node with extra processes, bring up the properties for the logical device and click on the processes tab. Remove any extra processes from the list box and select OK.
Method 2
Provided that the paths to the executables are the same on both CIM-IO servers, the <logical device>.csd file from the CIM-IO server with the correct configuration can be copied to the CIM-IO server with the incorrect configuration. For logical devices created using the CIM-IO Wizard, the .csd file can be found in the \Program Files\AspenTech\CIM-IO\management directory.
IMPORTANT--Before copying the .csd file, stop the CIM-IO manager service on both CIM-IO servers. The services on both machines should be restarted after copying is complete.
Keywords: redundant
redundancy
cimio
failover
backup
primary
mirror
configuration
changeover
change over
References: None |
Problem Statement: Why doesn't Aspen CIM-IO update Aspen InfoPlus.21 tags even if IO_DATA_STATUS is Good and the transfer record processes as expected? | Solution: CIM-IO will not update an Aspen InfoPlus.21 tag if the tag's InfoPlus.21 time stamp is more recent than the time stamp read from the CIM-IO server. This can happen, for example, when
A query, Aspen Calc calculation, user-written external task, or VB script also modifies the tag and
The field IO_TIMESTAMP_SRC in the Aspen InfoPlus.21 logical device record is set to CIMIO Server (Interface) and
The clock on the CIM-IO server is behind the the clock on the InfoPlus.21 server.
Keywords: IO_DATA_STATUS
IO_TIMESTAMP_SRC
tag not updating
tag not changing
References: None |
Problem Statement: Will Aspen CIM-IO work on a Novell Network? | Solution: Aspen CIM-IO is a TCP/IP socket based protocol and will work on a Novell Network. If the CIM-IO Server and CIM-IO Client can ping one another successfully, then the CIM-IO communication should work.
Keywords: novell
References: None |
Problem Statement: How can I determine solve time in PIMS-AO parallel solve? | Solution: The solve time can be determined from the files written to the model folder.
Files that end with 1, 2, 3 are processors of the machine in use. CaseParallelSlave# file will show the amount of time for which each case runs on particular processor
and the file name that ends with Zero provides the total time.
Keywords: PIM AO solve time
XLP solve time
XLP parallel solve
PIMS AO parallel solve
References: None |
Problem Statement: Where can I find the supported operating systems for Aspen Cim-IO? | Solution: Aspen Cim-IO and Aspen Cim-IO Interfaces are supported on Server and Desktop operating systems as documented in the Aspen InfoPlus.21 Product Family installation guides.
Keywords:
References: None |
Problem Statement: What is the cause for the Error: Database Results.mdb is missing when running AO analysis? | Solution: The error: Database Results.mdb is missing when running AO analysis such as Parametric Analysis, Feedstock Basket Reduction or Ranging Analysis is caused because the SP1 package for Windows is not installed. The fix for the error follows:
For Windows 7 machines
The root cause of the issue is Microsoft made a change for ADO with Windows 7 SP1 which can be found here: http://support.microsoft.com/kb/2640696. This problem can be resolved by installing Windows 7 SP1 or by simply running Windows update ensuring that Windows 7 SP1 is included. After the update the following message will appear
For Windows Vista machines
The problem can be resolved by executing the .exe file found in the attached .zip file 440425_intl_i386_zip. This is with reference to the fix provided by Microsoft (http://support.microsoft.com/kb/2640696)
Keywords: Error: Database Results.mdb is missing when running AO analysis?
References: None |
Problem Statement: The CimioSFMonitor.exe utility is used to interrogate the Cim-IO Store file. (See the Cim-IO User's Manual for information about using this utility.) There have been new installs of Cim-IO v2004 where this utility does not recognize existing store files in the default Cim-IO\IO directory. When opening this tool, the STORE FILE window is blank. | Solution: Try registering the cimiosfmonitor.dll. To do this, go to:
START -> RUN type: cmd
type: cd %CIMIOROOT%\code
type: regsvr32 cimiosfmonitor.dll
Try to use cimiosfmonitor.exe again.
Keywords: cimiosfmonitor.exe
cimiosfmonitor
cimiosfmonitor.dll
References: None |
Problem Statement: What is the purpose of the IO_REQUEST_CHANGES field of a transfer record? | Solution: The IO_REQUEST_CHANGES field is used as a quick and easy mechanism for the CIM-IO client tasks to detect a change in the list instead of comparing the list on each request.
It is important for the CIM-IO client tasks to track that at least one change was made to the transfer record (the list of tags) since the last request was sent. Changes must be tracked so the CIM-IO Client tasks can let the CIM-IO server know that the list has changed. The CIM-IO server may have to rebuild a list of internal ids or things of that nature when a list changes. Although the number of changes isn't important for the CIM-IO subsystem to monitor (anything greater than 1 requires an update to the list), this field is incremented for each modification to a field so a user can see how many changes have been made to the record.
Keywords: get request
updated scan list
References: None |
Problem Statement: After deleting an old device .CSD file in the Cim-IO Management folder, the file reappears after a system reboot. | Solution: CSD files are created as a result of using the Cim-IO I/O wizard or the Cim-IO Interface Manager to configure a Cim-IO Interface. The Cim-IO Manager loads the CSD file into memory and restores the file before exiting. Therefore attempts to delete the file while the Cim-IO Manager service is running results in the file reappearing.
Follow these steps to delete a device .CSD file:
1. Stop the Cim-IO Manager service
2. Delete the old.CSD file
3. Restart the Cim-IO Manager service
Keywords:
References: None |
Problem Statement: Why does the IO_LAST_STATUS_DESC of a transfer record show INVALID PRIORITY when viewed with SQLplus query but when the same string is viewed in ENGCON there is a difference in string length? | Solution: The reason for the difference in the description of the error is because the record was activated without setting the Priority level. When a record is activated and the IO_Priority field is left in the default state of <<, the resultant error is INVALID PRIORITY.
It is a must that the IO_PRIORITY of a transfer record be defined before the record is activated. The priority levels are defined on a scale of 1 - 9, with 5 - 9 representing a normal range and 1- 4 representing high priority read operation.
When the priority is set and the transfer record is re-activated, the IO_LAST_STATUS_DESC, if examined by an SQLplus query, will show a match in ENGCON as well as in Aspen InfoPlus.21 Administrator.
Note: Some Cim-IO device-specific interfaces may use this record field for another purpose. The device specific user guide must be checked for additional information.
Keywords: Priority level
Record
References: None |
Problem Statement: Often AspenTech-related services require third party services to be running before the AspenTech services can correctly run.
How do I delay the start of AspenTech services to wait for third party services to start? | Solution: An easy way to accomplish this is to change the default startup type of the service from Automatic to Automatic (Delayed Start).
This causes Windows to wait two minutes before starting a service when rebooting a server.
To change the startup type of a service, open the Windows Services page, right-click on the service, and select properties.
Then select Automatic (Delayed Start) as the Startup Type.
Â
Keywords:
References: None |
Problem Statement: When writing a value to the Device Control via Aspen CIMI-IO, the following error is reported in the IOputdef record
Data Type Not Supported | Solution: Check the quality of the value that is been written and make sure is not Suspect.
Put does not work when Quality Status is 'Suspect'
Keywords: IOPutDef
Suspect
References: None |
Problem Statement: After installing aspenONE V8 or later the Aspen Cim-IO Manager service will not start. | Solution: The Aspen Cim-IO Manager service attempts to checkout a SLM_CIMIO_Core license. The service will stop after determining A) the license request is not granted and B) the license request has never been granted to the Aspen Cim-IO Manager service.
If the Aspen Cim-IO Manager service fails to start due to a licensing issue it will log a message in the Windows Application Event Log.
To resolve this issue make sure the SLM License file or SLM License Server is available.
Keywords:
References: None |
Problem Statement: Is there a TDC3000 package for RTO? | Solution: The TDC3000 package for RTO provides custom data segments and cl for supporting tags on the dcs and operator displays.
Contact AspenTech Support for these packages. Keep in mind, these are not products, but project tools. These packages are not developed, tested or supported the way in which a product is supported. The version contained in this article are the latest to date, version 113.
The Users Guide for this tool is attached to this item, feel free to download.
Keywords:
References: None |
Problem Statement: Occasionally, due to the error Error 1075: The dependency service does not exists or has been marked for deletion a user may need to follow one of our kb articles 106428 or 132187 to remove a service such as the CimioManager Service. However after running the -remove, the service still appears in the Control Panel Services applet. Running the -remove again tells the user that it cannot be removed but it is marked for deletion. | Solution: Just close the Control Panel Services Applet and reopen it. Closing that applet causes any service marked for deletion to actually be deleted.
Keywords: applet, error, deletion, removal
References: None |
Problem Statement: It has been noticed that even with IO_Device_Processing set to OFF, the TSK_DETECT task still tries to reactivate. Even turning off the IO_Device does not stop the Re-activated message in the CIMIO log file. It takes a while until it really stops.
Is it just a nuisance message or is there something more sinister going on? | Solution: The Reactivation of READ transfer records in a redundant configuration allows to wake up transfer records that appear to be dormant. Every time the redundant configuration is monitored, the feature computes the time difference between now and the last update time posted on each valid READ transfer record for the active node. If this time difference is greater than twice the timeout value, the record in question is re-activated. Transfer records of devices with record processing set to OFF, S&F disabled, or IO_FREQUENCY=0 are not processed. Also, if the timeout value is less than 15 seconds, this value is replaced for calculation purposes.
Keywords: None
References: None |
Problem Statement: You have just applied the latest patch to your Cim-IO server and have restarted the machine. When manually starting the Aspen Cim-IO Manager service you receive the following error:
Windows could not start the Aspen Cim-IO Manager service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion. | Solution: The fact that this occurs after a recent installation of a patch suggests the problem is due to blocked files. Check the file properties of the Cim-IO files in the Code folder, eg. cimio_sf_store.exe file:
C:\Program Files (x86)\AspenTech\CIM-IO\code\cimio_sf_store.exe
In particular, look out for the Unblock button with the attendant Security message:
This file came from another computer and might be blocked to help protect this computer.
You could unblock each file in turn but to be thorough it is advisable to reinstall the patch, taking particular care to first unblock the compressed zip file which you downloaded from the support website.
Known Issue with Patching
There is an alternative explanation of this headline error. We have seen failures of the patching process to correctly install the cimio.dll file, this has happened without any error during installation. It should be repeated here though that if the installer needs to repeat the patch installation, then the installer must, every time, extract or copy all the ER files into the temporary directory before executing the installation utility.
Nevertheless, please check to see if the cimio.dll in the patch media has been copied over to the destination %COMMONPROGRAMFILES%\Aspentech Shared\cimio.dll. If this has not happened, use Windows Explorer and manually rename the old file and copy over the new one into the Aspentech Shared folder. You should then find that Aspen Cim-IO Manager service will start up without error.
Keywords: Patch
Security
Cim-IO Server
InfoPlus.21
Error 1053
CIO141017I
Install
Entry Point Not Found
References: None |
Problem Statement: How do you change the Framework Database Password? | Solution: This document describes how the password for the Aspen Framework SQL Databases can be changed.
All client applications use a common user name and password when connecting to the Framework databases. Both the user name and password is defined when the Framework is installed on the server.
To change this password, log into the Framework server's Administrator account. Then from the Start Menu, select Programs, Microsoft SQL Server, and Enterprise Manager. Expand the folders under the Framework. Open the Security folder, select Logins and then select the user name that was defined when the Framework was installed on the server. Right click and select properties. Change and confirm the password.
Keywords: SQL Database
AFWDB
PODB
password
References: None |
Problem Statement: Sometimes when the analysis doesn't complete in PID watch, it is because of problems with Regional Settings. | Solution: The attached executable has been applied to Italian systems and resolved this problem. It may work with other european settings, but be sure to save the original PIDWatch executable before replacing it with this one, in case it doesn't.
Keywords:
References: None |
Problem Statement: How do I make Cim-IO Redundancy work on a Windows 2008 Server? | Solution: Part of the configuration process when setting up Aspen Cim-IO Redundancy is running the utility ...C:\Program Files (x86)\AspenTech\CIM-IO\code\CimioProperties on the Aspen InfoPlus.21 Server. CimioProperties creates and maintains registry keys needed for redundancy.
On a Microsoft Windows 2008 server, you must run CimioProperties as an Administrator in order for the registry keys needed for redundancy to be written to the correct location HKLM\SOFTWARE\Wow6432Node\AspenTech\CIM-IO. If you do not run CimioProperties as an administrator, the operating system writes the registry keys to a location in HKEY_USERS, and they will be not be accessible to TSK_DETECT and the Aspen InfoPlus.21 Cim-IO client tasks, and this causes automatic failover to not work. Furthermore, since Windows 2008 gives no indication that the operating system has written the registry to the wrong location, it appears that CimioProperties worked correctly.
Keywords: CimioProperties
TSK_DETECT
failover
redundancy
administrator
registry
References: None |
Problem Statement: This knowledge base article describes how to use the Aspen Cim-IO Checksum feature. A checksum is a value that is used to check the integrity of data. | Solution: When checksum is enabled for Aspen Cim-IO the sending machine calculates a checksum and attaches it to the message to be delivered. The receiving machine then extracts the checksum from the message header, and compares the results with a second checksum that is performed locally on the receiving machine.
Important: If the checksum results of the sending and receiving machines do not match, the message is rejected and an error is logged in the cimio_msg.log file.
Enabling checksum offers two benefits
1. Documents network errors between the Cim-IO clients and servers.
2. Prevents the Cim-IO client from attempting to process corrupt responses.
The checksum functionality is enabled and configured via the Cim-IO Checksum Tab in the Cim-IO Properties utility located at \AspenTech\Cim-IO\code\CimioProperties.exe
To Enable Checksum
1. Checksum is enabled locally on the machine by clicking the ON switch.
2. This must be repeated on all servers and clients that support the checksum feature or those nodes must be added to the Excluded Nodes List.
Important: In order for checksum to be fully active, checksum must be enabled on the Cim-IO server and Cim-IO client machines.
Important: To prevent the occurrence of possible Cim-IO errors during transition to Cim-IO Checksum mode, it is highly recommended that client applications be disabled until after configuration of checksum is complete.
If Both Cim-IO Kernels Support Cim-IO Checksum
1. Enable checksum on the server and exclude all your clients initially.
2. As checksum is enabled on each client, remove the client name from the Excluded Nodes List.
If Both Cim-IO Kernels Do Not Support Checksum (Mixed Environment)
In the event that a newer version of Cim-IO configured with checksum needs to communicate with an older version of Cim-IO that does not support checksum functionality.
There are two options to allow successful communication:
1. Upgrade the older version of Cim-IO to a newer version that supports the checksum feature.
2. Add the node to the Excluded Nodes List to allow backwards compatibility. (Shown Below)
In this example, the checksum functionality is switched to ON. NODE1 is specified in the Excluded Nodes list. A checksum will be calculated and sent to all the Cim-IO machines except for NODE1.
Additional
? If the Cim-IO kernel on either side does not support checksum, you will have to upgrade to a newer version of Cim-IO to take advantage of this feature.
? The checksum feature adds a small load of approximately 2% to both the client and server.
Keywords: CIMIOProperties.exe
References: None |
Problem Statement: How do I start multiple devices when the Aspen CIM-IO Manager service starts if they were configured manually? | Solution: AspenTech recommends using the I/O Wizard in Aspen InfoPlus.21 Administrator to configure logical devices, which allows the devices to start/stop individually or when the Aspen CIM-IO Manager service starts.
If this configuration method can not be used then device startup can be configured in the %CIMIOROOT%\commands\cimio_autostart.bat file.
When Aspen Cim-IO Manager Service starts the cimio_autostart.bat file executes. If commands include batch files they must be called using the CALL command which allows multiple batch files to execute from within another batch file.
EXAMPLE:
The example below is for CIM-IO for PI, but it can be applied to any interface:
call C:\Program Files\AspenTech\CIM-IO\io\Cimio_rto\Cimio_rto_start.bat
call C:\Program Files\AspenTech\CIM-IO\io\cio_pih_api\cimio_pi_start logical device
Keywords: multiple
CIM-IO Interfaces
call statement
References: None |
Problem Statement: When trying to make a simple connection to a Logical Device, and the IO_LAST_STATUS field in an IoGetDef record reads 'Cim-IO Client Task Down', how can this be resolved?
The term Device as noted in this Knowledge Base Article refers to any Logical Device, such as a Programmable Logic Controller (PLC), or a Distributed Control Systems (DCS), | Solution: Try to resolve the problem as follows:
? Make sure your TSK_M_???? and TSK_A_???? records are defined by IoExternalTaskDef and not by ExternalTaskDef.
? Look in the Aspen InfoPlus.21 Manager and confirm that your TSK_M_???? is present and running.
? Look in the Aspen InfoPlus.21 Manager and confirm that your TSK_A_???? is defined and running?
? Try toggling the following off/on:
io_record_processing.
io_data_processing.
? Make sure your Security Client Service is running.
? Finally if none of the above works, try KB=103176 and/or KB=110241.
Keywords:
References: None |
Problem Statement: This knowledge base explains why integer data appears in the Aspen Cim-IO diagnostic log file (cimio_diag.log) as real data. For example, 3600 appears in the log file as 3600.00. | Solution: All numeric data are converted to real values when passed through the logging function. This means that any non-ASCII value will be converted to a real number when written to the cimio_diag.log file. This only occurs when data values are written to the log file. Data values are not converted to real values during normal Aspen Cim-IO client/server communications.
Keywords: Float
Floating point
References: None |
Problem Statement: How to change Unit of Measure for Aspen Plus Hydrocracker? | Solution: Generically, we have two unit sets for Aspen Plus Hydrocracker ? US and SI and also two modes (mild and to extinction). The default model invokes the script Plant_mphc_us.ebs when the model is connected and this, in turn invokes the script us_unit.ebs. If the user prefers the SI units, this can be changed. There is a hidden worksheet called EB Scripts which would first need to be unhidden. Column B of this worksheet controls which script is invoked. In that column you can see 5 potential scripts that can be called:
Plant_mphc_us.ebs
Plant_mphc_si.ebs
Plant_exting_us.ebs
Plant_exting_si.ebs
Plant_fcctreat.ebs
Actually, that last script isn?t delivered so it won?t do anything if the user tried to select that. The ?//? acts as a comment line, so the default has options 2, 3, 4, and 5 commented out and the plant_mphc_us.ebs is what is being invoked. If the user prefers SI, then that line could be commented out and the line for Plant_mphc_si.ebs could be uncommented. Similarly, if you had a unit running to extinction (this means there is a bottoms recycle), you could invoke either plant_exting_us.ebs or plant_exting_si.ebs. Note that only one of these should be invoked and all other should be commented out. If the user wants something other than SI or US, they would need to create their own script and set the variables accordingly. The us_unit.ebs and si_unit.ebs scripts just set the uom for each variable on a variable by variable basis.
Keywords:
References: None |
Problem Statement: Why does the Aspen Cim-IO Interface Manager not add an entry in the Cimio_Logical_Devices.Def file? | Solution: The Cim-IO Interface Manager [CIM] does not add an entry into the Cimio_Logical_Devices.Def file because is it not required by the Cim-IO Interface Server.
The CIM is designed to create a Aspen Cim-IO interface server instance which does not rely on an entry in the Cimio_Logical_Devices.Def. The logical device is a concept required by the Aspen Cim-IO client therefore the Aspen Cim-IO client configuration will add the required entry into the Cimio_Logical_Devices.Def.
Here are a couple examples where the entries in the Cimio_Logical_Devices.Def are required.
Aspen Cim-IO_T_API; After a Aspen Cim-IO Interface is created the user may wish to test reading/writing on the Aspen Cim-IO interface server. The Cim-IO_T_API application is a standalone Cim-IO client used for testing therefore it requires the creation of a logical device. Option 2 will add the appropriate entry into the Cimio_Logical_Devices.Def. Once logical device is added the user can test reading and writing data.
Aspen Cim-IO client for Aspen InfoPlus.21; The configuration of a Aspen Cim-IO client connection to a Aspen Cim-IO Interface can be completed by using the Cim-IO IP21 Connection Manager [CCM]. The CCM will add the appropriate entry into the Cimio_Logical_Devices.Def file along with creating the required records and tasks in Aspen InfoPlus.21. Once this configuration is completed, tasks are started, transfers are configured Aspen InfoPlus.21 will be able to read\Write data to the Aspen Cim-IO interface. Also the Aspen Cim-IO_T_API can be used on the Aspen InfoPlus.21 system without any additional configuration.
Keywords:
References: None |
Problem Statement: Is there a way to prevent AsyncDlgp.exe from crashing? | Solution: If AsyncDlgp.exe is crashing regularly, there might be an issue that requires further investigation. However, in some cases, where everything seemed to be correctly configured, and AsyncDlgp.exe keeps crashing for no apparent , there is a workaround that can help AsyncDlgp stability.
The workaround is to change the compatibility mode for AsyncDlgp.exe.
? Windows Explorer C:\Program Files (x86)\AspenTech\CIM-IO\io\cio_opc_api\
Find AsyncDlgp.exe file
Right-click on AsyncDlgp.exe
Select Properties
AsyncDlgp.exe Properties Window is opened
? Tick Compatibility mode
o Run this program in compatibility mode for
o Select the correct OS
Click on Change settings for all users
Apply
If this workaround doesn?t fix the issue, please make sure to apply the latest Cim-IO patches on the server and on the client, and contact AspenTech for further support.
Keywords: AsyncDlgp.exe, Cim-IO
References: None |
Problem Statement: I get the following error when launching Aspen Plus Hydrocracker or any other application in the Aspen Plus Based Refinery Reactors suite: “Compile error in hidden module: Com2Dcom” | Solution: This error commonly occurs when code is incompatible with the version, platform, or architecture of this application. Please make sure you are running MS Excel 32bit, Aspen Engineering Suite is not compatible with Office 64bit.
If you have more than one version installed, you can register and unregister COM components to set the default version of MS Excel in the registry. That version will be used with Aspen Engineering suite:
Unregister the current version:
1. Open a command prompt as administrator (this can be done by searching for cmd in the Start Menu, right clicking the cmd.exe, and selecting Run as Administrator
2. Run the command: <Excel installation path>\Excel /unregserver
Re-register the desired version:
1. Open a command prompt as administrator
2. Run command: <Excel installation path>\Excel /regserver
You can check what is the current version on the following registry key:
HKEY_CLASSES_ROOT\Excel.Application\CurVer
Keywords: Aspen Plus Refinery Reactors, Aspen Plus Hydrocracker, MS Excel version, Register and unregister COM components, compile error.
References: None |
Problem Statement: error during install failed to set special folder 25
Windows 9x and Windows NT make use of many operating system special folders. These folders represent specific locations for application data, users settings, etc. If the folders are not defined correctly the error may occur. | Solution: Run the attached file (FixShellFolders.exe) to correct the folders.
Keywords: special folder
References: None |
Problem Statement: After downloading the TCP_TESTER zipped file found in | Solution: 137654 to CIMIO server and CIMIO client machines. Trying to execute the TCP_TESTER exe. file on the CIMIO server via Command prompt would show this error This application has failed to start because MSVCP100.dll was not found. Re-installing the application may fix the problemSolution The reason for the error message in command prompt is that tcp_tester is 32 bit and would need 32 bit version of MSVCP100.dll in order to run properly but this was not available in 32 bit so to resolve the issue, you would need to download and install Microsoft Visual C++ 2010 Redistributable Package (x86) from the Microsoft website. The link to the website can be found below: http://www.microsoft.com/en-us/download/confirmation.aspx?id=5555 Installing the vcredist_x86 would add this dll in SysWOW64 and then you would be able to use the tester
Keywords: TCP_TESTER CIMIO MSVCP Microsoft Redistributable Package vcredist
References: None |
Problem Statement: When you have an Aspen Cim-IO redundant system (2 Aspen Cim-IO servers and 1 Aspen InfoPlus.21 Server) and you want to apply an Aspen Cim-IO core patch, AspenTech recommends applying the patch on all three servers.
This Knowledge Base article describes a procedure to follow to minimize real-time data unavailability time and prevent data loss when applying the patch | Solution: Below are the steps for applying an Aspen Cim-IO core patch on an Aspen Cim-IO redundant system:
1. Make sure that the Aspen Cim-IO is in normal operation mode: Aspen InfoPlus.21 is receiving data in real time and both Aspen Cim-IO servers are operational.
2. Check the TSK_DETECT record to note which server (primary or secondary) is the active server.
3. Stop the Aspen Cim-IO client tasks (TSK_M_xxx, TSK_A_xxx and TSK_U_xxx) on the Aspen InfoPlus.21 server.
4. Make sure that the active server from step 2 starts buffering data in its Store file.
5. Apply the Aspen Cim-IO core patch on the Aspen InfoPlus.21 Server (don't restart client tasks yet!).
6. Stop the device on the not-active Aspen Cim-IO server.
7. Restart the Aspen Cim-IO client tasks. Verify that the data from the active Aspen Cim-IO server is unbuffered and Aspen Infoplus.21 starts to receive data in real-time.
8. Apply the Aspen Cim-IO core patch to the not-active Aspen Cim-IO server.
9. When the patch is applied to the not-active server and it is back in operation, perform a manual switch-over in the TSK_DETECT record.
10. When the switch-over was successful and data retrieval is continued from the patched Aspen Cim-IO server, you can apply the patch on the other Aspen Cim-IO server.
Keywords: CIM-IO
Patch
Redoundancy
ER
Engineering Release
References: None |
Problem Statement: After installing Aspen Cim-IO in a non default location some Start menu shortcuts will not open. | Solution: Follow one of theSolutions below to correct the shortcut.
Review the Problem with Shortcut dialog and if the Nearest match location is correct then click the [Fix it] button the change the Target location.
Right-Click on the shortcut, select Properties and edit the Target path so it points to the correct location and exe.
Keywords: None
References: None |
Problem Statement: You may observe a different behavior for the IO_LAST_STATUS field in the Cim-IO Transfer records. When, in a Transfer record, you set the DATA_PROCESSING for one or more tags to OFF, the IO_LAST_STATUS of the Transfer record will display Some Bad Points for every scan cycle. in the past you would only get the Some Bad Points status when the device would send a bad status for one or more tags. | Solution: The IO_LAST_STATUS behavior has changed in version 2006.5. This was changed to align with the usage in Process Control environments. When a measurement is switched off on the device, this indicates that the value cannot be trusted and should be disregarded..
A tag in a Transfer record should be only switched off for the same reason. If you no longer intend to scan the tag value, you should remove the tag entry from the Transfer record.
Keywords: Unsolicited
Getrecord
Some Bad Points
References: None |
Problem Statement: What functions does the Aspen Cim-IO Manager service have? | Solution: The Aspen Cim-IO Manager service performs the following functions that refer to server instance creation, maintenance, operation, and deletion.
· CheckIn_CheckOutLicense
· Start_Stop_Command_Batch
· Set_Logical_Device
· Start_Server
· Stop_Server
· Get_Server_Status
· Get_Server_Configuration
· Add_Server
· Modify_Server_Configuration
· Remove_Server
· Remove_SF_Services
· Remove_TCPIP_Service
· Del_Logical_Device
· Set_Logical_Device
· Get_Mgmt_Params
· Set_Mgmt_Params
· CreateExternalTasks
· Get/SetCimio_C_Paramsset
· GetSNFEnabledflag
· SetHealthCheckFlag
· AgreeOnTCP/IPPort
· Get/Set Nowriteoption
· ListOPCUAEndPoints
· ListProcessDataSources
· EnumerateServers
· EnumerateDLGPServices
· GetRemoteServicePort
Keywords:
References: None |
Problem Statement: The Store and Forward process (cimio_sf_forward.exe) errors out. The problem may manifest itself when the 'Aspen CIM-IO Manager' service starts (when done manually or at machine startup). The error message that appears is:
cimio_sf_forward.exe - Application Error (title of dialog box)
The instruction at 0x00406cff referenced memory at 0X00000004. The memory could not be written.
Click on OK to terminate the application.
Click on CANCEL to debug the application.
This problem may ultimately lead to data records not being updated with values from the DCS (Distributed Control System) or PLC (Programmable Logic Controller). Why is this problem happening and what can be done to fix it? | Solution: The file where Cim-IO Store and Forward buffers (stores) its data on the Cim-IO server is called the store file. It is typically located in:
%CIMIOROOT%\io
One example of the location would be:
C:\Program Files\AspenTech\CIM-IO\io
The store file's name usually has a format like the following:
CIMIO_STORE_<name of InfoPlus.21 server where Cim-IO client resides>.<name of Cim-IO client asynchronous task>
One example would be the following:
CIMIO_STORE_PEGASUSBRIDGE.TSK_A_OPC_200
If one encounters the error one should stop Cim-IO, rename the store file, and then restart Cim-IO. If things begin to work normally (i.e. data records start receiving values from the device (DCS or PLC) then one may safely conclude that the store file has become damaged. It (the one that was renamed) can be discarded.
Keywords: None
References: None |
Problem Statement: Example source code is provided for development of a CIM-IO client and a CIM-IO server when CIM-IO is installed.A However, some of the source code uses the routine cimio_upper that requires header file cimiodev.h, but this is not distributed.
Re | Solution: To work around the problem you can delete the clause using cimio_upper and comment out the reference to this header file. Alternatively you can include the following code to make your own local version of cimio_upper.c and thus eliminate the reference to cimiodev.h
char* cimio_upper(char* str)
{
A A A unsigned int i;
A A A for(i=0; i<strlen(str); i++)
A A A A A A A str[i] = (char) toupper(str[i]);
A A A return(str);
}
Keywords: CIM-IO
References: None |
Problem Statement: How do I move an Aspen Cim-IO logical device defined using the Aspen I/O device wizard from one node to another? | Solution: Follow these steps to move an Aspen Cim-IO logical device defined using the Aspen I/O device wizard from one node to another:
1. Using the Aspen InfoPlus.21 Administrator, turn off device processing for the device record by setting the field IO_DEVICE_PROCESSING to OFF. This deletes the scanning list from the Aspen Cim-IO server.
2. Stop the Aspen Cim-IO client tasks for the device using the Aspen InfoPlus.21 Manager.Â
3. Stop the logical device using the Aspen I/O Device Wizard.
Wait for the red indicators to appear.
4. Right-click on the logical device, select Properties, take note of the Logical Device Name and Service Name, and press cancel.
5. Right-click on the logical device again. This time select Remove logical device. When the Logical device removal confirmation screen appears, uncheck the box Remove associated tcp entries and press OK. This removes the logical device from the file cimio_logical_devices.def but leaves the service names for the device in the Windows services file.
6. Use the Aspen I/O Device Wizard to add the device again pointing to the new Cim-IO server. Be sure to use the same logical device and service names as before. Note: You must use the same case for the service name as before. The Aspen Cim I/O device wizard will see the service name already exists in the Windows services file and will use the same tcp/ip port numbers as when the logical device pointed to the old node.
7. After adding the device again using the Aspen I/O device wizard, right-click on the logical device and select Start logical device.
8. Wait for the green indicator lights to appear, and then use the Aspen Cim-IO TestAPI utility on the Aspen InfoPlus.21 server to test communications between the Aspen InfoPlus.21 and Cim-IO servers.
9. After verifying communications using TestAPI, restart the Aspen Cim-IO client tasks using the Aspen InfoPlus.21 Manager.
10. Finally, delete Aspen Cim-IO from the original Aspen Cim-IO Server.
Keywords:
References: None |
Problem Statement: This knowledge base article describes which fields to examine to determine the current state of Aspen Cim-IO connectivity. | Solution: There are various Aspen InfoPlus.21 records which show the status of the device and of the individual transfer records. The data in these fields provide information about the current state of Aspen Cim-IO connectivity.
The following fields are found in the device record:
IO_COMM_STATUS - This field contains information about connectivity to the DCS, OPC server, etc. Note that this field may not always show the most current device status information.
The following fields provide information about when the store file began to forward:
IO_FWD_ASYNC_STATUS - This field shows the current state of the forward process.
IO_FWD_ASYNC_START - This field shows the time that the last store file began to forward data.
IO_FWD_ASYNC_END - This field show the time that the last data point was unbuffered from the last store file.
The following fields provide information about when the store file began to store data:
IO_STR_ASYNC_STATUS - This field shows the current status of the store process.
IO_STR_ASYNC_START - This field shows the time when data began being stored in the store file.
IO_STR_ASYNC_END - This field shows the time that the last data point was stored in the store file.
The following fields are found in the transfer record.
The following fields show when the Get transfer record last updated and the last status received:
IO_LAST_UPDATE - This field shows the last time that the transfer record retrieved data.
IO_LAST_STATUS - This field shows error codes which relate to the data transfer operations.
IO_LAST_STATUS_DESC - This field shows a text description to accompany the error code in the IO_LAST_STATUS field.
In the repeat area of each Get transfer record the following fields provide status information about each data record:
IO_DATA_STATUS - This field contains connectivity/error information regarding transfer of the individual data point.
IO_DATA_STATUS_DESC - This field contains a text description to accompany the error code returned in the IO_DATA_STATUS_DESC field.
Keywords: Information
unsol
References: None |
Problem Statement: The documented method for increasing the number of messages unbuffered by the cimio_sf_forward process doesn't work successfully when running CIM-IO v6.0.1 on an OpenVMS system. The section titled, Starting and Stopping a Store & Forward System in the CIM-IO v6.0.1 User's Manual (page 9-9) describes how to use the MSGS parameter to increase the number of messages the forward process reads and forwards to the CIM-IO client. | Solution: When running v6.0.1 on OpenVMS and using the MSGS parameter, you must have a space between the MSG and S. An example would be:
$ cmd :== $dka0:[setcim.code]cimio_sf_forward.exe
$ cmd CIMIOCHIP MSG S 100 5 DKA0:[SETCIM]
Where CIMIOCHIP is the name of the logical device, 100 is being used for the MSGS parameter, 5 is the socket timeout in seconds, and DKA0:[SETCIM] is the STORE file path.
Keywords: MSGS
References: None |
Problem Statement: Customer gets the following error message
Critical Error - Error in MoveInfoLstToSht(), module Funcs | Solution: Check to make sure that the license key for Aspen Hydrocracker has been entered into the license
server or is located in the license file. See the Licensing section on page 2-8 of the installation manual for more information.
Keywords: Keywords
AES 11.1
FlexLM
Aspen License Manager
RXRG
Hydrocracker
CatRef
MoveInfoLstToSht
References: None |
Problem Statement: How to prevent an Aspen Cim-IO server from writing to the device. | Solution: A new Aspen CIM-IO feature was introduced in Engineering Release CIO090807C for Aspen CIM-IO V2006.5 (August 2009) and will be rolled into the base product starting in V7.2. Customers now have the option to implement the Aspen CIM-IO No-Write Option which disables write commands from any type of CIM-IO client modules to any of the devices served in the current CIM-IO server. The Aspen CIM-IO core installation determines whether disabling of write commands is an option for the current server and prompts the installer to choose whether to enable the No-Write Option or not. Once the No-Write Option is enabled for a device, all CIM-IO Put transfer records to that device will display the text USR_PUT_NOT_ALLOWED, PUT not allowed. No-Write option enabled in field IO_LAST_STATUS_DESC.
For additional details about this feature refer to release notes included with Aspen Cim-IO 2006.5 ER CIO090807C (August 2009) in knowledge Base article 126949.
http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key=126949
Keywords: cim io
disable puts
CIMIO_USR_PUT_NOT_ALLOWED, PUT not allowed
CIMIO_USR_PUT_NOT_ALLOWED, PUT not allowed
References: None |
Problem Statement: Aspen Framework stores Security Information in a Relational Database such as Microsoft SQLServer.
Suppose I am running Aspen Framework, using an older version of Microsoft's SQLServer, and want to install a newer version of Microsoft SQLServer on another machine.  What do I need to do so that the contents of the old SQLServer security tables appear in the newer installation? | Solution: The Utility AFWTools via the Start => AspenTech menu option provides the capability to Export and Import tables containing security information; however, the easier method is to just copy the old relational database to the new installation.
Keywords: None
References: None |
Problem Statement: You have just applied the latest patch to your Cim-IO server and have restarted the machine. When manually starting a logical device you receive the following error:
CIMIO_USR_START_DEV_RECEIVE, Error receiving a STARTDEVICE reply from device
CIMIO_MSG_RECV_TIMEOUT, Time-out trying to receive a message | Solution: The fact that this occurs after a recent installation of a patch suggests the problem is due to blocked files. Check the file properties of the Cim-IO files in the Code folder, eg. cimio_sf_store.exe file:
C:\Program Files (x86)\AspenTech\CIM-IO\code\cimio_sf_store.exe
In particular, look out for the Unblock button with the attendant Security message:
This file came from another computer and might be blocked to help protect this computer.
You could unblock each file in turn but to be thorough it is advisable to reinstall the patch, taking particular care to first unblock the compressed zip file which you downloaded from the support website.
Keywords: Patch
Security
Cim-IO Server
InfoPlus.21
Time-out
References: None |
Problem Statement: When using the cimio_autostart.batA batch file to start the Cim-IO Store and Forward processes.
and then using the and cimio_autostop.batch file to stop the Store and Forward processes:
it was found that one of the processes, cimio_sf_store.exe, was still running in the system.
When running the batch program to stop the interface again, this time it stops it. | Solution: We found that in the Windows services file the entries for the CIOR1xprep_SC and CIOR1xprep_ST services had the same port numbers:
Once this was corrected the processes start and stop as expected.
Keywords: Cim-IO
start
stop
interface
References: None |
Problem Statement: When trying to create an Aspen Cim-IO device in the Aspen Infoplus.21 Administrator, using the I/O wizard, I receive the following error
Scanner service does not exist | Solution: To resolve this error and successfully create the Aspen Cim-IO device, make sure that the following is true:
1. The Aspen Cim-IO Manager service on the Aspen Infoplus.21 server and the Aspen Cim-IO server is started with an account that is member of the local Administrator's group.
2. In the services file in C:\WINDOWS\system32\drivers\etc there exists a CIMIOManager entry and both servers use the same port number for this entry (default is 7777/TCP).
3. No firewall exists between the Aspen InfoPlus.21 and Aspen Cim-IO server which blocks the CIMIOManager port from point 3.
4. Remove UAC restriction on the account being used for configuration (Control Panel | User Accounts | Turn User Account Control on or off.)
5. Even with UAC restrictions turned off (Point 4), the Services file (see point 2 for location) may not be editable by the Administrator. Test this by adding a space at the end and choosing File, Save. If the Save As dialog comes up, then the file is not editable. In this case, close the InfoPlus.21 Administrator, and open it with a right-click, choosing Run As Administrator. Run the Wizard again, and this time it should have the right to make changes to the services file.
6. Make sure there is no typo in the name of the 4 CIM-IO tasks including the 3 S&F tasks (Scanner, Store and Forward)
7. When using the IO Wizard in IP.21 Administrator to configure a Logical Device that is going to use an OPC server in a different system than the one where the Cim-IO Wizard program resides, delete the old .CSD file (if exists) on the remote OPC server and let it be recreated by the Wizard.
Keywords: None
References: None |
Problem Statement: Running TCP/IP Tester gave confusing and inconsistent results.
How can I run the TCP/IP Test in order to simulate Cim-IO Store and Forward capabilities across a WAN? | Solution: The instructions on TCP_TESTER.pptx that's available in the attached zip file may be a little confusing and don’t clearly explain how to gather the test results and how to interpret.
TCP/IP Tester requires TCP_CLIENT and TCP_SERVER applications to run on Cim-IO Server and InfoPlus.21 Server, and the general assumption is that the results will show the performance differences between Cim-IO Server and InfoPlus.21 Server, but that’s not correct, because only the TCP_SERVER results are useful to the test.
The proper logging of TCP/IP Tester happens on TCP_SERVER.EXE, not on TCP_CLIENT.EXE.
In order to emulate Cim-IO Store and Forward data transmission, you will need top log data only form TCP_SERVER.EXE. It’s useful to append the results to a log file.
Example:
TCP_SERVER /PS=10 > TCP_TEST_WAN.LOG
/PS=10 generates entry every 10 messages
> TCP_TEST_WAN.LOG append results to a TCP_TEST_WAN.LOG file
Test results example:
Inputs: TCP_CLIENT /SN=JOSHIR01 [/PN=27015] [/TO=120000] [/MS=12100] [/TD=-1] [/MD=0] [/PS=10]
Elapsed time : 0.05 minutes, 10 messages
Current timeout : 120000 milliseconds
Message rate : 3.30 messages/sec, each of 12100 bytes
Bytes rate : 0.04 MB/sec
Elapsed time : 0.10 minutes, 20 messages
Current timeout : 120000 milliseconds
Message rate : 3.49 messages/sec, each of 12100 bytes
Bytes rate : 0.04 MB/sec
Elapsed time : 0.14 minutes, 30 messages
Current timeout : 120000 milliseconds
Message rate : 3.57 messages/sec, each of 12100 bytes
Bytes rate : 0.04 MB/sec
Elapsed time : 0.18 minutes, 40 messages
Current timeout : 120000 milliseconds
Message rate : 3.64 messages/sec, each of 12100 bytes
Bytes rate : 0.04 MB/sec
Depending on how long you will be running the tests, you will have thousands of entries in the log file, therefore you will have to pick several entries (possibly at a few minutes if not hours interval) and average them in order to get a parameter to compare among LAN, LOCALHOST and WAN. You can also decide to log a message less frequently, by changing /PS=10 to a higher value. /PS=10 means that the test will log an entry every 10 messages.
The tests should be run as follows:
LOCALHOST Test:
· TCP_SERVER on Cim-IO Server
· TCP_CLIENT on Cim-IO Server
LAN Test:
· TCP_SERVER on Cim-IO Server
· TCP_CLIENT on IP.21 Server
WAN Test:
· TCP_SERVER on Cim-IO Server
· TCP_CLIENT on IP.21 Server
please find below the results comparison between the TCP/IP Tests and the Performance based on network diagnostics:
TCP/IP Tests
LOCALHOST
LAN
WAN
msgs/sec
MB/sec
msgs/sec
MB/sec
msgs/sec
MB/sec
Average Rate
415.9406
4.799375
280.4613
3.235625
1.98625
0.02375
Max Rate
1006.92
11.62
297.27
3.43
3.24
0.04
% of LAN
(TCP Test)
338.78
100
1.17
Performance based on network diagnostics
Results taken from TCP_SERVER.EXE Process with Network Activity
Receive (Bytes/sec)
13100314.00
3464818.00
42667.00
% of LAN
378.10
100.00
1.23
Test accuracy
89%
100%
94%
This comparison chart, basically shows the accuracy of the TCP/IP Tester compared to the network diagnostics (assuming that network diagnostics from Windows Server 2008 is more than TCP/IP Tester reliable).
The examples above are suggesting that the WAN performance is not ideal for Store & Forward, as the performance of the WAN (where the STORE file needs to be FORWARDED), is much slower than the LAN, where data is STORED.
Keywords: Cim-IO
TCP/IP Tester
WAN
LAN
References: None |
Problem Statement: How to determine the approximate Aspen Cim-IO store file size. | Solution: The space required by the Aspen Cim-IO Store file for each Get or Unsolicited reply can be calculated as follows:
? 500 bytes overhead, regardless of message data
80 bytes per point, regardless of tag type
An additional 40 bytes per point if long tag records are used
o (LongTagGetDef, LongTagUnsolDef, LongTagPutDef or LongTagPOCDef).
An additional 160 bytes if very long tag records are used
o (IOLLTagGetDef,IOLLTagPOCDef, IOLLTagPutDef, or IOLLTagUnsDef).
An additional 100 bytes per TextDef (String) point
o If a single point evaluates to a complex structure, such as a vector or
o structure of different data types, add a number of bytes equal to all of the
o data needed by all of the points of the structure. For example, an array of
o 500 Double Float numbers takes up 500x8 bytes = 4000 bytes.
The sum of all of the above elements is the number of bytes a store file will require per message. The file growth rate can be calculated by dividing the total above by the message rate. To calculate the total required file size, multiply the growth rate by the maximum desired outage time coverage. To find the total time coverage, divide the file size provided by the growth rate.
For example:
A LongTagGetDef is constructed with 100 integers, 100 reals, and 100 TextDef strings. The GetDef rate is once per 5 seconds. The amount of space
required for the store file is:
1. 500 bytes overhead
2. 300 * 80 bytes = 24,000 bytes for the points.
3. 300 * 40 = 12,000 bytes (since this is a LongTag record)
4. An additional 100 * 100 = 10,000 bytes string space
5. It has no complex structures
Thus, the total is 46,500 bytes. The update rate of 5 seconds results in a file size growth rate of 46,500 * 12 = 558,000 bytes per minute. An outage of 1 hour (60 minutes) would generate a file of size 33,480,000bytes (close to 32 MB). If the plant allocates 1Gb for the store file, the maximum outage time covered would be 1024 * 1024 * 1024 / 33,480,000 = 32.07 hours.
Keywords: cimio
store file
store and forward
References: None |
Problem Statement: How to add a second DLGP with CIM-IO for HP RTAP | Solution: To add a instance of the DLGP server:
Copy the executable /opt/cimio/V.1.3/code/cimio_rtap_dlgp1 to /opt/cimio/V.1.3/code/cimio_rtap_dlgp2
Create a second set of services in the file /etc/services
#
# Aspen CIMIORTAP Services
#
CIMIO_RTAP_DLGP1 13601/tcp
CIMIO_RTAP_DIOP_S1_R1 13602/tcp
CIMIO_RTAP_DIOP_S1_W1 13603/tcp
CIMIO_RTAP_DIOP_S1_R2 13604/tcp
CIMIO_RTAP_DIOP_S1_W2 13605/tcp
#
CIMIO_RTAP_DLGP2 13611/tcp
CIMIO_RTAP_DIOP_S2_R1 13612/tcp
CIMIO_RTAP_DIOP_S2_W1 13613/tcp
CIMIO_RTAP_DIOP_S2_R2 13614/tcp
CIMIO_RTAP_DIOP_S2_W2 13615/tcp
#
/$_$_END_CODE
* Add the new logical device to file /opt/cimio/V.1.3/etc/cimio_logical_devices.def
IORTAP tcthp03 CIMIO_RTAP_DLGP1
IORTAP2 tcthp03 CIMIO_RTAP_DLGP2
* Add the new DLGP2 to the startup script /opt/cimio/V.1.3/commands/cimio_rtap_startup.sh
nohup $CIMIOCODE/cimio_rtap_dlgp1 0
1>$CIMIO_RTAP/cimio_rtap_dlgp1.out 2>$CIMIO_RTAP/cimio_rtap_dlgp1.err &
nohup $CIMIOCODE/cimio_rtap_dlgp2 0
1>$CIMIO_RTAP/cimio_rtap_dlgp2.out 2>$CIMIO_RTAP/cimio_rtap_dlgp2.err &
The only issue that we see with this method is that the debug files for the DIOP processes are not specific to each DLGP. The debug files are created
with the same file names, regardless of which DLGP has started the process (cimio_rtap_diopr1.out and cimio_rtap_diop1.err). Both DGLP's seem to
append messages to the same file. Not a big problem.
Keywords: -----------------
cimio
hp rtap
hp-rtap
References: None |
Problem Statement: How do you start Cim-IO processes so they will continue to run if the user logs out? | Solution: Cim-IO processes need to be started as detached processes so they will continue running if the user logs out. On a Setcim system this is typically accomplished by adding them to the Setcim.run file and they are started when the startSetcim command is executed. However, If you heed to start them from a user account the following command is needed.
Create a cimio_start.com file to start the cimio client with the following line:
RUN /DETACH /PROCESS_NAME=CIMIO_MSIM CIMIO_C_CLIENT (This will start the main client task)
Execute the command:
@ cimio_start
Keywords: detach
cimio
vms
References: None |
Problem Statement: How do I resolve the Cim-IO Message Log Error: Invalid activation code = 4? | Solution: This error message indicates that there is a discrepancy between the record ID's as listed in the Aspen InfoPlus.21 (IP.21) database and the CIM-IO Store & Forward list files.
These errors are caused when a record id that is used by Store & Forward is no longer valid. One way this can happen is that after CIM-IO (with Store&Forward enabled) is activated and collecting current data, Aspen InfoPlus.21 is shut down and restarted with a different snapshot.
To resolve the issue you can either rename the scan list and activate your GET records or perform a clean restart of a Aspen Cim-IO Interface by following Aspen KB article 103176.
Keywords: IP.21, get records, store & forward
References: None |
Problem Statement: What is the distinction between the IO_DATA_DEADBAND and IO_DEVICE_DEADBAND fields in the repeat area of IoUnsolDef records? | Solution: IO_DEVICE_DEADBAND applies to servers which support unsolicited I/O. If the server does not support unsolicited transfers, this field should not be used. The server task uses the device deadband data to filter out minor changes in the input value before sending the value to the unsolicited client task.
IO_DATA_DEADBAND is used by the Aspen InfoPlus.21 client tasks to apply deadbands to incoming data.
Keywords: Dead band
References: None |
Problem Statement: Included in the Cim-IO User's Manual is a method to estimate the Store File size. This can help when planning for disk space requirements.
The formula used to estimate the store file size is as follows:
Total bytes = Number of Total Occurrences x Bytes per Occurrence
Where Number of Total Occurrences = (Downtime in seconds / Scan Frequency) x Number of Tags
The manual indicates that a good rule of thumb for estimating the number of Bytes per Occurrence is to assume 100 bytes of storage per tag occurrence. However, this 100 bytes of storage is specifically meant for IOGetDef records. How would this differ for other types of get transfers? How could it differ with text tag transfers? | Solution: For Unsolicited transfers (IOUnsolDef records) the message space would still be approximately 100 bytes. However, in unsolicited mode, if no data points change, no message will be sent. In this case, if you have sparsely changing data, the equation above may result in an inflated estimate because the frequency is larger than expected.
In Long Tag Name Get transfers (IOLongTagGetDef records) the longer tag names would require additional storage space. In this case, the estimate of 100 bytes per tag should be increased to 150 bytes.
Lastly, it is important to note that the 100 bytes per tag is strictly per numeric point. It does not take into account strings used for tags like IPTextDef records. To calculate the amount of bytes necessary for a string, add the string size (CIMIO usually transmits strings as fixed length arrays of 80 characters) to the size of a numeric point. Thus, a good estimate for strings is 200 bytes.
Keywords:
References: None |
Problem Statement: When attempting to install service packs from a CD, setup may fail with the message WININET.DLL cannot be found. The problem affects machines on which the CIM-IO Kernel software is installed. | Solution: This problem occurs because the 'Common' core component is not installed with CimIO. There is a work-around for this issue. Go to their 4.X distribution media and invoke setup.exe from the \Core\Common directory. This will install the necessary files for the SP installer to work properly.
The problem is targeted for a fix in version 5.0 of the Aspen Manufacturing Suite.
Keywords: patch
engineering release
References: None |
Problem Statement: Force updates causes Aspen Cim-IO to write new values into the Aspen InfoPlus.21 database even when the value does not change, but I do not want this to happen and may have tags that update less than once per year. | Solution: Set the Force Update (sec) in the Cim-IO for OPC Properties application to zero seconds and restart the logical device to enforce this change.
Keywords: Disable forced updates
References: None |
Problem Statement: Why does the Cim-IO Manager service terminate after being started? When looking in the Cimio_MSG.log error you will see the error message below.
CIMIO_DAL_INIT, Error initializing CIMIO
CIMIO_MSG_POLL_FIRSTTIME, Error accepting connection
CIMIO_MSG_ACCEPT_SOCK_CREATE, Error creating an inbound socket
CIMIO_SOCK_IN_LISTEN_FAIL, Error listening for messages on the inbound socket
WNT Error=10055 An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. | Solution: This error can occur if the Device cimio is installed on runs out of memory.
To try and resolve this issue you can:
1. Reboot the machine
2. Ensure that the device has enough hard disk space space available.
3. Ensure that the user Running the Cimio Manager service has administrator access and is not locked out.
Keywords: WNT Error=10055
CimIO
Cim-Io
system lacked sufficient buffer space
Manager
References: None |
Problem Statement: The default value for the maximum large_buffer parameter for ethernet type connections was 1500 for UCX version 2 but 200 for UCX 4.0 or later.
Also, the maximum limit of UCX large_buffer does not need to be set to 1500 anymore. This is because UCX version has to be 4.0 or later to be Y2K compliant and most of the system therefore use UCX 4.0 or later. | Solution: You can know the requirement of the UCX large_buffers parameter using the following command:
$ UCX show communication/memory
This will also show you the known peak, drop and wait numbers of large_buffers. Please note that the maximum limit of large_buffers should be more than the sum of peak, drop and wait numbers of large_buffers.
Keywords: UCX
large_buffers
References: None |
Problem Statement: It is often crucial to know whether or not a store file is in the process of forwarding after connection to an Aspen Cim-IO client has been re-established. This | Solution: provides methods to determine if forwarding is occurring.
Note: ThisSolution assumes Aspen Cim-IO Store & Forward has been properly configured and thoroughly tested.Solution
One method for determining if forwarding is occurring is to run Aspentech\Cim-IO\code\CIMIOSFMonitor.exe on the Aspen Cim-IO server system.
Another method is to examine the records in the Aspen InfoPlus.21 database.A The IO device record and the individual data records provide all necessary information regarding the status of the store and forward process. This information can be viewed easily with the Aspen InfoPlus.21 Administrator.
STEP 1. Examine the IO Device record:
The first record to examine is the IO Device record using the Aspen InfoPlus.21 Administrator.A Note: it is important to refresh (F5) periodically while viewing these records to ensure correct data is monitored.
IO_STORE_ASYNC_START & IO_STORE_UNSOL_START
This field displays the timestamp of the first reply received from the forward process.
IO_STORE_ASYNC_END & IO_STORE_UNSOL_END
This field displays the timestamp of the first reply from the DLGP after replies from the forward process have been completed. In other words, this marks the time the store file finished unbuffering.
IO_FORWARD_ASYNC_STATUS & IO_FORWARD_UNSOL_STATUS
This field states the status of the forward process.A Options are NOT STARTED, IN PROGRESS, and COMPLETE.
NOT STARTED indicates that the forwarding process has not yet begun. This is most likely due to no communication between the Aspen Cim-IO server and the Aspen Cim-IO client.A In other words, the problem which caused the store file to build has most likely not been resolved.
IN PROGRESS indicates that communication has been restored between the Aspen Cim-IO server and Aspen Cim-IO client.A The store file is now in the process of forwarding.
COMPLETE indicates the store file has completely unbuffered.
IO_FORWARD_ASYNC_START & IO_FORWARD_UNSOL_START
This field will display the timestamp of when the store file began to forward.
IO_FORWARD_ASYNC_END & IO_FORWARD_UNSOL_END
This field will display the timestamp of when the forward process stopped forwarding. This does not imply the store file has completely unbuffered. It is entirely possible for the store file to stop forwarding before it has unbuffered all of the data. This can occur if the store file becomes corrupt of if communications are once again severed between the Cim-IO server and Cim-IO client. If the store file stops unbuffering without completion, the IO_FORWARD_ASYNC_STATUS will not necessarily switch from IN PROGRESS to NOT STARTED.
IO_COMM_STATUS
This field consists of an integer selector defined by Io-Last-Status (the same selector as used by CIM-IO transfer records). IO_COMM_STATUS will contain information about the general state of CIM-IO communications with this device. The following are the possible states of this field.
SUCCESS indicates that communication is successful (i.e., the Aspen Cim-IO server can be pinged or the last READ was successful), the field will be set to Success.
CIM-IO SERVER ERROR indicates the CIM-IO client task detects broken communication with the DLGP or Store & Forward processes.
SERVER OR S&F SHUTDOWN, STORE & FORWARD DISABLED, CIM-IO CLIENT TASK DOWN indicate a problem with a transfer record exists (remember the Io-Last-Status selector provides selections for both the device record and the transfer records.A (Not all of the selections are applicable to the device record.)
STEP 2. Examine the data record:
The primary reason for examination of the data record is to verify that the IP_INPUT_TIME is updating as the data forwards from the CIM-IO server.A This is final verification that data from the store file has been sent all the way to the intended destination, the data record.A When data is sent from the store file to the CIM-IO client, the oldest data is sent first. After communications are restored between CIM-IO server & client, new data will continue to pass though the store file until the store file unbuffers completely. If network problems prevent data from quickly unbuffering from the store file, the store file may persist on the CIM-IO server for a significant period of time.
Keywords: Unbuffer
Store
Forward
References: None |
Problem Statement: What is the Aspen Cim-IO IP21 Connection Manager? | Solution: The Aspen Cim-IO IP21 Connection Manager provides an improved method of configuring Aspen InfoPlus.21 Interface connections.
Here are a few tips for using this method of creating an interface connection.
· The interface must be created first using the Aspen Cim-IO Interface Manager on the interface server.
· Logical device names must be 10 characters or less.
· Aspen Cim-IO environment variable configurations are found at the top Cim-IO Interfaces tree. Customers should review the settings and descriptions found in the Aspen Cim-IO Users Guide and make appropriate setting for the system.
· The Aspen Cim-IO IP21 Connection Manager will step through the interface discovery and configuration of the logical device. It will create the necessary records in Aspen InfoPlus.21, tasks in the InfoPlus.21 Manager, start them, and populate the Logical Devices and services files.
Keywords: Interface Manager
References: None |
Problem Statement: How to import an Aspen Watch KPI result as a miscellaneous tag?
Importing KPI data as Miscellaneous Tags is a method used to work around the issue that you cannot bind a custom KPI to a user-defined variable in the IP21 data base. | Solution: Configure a Cim-IO logical device, IODEV3 for example, to point to the Cim-IO server for IP.21 on the Aspen Watch Server.
Build a miscellaneous tag data file referencing the desired KPI value C03K AW_KPI_VALUE. Be sure and use a space rather than a period for the record and field separator.
The Cim-IO server for IP.21, cimio_setcim_dlgp.exe, will not be running by default on the Aspen Watch Server. This is not a standard task install, because the standard way of collecting data is by the DMCplus context service from DMCplus Online machines, and by going through Cim_IO for OPC for PID loop data collection. Start the cimio_setcim_dlgp.exe by starting the Cimio to Setcim interface.
Add the external task TSK_IP21_SERVER and point the executable to C:\Program Files\AspenTech\Cim-IO\io\cio_set_cim\ cimio_setcim_dlgp.exe. Start the task.
Keywords:
References: None |
Problem Statement: Aspen PID Watch Performance Monitor crashes with Run-time error '13':Type mismatche error message when we try to open a project file saved on Korean or Japanese Windows XP or Windows Vista. | Solution: Run Aspen PID Watch Performance Monitor on Windows Server 2003 SP2. Aspen PID Watch Performance Monitor can run Japanese and Korean Windows Server 2003 SP2.
Keywords: Japanese
Korean
Windows XP SP2
Windows Vista
References: None |
Problem Statement: Why are optimization options grayed out? | Solution: Outside stream flow optimization options are irrelevant when the calculation mode is Design with fixed airflow. That's why the fields under outside stream flow optimization options are grayed out. Capital cost is the only acceptable optimization criteria. That's why other choices are grayed out. Choose Design with varying outside flow as program calculation mode to have all the fields active.
Keywords: optimization, options
References: None |
Problem Statement: What are some modeling considerations for plant shutdown processes? In plant shutdown scenarios, assuming all the specs still making engineering sense (some of them zeros since the plant is shutting down), can Aspen Plus Dynamics simulate the process until all flows reduce to zero? | Solution: Here are some insights and rules of thumb regarding shutdown simulations:
(1) Typical difficulties encountered in shutdowns may be:
phase flipping
reverse or bi-directional flow
too large heat transfer due to fixed duty
complete drain hence zero holdup (zero pressure or zero density)
controller fails
(2) If a variable spec change during shutdown is required to avoid failure, one may use a conditional Task (could be used for Ramping method and executing Scripts, etc.) that monitors a designated variable during shutdown simulation run. The monitored variable doesn't have to be an Aspen Plus Dynamics model variable. You can use a custom variable defined in Flowsheet Constraints based upon need. But remember, a structural change is not allowed during runtime.
(3) Any failure should be a consequence of some event. Also, deciding a criteria of shutdown condition is recommended prior to a shutdown study to prevent running the simulation for a long time at zero flow conditions.
(4) Specifically, look for specs that prevent column to shutdown, for example, fixed duty, etc.
(5) Look for tuning parameters: global and local PropMode, FlashBasis etc.
(6). Look for features that was not designed to function under shutdown conditions, such as flooding calculations, since presumably flooding would not be a problem under shutdown calculations.
(7) Using padding gas when vessels are evacuated.
Keywords: Shut, Shutdown, padding, zero flow
References: None |
Problem Statement: After configuring a custom DCS, PID configuration fails. | Solution: If you make changes to any of the AWP_PIDC_CUSTOMx.SQL procedures, you must make sure there are no errors in the SQLplus syntax. If ANY of these procedures have an error (even if it is not used by any of your PID records), the entire PID configuration process will fail.
To test for SQLplus errors, open the .SQL file you may have edited in the SQLplus client program and press F9 to compile/execute the procedure. If any errors are present in the syntax, then it will tell you. You can also test the code against an existing PID loop by adding a call to it at the bottom of the procedure (just after the last End -- End of procedure statement in the file).
For example:
AWP_PIDC_CUSTOM1('FC2001')
This will execute the SQL procedure's logic on the specified PID record name. You can use the debugger feature (new in SQLplus 2004) to debug your procedure as well. To start the debugger, make sure you added the statement mentioned above (with the correct AW_PIDDef record name) and press F8 (step into) two times. Then use the View->Variables Window menu option to show the procedure's local variable values as you step through the code. You need to click on the Procedure TAB at the bottom of the window to see anything. Keep pressing F8 to step through the procedure one line at a time.
If you find any errors, correct them and use the Record->Save As menu (remove any .SQL part of the record name before saving. You should be prompted to overwrite if you have the name correct - choose Yes).
Finally, double-check any changes you made to the .CFG file(s) to see that you did not introduce a space or other character. All fields must be TAB-delimited in the .CFG files.
Keywords: PID, watch, sql, cfg, SQLplus
References: None |
Problem Statement: Air cooled exchangers can have multiple fans in a bay where the airside flowrate can be controlled by either switching a fan off or by varying the fan pitch but keeping the rotational speed unchanged.
Within Aspen Air Cooled Exchanger program, we can specify the unit as a grid (along and across) the unit where for each grid section we can specify the flowrate or inlet temperature.
Described below is how the option can be used to simulate a condition when a fan is switched off. | Solution: In Aspen Air Cooled Exchanger program user can use Outside distribution form under Input | Program Options | Outside Distribution option to account for the distribution of air flow through the various bundle sections of the exchanger. This facility allows the user to specify a two dimensional x side mass flow and/or temperature distribution at the bundle entry.
The elements of the distribution are specified in a grid which can have maximum of 12 elements along the tube length and 6 elements across the bundle width. An inlet outside mass flow or temperature distribution may be caused by the effect of adjacent structures. (See HTFS Handbook sheet AE1). Note that the Outside distribution is applied to a bundle and as the program treats every bundle identically, then the distribution data will apply to all bundles in a unit. The effect of the distribution on performance can be seen in the Results.
As the mass flow distribution and the temperature distribution are specified on the same grid size, then the grid dimensions must be large enough to accommodate the more complex distribution. The values to be entered in the mass flow distribution grid are either the flow through each element as a percentage of the highest element flow or the flow through each element as a percentage of the total flow through the bundle.
Assuming an air cooled exchanger with 2 bays (2 fans per bay) and we are simulating the case with one fan switched off, user can specify a grid of 2 X 2 for which the percentage of the total flow for the flow zones would be 33.33 % for three zones with one `0' (one fan switched off). Program would automatically allocate the total flow rate multiplied by the specified percentage for different zones. When we have one fan switched off, we also need to consider the reduction in air side flowrate. User need to take into account the reduced air side flow rate e.g. in this case where one of the fan is switched off, you would reduce the total air flowrate by ? which means you enter 270 kg/s instead of 360 kg/s as all the other three fans are operating at the set 90 kg/s each.
Keywords: None
References: None |
Problem Statement: Where to find the steps involved in the workflow for analyzing and tuning PID loops using PID Watch? | Solution: The basic procedure/workflow for using PID Watch involves four major steps-
1. Data Import- Importing the PID loop data to be analyzed and tuned. This involves data for Set Point, Process Variable, and Output values. This could be either live data or previously historized data in the form of vector files.
2. PID Analysis- This step involves analyzing the data imported in the previous steps to access the PID loop performance. PID Watch generates Impulse Response plots, Autocorrelation Error plots, Residual Autocorrelation plots, Performance Index plots, Frequency Response plots, Valve Output plots, and Valve Analysis Plots to assist engineers to analyze the behavior of the PID loops being analyzed.
3. Model Identification- PID Watch has the capability to perform Model Identification. PID Watch generates open loop step response model using any type of input data (closed loop, open loop or hybrid). PID Watch also generates additional analysis results such as Model Uncertainty, PV Prediction, and Model Validation plots to ease the work burden on a control engineer.
4. PID Tuning- PID Watch has built-in optimization solvers that analyze the information obtained in the previous steps and take the tuning inputs and information provided by the user to calculate optimum tuning parameters that provide the best possible performance for the PID loop in question.
Detailed procedure and workflow steps for analyzing and tuning PID loops can be found in the “Data Import,” “PID Analysis Results,” ”Model Identification,” and “PID Tuning” sections of the Aspen PID Watch help files.
Keywords: PID Watch
References: None |
Problem Statement: This knowledge base article explains how to troubleshoot the following error message:
System Error, errno=146 Connection refused | Solution: The aforementioned error can mean one of three things:
1. The remote host (the Aspen InfoPlus.21 system) is not listening on that socket.
Ensure that the Aspen Cim-IO server and the Aspen InfoPlus.21 server can ping one another by name.
Ensure that the Cim-IO client tasks (TSK_M_XXX and TSK_A_XXX) are running. Stop/restart the client tasks if necessary.
Ensure that the same port numbers are specified in the services files of both the Cim-IO server and the Cim-IO client.
Ensure that the names of the Cim-IO entries are spelled exactly the same in both services files.
2. A firewall is preventing access on that socket.
Ensure that the ports specified in the services files aren't blocked by the firewall.
3. Ensure that the vendor-specific application or API which communicates with the device is running. For example, if the Aspen Cim-IO for FoxAPI interface experiences this problem ensure that the Foxboro API is running properly. Restarting the device-specific API may be necessary.
Keywords: None
References: None |
Problem Statement: What causes the message GetProperties for xxxxxx is using default values. Run utility CIMIO Properties to create and adjust if required global CIMIO variables to appear in the Aspen Cim-IO message log file, where xxxxxx is the name of and Aspen Cim-IO logical device? | Solution: This message means that you have not run the utility CimioProperties on the server. To eliminate these messages, open Windows Explorer, navigate to C:\Program Files (x86)\AspenTech\CIM-IO\code, right-click on CimioProperties, and select Run as administrator.
You will see several screens similar to:
Press OK for each screen.
Finally, CimioProperties will display:
Exit CimioProperties and restart Aspen Cim-IO. The messages should no longer appear in the Aspen Cim-IO message log file.
Keywords:
References: None |
Problem Statement: Trying to upgrade CIM-IO kernel from v6.0 to v6.0 SP1. The SP1 installation does not list CIM-IO kernel as an upgrade item. | Solution: Run upgrade for CIM-IO kernel manually using the file: EIS_CimIO-Core.exe
Keywords: SP1, Installation, Upgrade
References: None |
Problem Statement: After changing the password for the account used to start the Aspen Cim-IO Manager service, this user account gets mysteriously locked out of the system. | Solution: When the Aspen Cim-IO Wizard is used to create and configure a logical device, a .csd file is automatically created on the Aspen Cim-IO Server machine in the AspenTech\Cim-IO\Management folder. When the Aspen Cim-IO Manager service starts, it runs this .csd file along with the cimio_autostart.bat file. If a user name and password is specified during the configuration process for the Start-up at Boot feature, this user name and the encrypted password will be stored in the .csd file.
If the password is changed for the account specified in the .csd file, and the .csd file is not updated, that user account will get locked out after a few minutes. This happens because the Aspen Cim-IO Manager will repeatedly try to log-in using the now invalid password. After 10 successive failed log-in attempts, the account may be locked out by a Windows network security rule. Since this password is hidden in the .csd file, it can easily be overlooked when updating Services passwords after making a password change.
TheSolution is to update the password for that logical device using the Aspen InfoPlus.21 Administrator. To update the password, right-click on the logical device name under the I/O object in the Aspen InfoPlus.21 Administrator and select Properties. Update the Password in the Properties dialog.
Another approach is to use an account where the password never expires. Alternately, Knowledge BaseSolution ID 118087describes a procedure for configuring a logical device without specifying a user name and password. If no user name or password is specified per thisSolution, then the logical device will run under the same account specified as the owner of the Aspen Cim-IO Manager service.
Keywords: account locked out
locked out
password
References: None |
Problem Statement: It has been noticed that a large number of bad or invalid tags can cause performance problems in certain OPC servers. A typical example of this is when tags are being requested by IP.21 which do not exist in the external data source. The repeated requests for these non-existent tags can cause response time from the Cim-IO server to degrade.
The best and obvious way to remedy this is to investigate the cause of why the tags appear to be bad or invalid and correct the problem. If the plant instrumentations has been turned off on purpose, then data collection for the corresponding tags should be turned off in the IP.21 GET record.
However, since the above approach is not always immediately possible, the following question may arise:
Is there a way to configure IP.21 systems to automatically take bad tags off scan in the IP.21 GET records when these tags cause performance problems on Cim-IO servers? | Solution: Yes, there is. Here is the information on how to set up Automatic Scan-Off for Problematic Tags.
This option is designed to allow users to configure IP.21 systems to automatically take certain tags off scan in the repeat area of IP.21 IOGetDef records when these tags cause performance problems on Cim-IO servers.
To enable this option, the computer running the InfoPlus.21 database needs to be configured to detect and take problematic tags off scan. This is done by adding the following string value to the registry.
HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\CIM-IO\ CIMIODeviceScanOff
The value CIMIODeviceScanOff will be set to a comma separated list of numeric Cim-IO device status codes for tags that should be taken off scan. For example when using the Cim-IO/OPC server, if a non existent tag is requested, the device status returned for that tag will be 77101. This number indicates a Cim-IO server facility of 77 for OPC and an error of 101 for invalid tag. In this example the registry value would be defined as 77101. If necessary, multiple values can be defined by separating them with commas. For example a string value of 77101,77116 would indicate tags with device status codes of 77101 and 77116 should be taken off scan in the repeat area of the IOGetDef record.
When a tag is taken off scan, the reason will be stored in the IO_DATA_STATUS_DESC field of the IOGetDef record. This will contain the descriptive text associated with the numeric device status code. In the above OPC example, if a device status code of 77101 was detected this field would be set to the string Invalid Tag.
These numeric codes and their associated descriptions are defined in the server specific .def file, which contains the error codes for the Cim-IO server. In the above OPC example the file would be called cimio_opc.def. For this feature to work properly, the .def file for the Cim-IO server must be in the etc directory of the CIMIO directory tree on the IP.21 computer and the file cimio_errors.def must contain an entry listing the server's .def error file. See the Cim-IO users guide for a complete explanation of errors files.
When problems with the tags have been corrected in the external data source, these tags will need to be put back on scan in the IOGetDef record. This can either be done manually or through an IP.21 SQLplus script.
Keywords: bad
invalid
scan-off
scan off
References: None |
Problem Statement: The cimio_autostart.bat script does not run successfully when the Aspen CIM-IO Manager service is started. | Solution: Go to the System properties and from the Advanced tab select environment variables, find the system variable %CIMIOROOTQ% and change it to C:\Program Files\AspenTech\CIM-IO instead of C:\Program Files\AspenTech\CIM-IO. Reboot the machine after making this change.
Keywords: CIMIO Kernel
CIMIO Manager
Autostart
References: None |
Problem Statement: When creating a redundant configuration via IO Wizard, Store & Forward can’t be enabled, as the option is greyed out. | Solution: The workaround is to complete the configuration and enable Store & Forward on the logical device Properties.
· Using the IO Wizard create a new logical device
· Select OPC and NEXT
· Processes:
o Enable Store & Forward is greyed out
· Click FINISH
· Select the device and check the Properties
· Select Processes tab and you will get the following message:
Ignore this error message (seeSolution # 136893)
· Enable Store & Forward:
· Click OK
· All processes are created correctly:
Keywords: IO Wizard
Store & Forward
Redundancy
References: None |
Problem Statement: The CIMIO_MSG.LOG file contains a message that is constantly repeated as follows:
DD-MMM-YYYY hh:mm:ss.sss, Logged by <DEVICE_NAME> on node <NODENAME>:
Error -3 accessing record and field id
No such record | Solution: This message indicates that the logical device has a get record with an occurrence have a blank value for the field IO_VALUE_RECORD&FLD.
Keywords: Error -3 accessing record and field id
No such record
CIMIO_MSG.LOG
References: None |
Problem Statement: In some occasions, users that have been configured in Aspen Framework (AFW) Security Manager and assigned to roles, are displayed as red instead of green on AFW Security Manager (or InfoPlus.21): | Solution: This issue can arise if there is an issue with the local cache on the machine:
Go to Control Panel > Services
Highlight the Aspen InfoPlus.21 Task Service
Right click and select Stop
Browse to ...\ProgramData\AspenTech\InfoPlus.21\db21\Group200
Delete the file IP21AFWCACHE.DAT
Go back to Control Panel > Services
Highlight the Aspen InfoPlus.21 Task Service
Right click and select Start.
Either check in the AFW Security Manager, or go open the Aspen InfoPlus.21 Manager. Select the Actions menu and User Roles.
Keywords: AFW
Users show as red
References: None |
Problem Statement: Cimio has a feature called Store and Forward (S&F). When communication is lost between the Cimio Server machine and the Database machine, because new values cannot be sent directly to the database, the Cimio Server will start writing the values to a store file located on the same machine as the Cimio Server.
The two most likely causes of this communication breakdown would be either Network problems, or if for some reason the Database is shut down and/or the Database machine is rebooted. When communications are re-established, the data that was being entered in the store file is then forwarded to the database machine. So the store file is a temporary buffer, that is filled and emptied, as necessary, depending on the existance of communication between the two machines.
A question was raised as to how Cimio determines that communications were lost between the Server and Database machines.. | Solution: As mentioned above, often the reason for a communication loss is due to Network problems. It is actually the Cimio Server machine that determines loss of communication with the Database machine. It is the server machine that is trying to send data to the database machine and gets some form of timeout error. It is at that stage it goes into a Store mode.
The Store 'mode' will remain until the client tasks (on the database) have re-established connection. To do this they are continually 'pinging' the Server machine until successfull communication is returned.
With Cimio version 4.9.7 a new option was introduced that allowed you to configuring that Pinging Frequency, but as described above, that is only used for re-establishing communication, not determining loss in communication
Keywords: S&F
References: None |
Problem Statement: Frequently when using regional settings which are non-US, the months are not recognized by PIDwatch resulting in failure.
InfoPlus.21 implicitly uses a US-English timestamp format to extract history, for example: 03-JAN-07. When importing data through the AutoRun operation, a locale-aware function CDate is used by another VB function DateDiff in determining the number of sample intervals. When the client PC is configured for non-English US Regional Settings - this breaks the CDate function and results in an error. | Solution: Obviously, changing to English-US regional settings will fix the problem.
Since this is only desirable in the US (or possibly other English speaking countries) another alternative is the attached executable which implements the above suggestion by the developer.
Simply download the zipped PIDWatch.exe file and use it to replace the same file on the AspenWatch host.
Prudence would suggest that the original executable be renamed and not discarded, in case the clients specific environment uncovers a previously unnoticed bug in the patch.
Keywords: watch, pid, aspen
References: None |
Problem Statement: You have just applied the latest patch to your Cim-IO server and have restarted the machine. When manually starting the Aspen Cim-IO Manager service you receive the following error:
Windows could not start the Aspen Cim-IO Manager service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion. | Solution: The fact that this occurs after a recent installation of a patch suggests the problem is due to blocked files. Check the file properties of the Cim-IO files in the Code folder, eg. cimio_sf_store.exe file:
C:\Program Files (x86)\AspenTech\CIM-IO\code\cimio_sf_store.exe
In particular, look out for the Unblock button with the attendant Security message:
This file came from another computer and might be blocked to help protect this computer.
You could unblock each file in turn but to be thorough it is advisable to reinstall the patch, taking particular care to first unblock the compressed zip file which you downloaded from the support website.
Known Issue with Patching
There is an alternative explanation of this headline error. We have seen failures of the patching process to correctly install the cimio.dll file, this has happened without any error during installation. It should be repeated here though that if the installer needs to repeat the patch installation, then the installer must, every time, extract or copy all the ER files into the temporary directory before executing the installation utility.
Nevertheless, please check to see if the cimio.dll in the patch media has been copied over to the destination %COMMONPROGRAMFILES%\Aspentech Shared\cimio.dll. If this has not happened, use Windows Explorer and manually rename the old file and copy over the new one into the Aspentech Shared folder. You should then find that Aspen Cim-IO Manager service will start up without error.
Keywords: Patch
Security
Cim-IO Server
InfoPlus.21
Error 1053
CIO141017I
Install
Entry Point Not Found
References: None |
Problem Statement: How do you change the Framework Database Password? | Solution: This document describes how the password for the Aspen Framework SQL Databases can be changed.
All client applications use a common user name and password when connecting to the Framework databases. Both the user name and password is defined when the Framework is installed on the server.
To change this password, log into the Framework server's Administrator account. Then from the Start Menu, select Programs, Microsoft SQL Server, and Enterprise Manager. Expand the folders under the Framework. Open the Security folder, select Logins and then select the user name that was defined when the Framework was installed on the server. Right click and select properties. Change and confirm the password.
Keywords: SQL Database
AFWDB
PODB
password
References: None |
Problem Statement: If you change the format record for an AW_PIDDef record so that the overall format is larger than 8 digits, the value is not displayed in the PIDWatch portion of the PCWS. | Solution: Download and apply the attached ProcedureDef record using the following instructions:
#####TO REPLACE SQL PROCEDURES IN ASPENWATCH DATABASE#####
The new SQL query should be loaded into the running AspenWatch database.
[Before starting the procedures, save a snapshot somewhere so it can be restored if something is wrong with the instructions, or if they are implemented incorrectly, or if the new procedure doesn't behave as we expect it to. ;^)]
1. Open the SQLplus Query writer.
2. Open the query file: File | open Then browse to the file and open it.
3. Choose the Record | Save As menu option.
4. In the resulting dialog change the record name by removing the .SQL from the name of the query. The query (procedureDef record) you are replacing is: PID_GROUP_TUNE.
5. Click the Save button. You should get a message asking if it is OK to overwrite the existing record. Click the Yes button. (If you do not get this message for the above query then you have specified the name incorrectly. Remember the name you used and call support for assistance.)
After you have replaced the existing ProcedureDef record with the contents of the attached query, you should be able to see the limits in the PCWS.
Keywords:
References: None |
Problem Statement: What is the differences between records defined by IoPutDef and IoPutOnCosDef? | Solution: Records defined by IoPutDef may activated manually using the Aspen InfoPlus.21 Administrator, from a scheduling record defined by ScheduledActDef, by a query calling the function ACTTSK, or by a change-of-state activation triggered by the contents of the field IO_ACTIVATION_COS.
Regardless of the method of activation, all the occurrences with the field IO_DATA_PROCESSING set to ON in the IoPutDef record are written to the process.
Records defined by IoPutOnCosDef may be activated in the same ways as records defined by IoPutDef, and when this happens, all the occurrences with the field IO_DATA_PROCESSING set to ON in the IoPutOnCosDef record are written to the process.
The difference between records defined by IoPutDef and IoPutOnCosDef is that when one of the IO_VALUE_RECORD&FLD fields changes in the record defined by IoPutOnCosDef, then only that occurrence is written to the process. This means that you do not have to schedule records defined by IoPutOnCosDef, trigger them using the contents of the field IO_ACTIVATION_COS, or activate them using a query.
Keywords:
References: None |
Problem Statement: Why does a yellow question mark (?) appear beside a logic device name under the I/O icon in the Aspen InfoPlus.21 Administrator? | Solution: The yellow question mark means either the device was not configured using the Aspen I/O Device Wizard or the Aspen InfoPlus.21 Administrator could not communicate with the Aspen Cim-IO Manager Service on the Aspen Cim-IO Server.
The Aspen Cim-IO Administrator sends a request to the Aspen Cim-IO Manager Service on the Aspen Cim-IO server asking for the statuses of the Aspen Cim-IO server processes.Â
If you did not use the Aspen I/O Device Wizard to configure the device, then the Aspen Cim-IO Manager does not have enough information to return the statuses of the Aspen Cim-IO server processes, and this causes the Aspen InfoPlus.21 Administrator to display a yellow question mark.
If you used the Aspen I/O Device Wizard to configure the device, then either the Aspen Cim-IO Manager Service is not running on the Aspen Cim-Io Server, or the port used by Aspen InfoPlus.21 Manager and the Aspen Cim-IO Manager Service to exchange information is blocked.
Look in the Windows services file on both the Aspen InfoPlus.21 and Cim-IO Servers and find the service CIMIOManager. Make sure the both servers use the same port and that the port is not being blocked by a firewall. The default port number is 7777.
Keywords:
References: None |
Problem Statement: How can I create a new tag in the RTO Watch database | Solution: This is the procedure to follow for this addition:
1) Create the tag in Aspen Online ? this could be a local tag or a tag from the plant database. Make sure that Aspen Online is picking up the value.
2) If everything looks ok in Aspen Online generate the rte.dmp and rte.ini files
3) It is a good idea to get a snapshot of the ip21 database just in case something doesn?t work correctly
4) Use RTO Watch Maker to update the ip21 database with the new tag
RTO Watch Maker updates the database with the new tag. It doesn?t update the entire database and it doesn?t destroy the history for data already being captured. The attachment describes creating a local tag and connecting it to a model variable for historization by Aspen RTO Watch. This is a little different from what is being requested since they only want to add a tag. But the final steps are the same: Steps 2) and 4) are covered in the document. Saving a snapshot is not covered but should be done as a precaution.
Keywords: RTO, Watch, Aspen, update, IP21, database, online
References: None |
Problem Statement: Can Aspen Cim-IO interface server instances be defined on cluster nodes? | Solution: Aspen Cim-IO interface servers should NOT be defined locally on cluster nodes. This is due to the dynamic nature of some features required by Aspen Cim-IO interface server instances.
However: All Aspen Cim-IO client features normally supported on single, non clustered computers are also supported under the cluster environment:
Consider basic tests of Cim-IO basic operations (get or put) in the actions checklist after installing Aspen software, and before joining single nodes to the cluster. Repeat tests after joining the cluster and after forcing failover and failback.
Keywords:
References: None |
Problem Statement: Aspen Cim-IO continues to create and update a store file even after deleting the the scanning list and the store file. | Solution: The Aspen Cim-IO scanning process cimio_sf_scanner.exe buffers the contents of the scanning list each time Aspen InfoPlus.21 creates or updates the scanning file.
If you stop the Aspen Cim-IO client tasks in Aspen InfoPlus.21 or if you switch nodes when using redundant Aspen Cim-IO nodes without performing changeover cleanup, and delete the scanning list on the Aspen Cim-IO server without stopping the server tasks (cimio_sf_store.exe, cimio_sf_forward.exe, and cimio_sf_scanner.exe), the scanning process continues to schedule points to scan because of the information buffered by cimio_sf_scanner.exe.
As a result, the DLGP continues to scan the process, handing the results of the scan to the store process cimio_sf_store.exe. Since the Aspen Cim-IO server is not communicating with Aspen InfoPlus.21 (because you have stopped the Cim-IO client tasks or have switched to a redundant node without performing a changeover cleanup), the store process creates and updates a store file.
To resolve this problem, be sure to stop the Apen Cim-IO server tasks (cimio_sf_store.exe, cimio_sf_forward.exe, and cimio_sf_scanner.exe) along with interface's DLGP and DIOP processes (if applicable) when deleting the scanning list or enable changeover cleanup when using redundant Aspen Cim-IO nodes
Keywords:
References: None |
Problem Statement: When working with the Cim-IO SF Monitor (CimioSFMonitor.exe), a tool to find additional details about a Cim-IO Store and Forward Store file, one might notice the following message when using the application:
339Component 'RICHTX32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid
In addition, some of the functionality in the Cim-IO SF Monitor may not work. What can be done to fix the problem? | Solution: The problem is caused because the file 'RICHTX32.OCX' is not present on the system. TheSolution is to:
1. Exit Cim-IO SF Monitor.
2. Place a copy of the file in the attachment to the location pointed by
%WINDIR%\system32
This location is usually one of the following:
\WINNT\system32
or
\WINDOWS\system32
3. Restart Cim-IO SF Monitor.
In case you have Aspen Cim-IO server running on a 64-bit machine please copy the attached .ocx file to the following folder location
\Windows\SysWOW64
Keywords: RICHTX32.OCX
Cim-IO SF Monitor
339 component
References: None |
Problem Statement: I get a strange error when I export my simulation from Aspen Plus to Aspen Dynamics, something similar to the following:
TRANSLATE USING COMPILED AST PROCEDURES IN D:\Program Files\AspenTech\Aspen Dynamics 11.1\Ast DIRECTORY.
TRANSLATING FEED STREAM FEED of TYPE MATERIAL.
363: ERROR: Variable ADA is undefined
363: One or more items of result data are missing. Please re-run the simulation and try again.
363: FATAL ERROR: Aborting procedure D:\Program Files\AspenTech\Aspen Dynamics 11.1\Ast\FEEDM.TBL
This is just an example (although if you face this one, see | Solution: 112040).
Solution
When you export a simulation from Aspen Plus to Aspen Dynamics, we invoke some scripts (the TBL files in Aspen Dynamics AST folder - these are binary files, you cannot read them). When things go according to plan, you may get warnings or fatal error messages with some meaningful explanation.
However, sometimes things go wrong. In this case, you should contact support for further assistance (or look in otherSolutions in case the specific problem has already been reported and documented). The number you see (like 363) is not some kind of undocumented error message number. It is simply the line number of the script on which the error is taking place. This is why it is very useful to report the exact error message, and specify which hot fix/patch you may have installed on the computer, as it helps us to identify where the error is occuring. As usual, an example file to reproduce the problem is the best way to report the issue (the message only says what went wrong, but there are sometimes many potential causes).
Keywords: None
References: None |
Problem Statement: Aspen Custom Modeler, Aspen Adsorption, Aspen Model Runner and Aspen Dynamics installed from V7.2 DVD crash during program startup | Solution: There could be many reasons for this kind of crash. With AspenONE AES V7.2 installs, a corrupted XML file could also cause the crash. To resolve this type of crash, the corresponding bad xml file either has to be repaired or a new file generated.
To generate a new file browse to X:\Documents and Settings\All Users\Application Data\AspenTech\AES and look for a file called apmodelcatalog.xml. Simply rename this file to badapmodelcatalog.xml. This should allow you to start the application without a problem. Afterwards, e-mail apmodelcatalog.xml file to AspenTech support and request a repair of the file. The file will be sent to development to be fixed and returned to you.
Keywords: Aspen Custom Modeler
Aspen Model Runner
Aspen Adsorption
Aspen Dynamics
Custom Modeler
Model Runner
Adsorption,
Dynamics
Crash
ACM
References: None |
Problem Statement: Why are there superseded models and why are they in newer versions of Aspen Plus Dynamics? | Solution: Superseded models are available under Library | Dynamics | SupersededModels in the Exploring Simulation window. These models are used in earlier versions and have been phased out with new models in recent versions. For example, Aspen Plus Dynamics has different pipe models: Pipe (compatible with Aspen Plus Dynamics 10.2), Pipe2 (compatible with versions 11.1 to 2004.1, and Pipe3 ( compatible with version 2006 to latest V7.1). Similarly, old control model PID has been replaced with PIDIncr which is based on an incremental algorithm to represent more closely real industrial controllers. Recent models are updated and improved with more robust algorithms.
The reason to keep superseded models in the recent versions is to allow users to open dynamics files created in older versions using older models in newer versions of Aspen Plus Dynamics. If one wants to replace any old model, he or she just needs to drag and drop the new model from the Dynamics library onto the current block on the flowsheet and answer Yes to change the model.
Keywords: Superseded Models, Pipe3, PID
References: None |
Problem Statement: While migrating from Aspen B-Jac models Aspen EDR (Exchanger Design and Rating) models, users might not have licenses for Aspen B-Jac products any more. (Should you refer to the sunset policy in the Problem Statement - search for 'product lifecycle' in our | Solution: s that should tell you when support was stopped.)
ThisSolution describes, besides using the 'File Conversion Utility' (Solution 125142), how to convert B-Jac models to EDR models inside the EDR program, even without B-Jac licenses.
Solution
To convert Aerotran models to Air Cooled exchanger models for instance:
Open a new EDR session and select 'Aerotran - Air-cooled & economizer thermal design'.
? A blank 'Aerotran' case will pop up. Now from the top menu of the diagram window go to File > Open, and navigate and select the Aerotran file that you want to convert. You should see the Aerotran application pop up, though you will receive license error messages because you don't have Aerotran license. Although you are unable to run the application, the application window should still stay opened. You should be able to read the input and view the results (so it acts as a browser), but will not be able to run the program.
? Now go to Run > Transfer, and select 'Air Cooled Exchanger'.
? Click 'OK'. You should see the data has been transferred into AirCooled. When you save the file, a EDR file will be saved rather than a BJAC file. Click 'OK'.
? Now you should still see the Aerotran window in front. Don't worry, as you can minimize or restore down the Aerotran window. This is because the AirCooled application has been created and opened already, but it is just behind the Aerotran window.
? Up on minimizing the Aerotran window, you should see the AirCooled application, containing all the data being transferred from Aerotran. You should be able to run the AirCooled application.
? When you save the file, you can choose to remove the Aerotran application since you don't have license to it any more. You can go to File > Remove Application, and select Aerotran and click OK.
Now this file only contains AirCooled application. You can save it, but you may want to save it as a separate file than the original Aerotran file. This will avoid over-writing the original Aerotran file which should be treated as a back-up.
For converting Hetran to Shell&Tube and converting Teams to Shell&Tube Mechanical, it is the same as transferring Aerotran to AirCooled.
Keywords: Convert B-Jac, EDR, Hetran, Aerotran, Teams, Shell&Tube, AirCooled, Shell&Tube Mechanical
References: None |
Problem Statement: Changes in pump curve polynomial coefficient are not taken into account in dynamic mode. Only in steady-state and initialize. Any possible work-around ? | Solution: This is by design.
Pump polynomial coefficients (and performance curve data) cannot be changed on the fly in a dynamic run. The reason for this is that the pump characteristic is calculated in a procedure call which loads all the parameters in workspace during a precall and subsequently accesses the workspace during the simulation - this improves the performance of the pump calculations. When you change coefficients on the fly in a dynamic run, it has no effect because the new values are not loaded into the workspace. An initialization run does do a precall and thus updates the workspace.
The same behaviour applies for compressor performance curves, as well as for tabular data for valve characteristics.
Keywords:
References: None |
Problem Statement: In some circumstances when I run the LogicCompare block, the output is a value between zero and one. The documentation states that the output value should be boolean, only zero or one. | Solution: The way to resolve this issue is to Solver Options | Integrator, and switch Integration Error Test as States and algebraics.
The default integration error test is for state variables only. This gives better performance for cases where there are mixed differential and algebraic equations. For the case on the LogicCompare block only, there are no differential equations and therefore no state variables. This is a rare case for an Aspen Plus Dynamics simulation, so we will keep the default behavior the same as before, testing for state variables only.
You will still find some values that are neither 0 or 1 for the output of the LogicCompare block even with the integration error test set to states and algebraics. This is because the plotting application interpolates the values sent from the simulation engine to the user interface at specific time intervals set by Run | Run Options? | Time control | Communication.
You can minimize the number of non 1 or 0 values by making the communication interval larger, though this will make the plots less detailed
Keywords: LogicCompare, Integration Error Test
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.