Dear Customer.

We have uploaded the requested updates to here.

The modifications are as follows:

1. Previous Value Reading Feature Added

A new function has been added to read previous values.

You can retrieve the value by calling the script function scada.getPreviousValue('station.point').

You can also check previous values on the Scada Summary screen.

2. Option to Execute Scripts in a Separate Thread

Scripts can now be executed in a thread other than the main thread if necessary.

To run a script in a separate thread, check the “Use Multithread” option as shown in the image below.

This feature operates in an interleaving manner rather than true parallel processing. For long-running functions (e.g., remote.setValue), control can be transferred to another thread while waiting for the call to complete.

3. Error Handling for Invalid Points in remote.setValue

If remote.setValue('not exist point') is called for a non-existent point, an error will now be thrown.

4. Script Example for Context Management

We’ve included an example for managing context in scripts.

For state management, you can either use app.getProperty and app.setProperty to store state in variables, or define a Python class to manage state.

If you have further question, please let us know.

Thank you

Dear Anygate,

It seems that running remote.setValue() on a point that does not exist does not return an error.

For example, I can run:

value = scada.getValue('station_name.point_no_exist')

and get the following error: invalid data name: station_name.point_no_exist'

but if I run:

result = remote.setValue('station_name.point_no_exist', 1)

print(result)

The output is:

True

I believe this should return a similar error like when running scada.getValue() on the point that does not exist.

Thank you,

Joe