Owner's manual

Table Of Contents
1.11.4 Loss of Communications Link: Spooling
Communications may be temporarily lost with the Host from time to time. GEM message responses and
requests are automatically spooled to disk when this happens. When communications are restored the
messages on the SPOOL file are automatically sent to the Host.
Spooling is enabled for FmNT. The Host may query the SPOOLSTSATE and CONTROLSTATE
variables with the Selected Equipment Status Request message (S1F3) in order to establish the success of
REMOTE operations. In addition, the Host will receive spooling update messages from FmNT.
The default spool state can be set through the FmNT SECS/GEM Setup dialog box.
1.11.5 Communications Error Messages
Occasionally messages are garbled between FmNT and the Host. Garbled message device IDs and
streams result in FmNT replying to the Host with S9F1 and S9F3 messages. Further distortion of the
message results in the device ignoring the message which causes the Host to resend the message. See
4.2.92 S9F1 – Unrecognized Device ID and 4.2.93 S9F3 – Unrecognized Stream for details of the
message exchange.
1.11.6 Normal Communications
1.11.6.1 Alarm Notification
Alarms are reports of errors (caused by the program or the operator) or events which may result in
production or Equipment damage or events which may cause a safety hazard to workers. When an alarm
state occurs, FmNT initiates an alarm notification (message S5F1) to the Host. The Process State transfers
into the Alarm-Paused state and the Equipment stops dispensing and retracts the dispenser apparatus from
the board.
The Operator will need to correct the alarm condition and guide the machine through the Paused state to
the Idle State.
The Host may poll the Equipment to receive lists of enabled or existing alarms. When the Host sends a
List Alarm Data message (S5F6) the Equipment replies with a list of the current active alarms. The Host
may receive a list of the currently enabled alarms with the List Enabled Alarms Request (S5F7).
1.11.6.2 Remote Control Operations
Both the Host and the Operator are allowed to request runtime control of FmNT from each other. When
the control state is Local, only the Operator has the ability to command FmNT, and Host run commands
are rejected. Conversely, when the Host has control of FmNT, the Operator is limited to requesting FmNT
status displays and Help screens. The Operator can stop, abort, or pause the process from the Run
Window. Host will receive an event if the Operator presses any of the buttons from the Run Window.
Refer to Appendix B for the list of these events.
Both the Host and the Operator may request that control be turned over to the requester. Each change in
the control state machine generates a notification event to the Host.
1-16 Equipment-to-Host Messages