00191134-03 - 第52页

GEM for SIPLACE V5.01 Page 52 of 252 ©Siemens AG, all rights reserved Trans m it Spool The SIPLACE is transm itting spooled m essages to the Host.  5HODWHG9DULDEOHV The f ollowing table lists the variables (SV&ap…

GEM for SIPLACE V5.01

 )URP 7ULJJHU 7R 'HVFULSWLRQ

this variable will be

sent.

9 No Spool

Output

The Host requests

the SIPLACE to

purge its spool.

Purge Spool SIPLACE will delete its

spool.

10 Spool

Output

Entire spool has

either been read or

purged by the Host.

Spool

Inactive

SIPLACE will continue

normal SECS

communicating.

6SRRO6WDWHV

Power Off

The SIPLACE is completely shut down.

Power On

The SIPLACE is "on" and in a stable state.

Spool Inactive

Spooling is not activated. This is either because CONFIGSPOOL

(VID 1002045) is "0" (disabled) in which case, spooling will never

be active, or because while GemConfigSpool is enabled ("1"), a

RTY error has not occurred. In this state, no messages are sent to

the spool. The Host may define or un-define messages eligible for

spooling should the link go down.

Spool Active

While CONFIGSPOOL (VID 1002045) is "enabled" ("1"), the

SIPLACE has experienced a transmission failure (RTY error).

Upon entry into this state, the first message sent to the spool is the

GemSpoolingActivated event (CEID 1000007), assuming that this

event is enabled and that spooling for the particular stream and

function have been enabled. This message will enter the spool

even before the message which originally caused the RTY error.

Spool Not Full

The file containing the spooled messages has not

reached its capacity.

Spool Full

The file containing the spooled messages has reached

its capacity.

No Spool Output

In this state, the Host is not reading or purging the

SIPLACE's spool.

Spool Output

This super-state contains the two sub-states in which

the Equipment's spool is either being read or purged by

the Host.

Purge Spool

The SIPLACE is purging its spool, erasing all

spooled messages.

GEM for SIPLACE V5.01

Transmit Spool

The SIPLACE is transmitting spooled messages

to the Host.

 5HODWHG9DULDEOHV

The following table lists the variables (SV's, EC's, or DVVALS) which are relevant to

spooling. For a more complete description of these variables, see "Appendix A --

Variables".

Variable Name VID

MAXSPOOLTRANSMIT 1002037

CONFIGSPOOL 1002045

SPOOLCOUNTACTUAL 1002038

SPOOLCOUNTTOTAL 1002039

OVERWRITESPOOL 1002046

SPOOLFULLTIME 1002040

SPOOLLOADSUBSTATE 1002041

SPOOLSTARTTIME 1002042

SPOOLSTATE 1002043

SPOOLUNLOADSUBSTATE 1002044

 5HODWHG(YHQWV

The following lists the collection events (CEIDs) which are relevant to spooling. For a

more complete description of these events, see "Appendix B -- Collection Events" or the

description in this chapter.

Collection Event CEID

GemSpoolingActivated 1000007

GemSpoolingDeactivated 1000008

GemSpoolTransmitFailure 1000009

GEM for SIPLACE V5.01

 6(&60HVVDJH'HWDLO

This section describes each message sent or understood by the Equipment.

 60/1RWDWLRQ

Message descriptions are shown using "SECS Message Language" (SML) notation. SML

is a general notation developed by GW Associates for describing SECS messages. SML

is similar to the notation used in the SECS Standards documents, but SML is a more

precise and regular notation. In SML, the format for a data item is as follows:

< type [ count ] value >

The components are:

! Angle Brackets. Each Data Item is enclosed within angle brackets ("less

than", "greater than"). This notation implies that each Data Item has a

Data Item Format and Data Item Length as required by SECS-II.

W\SH This specifies the SECS-II Data Item format. It will have one of the

following values:

A ASCII

B Binary

JJIS-8

I1, I2, I4, I8 Signed Integers

U1, U2, U4, U8 Unsigned Integers

F4, F8 Floating Point

BOOLEAN True/False

FRXQWCount of the element values that make up the item. If present, the count

is enclosed within square brackets "[ ]". The count may be omitted, in

which case the square brackets are also omitted.

The "count" specifies the number of value elements in the Data Item

Value. For String formats (ASCII, Binary, JIS-8), "count" specifies the

number of characters in the string. For Numeric formats (I1, I2, I4, I8, U1,

U2, U4, U8, F4, F8, BOOLEAN), "count" specifies the number of values in

the array. For simple scalar numeric values, "count" is usually "1". For

LIST items, "count" specifies the number of items in the list.

If "count" is omitted, then the length of the Data Item is implied by the

value which follows. The "count" can range between known limits. It may

be specified as minimum and maximum "counts", separated by two dots.

(For example, [0..40]).

YDOXH Value of a single item element. Values are shown in a notation that

depends on the item type. For example, ASCII values are shown as

characters enclosed in quotes, Unspecified Binary values are shown in

hexadecimal.

 Ellipsis (...) is used to indicate additional elements may occur, as for

example where substructures may repeat in a List structure.

As an example, a two-byte unsigned integer Data Item with an array of three values 21,

22, and 23 is represented as:

Numeric values shown are considered decimal integers unless otherwise indicated.

negative values shown with a leading minus sign "-". Hexadecimal values are shown in C-

Language convention, with a leading "0x".