Allen-Bradley 1444-TSCX02-02RB User Manual page 483

Monitoring system
Table of Contents

Advertisement

Table 229 - 0x4B Service Responses
Byte Offset
Structure Member
Within Structure
0
Processing Time
4
Status
8
Synch Data Control
10
Advanced Session
Instance
The Dynamix 1444 return the following as part of an 0x4B service response.
Data Type
Description
REAL
Anticipated time for the requested CM data processing to be completed (seconds). For queued requests
(multi-session), processing time also includes anticipated wait time. In extreme cases, the module is not
able to calculate an accurate processing time as the estimate doesn't include any allowance for the
acquisition time for additional samples that are needed. This is because in most circumstances, the
internal sample buffers are sufficient to service the demand. However, when a long TWF (say 65536
samples) with two or more averages is requested, the internal circular buffer is used completely and
additional samples must be acquired at the specified sample rate. Especially in the case where a slow
speed synchronous source is used, this sample acquisition time could be long. In such cases, the remote
system can continue to poll the module for data until it becomes available or can reset/abandon the
current session.
DINT
Any of the following can be returned:
• eUnrecognizedSession (1)
• e maxSessionsReached (2)
• ePacketCountOutOfSequence (3)
• eInvalidBufferSelect(4)
• eNoDataAvailable (5)
• eGeneralError (6)
• eDeniedRequestAlreadyInProgress (7)
• eSessionAccessDenied* (8)
• eAdvancedMeasurementRequestinProgress (9)
• eRequestQueued (10)
• eLiveMeasurementInProgress (13)
* An eSessionAccessDenied status occurs when trying to change an advanced setup with the wrong
Advanced Session Instance or before the timeout.
For all successful requests eSUCCESS (0) is returned, any other value ends the session.
UINT
A synchronizing tacho event, reference for this request
UINT
Multi-session, session control
Sync Data Control
Synchronized Advanced Data can be requested from modules that share a
TSCX module (use its tacho bus outputs). If the physical system is in place, no
pre-configuration* is required for the cross-module synchronization. The
scheme can be summarized as follows:
• The TSCX module regularly identifies a particular tacho pulse
(approximately every 60 seconds)
• Main modules on the tacho bus register this identification event and
start/restart a tacho event count
• Each tacho event is then similarly identified on the independent main
modules (same count value is applied to the same tacho event)
Rockwell Automation Publication 1444-UM001D-EN-P - June 2018
CIP Objects
Appendix A
483

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents