question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: Why does the emission calculation with electrolytes in Aspen Batch Process Developer return an error? | Solution: Batch Plus emission calculation only support the following electrolytes as solute:
Sulfuric Acid
Nitric Acid
Phosphoric Acid
Ammonia
Hydrogen Chloride
Carbonic Acid
If the above substance and water is in the contents, and emission calculation is your objective, then electroytes with ELECNRTL approach should be considered.
Important factor: CAS number for those substance should exist and correct. Batch Plus relies on Aspen Properties to do electrolytes simulation. And CAS number in this case is the only uniq identifier to notify Aspen Properties. For example, even if you have Nitric Acid for component name and Alias in Batch Plus, if the CAS number is blank or incorrect, then Chemistry paragraph will not be generated correctly.
It's good practice to check CAS nunmber is you are using ElecNRTL to do emission calculation.
Keywords: Electrolyte
CAS
References: None |
Problem Statement: OPCPROPERTIES ???T?[?o???C?A???e?I?EZ??s???A?G???[???b?Z?[?W : Run-time error '70'; Permission denied ???\Z|???e?e?B | Solution: OPCPROPERTIES.EXE ??SC??ZO?????AZA?s???e?B
Keywords: OPCPROPERTIES
Run-time error '70'
References: None |
Problem Statement: Tag values captured into Aspen InfoPlus.21 via Aspen Cim-IO for OPC do not match values in a Honeywell DCS for the same time period. | Solution: When the difference in tag values between a Honeywell DCS and Aspen InfoPlus.21 is not due to changes made to tags, corruption of the Aspen Cim-IO list files, or mismatch in the tag mapping between DCS and Aspen InfoPlus.21 Get records, it may be necessary to make changes to the IoGet entry configuration to add additional Honeywell-specific parameters to the DCS tag name. This is even more so if the data value difference is significant and cannot be attributed to the data compression routine.
For the problematic IoGet records, to enable reading the mode parameter on a Honeywell DCS controller, please append the parameter .mode.internal to the tag name in the IO_TAGNAME field and set the IO_DATA_TYPE to Default as shown in the example below:
IO_TAGNAME=YourDCSTagName.mode.internal
IO_DATA_TYPE=Default
Keywords: IOGet Records
DCS
Honeywell
TDC3000
App Node
References: None |
Problem Statement: Does the connection between Aspen Cim-IO for OPC and an OPC server use an 'in-process' or 'out-of-process' approach?
If Aspen Cim-IO for OPC supports both in-process and out-of-process connections, is there any way to force Cim-IO for OPC to choose out-of-process (other than making changes in OPC server preferences)? | Solution: Cim-IO for OPC supports both in and out of process connections. It will automatically pick one based on the server preferences.
There is no way to force Cim-IO for OPC to choose one over the other.
NOTE: A brief explanation of the meaning of 'in-process' and 'out-of-process' can be found inSolution # 110540.
Keywords: in process
out of process
References: None |
Problem Statement: The DIOP processes, which are Cim-IO server tasks that perform low-level communication with external hardware devices, need to be running for the InfoPlus.21 system to communicate with the Cim-IO server. The DIOPs that communicate with the Foxboro system cannot be started unless all the necessary Foxboro processes are also running. If the DIOP processes are started before the Foxboro services are running, the DIOP tasks will immediately die.
If the DIOP processes are not running, the cimio_t_api utility will return errors such as USR_GET_CONNECT error connecting to device | Solution: To ensure successful DIOP startups, the processes on the Foxboro side need to be started and running before the cimio_foxia_startup.bat file is executed. This can be implemented by including a sleep command in the cimio_autostart.bat file. The additional wait will give the Foxboro system enough time to start up correctly before the DIOP processes are started.
The following is an example cimio_autostart.bat script with the sleep command included.
# add any batch file to be run by the CIM-IO Manager service at startup
sleep 90
call%cimioroot%\io\cio_fox_api\cimio_foxia_startup.bat
call c:\AspenTech\InfoPlus.21\db21\commands\cimio_sf_start.bat CIMIOFOXIA
Keywords: diop
dlgp
References: None |
Problem Statement: There is a problem generating Excel Reports (e.g. Plan or Process Equipment Contents report) with Microsoft Office 2007 with or Without SP1. The following screen will repeatedly show up. If user keep hitting yes, then eventually will get to the report, but if user hit No, it will go into infinite loop, the only way out is to kill Excel with task manager.
Note if Excel is killed with task manager, Aspen Batch Process Developer will be left in unstable state. | Solution: Download and install Microsoft Office 2007 SP2 to resolve this problem.
http://www.microsoft.com/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en
Note: Due to the numerous upgrades from Office 2003 to Office 2007, the Aspen Batch Process Developer Excel Report Templates may not work. To fix the problem with Excel templates, install the hot fix attached to theSolution 127418.
Keywords: Excel 2007, SP1, SP2, Excel Reports, Office 2007, 127418
References: None |
Problem Statement: If Warnings and Errors indicators disappear from recipe view without modifying the preferences and settings, is there a way to refresh the recipe view to make them appear again? | Solution: To refresh the recipe view to show the warnings and error indicator in text recipe again, go to Tools | Options | Errors and Warnings.
On the Errors and Warnings tab, uncheck the show simulation error and warning icons and click OK.
Then go back to the same menu and check the show simulation error and warning icons and click OK.
Keywords: error, warning, indicator, icon, recipe
References: None |
Problem Statement: What does the Undo Previous Scaling will do? | Solution: Starting from version V7.0, Aspen Batch Process Developer offers a Single-Level Undo Scaling. The Undo Previous Scaling option under Recipe Scaling (Tools | Recipe scaling) will revert the recipe scale-up to one level back from the current scaling conditions.
Recipe scaling offers 8 different scaling options and when doing recipe scaling this option (Undo previous scaling) will help the user to quickly revert to the previous level recipe scaling results.
Keywords: Recipe Scaling, Recipe, Scaling, Scale up, Undo.
References: None |
Problem Statement: YOKOGAWA OPC server doesn't synchronize after Aspen Cim-IO for OPC installation | Solution: The CIMIO manager service is linked to the YOKOGAWA SIMMGR service.
In order to synchronize correctly, the CIMIO Manager service needs to be launched after the YOKOGAWA SIMMGR service. Creating a Service dependency between the two services, where CIMIO Manager service must wait until the YOKOGAWA Service has started resolves this issue.
Keywords: YOKOGAWA
OPC
CIMIO
Customer: SOLVAY ELECTROLYSE
References: None |
Problem Statement: When using the Pure Component Editor to enter or edit compounds, the Calculate button in the General folder does not calculate the molecular weight. The Molecular Weight value remains 0 or, the Molecular Weight becomes 0 if the Calculate button is pressed. All compounds have molecular structure files associated with them | Solution: To estimate the Molecular weight for a new component using the component editor, follow the steps below.
1. Go to Data | Pure Components
2. Click New and Assign the name
3. Then click the 'Estimate' Button and import the structure by clicking on the 'Import Structure' button.
4. Find the molecular structure files and then open the molecular structure files.
5. Click 'Calculate Bond' button to read the components and their bonds.
6. Now the 'Calculate' button is active and functional, you can click on the 'Calculate' button to estimate Molecular weight.
7. Then click the 'Import Selected properties' button to import the calculate Molecular weight.
8. If you would like to use the calculate button on the General TAB, then after calculating Bond click Import Selected properties and click Calculate on general TAB to estimate Molecular Weight.
On the general TAB, if you create a new component and import molecular structure files and click Calculate for estimating molecular weight, it will report a zero because Import molecular structure on the Pure component dialog does not populate the Atom count. The Calculate Molecular Weight is dependant on the Atom Count information not the molecular structure file information.
Keywords: Molecular weight, Pure Component Editor, molecular structure
References: None |
Problem Statement: You are attempting to export data from a model in SCM to an Oracle Database. You notice this is taking an extremely long amount of time. When this used to run, it would take five seconds. Now, it takes upwards of 35 minutes. | Solution: This is caused by enabling tracing on the ODBC driver. You can disable this as shown in the screenshot below:
Keywords: None
References: None |
Problem Statement: In Aspen SCM Planning Board, when is the rule for TDAT(@,PT) called by the simulator? | Solution: When creating a new activity or re-schedule an activity to a different location (especially to a different TIM) or changing lotsize, the scheduling logic will need to get TDAT(PT) to re-calculate MAKF(PT) and run the rule if you specify a rule there.
For M SIM, usually it does not need to re-calculate MAKF(PT) again as the it should stay the same IF the ST and AS are in the same time period (TIM). If in case AS falls into the different time period, it will need to get TDAT(PT) again (and need to run the rule in your case) to fill the MAKF(PT) as things specified in TDAT may be TIM dependent.
Keywords: Planning Board
M SIM
TDAT
References: None |
Problem Statement: This | Solution: provides information about OPC Enum service used for CIM-IO and others OPC clients applications and provided useful resource for troubleshooting issues with CIM-IO, regarding this service.Solution
As defined on the OPC Training Institute webpage:
OpcEnum (OPC Enumerator) is a software application that provides information about each OPC Server that resides on a PC. OPC Client applications (such as HMIs, Historians, various automation/process control applications, etc) use OpcEnum to browse (discover) the OPC Server applications that are available on the target PC. This enables users to easily connect to various OPC Servers. OpcEnum retrieves its information from the Windows Registry. Consequently, OpcEnum can only reveal information about local OPC Servers (i.e. the OPC Servers and OpcEnum must reside on the same PC). The OpcEnum executable is opcenum.exe. OpcEnum provides the Program Identifier (ProgID) and Globally Unique Identifier (GUID) for each OPC Server on the PC.
The server running CIM-IO asyndlgp process should also have OPC Enum installed as a windows service on it:
Troubleshooting Issues regarding OPC Enum:
1. Try starting OPCEnum from Windows Service using a user account with privileges to access the OPC server.
2. If OPCEnum is not presented on Windows services list look for the file OPCEnum.exe on:
64-Bit: C:\Windows\SysWOW64
32-Bit: C:\Windows\System32
try running the executable from a command windows. You should be able to see the process running on windows task manager:
3. If the executable cannot be launch from a command windows, look for specific issues on the Windows Event viewer.
4. If OPCEnum.exe cannot be found on the server, you can install it as part of the OPC Core components package that can download from here:
OPC Classic core components: https://opcfoundation.org/developer-tools/developer-kits-classic/core-components/
A free user account on the OPC Foundation site is required. Installing the OPC core components will also register OPCEnum as a windows service to run automatically.
For further details about OPC Enum refer to OPC Trainning Iinstitue white paper:
Cannot browse for OPC Servers on remote PC: http://www.opcti.com/cant-browse-opc-servers.aspx
Keywords: OPC Enum
OPCEnum.exe
CIM-IO
References: None |
Problem Statement: Why does InstallService.exe install the service using the name Cim-IO for OPC Interface and not Aspen Cim-IO for OPC? | Solution: If the Aspen installer does not create the Aspen Cim-IO for OPC service, you can use the utility InstallService.exe to install the service, however, the service will be created using the legacy name of Cim-IO for OPC Interface. To avoid any confusion when modifying services, the following procedure can be used to install the service using the name Aspen Cim-IO for OPC instead.
If you previously ran InstallService.exe to create the Cim-IO for OPC Interface service, it needs to be removed before recreating using the new name of Aspen Cim-IO for OPC.
Open a command prompt session using the Run as Administrator option and run the following command:
sc delete zzCIMIOOPCMGR
The command prompt should return
[SC] DeleteService SUCCESS
Now to install the service using the name Aspen Cim-IO for OPC use the following procedure (be sure to use the appropriate location depending on if the machine is 32-bit or 64-bit). Also note that the following command is sensitive to spacing, therefore run the command as it is written below.
sc create zzCIMIOOPCMGR binPath= C:\Program Files (x86)\AspenTech\CIM-IO\io\cio_opc_api\Manager.exe DisplayName= Aspen Cim-IO for OPC
The command prompt should return
[SC] CreateService SUCCESS
Open the Windows Services component (services.msc) or refresh the window if it is already open and confirm that the Aspen Cim-IO for OPC service is in the list.
Keywords: installservice
removeservice
Aspen Cim-IO for OPC
References: None |
Problem Statement: How does Aspen Batch Process Developer calculate the pure component density and molar volume? | Solution: If you have not entered a constant density, Aspen Batch Process Developer uses the following models to calculate temperature-dependent molar volume and density.
When calculating the density of a pure component, phase is the first parameter that determines which of the following density equations Aspen Batch Process Developer uses for calculation.
Liquid Phase:
If
Then
no parameters are specified under the Density and Surface Area | DIPPR Liquid Density Equation section of the Pure Component Dialog
Aspen Batch Process Developer uses the Rackett equation to calculate temperature-dependent molar volume and density for the liquid phase.
any of the three Rackett Equation parameters is specified outside of the equation's limits
Note: The Rackett equation uses these parameters:
Aspen Batch Process Developer uses a default density of 55.49 kmole/cubic m to calculate temperature-dependent molar volume and density for the liquid phase.
Parameter
Where specified
Critical Temperature
Data | Pure Components | Critical Properties | Temperature
Critical Pressure
Data | Pure Components | Critical Properties | Pressure
Rackett Parameter
Data | Pure Components | Thermodynamic Constants | Rackett Parameter
the first three parameters (C1, C2 and C3) are specified under the Density and Surface Area | DIPPR Liquid Density Equation section of the Pure Component Dialog
Aspen Batch Process Developer uses the DIPPR Liquid Density equation to calculate temperature-dependent molar volume and density for the liquid phase.
Solid Phase:
If
Then
no parameters are specified under Density | Solid Density Polynomial of the Pure Component Dialog
Aspen Batch Process Developer uses a default density of 55.49 kmole/cubic m to calculate temperature-dependent molar volume and density for the solid phase.
the first parameter (C1) is specified under Density | Solid Density Polynomial of the Pure Component Dialog
Aspen Batch Process Developer uses the Solid Density Polynomial to calculate temperature-dependent molar volume and density for the solid phase.
The DIPPR Liquid Density model and Rackett Equation are attached to theSolution.
Keywords: Liquid Density, Density, Pure Component Density, Solid Density.
References: None |
Problem Statement: After an upgrade of the Honeywell APP node OPC software the Cim-IO Get records stop updating. | Solution: By default during installation of the Honeywell software, the parameter Single Scan per Data Item is set to enabled, which is supposed to give the system better performance. This parameter must be DISABLED for Cim-IO to work properly.
The following steps may be used to modify the Honeywell APP node OPC software configuration:
1. Start the Honeywell Configuration Utility. Select the HCI Component utility program. In the dialog box that opens, select the OPC server in the 'Component Name' drop down list.
2. In the middle of the new dialog box, there is a 'Data Access Options' button. Select it.
3. In the bottom of the new dialog box that appears, there is a 'Single Scan per Data Item' area with two radio buttons. Make sure that the 'Disable' radio button is selected.
4. In order for this change to take effect, the TPN server (OPC server) has to be stopped and restarted. This can be done in the TPS Monitor program, or by rebooting the APP node.
Additional information: When this feature is enabled, it attempts to combine requests for data from different scan groups on the APP node into new internal scan groups that have no duplicate data requests from the DCS. The software creates an internal database to sort out all the information that it has to keep track of in order for this feature to be transparent to the OPC client user (Cim-IO and the IP.21 system in this case). A large number of requests from Cim-IO and IP.21 (via the Cim-IO Get records) can overwhelm the Honeywell APP node if this feature is not disabled.
Keywords: None
References: None |
Problem Statement: Where does Aspen CIM-IO fit in an OPC tunneling environment, and when is it appropriate to use an OPC tunnel? | Solution: OPC communications require two parts, a client and a server. In our world, the instrument vendor provides the OPC server. The purpose of the server is to send process signals to a client using OPC protocol. AspenTech?s CIM-IO for OPC interface is an OPC client that receives data from the instrument vendor?s OPC server. CIM-IO for OPC in turn serves the data to Aspen InfoPlus.21.
Usually, it is not difficult configuring OPC communications when the OPC client and OPC server reside on the same computer; however, OPC communications can be difficult when the OPC client and OPC server are on different computers. Putting a firewall between the two adds to the complexity.
The purpose of an OPC tunnel is to simplify OPC communications across a network. The tunnel has two ends ? one for the OPC client and the other for the OPC server. CIM-IO for OPC goes on the computer with the end of the tunnel for the OPC client, and the vendor supplied server goes on the computer with the end of the tunnel for the OPC server.
If the OPC server and the CIM-IO for OPC client reside on the same computer, then it is not necessary to use an OPC tunnel; however, if the OPC server and CIM-IO for OPC client are on different computers, then it makes sense to investigate using an OPC tunneler.
Keywords: CIM-IO for OPC
OPC
Tunnel
OPC Client
OPC Server
References: None |
Problem Statement: This Knowledge Base article provides steps to resolve the following error:
Could not create server RSLinx OPC Server on Node (null) on try number n, error is = Class is not licensed for use
which may be encountered in the CIMIO_MSG.LOG file when there is a connection failure between the Cim-IO for OPC server and the device. | Solution: If one is using RSLinx, make sure that a full-blown version of the RSLinx Classic software is being used, *not* RSLinx Classic Lite. Using the latter will produce the error message above and connectivity won't be established. Moving from the Lite version to RSLinx Classic involves activating a license. More details can be found at:
http://www.rockwellautomation.com/support/
Keywords: Cim-IO for OPC
CIMIO_MSG.LOG
Rockwell
References: None |
Problem Statement: This knowledge base article describes how to run SCM in Batch mode from Command Prompt window. | Solution: To run Aspen SCM in Batch mode from a Command Prompt window:
1. Display Command Prompt window Start | Programs | Accessories | Command Prompt.
2. Execute the command below.
Syntax:
mimias -cfullpathcasename -b[batchmacro]
· -c: Indicates that the string following -c is an SCM case name.
· fullpathcasename: The full patch of the case that you would like to run in Batch mode.
· -b: Indicates that you would like to run SCM in Batch mode. If you do not include a batch macro name, SCM runs the default macro, $BATCH.
Example:
mimias -cc:\programfiles\aspentech\aspenmimi\cases\juice.cas -b
Keywords: None
References: None |
Problem Statement: SCM 2006.1 with BPE is installed on a PC. MSOffice 2003 is also installed. When loading a profile in BPE, the MS Office Installer runs and BPE crashes. | Solution: Reinstalling the software via DVD adds the necessary files and will stop the MS Office installer from running.
The issue is that certain files were not installed during the initial install. These files which didn't get installed were in C:\program files\common files\VBA and C:\program files\Microsoft Shared\Office.
Keywords: BPE
MS OFFICE
VBA
MS OFFICE INSTALLER
References: None |
Problem Statement: We have seen cases where the use of PutOnCOS records can cause a memory leak for the OPC20ifix.exe process of the iFix 4.5 OPC Server.
The PutOnCOS records does a cancel/undeclare operation on the taglist and then declares the list with each COS activation. It looks like the iFix OPC Server cannot handle this properly. | Solution: Use the regular PUT records (i.e. IoPUTDef) instead which you can activate with a COSActDef or a SQL Plus query.
Keywords: IoPutOnCosDef,
IOLongTagPOCDef
memory leak
IOLLTagPOCDef
References: None |
Problem Statement: Tables listed in $MULTI that do not exist in TCAT results in a segmentation fault error when executing SCM in Batch Mode. | Solution: It has been found that a table listed in the $MULTI set (lists the names of all multidimensional tables in the current case) was not listed in TCAT. After eliminating this entry from $MULTI, the problem disappeared.
Keywords: None
References: None |
Problem Statement: You receive M0699 Cannot create scratch files error when copying tables. | Solution: The error is received due to the fact that there is not enough tables available in the catalog, although there seems to be exactly the right number of tables necessary.
The help files regarding COPY (under the Description of Arguments) specifically state the following:
source: (Required) The existing set or table that you want to copy from a case file into another set or table. The set or table must be local or scratch (Load Case attribute set to * or blank).
case|$cases_entry: (Required) Indicates the case from which you want to copy data
(taken from 2006.1 help files)
This is stating the product is designed to utilize scratch space when copying the table. Thus, a user may receive this error if they do not have enough tables available to allocate for the scratch space plus the designated copy.
To get around this issue, use the CMPRCASE command to increase the available number of tables in your case.
Keywords: M0699
Scratch
Copy Table
References: None |
Problem Statement: How do I fix the error message Invalid operating system command or not enough memory when running a SYS or DOS prompt command? | Solution: This is caused by the fact that when the SYS command is run, the DOS command interpreter is not available, hence all DOS executables such as DEL, COPY, and others are not available. As a work around, create a batch file with all the DOS commands that the user wants to run in the Aspen SCM case, and run that batch file with SYS. Since SYS will call a batch file, the batch file will open the DOS command interpreter and the DOS executables can be run in this manner.
Keywords: None
References: None |
Problem Statement: I received the following message when I try to run a MIMI command: $$$$$:ERROR-Cannot open message file. What could be causing this? | Solution: The most likely cause is MIMI cannot find the message file which should be located with the other MIMI system files. The user may have accidentally deleted or changed the path to the BIN directory of MIMI.
This path is specified in the System Files field on the Files tab of the System Options dialog box, which can be access through the Options | System... menu of MIMI.
This entry is automatically filled in during the installation of MIMI, but is editable or deletable by the user. The typical path for MIMI system files is C:\PROGRAM FILES\ASPENTECH\ASPENMIMI\BIN.
Once the user has entered the correct system path, MIMI will need to be shutdown and restarted for the changes to take affect.
Keywords: ERROR message
message file
MIMI commands
MIMI system files
References: None |
Problem Statement: How to specify that a batch process should be modified every given number of times ? For example, that every 3 batches a reactor should be cleaned, hence resulting in a longer batch time every three batches. | Solution: In the recipe use the Start Or/End Or keywords.
When running a Production Plan consisting of six batches in a row of the same batch, an additional Clean operation will be carried out after the React operation during the third and sixth batches.
The Start Or/End Or keywords can be inserted in the recipe by using the Edit menu, under the Insert Keyword/Or command.
This feature is typically used when a vessel should be inspected, cleaned, or when a longer QC test must be carried out at certain intervals.
Example:
To specify that every three batches a 'Clean' operation is to be carried out after the reaction, specify the recipe as follows:
Start Or
Series
React [...recipe text ...]
Series
React [...recipe text ...]
Series
React
[...recipe text ...]
Clean
[...recipe text ...]
End Or
Keywords: Series
End Or
Start Or
References: None |
Problem Statement: While putting a process into a production plan, can user specify the sequence of the batches to be simulated? | Solution: Yes, you can enter the sequence, but it has to be done manually.
When you create a production plan, you have the option of adding either processes or steps to the plan. A process in made up of one or more steps in a specified order. If a process is put into a production plan, you cannot control the sequence of batches to be simulated because the order is defined in the process. If you want to change the order of the steps in the production plan, enter the steps in the plan in the desired sequence rather than entering the process in the plan.
This is important since there are some cases where the sequence generated by Batch Plus is not the sequence desired. For example, in the case of the following process: Process 1 : A -> C
Step 1 : A + X -> B
Step 2 : B -> C + X (X is recycle to Step 1)
In the above example, if user specifies 2 batches for Process 1, the sequence generated by Batch Plus will be:
Step 1 - 1 batch
Step 1 - 1 batch
Step 2 - 1 batch
Step 2 - 1 batch
Which means the recycle of X from Step 2 to Step 1 will never take place.
Batch Plus assumes the step output intermediate is a bulk that will be transfered from plant site to plant site, so each step is produced as much as needed (specified) and transfered to produce next step. Because Batch Plus uses this assumption, the recycle is not considered.
So in this case, user will need to explicitly specify the steps and their order in the production plan data enty screen as below, instead of specifying the process:
Step 1 - 1 batch
Step 2 - 1 batch
Step 1 - 1 batch
Step 2 - 1 batch
Keywords: Production Plan, Process, Sequence
References: None |
Problem Statement: Having a logical device with transfer records configured and working, it is not possible to set up redundancy on it just by trying to change logical device’s properties. This | Solution: provides assistance on how to set up redundancy on these cases keeping all transfer records configurations.Solution
Even when it is possible to do all necessary changes to configure redundancy manually (which may include: adding task, modifying logical devices file, etc.
Aspentech's recommendation is to create a new logical device set up for redundancy and move the transfer recordsto the new logical device by changing the value of the IO_MAIN_TASK manually or with a query like:
Local OldTskName, NewTskName;
OldTskName = 'TSK_M_OLD'; --Change this for the TSK_M of old logical device
NewTskName = 'TSK_M_NEW'; --Change this for the TSK_M of new logical device
For (Select Name as MyTransferRecordName from IOGetDef where IO_MAIN_TASK = OldTskName) Do
--Set record processing off
Update IOGetDef Set IO_RECORD_PROCESSING = 'OFF'
where name = MyTransferRecordName;
--Set record unusable
Update IOGetDef Set Usable = False
where name = MyTransferRecordName;
--Change main tsk to use
Update IOGetDef Set IO_MAIN_TASK = NewTskName
where name = MyTransferRecordName;
--Set record back to usable
Update IOGetDef Set Usable = True
where name = MyTransferRecordName;
--Set record processing ON
Update IOGetDef Set IO_RECORD_PROCESSING = 'ON'
where name = MyTransferRecordName;
End
This query will change all IOGetDef (need to change this for other transfers records) transfer record from one logical to another keeping all current tags configuration. Since this represent a considerable big change on transfer records, it is convenient to run a CIM-IO clean restart process to recreate the scanner and store list so that all this changes can be written properly on those files.
Keywords: CIM-IO
Redundancy
References: None |
Problem Statement: Where are the arguments once found in the OPC Properties Utility? | Solution: OPC Properties is an obsolete utility although it may still be installed with some versions of Aspen Cim-IO for OPC. The OPC related arguments are found in the Cim-IO Interface Manager [CIM].
To adjust the arguments:
· Open the CIM
· In the tree view select OPC Interface
· Adjust the arguments as desired
· Click Save Configuration
Keywords:
References: None |
Problem Statement: Processing cost not shown correctly in Route Selection compared to Excel report. | Solution: The route selection block diagram process cost is calculated based on input, instead of like Excel report, on basis of 100kg of output intermediate.
Route Selection UI cost calculations are based on processing time and are not uniformly scaled as Excel report. Calculations in excel report are based on 100 kg of final product.
Attached document describe the details of these calculations
Keywords: route selection, cost, processing cost.
References: None |
Problem Statement: This knowledge base article describes how to open a SCM set and table in Microsoft Excel Spreadsheet, in a separate window. | Solution: 1. Opening a SCM set in a Microsoft Excel Spreadsheet using EXCELS Command
EXCELS Command:
The EXCELS Command opens a SCM set in a Microsoft Excel Spreadsheet. The Excel window will remain open if you close SCM.
Syntax:
EXCELS Setname | variable
Description:
Setname: The name of the set that you would like to open.
Variable: You can use &Variable or $Variable to store the name of the set that you would like to open.
Example:
EXCELS FAC
2. Opening a SCM table in a Microsoft Excel Spreadsheet using EXCELT Command
EXCELT Command:
The EXCELT Command opens a SCM table in a Microsoft Excel Spreadsheet. The Excel window will remain open if you close SCM.
Syntax:
EXCELT Tablename | variable
Description:
Tablename: The name of the set that you would like to open.
Variable: You can use &Variable or $Variable to store the name of the table that you would like to open.
Example:
EXCELT IDEMAND
Keywords: None
References: None |
Problem Statement: Cannot open Aspen SCM CAP's case Case File Open Failure due to the incompatibility of Aspen SCM CAP's version with Aspen SCM 2004.x versions. When this occurs, either of the following errors could appear when opening a CAP case:
1. Invalid case format
2. Case File Open Failure - Incorrect Case File Version | Solution: The invalid case format error will occur when the SCM_2004-2 CAP case is used with the Aspen SCM 2004.1 application (or earlier versions of Aspen SCM or MIMI). Incompatibility between the CAP's library and SCM application may also cause these error messages or prevent the case from opening. For example, the case will not open on MIMI 7.2.0930 because the DM CAP's libraries came from MIMI 8.0 version.
Please note that similar error messages will occur when the CAP's are not licensed.
Keywords: CAPs
Case
Versions
References: None |
Problem Statement: MIMIAS works on the local machine, but not when running in batch mode remotely. | Solution: Most likely, the cause of this problem is related to missing drive mappings or permissions. Things to check:
1. Check the batch script to see if it is calling any mapped network drive.
a. Double click on My Computer icon from your desktop and confirm existing mapped drive(s).
b. Select Map Network Drive to create a map drive connection between the two machines.
2. Make sure your userid has the correct permissions for those map drives.
a. Click on Start --> Settings --> Control Panel --> Administrative Tools.
b. Choose Services from the list of available icons.
c. Scroll through the list of Services until you see Task Scheduler and double-click.
d. Click on the Log On tab.
e. Review the permissions on this screen to make sure your userid has access to the mapped drive.
3. Contact your local IS support if you are having problem creating a map drive.
Keywords: interactive
non-interactively
remote
local machine
References: None |
Problem Statement: Is there is some change in the way p resolve works when a basis is supplied between versions 15 and 16 of Xpress? | Solution: If a basis is supplied it will be presolved when the matrix is presolved. If any presolve operation will invalidate the basis then that presolve operation will be rejected. So providing a basis will affect the final size of the presolved problem. This was the same in versions 15 and 16 but the presolve operations are different between the two versions.
Therefore, when using BARRIER for the LP solve (CXPRESS parameter ALGO), you should also UBAS (Use Basis from PreviousSolution) to NO because otherwise presolve can be badly affected, even though BARRIER doesn't use the basis.
Keywords: LP
GEN
BARR
OPT
References: None |
Problem Statement: Cannot refresh changes in a set automatically. One must close the set and reopen it to see the changes. For example,
1. open MAC set
2. Type mac = null on the mimi command line
3. close the mac set and reopen to see the changes - the set does not null automatically. | Solution: 1. Open MIMI5.0
2. Type switch 22 = on on the MIMI command line.
3. Click on the Options from the MIMI toolbar.
4. From the pull down menu choose Control.
5. Mimi Session Control Option dialogs opens
6. Make sure that number 22 is checked which is called switch 22.
7. Do the test example to see if it worked. a. Open the mac set by typing mac on mimi command line b. Type mac = null on the mimi command line
*See the magic works -- the set is automatically nulled.
Keywords: To change Switch 22, type this on the command line: SWITCH 22 = ON
References: None |
Problem Statement: PKTMP files build up in the temporary directory. Can the files be removed without incident? | Solution: Occasionally, pktmp files are found in the WINNT/System32 folder and the file type is ASPEN SCM CASE. Generally speaking these files can be deleted without any harm to Aspen SCM; however if the user should verify that the SLM does not point to the temp file before doing so. Below are the steps for verification on Windows XP:
1. Click on Start | Programs | Aspentech | Common Utilities | SLM Configuration Wizard
2. Once this opens, look for the box that asks Will you be connecting to an SLM server over the network? Check YES or NO as appropriate and click on the CONFIG button.
3. Scroll to the second half of the page.
4. Look for the path for License Source Directory. It should not end with the temp directory. If it does, do not delete the files. If the License Source Directory points somewhere other than temp, it is OK to delete the PKTMP files.
Key Words
PKTMP
License Source Directory
SLM Configuration Wizard
Keywords: None
References: None |
Problem Statement: What does the NumShiftsToKeepDeliveredOrders INI setting do? | Solution: When a confirmation record is picked up for a shipment that is delivered,
including shipments transferred to another group, the shipment inside the
Replenishment Planner now turns green and the status is updated to
?delivered?.
If you are using the NumShiftsToKeepDeliveredOrders INI setting, delivered
shipments will remain in the Replenishment planner until the order's shift is
no longer included in the value set by this ini. However, DQM will no longer
display orders that are already marked as delivered even though they will
remain in the replenishment planner.
Keywords: replenishment planner
References: None |
Problem Statement: How do I configure the DoFinalOptimization INI setting? | Solution: DoFinalOptimization =1 (Default)
The DoFinalOptimization setting is a client specific setting. If you are not familiar with this setting, it likely does not apply to you. The DoFinalOptimization setting allows you to increase the speed of optimization by allowing you to disable the final phase of the optimization process
Acceptable Values:
0 = Skips the final phase (improvement phase) of optimization
1 = Executes final phase (improvement phase) of optimization
Use the DoFinalOptimization setting if you want to increase the speed of the optimization process
Example
DoFinalOptimization=0
In this example, the final phase (improvement phase) of the optimization
process is disabled, improving the overall speed of the optimization
Process, but possibly forfeiting some financial benefits
Key words
Keywords: None
References: None |
Problem Statement: Why does the I sometimes see values populated in the Other Additions field? | Solution: If you have the Load Confirmation Service running and are receiving Confirmations throughout the day, it is possible if you process an Inventory update for these Confirmed Orders to be sent to the Delivered Loads log. If this occurs, the system will display the volume of the confirmed loads in the Other Additions field to complete the reconciliation of the previous day's Starting Inventory with the new Inventory for the following day.
Keywords: Other Additions
References: None |
Problem Statement: How do I pre-assign work in the optimizer? | Solution: Once shipments have been assigned to transports, the user can lock a shipment or several shipments on a transport if desired. Pre-Assigning enables the user to keep a desirable work schedule on one transport and re-optimize the rest of the work. Pre-Assigning also provides organized software for addressing delivery restrictions. The Resource Scheduling Optimization enables the user to lock a specific shipment on a transport or lock the transport itself, which in turn locks all the shipments on a transport. To lock a specific shipment on a transport:
To pre-assign on order follow these steps.
Select the shipment that is on a transport by clicking on it. Right mouse click on the highlighted shipment and select the pre-assign option. A 'P' appears next to the customer number indicating that the shipment is pre- assigned. Follow the same steps to remove the pre-assignment.
To pre-assign a whole truck follow these steps.
Highlight the transport and with the right mouse button and click on the transport. A 'P' will appear next to all of the shipments assigned to that transport. To unlock the assignment, highlight the transport and with the right mouse button click on it. The pre-assignment indicator, 'P', will be removed for all shipments on that transport.
Keywords: None
References: None |
Problem Statement: How can I track data changes? | Solution: Aspen Retail has several ways to track the data changes. Below is a list and a description.
Order Audit Log:
The Audit Log tracks all changes that are made to a shipment from the time the shipment is created to the time the shipment is considered delivered. The Audit Log captures the user information, the date and time, the origin, and the modifications that are made to the shipment. The user also has a choice of viewing the Audit Log or printing the Audit Log. The Audit Log can be accessed from the main Aspen Retail dialog box, the Replenishment Planner, or by right clicking on a shipment in Replenishment Planner. There is also an Audit Log Report that can be printed for a particular shipment.
RSO Audit Report:
The RSO Audit Report captures warnings and critical error messages generated in RSO when users manually schedule orders on to transports and do not heed warning messages.
Post Optimization Error Report:
The Post Optimization Error Report can be generated to view shipments that have been delivered outside of their delivery window. Shipment weights that exceeded the transport maximum weight. Product - Product restrictions on the same transport Product incompatibility with the last product contained in compartment.
As for ASR, if a user is not taking appropriate measures to reconcile Sales and Inventory data and chooses to override exceptions instead of investigating the cause of that exception, then this problem can retraced from both the History List and Info Update log .
The above mentioned utilities can serve as powerful training aides when used properly.
Keywords: Order audit log
Info Update log
RSO audit report
History List
Post Optimization Error Report
References: None |
Problem Statement: What does the error message 'invalid idcode' mean when importing through the optimizer? | Solution: The Manual Import through the optimizer uses the 'idcode' in the services ini file. If a file cannot be located the user will receive the error message. To correct the message, copy a valid services.ini file onto each user's directory. The error message will be resolved.
Keywords: Manual Import
Error Code
References: None |
Problem Statement: The 32318 error in an Aspen 'Get Transfer' record may be seen when:
Using the Aspen Cim-IO for Foxboro FOXAPI Interface
The Scan Rate of the Transfer record is larger than 2 hours. | Solution: The installation of the interface includes a file:
%CIMIOROOT%\io\cio_fox_api\cimio_foxia_config.dat
In that file there should be an entry called 'RECENTLY', distributed with a 'default' value of 120
This defines the number of minutes after which Cim-IO closes the sets.
The result of this default setting means that any scan rate longer than 120 minutes could result in the 32318 error.
The reSolution is to increase the value of 'Recently' to a value larger than the number of minutes used for the scan frequency.
The Cim-IO Interface needs to be restarted after making this change.
Keywords:
References: None |
Problem Statement: There are times when troubleshooting a problem requires that the debug function of the interface be enabled. The CIM-IO for Bailey SemAPI User's Manual describes the method for enabling the debug flag, but it stops short of detailing the various debug levels that can be applied. | Solution: The following debug levels can be enabled for the DLGP and/or the DIOP processes:
0 = OFF (this is the default when the debug flag is not used) 1 = ERROR
2 = WARNING
3 = LOW
4 = MED
5 = HIGH
6 = DEBUG
16 = debug level for detailed logging of unsolicited processing.
Note: Log level DEBUG should not be used unless you are getting crashes because it logs everything that the program does and could quickly use all available disk space.
Keywords: debug
References: None |
Problem Statement: Some users have multiple OPC servers on one machine, but do not wish to have CIMIO for OPC use all of them. Since CIMIO for OPC automatically starts all OPC servers (and DLGPs for each) when it is started, it is necessary to specify any OPC servers to exclude from starting. The following | Solution: describes how to exclude specific OPC servers from being started, with information on changing service names if necessary.Solution
When CIMIO for OPC is started, it detects any OPC servers on that machine, starts them and also starts the DLGP process (asyncdlgp.exe) for each one. At the same time it automatically creates a logical device name and DLGP service name for each OPC server and places it in the cimio_logical_devices.def file, as well as placing an entry for the DLGPservice name in the NT services file (if these entries didn't already exist). If you do not want to start a particular OPC server and DLGP for that server, simply enter the DLGP service name (which can be found in the cimio_logical_devices.def file) into the excludedservices.txt file. This file is located in the directory: Aspentech | InfoPlus.21 | db21 | io | cio_opc_api. The next time CIMIO for OPC is started, it will first check for any service names specified in this file and it will not attempt to start them.
Since CIMIO for OPC also creates the logical device name and DLGP service name for all OPC servers it finds, often the same service names are defined for multiple OPC servers. (DLGP service names are limited to 15 characters, so usually the DLGP service name of the OPC servers is a truncated version of the program id, therefore duplicating the name.) If an OPC server that needs to be excluded from startup shares a DLGP service name with another that SHOULD be started, it is necessary to change the service name of one of them (preferably the one that shouldn't be started) in the servicenames.txt file. (This file is also located in the directory: Aspentech | InfoPlus.21 | db21 | io | cio_opc_api.) In servicenames.txt, create an entry where the program id for the desired OPC server is listed, followed by a new DLGP service name (make sure this name doesn't exceed 15 characters). Example:
ABBMAESTRONT.OPCServer.1 CIOABBMAESTRO1
Now that the service name has been changed for one of the OPC servers, the new name can be specified in the excludedservices.txt file. Example:
CIOABBMAESTRO1
The cimio_msg.log file will indicate, during CIM-IO for OPC startup, which OPC servers it finds. An example entry:
Apr 01 12:58:49 2004, Logged by CIMIOOPCMGR on < nodename> : Found a 1.0 server: ABBMAESTRONT.OPCServer.1
The next time CIMIO for OPC is started, it will not start the OPC server identified by the DLGP service name of CIOABBMAESTRO1.
After the modifications to the ExcludedServices.txt file, the startup of CIM-IO for OPC will show something like the following in the cimio_msg.log file:
CIOABBMAESTRO1 is Excluded from launching
Note: Version 2.0 of CIMIO for OPC did not use the servicenames.txt file, so thisSolution only applies to versions 2.01 and higher. Information on excluding services and changing service names is also contained in the CIMIO for OPC Interface User's Manual.
Keywords: progid
tcp/ip service name
asyncdlgp.exe
asyncdlgp
References: None |
Problem Statement: What can cause read/write or connection timeouts on Aspen Cim-IO for OPC connections through a Matrikon OPC Tunneler. | Solution: A new setting Autotuninglevel was introduced in windows 7, and Windows Server 2008 that optimizes file transfer and Internet but can cause issues with other TCP communication.
To resolve timeout issues; Matrikon OPC Tunneller help recommends setting the Autotuninglevel=highlyrestricted on the system running the Matrikon OPC Tunneller.
There are also a couple Microsoft articles that discuss this setting. [kb/947239, and kb/951037]
Here are some useful commands:
To inspect the current system settings, from an admin command window. run netsh int tcp show global store=active. The command produces and output similar to the following.
TCP Global Parameters
Keywords: None
References: None |
Problem Statement: On the DCOM Config > properties > location tab Run application on this computer is grayed out. | Solution: On Windows 64bit OS's the default 64bit Component Services, DCOM Config may not display all check boxes properly. TheSolution to this behavior is to run the 32bit DCOMCNFG with the following command.
Start -> Run -> mmc comexp.msc /32
Keywords: grey
greyed out
References: None |
Problem Statement: The term Facility=77 is seen in output from the Aspen Cim-IO test api, in the Aspen Cim-IO log files and in the IO_LAST_STATUS_DESC field of transfer records when viewed through the Aspen InfoPlus.21 Administrator. See below for an example.
This knowledge base article explains what Facility=77 means. | Solution: Each Aspen Cim-IO interface is assigned a two digit facility code which is used to identify the interface on a programmatic level. The facility number assigned to the Aspen Cim-IO for OPC interface is 77. This facility code is also used as the first two digits of Aspen Cim-IO interface error codes. Therefore, by examining the first two digits of any Aspen Cim-IO error code, we can tell which Aspen Cim-IO interface generated the error.
The facility code for each Aspen Cim-IO interface can be found by viewing the *.def file for the respective interface, which is located here:
<drive>:\Program Files\AspenTech\CIM-IO\etc
Keywords: Troubleshoot
general
definition
References: None |
Problem Statement: When Changing a Forecasted Customer to a Manual Customer orders are not automatically deleted | Solution: If a dispatcher is changing a Forecasted Customer to a Manual Customer, all previously Forecast Orders will still be pending orders for this customer. If the Dispatcher or Customer does not want these Forecasted Orders to be delivered, the Dispatcher must go into Replenishment Planner or Optimizer to have these removed.
Alternatively, the Dispatcher could also simply inform the Station Owner that these are still pending and they have the option of modifying them through the IVR or eChain if these technologies are being employed.
Keywords: Forecasting
Manual customers
Forecasted Customer, Manual Customer, Forecasted Orders
References: None |
Problem Statement: Why is Shift Work Planner extremely slow when opening? | Solution: There is an ini setting in the Customize.ini INI file that has a default value of 62. The INI setting is 'ShiftworkPlannerForecast Numberofshifts'. Changing this value to the the actual number of shifts ahead you would like the shift work planner to forecast will speed up the process of opening the shift work planner.
Keywords: Customize INI
ShiftworkPlannerForecastNumberofshifts
Shift Work Planner
References: None |
Problem Statement: What is the flow of sales and inventory data prior to reaching the TPS tables? | Solution: Although not every Customer is using every table depending on their installation, the complete path would be as follows:
1. Hourly Sales as deposited by Customer Interface are deposited into TCIF_METEREDSALES table
2. Individual Tank Inventories are deposited by Customer Interface into TCIF_TIM table.
3. Aspen Metered Sales Service picks up the hourly sales data totals these into a 24-hours sales record and posts it to the TCIF_SIIMP table
4. Aspen TIM Import Service picks up the Tank inventories and totals them by product to import into the TCIF_SIIMP table. This service also takes the sales and inventories by tank and makes updates into the TPS_TIM table to accommodate Tank Sales Percentages.
5. Aspen SalesImport Service picks up the Sales and Inventories from TCIF_SIIMP and imports them into different TPS tables depending on the type of Sales or Inventory Update being sent in.
Keywords: Sales and Inventory Updates
References: None |
Problem Statement: When accessing .mode and other enumerated points on a Honeywell APP node they show up as bad tag. | Solution: Append .internal to the end of the tag name.
Note: You should ONLY add the .internal extension to the IO_TAGNAME in the GET record for the MODE tags.
Keywords: Appnode, OPC, Honeywell
References: None |
Problem Statement: You might receive the following error in the CIM-IO Test API or the IO_LAST_STATUS_DESC field of a transfer record:
49217, Could Not Establish Point In ICI | Solution: This is a not a CIM-IO or CIM-IO for Bailey semAPI problem. This is a problem within the Bailey system. CIM-IO is unable to establish a connection with this point. Verify that the point exists within Bailey.
Keywords:
References: None |
Problem Statement: Some tags do not read the correct value when the AspenTech Cim-IO Test Utility (cimio_t_api.exe) GET test (option 9) is performed. The driver status returned for the request is 49229. This driver status has the following definition:
PS_BAILEY_INCORRECT_CONTROL_VALS,49229,Controller setpoint may not be changed | Solution: The control station needs to be set to AUTO. The problem is with the DCS configuration, as the CIM-IO interface cannot write to the control block unless it's configured in auto mode.
Keywords: None
References: None |
Problem Statement: The following errors are displayed during installation.
Setup could not remove the AutostartCIMIO service Error code: -2 Last Error 1060
Setup failed to create AutostartCIMIO service Error code -2 Last error 1057 | Solution: In this case an invalid account was listed as the startup account for Cim-IO Manager. Changing the startup account to the system account allowed the installation to complete.
Keywords: None
References: None |
Problem Statement: SCM is Isolated error message appears after upgrading Aspen SCM. | Solution: Later versions of Distributed Aspen SCM has isolation turn on by default. Therefore, you must manually turn off this feature. You can do this by running the ISOLATION OFF command from Aspen SCM's command line. For more details, consult the Distributed Aspen SCM documentation.
Keywords: None
References: None |
Problem Statement: When Aspen Cim-IO for OPC is started as a service it will not connect to a Intellution fix OPC server called FIX32. If it is started interactively then it works fine.
The register name of the OPC server is Intellution.OPCEDA.1
The Intellution iFIX is another newer product called Intellutionfix.OPCEDA and it works fine.
As a test try to start the asyncdlgp interface from the command line. (The nodename parameter can be left out if the OPC server is local.) This will work if FIX is a service and if FIX is started interactively.
%CIMIOROOT%\io\cio_opc_api\asyncdlgp -tcpserviceCIOINTELLUTIONO-opcserverIntellution.OPCEDA.1-nodename FR600 | Solution: Fix needs to be started as a service and the fix32 directory has to be in the system path for this to work.
Keywords: None
References: None |
Problem Statement: Using InfoPlus.21 to collect data from a Modicon Programmable Logic Controller (PLC). An OPC server called KEPServerEX (from Kepware) communicates with the PLC. CIM-IO server and the CIMIO-to-OPC interface are installed on the same Windows NT box that is running the OPC server. It appears that the CIM-IO client (on the IP.21 server box) is communicating with the CIM-IO server, but that CIM-IO server is unable to connect to the OPC server. | Solution: The account configured for starting the OPC Server did not have any permission specified. For this reason, the OPC client was not able to access the OPC Server because the OPC Server wasn't able to start successfully, and therefore generates the following error in the cimio_msg.log file:
Could not create server, hresult is -2147024891 or a similar error with a different number: Could not create server, hresult is -2146959355.
These two errors have the same meaning: Access Denied.
This problem can be resolved by setting permission in the DCOM Configuration area. To set DCOM Permissions for AspenTech OPC Client:
Run DCOMCNFG.EXE
1. On the Default Properties tab:
Enable Distributed COM on this computer : Checked
Default Authentication Level : None
Default Impersonation Level: Anonymous
Provide additional security: Not Checked
Then click Applications tab and double click OPC Server
2. Properties for OPC Server:
On the Security tab:
Use custom access permissions: Everyone -> Allow Access
Interactive -> Allow Access
Use custom launch permissions: Everyone -> Allow Start
Interactive -> Allow Start
SYSTEM -> Allow Start
On the Identity tab:
Select 'Interactive User'
Note: Dcomcnfg.exe resides in C:\\Winnt\System32
If the same error message is returned by other OPC servers besides KEPServerEX, then check to make sure that the CimIO to OPC Interface service gets started with a user account which does have sufficient DCOM permissions.
Additionally, in some cases, starting the CIMIO to OPC service from the system account will fix the problem.
Also if the same error message is returned when trying to launch an OPC Server with a GUI (a service that interacts with a desktop), then the following needs to be done:
In Start/Settings/Control Panel/Services , double click the Cimio to OPC Interface service and check the box : Allow Service to Interact with Desktop under the Local System account of the LogOn As area. Restart the service. After restarting the CIMIO-to-OPC Interface service, the OPC Server should have no problem launching. If it doesn't launch, please contact our Technical Support department at the location near you.
Keywords: -2147024891
-2146959355
-2147221005
References: None |
Problem Statement: The Cim-IO for OPC interface supports the use of an access path to locate a point on the OPC server. This knowledge base article describes some naming conventions that are used to specify the access path + tag name. | Solution: Different OPC servers use different naming conventions for the access path + tag name, so there is not a single naming convention which will work for every OPC server. Some examples of access paths + tag names that various OPC servers use are:
[access_path]tagname
access_path.tagname
access_path/tagname
This is not a complete list, rather, it is what we've observed from working with various OPC servers. If one of these conventions does not work with your OPC server then check with the OPC server vendor to find out how the access path needs to be specified when communicating with your specific OPC server.
Keywords:
References: None |
Problem Statement: When I try to uninstall Aspen SCM, I get the error message unable to find uninst.isu. File may be missing or corrupt. | Solution: This problem is caused by the file uninst.isu being accidentally deleted or corrupted due to a computer crash or abend. Also, it has been deleted on occasion by users trying to free space on their hard drives by deleting files that they did not think was necessary.
TheSolution for this problem is to:
1. Install SCM on top of the old installation. This is the only time you should ever install SCM on top of a previous installation. Be sure that the installation path is the same as the previous installation. This will ensure that all of the registry settings and files that may have gotten corrupted or gone missing will be restored correctly and match the previous installation of SCM.
2. Reboot the computer but do not start SCM.
3. Rename your copy of the file \Mimi\uninst.isu to uninst.old.
4. Copy uninst.isu from a working machine to your machine and place it in the same directory as uninst.old.
5. Uninstall using the uninstall option from the Aspen SCM menu.
Keywords: None
References: None |
Problem Statement: I am trying to import an equipment from another project but I cannot find it listed under source equipment. | Solution: The Import Equipment window will default to the Batch Plus Equipment Catalog. To access equipment from the other project that you have selected, you need to select it from the dropdown list as shown in the screenshot. Note that the dropdown list will include all the facilities so you need to select the appropriate one.
Keywords: import equipment, facility
References: None |
Problem Statement: Honeywell Appnode with Cimio to OPC server. What order to startup the services? | Solution: Honeywell Appnode Service Startup Order
Description: Honeywell Appnode with Cimio to OPC server. There are 3 services that must start in the correct order:
1. First, TPSAdmin must startup completely.
2. Cimio to OPC and Cimio Manager must start after TPSAdmin is ready.
Problem: The TPSAdmin service starts up at boot and immediately tries to do a Netlogon. It cannot find a domain controller at this time and fails. Cim-IO to OPC and Cim-IO Manager will startup, but no data is passed because the TPSAdmin service is not working. This can be seen in the event viewer and the TPS Status auxiliary display. The affect is that the appnode will not boot properly and come back online without human intervention.Solution This problem can be corrected by insuring the TPSAdmin gets its logon request serviced before the Cim-IO services try to start. This can be accomplished by setting a delay on the Netlogon service so that it will keep trying until the request from TPSAdmin is serviced. Next, for the Cim-IO to OPC and Cim-IO Manager services, create a dependency on the TPSAdmin service so that they will not start until TPSAdmin is completely up and running.
Procedure:
Login to the Appnode as the Local Administrator (Not the TPSAdministrator). Using Regedt32 (or regedit) go to HKEY_LocalMachine|System|CurrentControlSet|Services|Netlogon|Parameters
(you can view the screen grab for this section from the Appnode Service Startup Documentation attached)
Click Edit|Add Value. Enter the Value Name of ExpectedDialupDelay with a datatype of REG_DWORD. Click OK and the another dialog box will pop up.
(you can view the screen grab for this section from the Appnode Service Startup Documentation attached)
Enter the number of seconds for the delay, ie. 30. Don't forget to click the Decimal radio button. Click OK to finish.
(you can view the screen grab for this section from the Appnode Service Startup Documentation attached)
Next, make the Cim-IO services depend on TPSAdmin starting up. Scroll down to the AutostartCIMIO service. It already has a dependency on LanmanServer. In the right pane, click on DependOnService and click Edit|Multi-String. Add TPSAdmin to the existing list.
Note: When creating dependencies, you MUST use the service name as it appears in this list in the registry.
(you can view the screen grab for this section from the Appnode Service Startup Documentation attached)
Scroll down to and highlight the zzCIMIOOPCMGR service. On this one, the DependOnService value must first be created. Click Edit|Add Value from the menu. The value name is DependOnService, the data type is REG_MULTI_SZ, and the data is TPSAdmin.
(you can view the screen grab for this section from the Appnode Service Startup Documentation attached)
NOTE: You can find supporting documentation in the Microsoft Knowlege Base, key word DependOnService.
Also, this is additional information forSolution ID 103189 Tips and Tricks for Honeywell App Nodes Section II-C Starting and Stopping the Cimio Server.
Credit: Thanks to Lynn Broomfield with Valero in Corpus Christi, TX for the information.
Keywords: Cimio Manager
TPSAdmin
Appnode
References: None |
Problem Statement: Error message located in the CIMIO message log file on the CIMIO server side: not available for this send. In the transfer records, the error message is Wait for Async. The cause of the error message is that the CIMIO server cannot determine where to send the data. The configuration path from the CIMIO server to the CIMIO client (InfoPlus.21 server) has been modified. Also, the Forward process will not stay running because the process dies after 2-3 secs. | Solution: The cause of the problem typically has to do with the node name being changed from the fully qualified nodename to the short node name. The new short node name will not be recognized by the CIMIO Forward process because in the CIMIO configuration files, the node name still refers to the fully qualified node name. This node name mismatch is the cause of the error message in the CIMIO server message log file.
Change the node name from the fully qualified node name to the short node name in the logical devices.def file and in the device record.
FollowSolution 103176 to remove wait for async error mssage if it is still present in the transfer records.
Keywords: node name
fully qualified
available
References: None |
Problem Statement: After installing the CIM-IO for OPC Interface onto a Honeywell APP node running an Hci.TPNServer OPC Server, starting the interface gives the following error in the CIMIO_MSG.LOG file:
Could not create server Hci.TPNServer on Node (null) on try number 1, error is = No such interface supported
This error will be repeated several times and the interface will not successfully connect to the OPC Server. | Solution: According to Honeywell Support, the error is caused when an OPC Client which uses opcenum as part of making the DCOM connection, is the first OPC client to connect with the OPC Server. CIM-IO for OPC does utilize opcenum when establishing the DCOM connection.
TheSolution offered by Honeywell Support suggests using a utility named opctest.exe to connect to the OPC Server.
Go to www.opcconnect.com, and under free stuff, select the Rockwell client using the link provided. This will take you to Rockwell's site, where you can download Rockwell's free RSI Sample OPC Client, opctest.exe (300 kb executable).
Use the opctest.exe utility to connect to Honeywell's OPC server - Hci.TPNServer. Set up a group and add an item. It should immediately begin updating the tag with current information from the DCS.
At this point, the CIM-IO for OPC interface should be able to connect and collect data from the Hci.TPNServer.
Running opctest.exe (actually making a connection without using opcenum and starting the scan of one tag) forces Hci.TPNServer, Honeywell's OPC server, to do some internal initializations that didn't occur during installation for whatever reason. After those initializations have occurred, Honeywell's OPC server will then work with any third party client.
Keywords: opcenum
opctest.exe
References: None |
Problem Statement: CIMIO_T_API and IP.21 are not showing updated values from FOXAPI interface. FOXIA DCS interface can show these value changes.
These values are typically very small e.g. 0.04151 and 0.03241.
Other environment properties are:
- IP.21 and CIMIO_T_API do not show any collection or CIMIO errors.
- IP.21 IoGetDef or IoGetHistDef are not configured to utilize deadband features.
- IP.21 tag is not configured to with DC Significance.
- Bigger tag values do not exhibit this behavior.
- In CIMIO_FOXIA_CONFIG.DAT, RDELTA has a default value of 0.01. | Solution: Adjust RDELTA value to match the significance required. For example, if you want to capture the changing tag values from 0.031x to 0.032x, RDELTA needs to have a value of 0.001. If you want to capture the changing tag value from 0.03x to 0.04x, then RDELTA needs to have a value of 0.01.
After changing any values in CIMIO_FOXIA_CONFIG.DAT, the foxapi interface needs to be restarted.
Keywords: FOXIA
References: None |
Problem Statement: Aspen Cim-IO for OPC may return the error message
?Declare Failed - Invalid Tag?
in the IO_DECLARE_STATUS field of the Unsolicited transfer record when connecting to a Metso MaxDNA OPC server. For the tags which are declared there is no interruption in getting the data, but for the tags which didn't declare no data is imported. | Solution: The problem is due to a limitation of 2000 point subscriptions for the Metso MaxDNA OPC server. See the following link for further information about this limitation with the Metso MaxDNA OPC server.
http://www.metsoservices.com/support/archive/DocLibrary/Manuals/OPC/OPC_Ch01_Introduction.pdf
Configuring OPC-Getting Started（Page 7）
Symptoms that will points to this limitation:
1. OPC server is Metso MaxDNA
2. The number of tags that were declared will be constant, the rest will fail i.e. 'Declare Failed' status.
3. CIMIO_T_API on both the Aspen InfoPlus.21 and CIM-IO servers; all show 'Bad Tag'.
4. For the same tags that gave 'Bad Tag' status in (3):
o Stop Device processing (IO_DEVICE_PROCESSING).
o Restart the related TSK_A, TSK_M and TSK_U tasks.
o Redo the CIMIO_T_API on both the Aspen InfoPlus.21 and CIM-IO servers.
o This should now show 'Good' status.
5. Using the OPC Server utility, you should be able to identify the number of simultaneous subscriptions.
o When we closed TestAPI, the number of simultaneous subscriptions went to x-1.
o We also disconnected the OPC client which also brought the number down by 1.
o Turn on device processing(IO_DEVICE_PROCESSING) and restart the CIM-IO client tasks, the subscription numbers will go up.
Keyword:
Metso MaxDNA
Declare Failed
Invalid Tag
Keywords: None
References: None |
Problem Statement: What do commands COLLECT and LINK do? And, what is the automatic linking feature in MIMI/E? | Solution: You should know that performing a COLLECT and LINK every time you make a change to a MIMI/E rule is at best unnecessary and could actually cause problems in some applications.
COLLECT looks at every set in the model and sees if it contains IF statements in the CODE portion. If it does, it puts the name of the set in the CODE part of the RULES set. Sounds innocent. However, if you are testing and debugging rules, you may want to rename a rule set temporarily and test a variation on it. The COLLECT command would put both rules in the RULES set and the predicates would be evaluated in sequence based on their position in the RULES set. This could make debugging very hard.
LINK is normally not required, as automatic linking is by default set to YES in table CNTLE. This means that MIMI will first execute LINK every time you execute a rule with >.
MIMI/E was written because macros were too slow. Macros interpret all the data and lookup tables, sets and codes each time a command is executed in a macro. With rules, instead, the table, set and code references are resolved in a pre-compile step we call LINK. Therefore, you must beware of the following things, which will cause a rule to fail:
Changing the relative location of a named code in a set by rebuilding the set dynamically in the rule.
Changing the relative location in the catalog of a table or set by deleting a table or set above the named table or set in the catalog.
Changing the relative location in the catalog of a table or set by using the POSITION command. Also using any hard coded references to TCHOSEN and $VIEW is a very dangerous practice.
Keywords: COLLECT
LINK
AUTOMATIC LINKING
POSITION COMMAND
References: None |
Problem Statement: User configured the Cim-IO for OPC system by using the OPCProperties and related programs, not using the I/O Wizard in the Aspen IP.21 Administrator, and when trying to start the Cim-IO for OPC Interface, CIM-IO Manager service is not starting, and produces an error like:
Could not start the CIM-IO for OPC Interface Manager service on Local Computer
Error 1058: The specified service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
user confirmed that the account used to start the service has Administrator privileges on the system.
Tried changing the account for the CIM-IO for OPC Interface Manage service to use a System Account but received the same error. | Solution: Since the customer opted to configure the Cim-IO for OPC system by using the OPCProperties and related programs it's possible the service did not get installed correctly. Un-installing and re-installing the service may resolve the problem.
To do this:
Open a CMD window and go to the C:\Program Files\AspenTech\Cim-IO\io\cio_opc_api folder, and issue the command:
removeService
A message ERROR: could not delete registry key., confirms that the service was not properly installed.
Reboot the system, and then open a CMD window and go to the C:\Program Files\AspenTech\Cim-IO\io\cio_opc_api folder, and issue the command:
InstallService C:\Program Files\AspenTech\Cim-IO\io\cio_opc_api\Manager.exe
The service starts fine this time.
Keywords: None
References: None |
Problem Statement: OPCPROPERTIES failed to add server with error message : Run-time error '70'; Permission denied | Solution: Execute OPCPROPERTIES.EXE as administrator
Keywords: OPCPROPERTIES
Run-time error '70'
References: None |
Problem Statement: Is it possible to configure two DLGPs for connection to the same OPC server?
Yes, it's possible to start two AsyncDlgp.exe processes that connect to the same OPC Server. See the steps below. | Solution: First, configure two service names in the services file, each with a unique port number, eg.
CIOPROCESSXOPC1 12345/tcp
CIOPROCESSXOPC2 12346/tcp
Next, in the servicenames.txt file, insert the OPC server name and the DLGP service names:
ProcessX.OPC.Simulation.1
CIOPROCESSXOPC1
ProcessX.OPC.Simulation.1
CIOPROCESSXOPC2
Now, in the cimio_autostart.bat file, configure the startup of the asyncdlgp processes using the following commands:
Start/b/min %cimiorootq%\io\cio_opc_api\AsyncDlgp.exe -tcpserviceCIOPROCESSXOPC1 -opcserverProcessX.OPC.Simulation.1 Start/b/min %cimiorootq%\io\cio_opc_api\AsyncDlgp.exe -tcpserviceCIOPROCESSXOPC2 -opcserverProcessX.OPC.Simulation.1
Replace CIOPROCESSXOPC1 and CIOPROCESSXOPC2 with your service names, and replace ProcessX.OPC.Simulation.1 with your OPC server name.
Next, disable the CIMIO for OPC interface service, since the interface processes will now be starting up via the CIM-IO Manager service.
Finally, stop and restart the CIMIO Manager service, and check that two AsyncDlgp.exe processes are started up successfully. Also check the cimio_msg.log file to ensure that there are no errors.
Keywords: duplicate
OPC
DLGP
asyndlgp
References: None |
Problem Statement: How to start and stop the Cim-IO devices with Aspen Cim-IO Manager Service using the cimio_autostart.bat and cimio_autostop.bat files (without using the I/O wizard in Aspen Infoplus.21 Administrator or the Aspen Cim-IO for OPC Interface service)?
Note: Please note that this | Solution: does not apply when the Cim-IO devices are created using I/O wizard with start up at boot option selected as the Cim-IO manager service automatically start the devices upon restart without need to edit the bat files.Solution
Start the Aspen Cim-IO for OPC Interface
Edit the cimio_autostart.bat file, which by default is located at C:\Program Files\AspenTech\CIM-IO\commands, add a line using the following syntax :
START /B/MIN C:\Progra~1\Aspentech\CIM-IO\io\cio_opc_api\asyncdlgp.exe -tcpservice<DLGP servicename>-opcserver<OPC Server name>-nodename<OPC Server node>
where <DLGP service_name> is the TCP/IP service name of the DLGP used for the Cim-IO device (specified in cimio_logical_devices.def and in the systems services file) and <OPC Server name> is the full name of the OPC Server being connected to.
The nodename parameter is only required when you connect to a remote OPC Server. If the Cim-IO software and OPC Server reside on the same node it can be omitted.
If you want to use the Cim-IO for OPC Automatic Failover (not to be confused with Cim-IO redundancy) you can add the parameter: -alternatenodename<alternate OPC Server node> to specify the node of the failover OPC Server.
NOTE: There are no blanks between the different parameters.
Below is an example of how the cimio_autostart.bat file looks like for a device with DLGP Service name CIOOPCDLGP when its connecting to a Matrikon OPC server on node OPCServ1
START /B/MIN C:\Progra~1\Aspentech\CIM-IO\io\cio_opc_api\asyncdlgp.exe -tcpserviceCIOOPCDLGP-opcserverMatrikon.OPC.Simulation.1-nodenameOPCServ1
Stop the Aspen Cim-IO for OPC Interface
Edit the cimio_autostop.bat file, which by default located at C:\Program Files\AspenTech\CIM-IO\commands, add a line using the following syntax:
START /B/MIN C:\Progra~1\Aspentech\Cim-io\code\cimio_shutdown.exe <Cimio_Logical_Device_Name>
where <Cimio_Logical_Device_Name> is Cim-IO device name, specified in the cimio_logical_devices.def file.
Example:
START /B/MIN C:\Progra~1\Aspentech\CIM-IO\code\cimio_shutdown.exe CIOOPC
Note: When Cim-IO server is installed on a 64-bit Operating system please note that the executables and bat files will be located on C:\Program Files (x86)\AspenTech\CIM-IO. In that case, make sure you change the path in the above mentioned syntax to point it to C:\Program Files (x86)....\ instead of C:\Program Files...\
Key Words
Cim-IO Auto start
Batch files
Keywords: None
References: None |
Problem Statement: With the release of CIM-IO for OPC v2.5, the interface is now capable of connecting to another OPC server with the same name but residing on an alternate node in case the connection to the primary node fails.
With this feature configured, it would seem likely that a message would be logged to the CIMIO_MSG.LOG file indicating when a switch over has taken place. At this time however, no indication is given in the CIMIO_MSG.LOG file when a failover occurs. | Solution: The v3.0 release of CIM-IO for OPC will create entries in the CIMIO_MSG.LOG file regarding fail over.
Keywords:
References: None |
Problem Statement: This knowledge base article provides a correlation table between the compatible versions of Aspen Cim-IO for OPC, the OPC specification and the required versions of Aspen Cim-IO Core. | Solution: This table lists 3 items.
1. Version of Aspen Cim-IO for OPC interface.
2. Version of the OPC specification. The OPC foundation (www.opcfoundation.org) has laid out various standards regarding OPC connectivity. Moreover, different OPC servers conform to different versions of the OPC specification. In order for Aspen Cim-IO for OPC to successfully communicate with a particular OPC server, a version of the Aspen Cim-IO for OPC interface must be used which complies with the same OPC standard as the OPC server.
3. Version of Aspen Cim-IO Core. The version of Aspen Cim-IO Core listed in this table is required to use the stated version of the Aspen Cim-IO for OPC interface.
Cim-IO for OPC
OPC Specification
Cim-IO Core
1.x
1.0A
Any
2.0 - 2.1.0
2.0.5 & 1.0A
4.9 or later
2.1.1 up to (but not including) v.3.x
2.0.5 & 1.0A
5.0 or later
3.x
1.0A, 2.0.5 & 3.0
6.0.1 or later
Keywords: Matrix
Chart
requirement
References: None |
Problem Statement: 77025 Failed to Connect Sink, the Dadvise Method Failed error
HRESULT Code -2147220990
?E???I?G???[???b?Z?[?W???-?????AHitachi EX7000 OPC server ???IDCOM?U`??EZ??s???e?B | Solution: HRESULT Code -2147220990 ?I DCOM Callback failure ???O?!???A???U???B
CIMIO for OPC(asyncdlgp.,exe) ???i?????A???e?}?V?????E?E???I???[?U?A?J?E???g???i?????U???B
user name: ex
password: admin
User Group: Administrators
???I???[?U?A?J?E???g?IHitachi EX7000 OPC?T?[?o??OPC?T?[?o?v???Z?X?I?i???p?EZg?p???e?A???e?a?I?????B
Keywords: Hitachi
EX7000
77025
Dadvise
-2147220990
JP-
References: None |
Problem Statement: Are there any utilities for diagnosing OPC connection issues? | Solution: OPC Rescue is a utility that is available from the OPC Training Institute that allows users to diagnose OPC communication and security problems and repair them if needed.
The free version of the utility can diagnose communication problems, provide DCOM settings, run a security audit, and diagnosis security issues. In addition to these capabilities, the full version of OPC Rescue can repair communication and security problems. For complete details on this utility go to the OPC Rescue site using this link. OPC Rescue
Keywords: cimio for opc
dcom
aspen.infoplus21_da.1
References: None |
Problem Statement: This knowledge base article describes the reason why the Aspen Cim-IO for OPC interface can attempt to connect to the Matrikon OPC Logging Delegator even though the Matrikon OPC Logging Delegator has not been installed. When this occurs, the following message will be logged in the cimio_msg.log on the Aspen Cim-IO server.
Could not create server Matrikon.OPC.LoggingDelegator.1 on Node (null) on try number 1, error is = Invalid class string | Solution: The Aspen Cim-IO for OPC interface will attempt to connect to this OPC server,
Matrikon.OPC.LoggingDelegator.1
(even though the Matrikon Logging Delegator isn't installed) if no OPC servers are detected on the network.
If this occurs please verify:
The version of the Aspen Cim-IO for OPC interface used, supports the same OPC standard as the OPC server. For a list of which OPC specification is supported with each version of the Aspen Cim-IO for OPC interface see knowledgebase article 116138.
At least one OPC server is installed correctly and is running.
There are no network problems which prevent communications between the Aspen Cim-IO for OPC server and the OPC server computer.
A 3rd party OPC client can also connect to the OPC server. (A free OPC client is the Matrikon OPC Explorer, downloadable from www.matrikon.com)
Keywords:
References: None |
Problem Statement: Factor tolerance in the MIMI code influences the Actual End Time in the Activity Editor of the PB | Solution: When the Planning Board calculates the Actual End Time (shown in the Activity Editor), there is a tolerance factor of 0.0001 that is added in the C code level of MIMI. This tolerance cannot be changed at the user level.
Let's make an example. If MAKF(AE) for a specific activity is 0.416663, the Planning Board will actually use value 0.416763 (= 0.416663 + 0.0001). That is why a user can experience a difference between the Actual End Time shown in a rule and the one shown in the Activity Editor on the Planning Board.
So, an Actual End Time value for an activity of 0.416663 in table MAKF - which is converted in a rule by command TIMEDATE to 95/06/01 09:59 - will be displayed by the Activity Editor as 95/06/01 10:00 - which corresponds to TIMEDATE(0.416663 + a tolerance factor 0.0001).
Keywords: None
References: None |
Problem Statement: If values are coming in to InfoPlus.21 via Cim-IO for OPC and they are the same value each time (but the date is changing) what can one do to fix this? | Solution: Although the Get records and the rest of Cim-IO for OPC are configured correctly and a clean start of Store and Forward is performed, the values that come in from Cim-IO for OPC are the same each time (although the date changes.) The problem may be the result of the cache on the OPC server being stale. If the OPC server features a way to reset the cache please try that, otherwise a reboot of the OPC server may clear the issue.
Keywords: None
References: None |
Problem Statement: Suppose you are using Aspen CIM-IO for OPC with remote OPC servers (i.e. located on a different machine than the one running Aspen CIM-IO for OPC) and dislike the fact that CIM-IO for OPC stops when it reaches the number of retries specified through the OpcProperties.exe tool. Is there a way to disable this retry counter so that the CIM-IO for OPC will try to connect to the OPC server forever? | Solution: It is not possible to make CIM-IO for OPC try indefinitely to connect to a remote OPC server. However, the number of retries that can be specified through the OpcProperties.exe tool is stored as an unsigned integer. An unsigned integer is 32 bits long so you can put up to 4294967296 retries in the configuration. That is not indefinite, but in OPC terms, it's pretty close.
Key Words
Keywords: None
References: None |
Problem Statement: There are many considerations when deploying AspenTech products in complex network configurations. This article provides a recommendation for deployment of the Aspen Cim-IO for OPC interface. | Solution: Aspen Cim-IO for OPC is an OPC Client application, which follows the OPC Foundations standards for connectivity to OPC Servers. The OPC Foundation dictates requirements for connecting to OPC Servers that are:
1. Installed on the same computer as the OPC Client
2. Installed on computers that are remote to the OPC Client
Security is a concern when connecting to remote computers. The OPC Foundation requires that the OPC Clients and OPC Servers only allow connections from client user accounts that have been granted permissions on the OPC server. The OPC Foundation has chosen the DCOM protocol to be used when configuring the account access permissions between the OPC Client and OPC Server.
DCOM is a technology that was developed in the 1990's. In more recent times, however, it has become common for IT departments to preconfigure security on operating systems so that some of the required DCOM functionality is restricted. This can make connecting Aspen Cim-IO for OPC to an OPC Server more difficult. In addition, adding a level of user authentication and remote connections increases the possibility for connectivity problems in a production environment.
When the OPC Client and OPC Server are installed on the same computer each process can run under the exact same account. This mitigates the need to authenticate a remote user when making the OPC connection.
For these reasons, AspenTech recommends to install Aspen Cim-IO for OPC directly on the OPC Server.
Keywords: None
References: None |
Problem Statement: The following message can sometimes be found in the cimio_msg.log or cimio_diag.log.
BuildReadArray created XX out of YY items
This knowledge base article describes what this message means and under what conditions it will be logged. | Solution: The BuildReadArray created XX out of YY items indicates that the requested XX tags validated properly on the OPC server. If XX = YY then this message indicates that all of the tags were validated on the OPC server.
If YY > XX then it means that some of the tags could not be validated on the OPC server. This is the OPC server's way of saying that the requested tags do not exist on the OPC server. However, it is possible that the tags exist on the OPC server, but are inaccessible. Trying to access such items will generally not be possible. When this occurs please check the following:
- If the tag is misspelled or incorrectly identified, fix the tag name.
- If the tag is not misspelled, check the device to see if:
a) the tag exists
b) the tag is supported by the OPC server
c) the tag is not in any type of uncommunicative state (e.g. offline).
This is an OPC server-related message and will be logged in the cimio_msg.log under normal conditions when the 'Debug On' flag is checked in OPCProperties.exe in versions up to v.2.5.3. For v.3.0 and later this message will appear in the cimio_diag.log when the OPCLOG category is enabled. See KB article 116844 for instructions to enable diagnostic logging on a category basis.
Keywords:
References: None |
Problem Statement: Aspen Cim-IO for OPC 错误信息
Declare Failed - Invalid Tag
当连接到Metso MaxDNA OPC服务器的时候，在Unsolicited transfer record的IO_DECLARE_STATUS会出现如上错误。
Declared的tag可以没有问题的取数据，但是那些没有declare的tag就无法取到数据。 | Solution: 这个问题是因为Metso MaxDNA OPC服务器有2000个订阅点的限制。详细的有关此限制的内容可以查看如下链接。
http://www.metsoservices.com/support/archive/DocLibrary/Manuals/OPC/OPC_Ch01_Introduction.pdf
Configuring OPC-Getting Started（第 7 页）
此订阅点限制的特征：
1) OPC服务器是Metso MaxDNA
2) Declared Tag是不变的，但剩下的会处在 'Declare Failed' 状态
3) 在Aspen InfoPlus.21 和 CIM-IO服务器上运行CIMIO_T_API会出现 'Bad Tag'结果
4) 对步骤三中出现 'Bad Tag'的Tag进行如下操作:
停止 Device processing (IO_DEVICE_PROCESSING).
重新启动相关的 TSK_A, TSK_M and TSK_U 任务
重新在 Aspen InfoPlus.21和CIM-IO服务器上运行 CIMIO_T_API
现在返回的状态为 'Good'
5) 通过OPC服务器的工具，可以确认可同时存在的订阅点数
当关闭 TestAPI, 同时存在的订阅点数是 x-1.
如果我们断开OPC客户端的连接，同时存在的订阅点数也会减少1
如果开始 device processing(IO_DEVICE_PROCESSING) 和重新启动CIM-IO客户端任务，同时存在的订阅点数会增加
Keyword:
Metso MaxDNA
Declare Failed
Invalid Tag
CN-Solution
Keywords: None
References: None |
Problem Statement: OPC Server?I?R???s???[?^?????I?X???e???AGet request timeout???-?????ACIMIO for OPC??OPC Server???c?f?[?^??Z??e?E?-?E?e?B | Solution: OPC Server?I?R???s???[?^???I?X???e???AOPC server?ICOM?Z?L???S?e?B?Y?e???f?t?H???g?E???A?A???U???U???B
?>?I???E, CIMIO for OPC???c?I?U`??v????OPC server???`?U???e?????E?E?A?A???U???U???B
OPC server?ICOM?Z?L???S?e?B?Y?e??OPC ?N???C?A???g???c?I?U`??????A???e?????E?I?X???e???A Cim-IO for OPC??OPC Server?E?A?N?Z?X???
Keywords: COM Security
DCOM
References: None |
Problem Statement: What is the maximum string length and maximum number of array elements that can be processed by CIM-IO for OPC? | Solution: CIM-IO for OPC is dependent upon libraries supplied by the OPC foundation. Currently, these libraries allow a maximum string length of 2^31 (2,147,483,648) characters. Similarly, an OPC array can have a maximum size of 2^31 locations.
The array data type is not supported for versions prior to 2.1.1 of CIM-IO for OPC.
Although CIM-IO for OPC can handle an array of this size, it is important to note that the maximum number of fields possible in any InfoPlus.21 record is 1023. Because of this limitation, restrictions may be placed upon OPC array data brought into InfoPlus.21.
Keywords: size
element
References: None |
Problem Statement: After the installation of the Aspen CIM-IO Core and Aspen CIM-IO for OPC interface, the machine hangs during a reboot when attempting to start the CIM-IO for OPC Interface service and/or the CIMIO Manager service.
When the machine is rebooted, it just hangs and shows a black screen.
The logon for the machine is verified through a Novell client.
If the machine is booted into safe mode and the CIMIO Services are disabled, the machine can be rebooted successfully. | Solution: The problem most likely is an issue with the Novell client products (Application Explorer) on the machine. Installing the CIM-IO products onto a machine without the Novell client software (Application Explorer) should resolve this problem.
Keywords: novell
References: None |
Problem Statement: This knowledge base article provides steps to resolve the following error:
CIMIO_OPC_REGISTER_FAILED, The Register function Failed
CIMIO_OPC_ADDGROUP_FAILED, The AddGroup Method Failed
and
hresult is -2147024891
which may be observed sometimes in the CIM-IO Message log file under various circumstances, such as, for instance, when the OPC server is not installed on the same machine as the CIMIO server (NOT a preferred configuration). | Solution: Most of the troubleshooting steps for the above-mentioned error message are provided in Aspen KB article # 104355. In this particular case, the CIMIO for OPC Interface service (installed on the same machine as the OPC server from DeltaV) was started using a local user account that was a member of the DeltaV Administrator group. After consulting with DeltaV support, it was discovered that there were issues accessing the DeltaV OPC server as a local user and not a domain user. TheSolution was to configure the CIM-IO for OPC service to use a DeltaV domain user account who was also a member of the local APP node Admin group.
Keywords: -2147024891
asyncdlgp
DeltaV
References: None |
Problem Statement: When entering a Cim-IO tagname (this is the tagname from the DCS or Scanner node) into a Cim-IO client (such as an Infoplus.21 IoGetDef record's IO_TAGNAME or cimio_t_api tagname), you receive a status of Bad Tag. Other points may read correctly, verifying that communication in general is working. But this tag, even though spelled correctly, gives the Bad Tag status. | Solution: When entering the tagname, confirm that each character is using the correct case (upper or lower). Some OPC Servers, or the databases they are reading, are case sensitive.
Keywords: 19003
bad tag
References: None |
Problem Statement: Stopping the Aspen Cim-IO for OPC Service on an InfoPlus.21 Server may cause shutdown of the asyncdlgp.exe on the OPC server. | Solution: This problem happens when DCOM communication with the remote OPC server is configured on the InfoPlus.21 server using the same service name and TCP port number and CIMIO_LOGICAL_DEVICES.DEF is modified to use remote asyncdlgp.exe on the OPC server. In this circumstance, the cimio_msg.log file on the remote OPC server records the following message.
Received SHUTDOWN Request, Shutting Down
This Problem can be prevented by removing the DCOM communication settings on InfoPlus.21 server using OPCProperties.
Keywords: DCOM
remote
asyncdlgp.exe
cimio_logical_devices.def
Received SHUTDOWN Request
References: None |
Problem Statement: The CIM-IO client UNSOL and ASYNC tasks are consuming a lot of RAM and no specific issues can be found. | Solution: It has been noticed on a specific customer site that if CIMIO for OPC is connected to the DCS via Matrikon OPC Tunneler and the license on the OPC Tunneler runs out without the CIMIO client tasks being switched off, then the client tasks will continue to run and consume memory.
The work around is to ensure you have communication and if not then investigate if all components are active and licensed. If unable to diagnose the problem it is advised to stop the client tasks and continue diagnosis of the problem.
Keywords: Matrikon OPC Tunneler
References: None |
Problem Statement: How can I use Matrikon OPC Simulation server with CIMIO? | Solution: Matrikon provides a free OPC simulation server for testing purposes. This document shows how to add tags to the Matrikon OPC server and access those tags using CIMIO for OPC.
1. Download a copy of Matrikon OPC simulation server from their web site.
2. Install the software.
3. Launch MatrikonOPC server for simulation
The tag name that you are adding is under Alias configuration. If there is a . in the tag name such as FC001.PV, then you have to add alias group and alias element.
As you can see, it would be tedious to add the tag manually, but you can export the alias to see what is the format, and make changes in excel and import the alias back.
The csv file should have the format with comment line mark with #
# e.g.: [MyGroup1,MyAlias,Plc1.4:1001,3,1,1,500,
FC0001,PV,,5,0,0,0,0
Once you import your whole tag list, it should look like this
Click on view OPC tags for this server
Right click on configured alias and add all items.
You should see a list of tags in the left panel. If there is an error in the tag, it would give you an error at this time.
Click on OK and it should open up with the MatrikonOPC Explorer
So right now, we have tags in Matrikon OPC server. We still have to connect CIMIO for OPC to this server. To do that, go to Start>AspenTech>Aspen Manufacturing Suite>Aspen CIMO-IO>Servers>CIM-IO for OPC>CIM-IO for OPC properties. Then click on Configure OPC servers.
Select the available OPC servers on the left and click on add server
Once you click on OK and close out OPC servers configuration, it should add to the logical devices name and the services file with the corrected port number. Check and make sure you have those items added correcty.
Stop Aspen CIMIO for OPC and Aspen CIMO manager. Start Aspen CIMO manager then start Aspen CIMIO for OPC. You can check to see if everything is working properly back using cimio_t_api to read any tags in the Matrikon OPC server.
Keywords:
References: None |
Problem Statement: A message box entitled OPC Core Components Redistributable Files in Use saying The following applications are using files which the installer must update appears when installing Aspen Cim-IO for OPC, The box specifies the applications DvOPCAE and frsopcdv. | Solution: The applications DvOPCAE.exe and frsopcdv.exe are part of the DeltaV OPC Server interface developed by Fisher-Rosemount Systems, Inc.
The Aspen Cim-IO for OPC installation procedure tries to update/replace several OPC core component files. The message box indicates the installation cannot proceed because the applications DvOPCAE.exe and frsopcdv.exe have these files locked.
Stop the applications to proceed with the installation.
Keywords: Cim-IO, OPC, install, DvOPCAE, frsopcdv
References: None |
Problem Statement: A site has four OPC servers connected to the field devices. Rather than installing
Cim-IO core and Cim-IO for OPC on all these, is it possible to install Cim-IO on a single system and connect to the four OPC servers? | Solution: Dr. Daniel Lessen has submitted the following as an optionalSolution
This can be done.
You do not need a powerful system. The effort is in IO not CPU or disk access speed. And, I suspect that you have less that 100 tags per device. Any CIM-IO for OPC server where the kernel is over 5.x will do and the CIM-IO for OPC is 2.2.2 or greater will work.
Do the standard installation/configuration for CIM-IO for OPC, plus run the Find Remote utility. If the remote OPC server doesn't show up, as is the case for DeltaV and some others, you will have to install a client OPC component from the respective vender.
Communication is via DCOM and the settings vary per vender. OPCEnum must be running. In some cases you may have to make generic username and password between the client and server.
I have seen this arrangement work well for many vendors, the one exception being remote OPC for Cimplicity.
AspenTech Support does not recommend this configuration even though it is technically correct. Our reservations relate to the remote use of DCOM to connect to the OPC servers. If you have any network issues between the Cim-IO server and the OPC server you will not get the benefit of Cim-IO's Store and Forward functionality to buffer the data. Secondly, DCOM introduces added complexity to your data stream.
Keywords:
References: None |
Problem Statement: During configuration of a CIMIO for OPC interface it may necessary to change the configuration of the DCOM parameters for the OPC Server to make it run as the Interactive User.
This issue arises when an OPC server runs in the foreground, in this instance the CIMIO for OPC interface were to run in the Windows Service context it would not be able to read any tags.
When running DCOMCNFG.exe to change the parameters for the OPC Server it is not possible to find the 32-bit servers listed on a Windows 7 64-bit system. | Solution: To be able to see 32-bit OPC servers within the DCOM settings on a Windows 7 64-bit OS you will need to run the following command:
MMC comexp.msc /32
This command can be used within the command line in a DOS window or using the Run command window.
Once completed you will be able to see the OPC Server listed within the DCOM Config level.
Browse to select the OP Server, either by name or class ID, right click the object, select properties, and then the identity tab.
Under this tab select The Interactive User as shown:
Keywords: The Interactive User, OPC Server, Windows 7 64-bit
References: None |
Problem Statement: Cim-IO for OPC will not startup from the I/O section of the InfoPlus.21 Adminstrator. | Solution: If you are starting Cim-IO for OPC with the InfoPlus.21 Administrator, you must disable the OPC Manager service first.
Keywords: cimio for opc
i/o
References: None |
Problem Statement: When using CIM-IO for OPC the interface service sometimes starts before the OPC server is running. Therefore, it's sometimes necessary to make startup of the CIMIO to OPC Interface contingent upon startup of the OPC server. If this is the case, the AsyncDlgp process will not be able to connect to the OPC server. | Solution: There are a few methods of achieving this result.
1. An important change has already been made to the name of the CIMIO to OPC Interface service. If you look in Start | Run | regedt32 under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services, the name of the service (for recent versions of the interface) should be zzCIMIOOPCMGR--making it that last on the list of services. The services are started in this order when the system comes up.
In some instances, however, starting the interface service last does not allow enough time for the OPC server to start completely. In such a situation, it is necessary to make startup of the service dependent upon the OPC server service.
To do this, go to Start | Run | regedt32. Then select HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CIMIO to OPC Interface. From the Edit menu, add a value called DependOnService of type REG_MULTI_SZ double click on it and set it to the desired OPC server service name.
2. Use a DOS delay command in a batch file launched from cimio_autostart.bat, and then set the CIMIO for OPC service to depend on the CIMIO Manager service. DOS delay commands such as sleep.exe that is available in the WinNT and Win2k resource kit may be used. Some freeware such as the wait.exe utility (available from http://www.downloadfreetrial.com/utilities/util5666.html) also perform a similar delay function. The amount of delay is usually specified as a parameter.
3. In CIMIO for OPC v6.0.1 and higher, the delay can now be set using the OPCProperties.exe utility found in the \cim-io\io\cio_opc_api\ folder. In the OPC Properties dialog box, click on the Edit button, add the OPC server name, and enter a suitable delay (in seconds). Restart the interface and you're done.
Keywords: connection
services
References: None |
Problem Statement: What procedure / algorithm is implemented in the Aspen Split Conceptual Design block and are there any references to any journal articles? | Solution: The Aspen Split Conceptual Design component uses the boundary value design procedure.
For more details on the algorithm see
Chapters 4 & 5 in Conceptual Design of Distillation Systems by Doherty & Malone
Julka, V. and Doherty, M.F., Geometric Nonlinear Analysis of Multicomponent Nonideal Distillation: A Simple Computer-Aided Design Procedure, Chem Engng. Sci. 45, 1801-1822 (1990)
Keywords: conceptual
design
algorithm
procedure
References: None |
Problem Statement: What does the IO_Frequency field do when using Unsolicited (UNSOL) requests with Aspen Cim-IO for OPC? | Solution: OPC servers do not truly support unsolicited requests. What they do is perform the filtering of the fixed-frequency polling. This frequency can be set in the UNSOL transfer record. The faster the frequency, the more accurate the unsol will be, which means that the differences between normal polling and filtered polling will vanish.
The behavior of the IO_Frequency parameter is determined by the OPC DA specification. It relates to cached data for unsolicited read operations and tells the OPC server how often we want it to send us an update of the value from cache, provided the deadband requirements are met.
Keywords: unsol
frequency
References: None |
Problem Statement: Changes to FoxAPI version 4.2.7 may cause compatibility problems with the Aspen Cim-IO for Foxboro FoxAPI interface. These issues may prevent the Aspen Cim-IO for Foxboro FoxAPI interface from starting. | Solution: To resolve this edit the configuration file ...\cio_fox_api\cimio_foxia_config.dat
Add the following argument which sets backwards-compatibility flags for Foxboro v4.2.7.
IA_BADSTAT=0
The Aspen Cim-IO interface should now function correctly.
After adding the parameter, stop Aspen Cim-IO for FoxAPI, restart the Foxboro processes, restart Aspen Cim-IO for FoxAPI, and toggle device processing for the Cim-IO Logical Device record in Aspen InfoPlus.21 to initiate data collection again.
Keywords:
References: None |
Problem Statement: How to determine the logical device and the tcp/ip service name for an OPC server if one is not automatically generated by the CIM-IO to OPC interface. | Solution: Use the Start | Programs | AspenTech | Cim-IO | Opc | Display Tags Utility
This utility will list all of the names of any OPC Server found on the local machine.
The names will have a syntax similar to the following:
OPC.Server.1
The Service name becomes the concatination of the string CIO to the name of the OPC Server (as found with the Display Tags Utility) excluding the periods. For example, the OPC Server listed above would require a Service entry of:
CIOOPCSERVER1
This is also the name of that should be used for the IoDevice. So the cimio_logical_devices.def file entry needed for this example would be:
CIOOPCSERVER1 <node_name_of_machine> CIOOPCSERVER1
In cases where the OPC Server name is quite long, the Service name must be truncated to 15 characters. So if the OPC Server name is:
Process.Data.Opc.Server.1
The corresponding Service entry would be:
CIOPROCESSDATAO
This can also be used for the IoDevice name.
If for any reason the service name generated by the interface is not acceptable, the user can specify the service name to be used by adding a line to the file ServiceNames.txt located where the interface was installed.
Enter OPC server name, tab once, and then add the desired service name to replace the one generated by the CIM-IO for OPC interface. The TCP/IP service name can not be more than 15 characters long.
Example: The following line will assign the service name myservicename to the server OPC.MYSERVER.1
OPC.MYSERVER.1 myservicename
After making the above changes, restart the CIM-IO client programs.
Keywords: logical device name
services file
References: None |
Problem Statement: Is there a place that provides an extensive library of OPC errors that are not listed in the Aspen Cim-IO for OPC User's Manual? | Solution: Each error code returned by an OPC server through Cim-IO for OPC is passed into the repeat area entry of the transfer record in Aspen InfoPlus.21. The valid codes are defined in the Cim-IO for OPC documentation. For codes that are not listed in this User's Manual and for general information about OPC, visit the OPC Foundation website at: http://www.opcfoundation.org/ . Also, view the document attached to thisSolution. Though this article was written in 2000, it remains relevant.
Keywords:
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.