TRS GEM Manual for Intel Ver 1.1 - 第24页
GEM Manual for DEK P rinters Capabilities Issue 1.1 March 20th, 2014 Page 24 of 152 Page 24 of 152 When event CEI D occurs, the equipment sends eve nt report S6F11, which includes the report(s) RPTI D. Multi -block re po…
GEM Manual for DEK Printers Capabilities
Issue 1.1 March 20th, 2014 Page 23 of 152 Page 23 of 152
Communicating
Enabled –
Online Local
Enabled –
Online Remote
Disabled
Enabled – No
Comm
Enabled –
Offline
5.2 Data Collection
5.2.1 Event Reports
This capability enables the host to receive machine variable data when specific events
occur within the equipment. The host can control which events will cause a report to be
sent and which data items to include in a report (dynamic event configuration).
In addition, the operator can control which specific events are to be written to the
equipment’s local event log. The operator can also view the events enabled by the host.
Appendix B shows the operator procedures to achieve this.
The following outlines the steps that must be taken by the host system in order to cause
an event report to be sent. See chapter 5 for details of SECS II messages referred to as
SxxFxx.
The Host defines unique report with it’s own id. RPTID using S2F33. A report
includes one or more machine variables.
The Host links one or more reports to a collection event CEID using S2F35.
The Host enables collection event CEID with S2F37.
GEM Manual for DEK Printers Capabilities
Issue 1.1 March 20th, 2014 Page 24 of 152 Page 24 of 152
When event CEID occurs, the equipment sends event report S6F11, which
includes the report(s) RPTID. Multi-block reports are proceeded by a S6F5/F6
transaction.
The host may request event reports at other times using S6F15. However, care
should be taken not to request discrete data in this way, since the data may not
be valid at request time.
The reports defined by the Host and the Events enabled by the host are saved in
a file called “gem.cfg” and are loaded when the equipment powers up.
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