Known limits
8 min readTroubleshooting
Known limits for Live, remote monitoring and TV, script engines and installation, and a setting that does not work. Next to each limit it is stated what to do.
What this topic contains
The following are behaviors that the product does not cover in this version, either deliberately or not yet. Each row has been verified against the code and the user interface. The limits of the communication drivers are in their own topics (Connection diagnostics).
Design and operation: summary by section
The limits below are described in detail in the relevant topics; this table collects them at a glance. The limits of the drivers themselves (such as unsupported data types) are in the driver topics (Drivers).
| Field | Limit | Details |
|---|---|---|
| Acquisition cycle | On change is not a separate read mode; Live converts a cycle with a duration of 0 to 1 s. For fast reading, select a cycle such as 100 ms. | Cycles |
| Connections | To connect to the same PLC with a second protocol, the same IP cannot be given to the second connection; there is no automatic switchover to a standby PLC. | Connections table |
| Tag errors | The tag error message of the driver is not shown in Live; only the connection state and the last error message of the connection are visible. | Connection diagnostics |
| Animations | For control objects (trend, alarm, recipe, report, camera, Screen window) Live applies only position, size and visibility; the Flashing, Opacity (%) and Angle bindings have no effect. | Animations |
| Events | The Release event runs if the mouse button is released over the object; it does not run if it is released outside. Jog bits of the form “1 on press, 0 on release” can remain at 1. | Events and functions |
| Controls | The Close button setting of the Screen window and the Users editable setting of the User view have no effect in Live. | Controls |
| Menus | An unauthorized menu item is drawn inactive and no warning appears; buttons that do not fit in the horizontal toolbar are cut off; hiding a screen from the Navigation menu does not block access to it. | Menu design, Navigation menu |
| Alarms | A Help text cannot be entered for an analog alarm (it exists only for discrete alarms). | Alarm definition |
| Reports | The Record time switch in Additional fields has no effect; every record always carries a time. | Report design |
| Users | The Level value of the group is not used in Live. A deleted authorization makes the object bound to that authorization open to everyone. | User administration, Applying authorizations |
| Tasks | If the On change cycle is selected in a cyclic task, the task is never scheduled. | Scheduled tasks |
| Device configuration | Computer name and Operating mode are not used in Live. | Device configuration |
Live
| Limit | What to do |
|---|---|
| Live runs only one project at a time. When the project is changed, monitoring, alarms and logging stop until the new project is opened. | Open the projects one after another (Change project…); you cannot run two at the same time. |
| A change made in Studio is not reflected immediately in a running Live. | Upload the project to Live and reopen the project in Live. |
| The Live settings › General › View › Font scale (%) field has no effect: Live does not read this value. | Select the font size in Live per station with the Font size buttons in the system menu. Changing the field has no effect. |
| In local Live there is no theme switch in the system menu. The theme comes from the Default theme setting in the project: Light, Dark or Automatic (by time of day) (dark between 19:00 and 07:00). | Select the theme in Studio under Live settings. A user monitoring from a browser has their own theme button. |
| The on-screen keyboard is available only in the Turkish Q layout and works only in the local Live window. | If another layout is needed, use a physical keyboard. |
| The window, keyboard and additional application settings do not apply in browser monitoring or on the TV. | Consider these settings only for the Live computer. |
| The event log, the alarm records and the recipe transfer log are not deleted automatically. | Watch for the disk filling up; back up and delete old monthly files (Files and folders of Live). |
The passwords of connections that require a user name and password are stored as plain text on the computer in the file baglanti_sifreleri.json. | Restrict access to the .veri folder to authorized Windows users. |
| The connecting state is not shown in the connection status; no connection is displayed until the connection is established. | Wait for the error message to appear (Connection problems). |
Remote monitoring and TV
| Limit | What to do |
|---|---|
| Browser monitoring uses plain HTTP; there is no HTTPS. Passwords and data are not encrypted. TV addresses are password-free by default. | Do not expose it to the internet; use a VPN (Remote access over VPN). If it is not needed, turn off TVs watch without password. |
| The viewer is read-only: there is no control, alarm acknowledgement or setting changes. | Do these tasks on the Live computer. |
| Scripts, tasks and drivers do not run in the viewer or on the TV; they run only on the Live computer. | Put the logic in Live; the viewer sees the result. |
| The port must be in the range 1024 – 65535. If another program is using it, the server is opened on a random port bound to this computer only. | In Studio, change Remote monitoring › Port. |
| 5 failed logins from the same address lock that address for 60 seconds. | Wait, or correct the password. |
| A maximum of 8 TVs can be defined; the display sequence has at most 40 rows; the duration is 5 – 3600 seconds. Pop-up window and template (fixed area) screens and the fixed upper / lower areas are not shown on the TV. | Design full screens for the TV. |
| The second-display TV requires a display that is covered neither by Live nor by the multi-monitor setup; otherwise the TV window does not open. | Monitor the state in Live from the system menu › Remote monitoring… window (Multi-screen and TV). |
| Multi-screen is applied only in full screen. | Leave Open in full screen on. |
Scripts
The script engines are the product's own engines and support a subset of the languages. The full scope is given in the language topics (VBScript, JavaScript, C, Python).
| Limit | What to do |
|---|---|
| A VBS, C or Python call can compute for at most 30 seconds; waiting, database and window times are not counted. There is no limit in JavaScript: an infinite loop can lock up the interface. | Do the waiting with a scheduled task, not with a loop. |
| In VBS, C and Python, a call that arrives for the same trigger while the previous call is still running is skipped. JavaScript has no such check. | Lengthen the task cycle (Script and task problems). |
| There are no breakpoints, step-by-step execution or autocomplete. There is no reference panel for JavaScript either. | Print a trace (Trace, printf, print) and look at the event log. |
VBS: there is no Execute, ExecuteGlobal, Eval, GetObject, GetRef, On Error GoTo etiket or Resume; Class_Terminate is not called. | Use Err with On Error Resume Next. |
VBS and Python: there are no HMIRuntime.Alarms, AlarmLogs, DataLogs, Logging or MenuToolBarConfig; generating and acknowledging alarms and archive logs cannot be done from a script. | Generate the alarm with a definition bound to a tag; do the logging with an archive definition. |
C: bit fields, long long / __int64, K&R parameters, goto to a label in an inner block and named initializers produce a compile error; scanf, gets and getchar do not exist; a real DLL cannot be loaded. | Adapt the code to these rules. |
Python: async / await, eval, exec, threads, network access and third-party packages (numpy, pandas, requests …) are not available. | For database work, use ODBC with pyodbc. |
The database connection is stateless: there are no transactions and no temporary tables. WScript.Shell.Run starts the program but does not wait for it to finish. | See the topic Database access. |
| The database, program execution and file permissions are off by default. These functions do not exist at all in JavaScript. | Turn on Script permissions only in a project you trust; use VBS, C or Python for these functions. |
Installation
| Limit | What to do |
|---|---|
| Windows 10 or later and .NET Framework 4.8 are required. Windows 7 and 8 are not supported. | Update the computer (Installation). |
| If WebView2 Runtime is not installed, the setup downloads it from the internet. On a computer without internet access, Studio and Live do not start until Runtime is installed. | Copy the Evergreen Standalone Installer from another computer and install it. |
| The setup program is not signed; Windows SmartScreen may show a warning. | After making sure of the source of the file, select Start anyway. |
Uninstalling deletes the logs folders and the two settings files. | Before deleting, copy the logs needed for support (Log files). |