Limits¶
These are the declared limits of the product. A project that exceeds one is refused when it is compiled, so it is found at your desk rather than as a stuttering panel on a machine. They are also the numbers for a datasheet.
| Limit | Value |
|---|---|
| Tags | 512 |
| Alarms | 128 |
| Screens | 32 |
| Widgets per screen | 64 |
| Raw CAN frames | 32 |
| Raw CAN signals in total | 128 |
| Published MQTT tags | 64 |
| Distinct Modbus TCP targets | 4 |
| Retained variables | 64, or 16 without a memory chip fitted |
| WebVisu clients | 2 |
Why a limit is a feature¶
A limit that is checked is a promise about behaviour. Without it, a project that is slightly too big does not fail — it runs badly, on a machine, in front of a customer, and the reason is nowhere near the symptom.
Board limits are separate¶
Beyond these, a project is checked against the board it is meant for: whether the board has a display of the right size, whether it has the buses the project uses, whether the pins a project wants are free, and whether the package fits the flash slot. Those depend on the board, not on the product — see the hardware reference.