{"id":5857,"date":"2022-06-22T13:58:04","date_gmt":"2022-06-22T13:58:04","guid":{"rendered":"https:\/\/doeet.com\/auto-stops\/"},"modified":"2022-11-23T10:11:46","modified_gmt":"2022-11-23T10:11:46","slug":"auto-stops","status":"publish","type":"page","link":"https:\/\/doeet.com\/en\/auto-stops\/","title":{"rendered":"Auto-stops"},"content":{"rendered":"
\n
\n
\n
\n
\n

Auto-stops<\/h1>\n

Create your auto-stops system to automatically justify machine stops by indicating their causes.<\/p>\n

Request more information<\/a><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n

Justify stoppages automatically<\/span><\/h2>\n

The Auto-stops doeet module allows setting a serie of conditions so that the machine’s alarms automatically justify a machine stop<\/strong>.<\/p>\n

This is especially useful when a stoppage may occur, the cause of which the operator does not know how to identify. The system will detect and display the cause on the terminal, self-justifying the shutdown.<\/p>\n<\/div>\n

\n

Configure your shutdown system<\/span><\/h2>\n

Configure the different systems and subsystems<\/strong> to which the shutdowns are linked. There can be several subsystems depending on the same system, which will occur if they are extensive process lines, or if we have machines divided by sections. It can also be applied to give priority<\/strong> to some subsystems over others.<\/p>\n

Indicate the shutdown lockout times<\/strong>, which is the time in seconds that the system or subsystem stores the signal to self-justify the shutdown. <\/p>\n<\/div>\n

\n

Configure<\/span> your auto-stops<\/h2>\n

First, we must create a cause of stoppage<\/a> with which we associate the auto-stop<\/strong>. We will indicate the machine to which it applies and its identification code, and if we want it to be visible to the operator.<\/p>\n

It identifies each shutdown, indicates the subsystem to be associated, its code, priority and blocking time<\/strong>. <\/p>\n

Activate the alarms if you want the operator<\/strong> to be alerted<\/strong> every time a shutdown is automatically registered. You can reset the auto-stops to reset all currently active ones.<\/p>\n<\/div>\n

\n

\"Auto-stops<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n

Advantages of the Auto-Stops system<\/h2>\n<\/div>\n
\n
<\/i>
\nReduce operator intervention time with the system.<\/div>\n
<\/i>
\nKnow the reality of the condition of your machines with the self-justification of shutdowns.<\/div>\n
<\/i>
\nCheck through the associated report for the alarm reasons for your equipment.<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

States of<\/span> stoppages<\/h2>\n

The states represent the signal<\/strong> labels of the machines<\/strong> in question: Active, fault, warning or running<\/strong>.<\/p>\n

We will indicate for each state the initial and final bit or if it is reset, in addition to the appropriate observations. After configuring the auto-stop, we must create a stop as an auto-stop<\/strong> and associate them using their code. <\/p>\n<\/div>\n

\n

See the auto-stops report<\/span><\/h2>\n

Doeet generates reports that associate the auto-stops with the variables<\/strong> configured in the system.<\/p>\n

The table of variable states or self-justification shows the combination of auto-stops and self-justifications<\/strong> for each subsystem. The report also shows the tags or machine states in the system. <\/p>\n<\/div>\n

\n

Auto-stop system functions<\/h3>\n<\/div>\n
\n

\"Auto-stops\"<\/p>\n<\/div>\n

\n