Specifications

Alarms can be divided into groups and displayed by system or levels, or can be displayed all at the same time.
Troubleshooting multiple alarm occurrences may be complicated in a large system, however, breaking down the alarms
leads to effective and fast resolution. The alarm log data can be saved in the built-in SRAM even if the power fails.
Where is
the error?
What kind
of error is it?
When will
recovery occur?
Alarm
occurrence
Upper step
Alarms by line
Alarms by unit
Middle step
Alarm content
General step
Trouble
shooting
Detail step
Step
2
Step
3
Step
4
Step
1
Device "A" error
Out of material
Material
replenishment
Line "A" stops
Example of using the four steps
Information such as the channel No., network No., station No., and CPU No., has been added to the system alarm
making it possible to identify the abnormal device just by looking at the current alarm.
The number of the screen and the ID of the object that caused the alarm are also recorded and displayed, so that
operators can easily identify what operations caused an alarm.
CH1
Station No. 2
Network No. 1
Station No. 1
Station
No. 3
Station
No. 4
CH2
CH3
CH4
G01-402 communication time out.
Check the communication path or unit.
DEV/Ch: 1 1-2/main unit function
Error!
The alarm function works with the logging graph, so that the situation at alarm occurrence or graph error can be seen easily.
Check graph at alarm occurrence!
Check alarm at graph error!
Time specification jump
Display error
as graph
Alarm
occurrence
Identify the cause of alarms
System Alarms
Easily search for causes when alarm occurs
Alarm Function
An Easy and Flexible HMI Solution
GT27
GT27
Graphic Operation Terminal
18
Functions