Automation is primarily used for data processing and non-time-critical automation applications.
Sinolta Automation is a powerful automation tool that can be used for wide area automation.
Sinolta is not a replacement to PLC for time-critical applications.

Drag and drop one of the Automation Script function blocks (VB or C# .Net) function blocks to a module.
Double click on the function block to see the Editing dialog.
Select the reference tab at the top of the dialog box.
You can add a reference to the DLLs that you have received.
While the DLL files can be saved anywhere on the hard drive, we strongly recommend that you save the DLL files under
“C:\Sinolta projects\<>projectname>\\Cofigruation\Online\Autoamtion\DLL” folder.
Saving the DLL files in the above folder will include them in the Archived file, so you will always have a copy of the DLL with your project when arching and restoring.

You cannot create a logic point from Automation. You can create or delete logic points only from the Database Builder.

BWF is primarily designed to transfer large data such as files between the client and the server.
You can set up the real-time viewer to receive various types of files such as reports, images, drawings, etc. by sending a BWF request and ask the server to perform necessary functions to collect and transmit a response.
BWF can be a useful tool to send a database query to a BWF flow, which in turn can forward it to an external SQL server. The result can come back as a large string or a file to be viewed or parsed at the real-time viewer.

The Sinolta License only uses System Points (Digital, Analog, Text, Date, Logic, Timer and Alarm points) that are configurable within the Database builder.
All automation points that are not a System point will not be counted towards your license point count.

You can use Sinolta Automation API to exchange real-time data with an external application.
Set up an external application and include Sinolta Automation lib within your application. Now you can use Automation APIs (similar to what you would use inside a script function block) to subscribe, read/read and query various information.

The start-up module is used to initialize all variables before executing other modules. The Start-up modules can be used to read or write to external databases or files to retrieve necessary information that all other modules can use during the runtime.

Logic points are event-triggered modules that are defined as database points. They are created and removed as a database point whereas the Event-Triggered modules are entirely managed by the Automation Engine.
Logic points can be used to create easily reusable logic, primarily when used as part of a Class. Logic points that are part of a Class can use relative class names to handle dedicated logic for various members of their own class. This capability allows system integrators to create highly intelligent Classes with built-in automation that can be replicated by copying the Class objects.

Both modules are triggered by an event. Event Trigger modules are triggered by their configured Triggered points or called up from other modules.
The business workflow is triggered by the arrival of a Business workflow requisition message. When a message arrives, the Business workflow module is triggered and uses the incoming message to process and then send a response. The Business Workflow module can be triggered from outside of Automation, such as from an HMI screen, Excel or a webpage.

There are two ways that this can be achieved:
Use the Event Modules and add the points that are used to calculate the logic as trigger points. Note that if you have multiple trigger point, any one of them will result in the execution of the module.
Set up a Data Simulation task. Add a dedicated point with a sub-second pulse (square wave) simulation. Use this point as a sub-second trigger point.
We strongly recommend the first option as it is much quicker and also does not use any CPU when there is no change in your points. Using this method, you can build very large logic routines that are only triggered when needed resulting in a more efficient system.

After making changes to an automation module, right-click on the editing area of the module and select Set Online. The edits of that module will be published to the Automation engine and will begin executing without restarting all the modules.
Using Module update by publishing the current module, suspends only the current module, transfers the existing module to the server and resumes the execution of this module. The whole process takes a few milliseconds without interrupting the operation of other modules.