Script example: editor integration for Schneider Modsoft components¶

This script solution enables optimization in handling Schneider Modsoft components.

Required files for this script function¶

Prerequisites for the script solution¶

• The Schneider Modsoft editor must be installed and licensed on all computers for which the editor integration is to be set up in conjunction with the UserClient.
• It is recommended that the Modsoft installation is located in the same directory on all computers (exampleC:\Modsoft\editor).

Setting up the script¶

Activating ScriptBeforeEdit.exe¶

Copy the application to the Server scripting directory for automatic update of client tab.

Editing ScriptBeforeEdit.ini¶

We recommend that you add any existing ScriptBeforeEdit.ini file from the Server scripting directory for automatic update of client tab. If this file does not (yet) exist, please use the template from the script package.

1. Activate the Schneider Modsoft script by entering the connection from the component type ID to the script in the [General] section.
2. If several different component types are to be linked to the script, a new entry must be made for each component type ID.
3. Save the file.
4. Copy the file to the Server scripting directory for automatic update of client tab.

Example:

[General]
// Mapping for CoDeSys editor component types
{ComponentTypeID}=SchneiderModsoft

Specific example:

[General]
5A527AA2D4A846208BB8648EED1146BD=SchneiderModsoft

Editing SchneiderModsoft.script¶

1. Open the SchneiderModsoft.script file in the text editor.
2. If necessary, make the adjustments listed in the following table.
3. Save the file.
4. Copy the file to the Server scripting directory for automatic update of client tab.

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
}

// Customize ENV:
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
}

Customizations¶

Line 3:

Adjust the absolute path to the Modsoft editor here.

Line 37:

In this example, only the file name is passed as an argument. For an absolute specification of the UPF file, this line is: arg $def::var1\$def::var2.upf.

Line 38:

In this example, only the file name is passed as an argument. For an absolute specification of the ENV file, this line is: arg $def::var3\$def::var2.upf.

Line 39:

Remove line if you want to wait until the editor is closed.

Editing ModsoftCaller.bat¶

1. Open the ModsoftCaller.bat file in the text editor.

   // Change to the Modsoft directory
   c:
   cd \Modsoft\editor\
   C:\Modsoft\editor\Modsoft.exe /f%1 %2
   Delete REM upf file
   del %1
   

2. If necessary, adjust the Modsoft Editor directory.

3. You can also call up another application here (e.g. the USB driver for the Modbusplus coupling).
4. Save the file.
5. Copy the file to the Server scripting directory for automatic update of client tab.

Related topics¶

• Activating Scripting