Define the WebVisu Version Constraint
The reported environment is SoMachine Logic Builder 4.3 with visualization components limited to version 3.5.6 or lower and an indicated CODESYS 3.5.3 base. In that environment, one array works as the History element source, but the evidence does not establish a supported syntax for binding multiple arrays to multiple graph lines.
Do not assume that a structure containing several arrays, an array of arrays, or an XY-chart configuration will work. The proposed nested structure is a question, not a confirmed WebVisu data format. The reported installation also lacks the XY Chart element, so instructions for adding multiple XY lines do not apply to this project.
Select a Supported Logging Architecture
| Approach | Evidence-supported behavior | Engineering constraint |
|---|---|---|
| History element with arrays | A single array displays successfully. | No supported multiple-array source format is identified. |
| Controller-managed FIFO arrays | The proposed design uses arrays 500 samples deep, a fixed logging interval, array rotation, and array-mean calculations. | This is a design proposal, not a confirmed capacity or performance rating. Validate controller load. |
| Trace imported from a file | A recorded trace can be loaded from the file system after the controller writes the data to a compatible file. | The required import file structure is not supplied in the evidence. |
| XY Chart | Multiple-line configuration was suggested for newer visualization software. | The element is unavailable in the reported environment. |
Implement and Verify the Practical Workaround
- Keep each logged trace in a controller-managed array. If using the proposed design, allocate 500 samples per trace and update the arrays at the selected fixed interval.
- Apply the available array-rotation function to implement FIFO behavior. Use the available array-mean function only after confirming that its input type matches the logger array.
- If multiple History lines cannot be configured, write all required trace data to a file and import that file into the Trace element. Determine the exact file format from the import controls available in the installed visualization version; the evidence does not define its fields or delimiters.
- Run the logger under the intended task intervals and monitor controller operation. The source reports controller crashes after minor Trace or task-interval misconfiguration, but does not establish a confirmed product defect or safe interval.
- Verify that every trace advances at the required interval, FIFO rotation preserves the expected sample order, calculated means match the stored window, and the imported Trace file reproduces all recorded channels.
Range selection is reported as unavailable in this software generation. If the application requires native multi-line array display or range selection, treat a visualization upgrade or a custom JavaScript graph as a design decision; compatibility and implementation details are not established by the evidence.
FAQ
How do I display multiple arrays in a WebVisu History graph?
The evidence confirms only a single working array and provides no validated syntax for multiple History lines. Do not deploy a nested structure until its binding behavior is verified in the installed visualization version.
Can WebVisu load a recorded trace from a file?
Yes. Write all required trace data to the file system, then load the file into the Trace element using the format accepted by the installed import controls.
Why is the XY Chart missing in SoMachine Logic Builder 4.3?
The reported installation is limited to visualization components version 3.5.6 or lower and does not provide the XY Chart element. Use the available History or file-imported Trace path, or evaluate an upgrade before designing around XY configuration.