6 hours ago
Thank you for the clarification.
Yes, we understand that the RGB control logic itself can be handled with native widgets, a global ETS object, or LM scripting when needed.
Our remaining question is mainly about the recommended architecture for the visualization layer in the new Visu.
Our goal is to build a single RGB supervision page with a custom user interface, including:
So what we want to confirm is the following:
For this type of advanced RGB supervision page in the new Visu, is the recommended / supported approach to:
If this understanding is correct, we will proceed with that architecture.
Thank you.
Yes, we understand that the RGB control logic itself can be handled with native widgets, a global ETS object, or LM scripting when needed.
Our remaining question is mainly about the recommended architecture for the visualization layer in the new Visu.
Our goal is to build a single RGB supervision page with a custom user interface, including:
- a background floor plan,
- several RGB zones directly accessible from the plan,
- one global RGB control area,
- individual zone interaction (ON/OFF + color),
- and a more intuitive / modern page layout than a standard list of widgets.
So what we want to confirm is the following:
For this type of advanced RGB supervision page in the new Visu, is the recommended / supported approach to:
- use the floor plan image as the visual base,
- place multiple native Visu widgets on top of it as the interactive layer (switches, RGB/color widgets, buttons, links, indicators, etc.),
- group them visually into one custom page layout,
- and keep ETS / LM scripts only for the backend logic if some global behavior is required?
If this understanding is correct, we will proceed with that architecture.
Thank you.