TRS GEM Manual for Intel Ver 1.1 - 第26页

GEM Manual for DEK P rinters Capabilities Issue 1.1 March 20th, 2014 Page 26 of 152 Page 26 of 152 5.2.3 Trace Data Collection This capability enables reports to be sent at fixed intervals. This is achieved a s follows: …

GEM Manual for DEK Printers Capabilities

Issue 1.1 March 20th, 2014 Page 25 of 152 Page 25 of 152

Scenario:

Collection event report set up and send:

Comments

Host

Equipment

Comments

[IF] Define report is multi-block

[THEN] Send multi-block inquire

S2F39 -->

[END_IF]

<-- S2F40

Multi-block grant

Send report definition

S2F33 -->

Receive DATAID’s, RPTID’s, & VID’s

<-- S2F34

Send DRACK = 0 report is OK

[IF]Link event report is multi-block

[THEN] Send multi-block inquire

S2F39 -->

[END_IF]

<-- S2F40

Multi-block grant

Link reports to events

S2F35 -->

CEID's & RPTID's received

<-- S2F36

LRACK = 0

Enable specific collection events

S2F37 -->

CEED's & CEID's received

<-- S2F38

ERACK = 0

CEID, RPTID's & values received

<-- S6F11

Sometime later, an event occurs

Acknowledge report

S6F12 -->

5.2.2 Variable Data Collection

This capability facilitates synchronisation and initialisation. It enables the host to

request equipment data variables, but should not be used for discrete data.

The host can request any, previously defined, RPTID (see 3.2.1). The equipment sends

current values for Status variables (SV's) and Equipment Constants (ECV's). Discrete

variables (DVVAL's) are not valid.

Scenario:

Collection event report set up and send:

Comments

Host

Equipment

Comments

Host requests data variables

S6F19 -->

<-- S6F20

Equipment responds with list of variable data

for given RPTID

GEM Manual for DEK Printers Capabilities

Issue 1.1 March 20th, 2014 Page 26 of 152 Page 26 of 152

5.2.3 Trace Data Collection

This capability enables reports to be sent at fixed intervals. This is achieved as follows:

The host initialises a trace by sending S2F23. This message defines the trace

report including, time interval (DSPER), total number of samples (TOTSMP),

the number of samples per trace report (REPGSZ) and a list of data to report

(SVID's). The host also provides an identity for the trace (TRID) so that it can

later differentiate between simultaneous traces.

The total number of reports sent will be TOTSMP/ REPGSZ unless the host

sends a new S2F13 with the same TRID, when the trace replaced by a new one.

The host can end a trace by sending the same TRID, with TOTSMP = 0.

For a detailed example, of trace data collection, refer to note A.4 of SEMI E30 standard.

Scenario:

Collection event report set up and send:

Comments

Host

Equipment

Comments

Trace Data Initialisation Request

S2F23 -->

<-- S2F24

Acknowledge trace init.

[DO] TOTSMP / REPGSZ times

[DO] REPGSZ times: collect

SVID1-SVIDn data, wait DSPER

[END_DO]

<-- S6F1

Send report.

Acknowledge report

S6F2 -->

Optional terminate. TOTSMP = 0

S2F23 -->

<-- S2F24

Acknowledge premature terminate. Stop trace.

[END_DO]

GEM Manual for DEK Printers Capabilities

Issue 1.1 March 20th, 2014 Page 27 of 152 Page 27 of 152

5.2.4 Status Data Collection

The host can use this capability to request selected status information. It provides for

synchronisation of equipment status.

To obtain a status report, the host sends a request with a list of specific SVID's. The

equipment will respond with a list of status values.

Scenarios:

Equipment status variable report request:

Comments

Host

Equipment

Comments

Host requests report of selected status

values.

S1F3 -->

<-- S1F4

Equipment replies with requested data

Equipment status variable namelist request:

Comments

Host

Equipment

Comments

Host requests equipment to identify

selected status values.

S1F11 -->

<-- S1F12

Equipment replies with requested status variable

descriptions.

5.2.5 On-Line Identification

Using this capability, the host can confirm the presence of the equipment. The

equipment will send its identity MDLN and software revision SOFTREV in response to