Example for integrating the script editor for Schneider Modsoft components

This scripting solution enables an improvement with regard to the use of Schneider Modsoft components.

Necessary files for this script function:

File name	Description	Function
ScriptBeforeEdit.exe	Available in the scripting package	Links the configurable project file with an editor, depending on the Component type ID
ScriptBeforeEdit.ini	Can be edited with a text editor	Defines the script BeforeEdit for a specific component type ID
SchneiderModsoft.script	Can be edited with a text editor	versiondog script, which was processed by the script interpreter
ModsoftCaller.bat	Can be edited with a text editor	Batch file for opening the Modsoft editor or another editor

Requirements for scripting solutions

The Schneider Modsoft editor needs to be installed and licensed on all computers for the editor integration can be set up with the UserClient
We recommend that you install Modsoft on all computers under the same directory (e.g. C:\Modsoft\editor)

Set up script

Activate ScriptBeforeEdit.exe

Copy the application into the Server scripting directory for automatic update of client

Edit ScriptBeforeEdit.ini

We recommend that you edit the ScriptBeforeEdit.ini taken from the Server scripting directory for automatic update of client. If this file is not yet available, use the template from the scripting package.

Activate the Schneider Modsoft script by entering the Component type ID connection to the script in the section [General])
If more than one different component type is connected to the script, a new entry is required for each component type
Save the file
Copy the file into the Server scripting directory for automatic update of client

General example:

                            [General]
                            // Mapping for CoDeSys editor component type
                            <ComponentTypeID>=SchneiderModsoft
                        

Example:

1 2	[General] 5A527AA2D4A846208BB8648EED1146BD=SchneiderModsoft

SchneiderModsoft.script

Open the SchneiderModsoft.script in the text editor

Script:

                            Function ScriptBeforeEdit
                            {
                            $def::var1 = C:\Modsoft\Editor
                            $def::var2 = $func::getfilename($vdog::specific->SelectedFile)
                            $def::var3 = $func::getshortdir($vdog::specific->WorkingDir)
                             
                            // Create UPF file:
                            file.create $def::var1\$def::var2.upf
                            {
                            write.line rt_directory $def::var1\RUNTIME
                            write.line tmp_directory $def::var1\TMP
                            write.line files_directory $def::var3
                            write.line names_directory $def::var
                            }
                             
                            // ENV edit:
                            file.replace $def::var3\$def::var2.env
                            {
                            row.1 $def::var3\
                            row.2 $def::var3\
                            row.3 $def::var3\
                            row.4 $def::var3\
                            row.5 $def::var3\
                            }
                             
                             
                            // Update Modsoftcaller:
                            file.copy
                            {
                            source $vdog::myrundir\ModsoftCaller.bat
                            dest $def::var1\ModsoftCaller.bat
                            }
                             
                            // Execute Modsoft-Batch:
                            call $def::var1\ModsoftCaller.bat
                            {
                            arg $def::var2.upf
                            arg $def::var2.env
                            wait 0
                            }
                             
                            done
                             }
                        

Carry out the following changes:

Lines	Description
3	Edit the absolute path to the Modsoft editor.
37	In this example, only the file name is given as argument. The line for the absolute specification of the UPF file:arg $def::var1\$def::var2.upf
38	In this example, only the file name is given as argument. The line for the absolute specification of the ENV file:arg $def::var3\$def::var2.upf
39	Remove line, if you want to wait until the editor is closed.

Save the file
Copy the file into the Server scripting directory for automatic update of client

Edit ModsoftCaller.bat

Open the file ModsoftCaller.bat in the text editor.

// swap to Modsoft directory

cd \Modsoft\editor\

C:\Modsoft\editor\Modsoft.exe /f%1 %2

Delete REM upf-file

del %1

If necessary, adjust the Modsoft editor directory.
You can also call another application here (e.g.: the USB driver for the Modbusplus coupling).
Save the file.
Copy the file into scripting directory for automatic update of client.

For more information about activating scripting functions and moving scripts into the server-sided scripting directory and/or the client-sided scripting directory, see Activate scripting.