08 Cimio

CIM-IO Interface Sub-System
InfoPlus.21 Foundation Course
©2004 AspenTech. All Rights Reserved.

Objectives
• Understand CIM-IO’s opportunities
– Functionality
– Architecture
– Various data-transfers and data-treatment
– Record-based configuration
• Know how to administer and configure CIM-IO

– Investigate and maintain CIM-IO
– Configure a typical CIM-IO connection

Glossary of Terms
• Activation • ‘Get’
• Asynchronous Transfer • History Recovery
• CIM-IO Client • Logical Device
• CIM-IO Kernel • ‘Put’
• CIM-IO Server • Security
• CIM-IO Task • Solicited Transfer
• Device Record • Store and Forward
• DIOP • Synchronous Transfer
• DLGP • Unsolicited Transfer
• External Task • Wizard

Lesson Overview
• High-level overview of functionality
• Architecture of data flow
• CIM-IO backbone … the records
• Configuring a CIM-IO System: Server and Client
• Understanding Store and Forward
• Configuring a CIM-IO system using the Wizard
• Maintaining CIM-IO
• Specialized data transfer

Functionality of CIM-IO
Source CIM-IO Server CIM-IO client InfoPlus.21
Interface IP.21 record
TAG
Interface any data field
VALUE
• Read and write data

DCS, • Act upon an activation from inside InfoPlus.21
PLC,
ASCII • Act upon a value-change from the external source
or
other
• Automatic buffering and recovering of data
• Data treatment
Basic Elements of CIM-IO
Interface IP.21 record
DCS / PLC / other
TAG
Interface vendor API any data field
VALUE
CIM-IO to XXX CIM-IO External Tasks

CIM-IO records
CIM-IO Kernel TCP/IP CIM-IO Kernel
CIM-IO to XXX – communicate with vendor API

DCS,
CIM-IO Kernel – communicate with TCP/IP
PLC, CIM-IO Tasks – communicate with InfoPlus.21 records
ASCII CIM-IO Records – configures CIM-IO
or
other
NOTE: CIM-IO client is integrated in InfoPlus.21 as records
and tasks
Overview of CIM-IO Architecture
CIM-IO Server CIM-IO client InfoPlus.21

DCS / PLC / other source
vendor API
IP.21 record
any data field
CIM-IO
client / server
CIM-IO to XXX CIM-IO External Tasks on different
CIM-IO records nodes

vendor API
IP.21 record
any data field
CIM-IO
client / server
CIM-IO to XXX CIM-IO External Tasks on the same
CIM-IO records node

How a Typical Data Transfer Occurs
Interface TAG DCS / PLC / other source IP.21 record
Interface Value vendor API any data field
CIM-IO to XXX CIM-IO External Tasks
DCS, CIM-IO records

PLC CIM-IO Kernel CIM-IO Kernel
or other
0. Settings of data-transfer are stored in the CIM-IO records.

1. CIM-IO records are activated and request data from CIM-IO External Tasks.
2. The CIM-IO client submits the request to the CIM-IO server, which requests
the data from the source-API, then returns it to the appropriate CIM_IO client.
3. Data is passed to the InfoPlus.21 data-record, and transfer status is updated
in CIM-IO record.

Alternative CIM-IO Architectures
•• Multiple servers
Single server feeding
feeding single clients
multiple client

DCS / PLC / other source IP.21 record
vendor API any data field
CIM-IO to XXX CIM-IO

CIM-IO
External
TasksTasks
CIM-IO records
CIM-IO Kernel CIM-IO Kernel

DCS / PLC / other source IP.21
IP.21 record
record
vendor API any data
any data field
field
CIM-IO to XXX SECOND CIM-IO

CIM-IOTasks
External Tasks
CIM-IOTasks
FIRST CIM-IO External records
CIM-IO Kernel CIM-IO Kernel FIRST CIM-IO records
CIM-IO Kernel SECOND CIM-IO records

Lesson Overview

How Data Flow is Initiated
• Solicited Transfers
– Data is requested after a client-side activation
• ScheduledActDef, ChangeOfState or SQLplus
– Network traffic consists of a request and a reply
• Unsolicited Transfers
– External device sends data upon a value-change
– Network traffic consists solely of unsolicited replies
– External device has to support unsolicited functionality

Synchronization of Solicited Data Flow
• Synchronous Transfers (typical)
– Request and reply are handled by the CIM-IO Main task
– Main task waits for a reply before processing next set
of data-requests
• Asynchronous Transfers
– Reply is processed by another task: the ‘Async’
– CIM-IO client does NOT wait for a reply before processing next
set of data requests

Buffering and Recovery @ External Device
• By default, CIM-IO reads current data
• Additionally, CIM-IO can read historical data
– After a communication-disruption, the Cim-IO client can
automatically read the ‘missed’ data
– This historical data is inserted into InfoPlus.21 with the original
timestamps
– Retrieval of current data continues once the “catch-up” is
completed
• The external device itself must have capability to store

historical data

Buffering and Recovery @ CIM-IO Server
• During a communication-disruption, the CIM-IO server
can automatically buffer the “missed” data
– The S&F “scanner” processes all transfers
– The S&F “store” process will buffer the data during the
unavailability of the CIM-IO client
– When available again, the “forward” process sends the
buffered data to the CIM-IO client
• Store and Forward does NOT require buffering on the
external device itself
• Store and Forward operates independently; network
traffic always consists solely of “replies”

CIM-IO Server Internal Data Flow
CIM-IO Server • CIM-IO to XXX Components

DCS / PLC / other source – DLGPs
vendor API • Manages all dataflow
– DIOPs
• Speak “foreign language”
DIOP DIOP • Handle specific data flow
DIOP
– Store and Forward (optional)
CIM-IO to XXX
• Store file
S&F DLGP • Store and forward processes
• CIM-IO Kernel Components

• Communication Layer – TCP/IP communication
• TCP/IP
CIM-IO Kernel
settings TCP/IP
logical device name – TCP/IP services and nodes
– Logical device name
T
Architecture and Data Flow Review
CIM-IO Server 1 CIM-IO client InfoPlus.21

DCS / PLC / other source IP.21 record
vendor API any data field
CIM-IO Server 2
DIOP DIOP
DCS / PLC / other source TSK_M_XXX
vendor API
DIOP 2nd CIM-IO Tasks TSK_A_XXX
TSK_M_XXX
1st CIM-IO Tasks TSK_A_XXX
DLGP
S&F
DIOP DIOP 1st CIM-IO records
DIOP
2nd CIM-IO records
• Communication Layer • Communication Layer
DLGP • TCP/IP settings • TCP/IP settings
S&F TCP/IP
logical device name 2 logical device names
• Communication Layer
• TCP/IP settings TCP/IP
logical device name
Synchronous vs. Asynchronous

Solicited vs. UnSolicited
History Read vs. Store and Forward
Lesson Overview

CIM-IO Backbone ... The Records
• Infrastructure records
– Define communication – route
• Use which CIM-IO external tasks?
• Connect to which logical device?
• Transfer records
– Define communication – process
• Solicited?
• Synchronous?
• Store and Forward?
– Link tag from the external device to InfoPlus.21

Infrastructure Records
• External Task Records
– Define CIM-IO external tasks for InfoPlus.21 manager
– Link these tasks with a logical device
• Logical Device Record

– Define the logical device names for CIM-IO server
– Link this logical device with the external tasks
– Define global settings for History Recovery
– Define global settings for Store and Forward
– Define source of timestamp

External Task Records and the IoDevice Record
IO External Task Records IO Device record
Main External Task Defines the logical device
LOGICAL DEVICE
TSK_MSIM
TSK_ASIM
IO External
tasks
TSK_USIM settings
Async External Task
History
recovery
Unsol External Task settings
Store and
forward
settings
Transfer Records
• ‘Get’ records
– Transfer Solicited data
– Defined by IoGetDef, IoLongTagGetDef, IOLLTag
• ‘Unsol’ records
– Transfers Unsolicited data
– Defined by IoUnsolDef, IoLongTagUnsDef
• ‘Put’ records
– Transfers data that is to be written to the External Device
– Defined by IoPutDef, IoLongTagPutDef
– Defined by IoPutonCosDef, IoLongTagPOCDef for COS processing
• ‘Get-History’ records
– Transfers data to be retrieved from the device data buffering system
– Defined by IoGetHistDef, IoLongTagGetHistDef

Structure of a Transfer Record
• Fixed Area
– Global processing settings
– Global status information
• Repeat area
– Each occurrence defines one item to transfer
• Destination: record and field in InfoPlus.21
• Source: device tagname
• Data Treatment
• Status information
– Processing of datapoints is started simultaneously

Transfer Record – Fixed Area
Identification
Global processing info
Group processing
Communication settings
Global status
Group processing
Size of repeat area

Transfer Record – Repeat Area
InfoPlus.21 tag
Device tag  LINKED TO 
and field
. . . continued
. . . continued

CIM-IO Backbone Records – Review
CIM-IO client InfoPlus.21
DEVICE RECORD TRANSFER RECORD IP.21 RECORD
by IODeviceRecDef by IO_XXX_Def
ANY DATA FIELD
IO_Main_Task: TSK_M_xxx IO_Main_Task: TSK_M_xxx
IO_Async_Task: TSK_A_xxx IO_Async? YES / NO
IO_Unsol_Task: TSK_U_xxx Repeat Area
IO_Async? YES / NO IO_Value_Field: IP.21 tagname
IO_Unsol? YES / NO IO_Value_Record: IP_Input_Value
IO_Store_Enable? YES / NO IO_Tagname: Interface tagname
<LOGICAL DEVICE NAME>
UNSOL Ext.TaskDef
ASYNC Ext. TaskDef kDef InfoPlus.21 External Tasks
MAIN Ext. TaskDef kDef me> by IP.21 Manager
by IOExternalTaskDef me> > <TSK_U_xxx> ^ Ext.Task
<logical device name> > <TSK_A_xxx> ^ Ext.Task
<TSK_M_XXX> <TSK_M_xxx> ^ Ext.Task
• Communication Layer
• TCP/IP settings
TCP/IP logical device name

CIM-IO Lab 1: Exploring the CIM-IO Records
• The InfoPlus.21 tag “F106A.PV“ is being updated by CIM-IO
• See if you can follow the trail of pointers between the various
records associated with the update of F106A.PV?
– Which Get record updates the tag F106A.PV?
– What is the name of the main CIM-IO task handling the data transfer?
– To which external logical device do the get record and main task
belong?
– How was the data transferred?
• Is it a solicited or unsolicited transfer?
• Does the transfer use the Asynchronous task?
• What is the communication-status?
– What is the source on the external device for the data stored in
F106A.PV?
– Does the data receive it’s timestamp from the CIM-IO Server or the
InfoPlus.21 database?
– Why is there a lack of current data? There are several reason
Lesson Overview

Review of CIM-IO Server Internal Data Flow
CIM-IO Server • CIM-IO to XXX Components

DCS / PLC / other source – DLGPs
vendor API • Manages all dataflow
– DIOPs
• Speak “foreign language”
DIOP DIOP • Handle specific data-flow
DIOP
– Store and Forward (optional)
CIM-IO to XXX
• Store file
S&F DLGP • Store and forward processes
• CIM-IO Kernel Components

• Communication Layer – TCP/IP communication
• TCP/IP
CIM-IO Kernel
settings TCP/IP
logical device name – TCP/IP services and nodes
– Logical device name
Steps to Configure a CIM-IO Server and Client
• Define TCP/IP services used by the CIM-IO server
processes
• Define a Logical Device for each CIM-IO server DLGP
process that will be communicating with a CIM-IO client
• Update the cimio_errors.def file with the CIM-IO server’s
error definition file
• Setup the CIM-IO client such as creation of external task
records, etc.
• Setup the CIM-IO server

CIM-IO_Logical_Devices.Def and Services File
• The CIM-IO_Logical_Devices.def file and the Windows
Services file are critically important to establishing a
communication link between the CIM-IO server and the
CIM-IO client:
– These files are located on the CIM-IO server and the CIM-IO
client. The CIM-IO_Logical_Devices.def file must be identical
on both machines
– Entries in the Services file that pertain to CIM-IO must be
identical on both machines
• Make sure that there is an empty carriage return at the

end of the Windows services file before saving it

Troubleshooting the Communication Link
• The CIM-IO Test Utility Program, cimio_t_api.exe, is a
CIM-IO program used to test communications between the
CIM-IO server and client machines. The Test Utility program
is supplied with the CIM-IO core
• This program runs in a command window. The user
responds to a series of prompts. Several basic CIM-IO
functions can be tested manually with this program. It is an
excellent troubleshooting tool
• The CIM-IO Test Utility Program can be launched from the
AspenTech/Manufacturing Suite/CIM-IO program menu.
The executable is located in the
Program Files\%SETCIMCODE% directory

Results of using the CIM-IO Test Utility

CIM-IO Lab 2: Configure CIM-IO
• In this lab, you will:
– Configure CIM-IO for OPC
– Bring data from an OPC server into InfoPlus.21
• The instructor will designate machines on one side of the

classroom to act as the CIM-IO server (the designated
machines have both a Matrikon OPC server and CIM-IO
for OPC installed), and the machines on the other side of
the classroom will act as the CIM-IO client (InfoPlus.21).
Please pair up with the student(s) across from you to do
the following lab

Lab 2: Matrikon OPC Server

Lab 2: Start CIM-IO to OPC
• Starting the CIM-IO for OPC • Cimio_msg.log indicating
interface (diagram 1) startup (diagram 2)

Lab 2: Configuring CIM-IO

Lab2: Configure the Main Client Task
• In the InfoPlus.21
Manager, configure
the main client task

Lesson Overview

Buffering and Recovery @ CIM-IO server
• Store and Forward buffers on the CIM-IO Server
– When the CIM-IO client is not accessible, incoming data is
stored to a disk file
– When the CIM-IO client is accessible, the stored data is
forwarded
• Any Get or Unsol record can be used

• CIM-IO server operates autonomously
– Activation builds a CIM-IO server scanlist
– Uses scan-frequency from transfer record

Store and Forward Data Flow

TRANSFER RECORD IP.21 RECORD
DIOP DIOP by IO_xxx_Def
DIOP ANY DATA FIELD
3 IO_Frequency: xxx
IO_Async? YES
DLGP Repeat Area
2
SCANNER 1
4 InfoPlus.21 External Tasks
by IP.21 Manager
A STORE 5
store <TSK_M_xxx> ^ Ext.Task
file <TSK_A_xxx> ^ Ext.Task
FORWARD
B C <TSK_U_xxx> ^ Ext.Task
1. Main Task sends data request to the SCANNER process

2. SCANNER sends requests to DLGP at the IO_frequency set in the transfer record
3. DLGP determines the type of request and passes it on to the appropriate DIOP
4. Data returned to DLGP is sent to the STORE process
5. If the connection is up, the STORE process sends data back to the ASYNCHRONOUS task
A. If the connection is down, the STORE process sends data to the STORE File
B. When the connection comes back up, the FORWARD process reads the STORE File
C. The FORWARD process sends the data back to the ASYNCHRONOUS task
Configuring Store and Forward
Create Specify this Enable Async Have the
an Async Async task in the IoDevice Async Task
External in IoDevice AND in the in the IP.21
Task record record transferrecord manager
(re)Start the Start server

Test and check Disable
Main and processes
the async any automatic
Async Task DLGP, DIOP,
time&status in activation of
in the IP.21 scanner, store,
transferrecord transferrecord
manager and forward
Check the
Enable
Activate the time&status
“STORE?”
transferrecord in the IoDevice Test
in IoDevice
ONCE and in the
record
transferrecord

Changes to Get Records for Store and Forward
Records using Store and
Forward should only be activated
ONCE (Records may NOT be
scheduled)
Store and Forward processing

returns data to the Async Task,
therefore the IO_ASYNC? Field
must be set to YES
Set IO_TIMEOUT_VALUE to a
non-zero value to avoid hang-up
The IO_FREQUENCY field

must be set to a positive value.
This is the frequency the S&F
Scanner process will use to
read data from the device
Changes to IoDevice Record for Store and Forward
Store and Forward for GET transfers
returns data to the Asynchronous
Task, therefore the IO_ASYNC? field
must be set to YES
The IO_ASYNC_TASK name must

be defined
IO_STORE_ENABLE must be enabled
IO_STORE_MAX_SIZE sets the

maximum size of the STORE file in
megabytes. The OS limit is 2 GB
When the maximum size is reached,

the store file will start overwriting the
oldest data

Section Review
CIM-IO Server • Special TransferRecords are
DCS / PLC / other source vendor API used to configure:
– Unsolicited transfers
hist. write read unsol
DIOP DIOP DIOP – Historical transfers
DIOP
• CIM-IO server operates
Hist. DLGP store autonomously for:
DLGP file – Unsolicited transfers
– Store and Forward
• After ONE activation
STORE
SCANNER FORWARD • Configure the CIM-IO server by
the transfer and IoDevice
cimio_logical_devices.def file TCP/IP Hosts file records
IP address CimIO server
logical CimIO DLGP
device server service TCP/IP Services file
name name name DLGP name portnumber

CIM-IO Review
Source CIM-IO Server CIM-IO client IP.21
IP.21 RECORD
ANY DATA FIELD
DEVICE RECORD TRANSFER RECORD

Interface TAG DCS / PLC / other source
? by IODeviceRecDef by IO_XXX_Def
Interface Value vendor API IO_Main_Task: TSK_M_xxx IO_Main_Task: TSK_M_xxx
IO_Async_Task: TSK_A_xxx IO_Async? YES / NO
hist. write read unsol IO_Unsol_Task: TSK_U_xxx Repeat Area

DIOP DIOP DIOP DIOP IO_Async? YES / NO IO_Value_Field: IP.21 tagname
IO_Unsol? YES / NO IO_Value_Record: IP_Input_Value
device IO_Store_Enable? YES / NO IO_Tagname: Interface tagname
Hist. Hist. DLGP

<LOGICAL DEVICE NAME>
store
DLGP
file UNSOL Ext.TaskDef
ASYNC Ext. TaskDef kDef IP.21 Ext. Tasks
MAIN Ext. TaskDef kDef by IP.21 Manager
me>
STORE by IOExternalTaskDefme> > TSK_U_xxx ^ Ext.Task
DCS, <logical device name> > TSK_A_xxx ^ Ext.Task

SCANNER FORWARD
PLC, <TSK_M_XXX> TSK_M_xxx ^ Ext.Task
ASCII cimio_logical_ TCP/IP Hosts file cimio_logical_

devices.def file
TCP/IP Hosts file
devices.def file IP address cimio server IP address cimio server
TCP
or logical
device
CimIO
server
DLGP
service TCP/IP Services file IP
logical
device
CimIO
server
DLGP
service TCP/IP Services file
other name name name DLGP name portnumber name name name DLGP name portnumber

CIM-IO Lab 3: Configuring Store and Forward
• In this lab, you will:
– Modify the configuration from Lab 3, to
enable the Store and Forward
functionality
– Test Store and Forward, and
investigate the implementation – after
properly configuring Store and Forward

Lab 3: Modifying the CIMIO_AUTOSTART.BAT File
• Three executables manage the Store and Forward
process. You can start them manually each time you
start the CIM-IO server, or you can modify the
cimio_autostart.bat file so that each time the CIM-IO
Manager service is started, it also starts the Store and
Forward processes
• For this lab, we will configure the cimio_autostart.bat file
to start Store and Forward

Lab 3: Autostop and Store and Forward File
Entries
• Cimio_autostop.bat (diagram 1) • Modifying the services file
– (notice the double quotes) (diagram 2)

Lab 3: Viewing CIM-IO Active Processes via the
Windows Task Manager
• In the Windows Task
manager, verify that the
following four processes
are running:
– cimio_sf_forward
– cimio_sf_scanner
– cimio_sf_store
– AsyncDlgp.exe

Lab 3: CIM-IO Client Configuration
• This is done on the
InfoPlus.21 server

Lesson Overview

Setup the Infrastructure
Specify the Specify the Specify the

ADD next logical next CimIO server next CimIO server
1 I/O device device
name
TCP/IP
node name
DLGP
service name
ADD auto Startup: Setup

next Specify the next next
username CimIO server
2 CIM-IO
server
server
name
password
healthcheck
processes +
health check
Choose
ADD next drag & drop next type of com- next Start
3 CIM-IO client
I/O device
to CimIO
munication
and origin of
external
tasks
timestamp

1. Add New Device to the I/O Group
Right-click
Logical devicename
Use the CIM-IO server CIM-IO server
TCP/IP nodename
specific .csc template
TCP/IP servicename
and / or (check CimIO manual)
TCP/IP servicename
Complete the settings
manually

2. Add CIM-IO Server
Any name you like
Automatic startup @ boot

using the CIM-IO Manager
service. This needs a valid
username and password
with sufficient rights
Automatic health check

(and restart) of CIM-IO
server processes

2.a Add CIM-IO Server Processes
(any name you like)
TCP/IP servicename
(check CimIO manual)
Add necessary DLGP and DIOP’s for the CimIO server

When using the .csc file, this is done automatically
3. Add CIM-IO Client External Tasks
Drop
Drag
Main task is created

automatically
Async and Unsol task

are created on request
Select the origin of

the data timestamp
3.a Start CIM-IO Client External Tasks

Setup the Data Transfers
Create enable
select an
repeat area, define data
1 data records
(tags)
IO_Value_
Format
repository
archiving
compression
link
Create Specify the define a
device tag
IO_MainTask schedule,
2 transfer
records
Async?
IO_Priority
with
IP.21 record
COS or IO_
frequency
and field
Initiliaze Switch Switch

processing processing Activate
and
3 activate
ON
in device
ON
in transfer
transfer
records
processing and transfer records

1. Create Data Records to Store the Data
• Standard InfoPlus.21 tags can store data from a device
– IP_AnalogDef for real data
– IP_DiscreteDef for integer data
– IP_TextDef for string data
• However, any record and field in the database may be
used including custom records, for example:
– Custom recipe records
– Records used for updating setpoints or alarms
• Values to be ‘PUT’ can be obtained from any record and

field within the InfoPlus.21 Database

2. Create a Transfer Record Using the Wizard
• Drag and drop the field that is to be linked to the CIM-IO
logical device
DRAG
DROP

2.a Configure a New Transfer Record
Name of the
transfer record
This frequency is
ONLY used for
Store and
Forward

2.b Advanced Transfer Parameters
CIM-IO client processes transfer
records group-wise. By default,
only one group is configured
CIM-IO client waits for every reply

until the timeout.
Recommended is at least 5 sec.
Upgrade your network if you need
a timeout higher than 60 sec.
Enter a processing priority 1 - 9,

1 is the highest, for this transfer
record
Optionally, Asynchronous communication can be enabled for a transfer

record, not only when Asynchronous communication has been enabled
for this device.
Note: Asynchronous communication is a prerequisite for Store and
Forward
2.c Link InfoPlus.21 Tag to a Device Record
Enter the device tagname
Highlight the transfer

record then click the Next
button
Set the link
2.d Populate Transfer Record using SQLplus
Text file
from
MS-Excel
SQLplus
INSERT
Statement

3. Initialize Processing
• All CIM-IO record processing needs to be
turned ‘on’
• IoDevice Record
– Switch ’IO_DEVICE_PROCESSING’ from ‘OFF’ to ‘ON’
• Transfer Records
– Switch ‘IO_RECORD_PROCESSING’ from ‘OFF’ to ‘ON’ in the
fixed area
– Turn ‘IO_DATA_PROCESSING’ ‘ON’ for each point in the
repeat area Turn me
on

3.a Activate Transfer Records
• For transfer records using Store and Forward or
Unsolicited Transfers:
– Only ONE activation is needed
– CIM-IO server acts ‘automagically’
• For other transfer records:

– A client-wise activation is needed for every new datapoint
– The CIM-IO client has the initiative
– It is possible to automate this

3.b Setup Automatic Activation
• Use server IO_Frequency when using Store and Forward
• Otherwise, use client-wise activation
– ScheduledActDef
– SQLplus
– COSActDef
– “Internal” IO_ACTIVATION_COS

3.c Check for Results
• Check for timestamp and status in transfer:
– Record
– Record repeat area

CIM-IO Lab 4: Configuring a New CIM-IO Sub-
System
• In this lab, you can setup a Cim-IO configuration,
reading data from a simulated external device
– Setup the infrastructure
1. ADD I/O device
2. ADD CIM-IO server
3. ADD CIM-IO client
- Setup the data transfers

1. Create tags if necessary
2. Create and populate the CIM-IO transfer records
3. Switch processing ON for all records
4. Activate the transfers

Lesson Overview

Health Checking
• Check health of CIM-IO servers in the I/O folder

• Check health of CIM-IO client in the InfoPlus.21 records
– Recent timestamp in the transfer record
– ‘Good’ IO_LAST_STATUS in the transfer record fixed area
– ‘Good’ IO_DATA_STATUS in the transfer record repeat area
Data Stopped Coming In …
No new
APEx data
Got yes Ping yes Error Start CIM-IO server

S&F / server
historical CIM-IO in transfer (start Store&Forward)
shutdown
data? server? record? check DIOPs, Dlgps
no no success Check IO_tagname,

cimio error check devicename,
usr get/rec hosts, services, and
Ping cimio_logical_devices
no Last check cimio_t_api
IP.21
update?
server? old
cimio error Increase time-out
time-out or decrease NW traffic
yes recent
OTHER Check cheat sheet for
Check timespan, Fix Activate Check ERRORS errors and actions
tagname, historian TCP/IP record source
Check TCP/IP Communication Properties
• The entries in these three files need to exactly match each other at
CIM-IO server, CIM-IO client, AND the I/O Administrator
Or Contact SUPPORT.AspenTech.com

Lesson Overview

Specialized (Advanced) Data Transfer
• Data treatment “on the fly”
• Unsolicited data transfer
• Buffering and Recovery

– @ Ext. Device: Historical Gets

Data Treatment “On the Fly”
• The following type of Data Treatment are available:
– Change of datatype
– Data Conversion
– Deadbanding
• Configured:
– In the transfer record - repeat area
– Using special ‘selector’ records
• Processed at the CimIO-client,

just before data enters InfoPlus.21 records

Change of Data Type
DataType field in fixed area DataType fields in repeat area
The InfoPlus.21 data type, The Device Data Type,

e.g., Real/Float, Integer, ASCII, or e.g., Real/Float, Integer, ASCII,
Absolute Time. “Default” selects Absolute Time, Enumerated,
the InfoPlus.21 destination Ordinal, or Smart. Conversion is
datatype automatic
Data Conversion
• Selected in CIM-IO transfer record – repeat area
Input Range Output Range
• Configured in Io-Eu-Conv record

Data Deadbanding
• Selected in CIM-IO transfer record – repeat area
• Configured in Io-Deadband record
• Processed at CIM-IO client

Unsolicited DataTransfers
• When a subscribed tagvalue changes – and only then – the device
will send it to the CIM-IO server
• Data traffic consists solely of unsolicited replies
• The device operates in an unsolicited manner (i.e., automatically)
– To know which tags to process, the CimIO MainTask creates a
subscribed scanlist upon:
• Start-up of the main task (i.e., startup of InfoPlus.21)
• Activation of the transfer record
• Only ONE initialization is necessary

• External device needs to support unsolicited functionality

Unsolicited Data Flow
transfer record defined IP.21 RECORD
by IO_UNSOL_Def
vendor API ANY DATA FIELD
IO_Main_Task: TSK_M_xxx
IO_Async? YES / NO
Repeat Area
IO_Value_Field: IP.21 tagname
unsol read IO_Value_Record: IP_Input_Value
DIOP DIOP IO_Tagname: Interface tagname
InfoPlus.21 External Tasks

by IP.21 Manager
DLGP
<TSK_M_xxx> ^ Ext.Task
<TSK_A_xxx> ^ Ext.Task
<TSK_U_xxx> ^ Ext.Task
• No change-of-value  no communication
Configuring an Unsolicited TransferRecord
• An unsolicited record is configured in a similar manner to a Get
record
• However, it only needs to be activated ONCE
– Device scanlist is created
– Device operates “automatically”
• Additional activation will re-create the scan list

• Check declare time and status
in Unsolicited record – repeat area

Buffering and Recovery @ External Device
CIM-IO Server • Historical read allows CIM-IO to gather
buffered data from external device (read
DCS / PLC / other source only!)
vendor API
• For example, “catch-up” situation
• Historical data is inserted correctly into
InfoPlus.21
Hist. read
DIOP DIOP • Retrieval of current data continues once
the “catch-up” is completed
• Device must have capability to buffer
Hist. historical data
DLGP
DLGP

History Transfers and the IoDevice Record
• IoDevice record configures global parameters
– How to handle a “Gap” in history:
• Ignore
• Insert a real or ASCII value
• Interpolate the gap
– Contains diagnostic information

Additional Fields in GetHist Transfer Records
Fixed area
Repeat area

08 Cimio

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

08 Cimio

Caricato da

Copyright:

Formati disponibili

CIM-IO Interface Sub-System

InfoPlus.21 Foundation Course

©2004 AspenTech. All Rights Reserved.

• Know how to administer and configure CIM-IO

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

• Read and write data

CIM-IO to XXX CIM-IO External Tasks

CIM-IO to XXX – communicate with vendor API

CIM-IO Server CIM-IO client InfoPlus.21

CIM-IO Server CIM-IO client InfoPlus.21

©2004 AspenTech. All Rights Reserved.

CIM-IO to XXX CIM-IO External Tasks

DCS, CIM-IO records

0. Settings of data-transfer are stored in the CIM-IO records.

©2004 AspenTech. All Rights Reserved.

CIM-IO Server CIM-IO client InfoPlus.21

CIM-IO to XXX CIM-IO

CIM-IO Server CIM-IO client InfoPlus.21

CIM-IO to XXX SECOND CIM-IO

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

• The external device itself must have capability to store

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

CIM-IO Server • CIM-IO to XXX Components

• CIM-IO Kernel Components

Architecture and Data Flow Review

CIM-IO Server 1 CIM-IO client InfoPlus.21

Synchronous vs. Asynchronous

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

• Logical Device Record

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

Global processing info

Size of repeat area

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

CIM-IO Server • CIM-IO to XXX Components

• CIM-IO Kernel Components

©2004 AspenTech. All Rights Reserved.

• Make sure that there is an empty carriage return at the

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

• The instructor will designate machines on one side of the

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

©2004 AspenTech. All Rights Reserved.

• Any Get or Unsol record can be used

©2004 AspenTech. All Rights Reserved.

CIM-IO Server CIM-IO client InfoPlus.21

1. Main Task sends data request to the SCANNER process

(re)Start the Start server