Hello. There are situations when limiting the number of events to 100 per day is not enough and this leads to the fact that an extremely important function disappears completely, and this is a big problem. Let me explain. Most often, events are used as alarms, and there are not too many of them, everything is ok. But when some kind of emergency or malfunction occurs, one accident often leads to another - this is a feature of the construction of many engineering systems. As a result, a dozen or more events can be sent at a time. Further, when the engineer fixes the malfunction, events usually also occur during the work and during the start-up of the equipment, their number varies, but a situation may arise when the limit has been exhausted. As a result, after the fault is cleared, the event function (critical function!) disappears completely. This is very bad.
In addition, in the type setting of each event, in addition to the “critical” and “attention” types, there is also the “information” type. But after all, information is not an abnormal type of event, but a completely working, current one, that is, it is the type of data that constantly comes in like a regular variable. For example: a door has opened or the appliance has heated up to the set temperature, etc. How can current information be limited to 100 per day?
I don’t really understand the reason for this limitation. After all, we can use a huge number of integer or float variables, data on them goes continuously, they are stored in the archive, there are a lot of them, they are not limited (and cannot be limited, because then the meaning is lost), why are events limited , and such a small number?
It would be great if the Founders reconsidered this critical function.
Thank you for reading to the end