[kumajaya]

Still working as OPC UA client and server but in log:

Resolver could not find assembly 'Opc.Ua.Bindings.Https, Version=1.4.370.0, Culture=neutral, PublicKeyToken=bfa7a73c5cf4b6e8'
    requested by 'Opc.Ua.Core, Version=1.4.370.0, Culture=neutral, PublicKeyToken=bfa7a73c5cf4b6e8'

Communicator seems like not handle server restart nicely:

Data source ScadaServer: Error receiving telecontrol commands:
Scada.ScadaException: Incorrect format of data received from the server: unable to read data packet header
   at Scada.Client.ClientBase.ReceiveResponse(DataPacket request)
   at Scada.Client.ScadaClient.GetCommand()
   at Scada.Comm.Drivers.DrvDsScadaServer.Logic.ScadaServerDSL.ReceiveCommands()

Data source ScadaServer: Error receiving telecontrol commands:
System.IO.IOException: Unable to write data to the transport connection: Broken pipe.
 ---> System.Net.Sockets.SocketException (32): Broken pipe
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at Scada.Client.ClientBase.SendRequest(DataPacket request)
   at Scada.Client.ScadaClient.GetCommand()
   at Scada.Comm.Drivers.DrvDsScadaServer.Logic.ScadaServerDSL.ReceiveCommands()

[kumajaya]

My previous build still left some native library in place. For a big clean Administrator distribution:

cd ScadaAdmin/ScadaAdmin
dotnet publish ScadaAdmin.sln -c Release -r win-x64 --self-contained true -p:PublishReadyToRun=true -p:PublishSingleFile=true -p:IncludeNativeLibrariesForSelfExtract=true

[kumajaya]

Xct will remove no existence key, add a new key with a pink background cell (a mark for empty translation), but can’t detect content changes.

[kumajaya]

My modified Xml Content Translator always sync to github for base language 😀 A complete SCADA 6 xml language raw url included. Yes, I’ll make a pull request for Indonesian language support.

[kumajaya]

Don’t worry, Administrator run so smooth on Wine.

[kumajaya]

Scheme editor a bit problematic, the best solution for now run it using mono:

mono ScadaSchemeEditor.exe

[kumajaya]

Administrator run smoothly on Ubuntu Linux, feel like a native app. With all my patch to github, my publish command to make a single-file executable with dotnet runtime included:

From scada-v6 source root:

cd ScadaAdmin/ScadaAdmin
dotnet publish ScadaAdmin.sln -c Release -r win-x64 --self-contained true -p:PublishReadyToRun=true -p:PublishSingleFile=true

and Administrator ready for us in:
ScadaAdmin/ScadaAdmin/ScadaAdmin/bin/Release/net6.0-windows/win-x64/publish

I believe a fix for crypto problem to make OPC UA client works will come from Wine soon or later.

• This reply was modified 1 year, 6 months ago by kumajaya.

[kumajaya]

Sorry, the correct one:

<?xml version=”1.0″ encoding=”utf-8″ ?>
<ScadaDictionaries name=”English”>
<General>
<CultureName>en-GB</CultureName>
</General>
<!– ScadaCommon.dll –>
<Dictionary key=”Scada.Application”>
<Phrase key=”ProductName”>Rapid SCADA</Phrase>
<Phrase key=”ServerAppName”>Server</Phrase>
<Phrase key=”CommAppName”>Communicator</Phrase>
.
.
</ScadaDictionaries>

[kumajaya]

Unmodified vs modified Xml Content Translator:

https://drive.google.com/file/d/11wvlILgn69QzILmo7sKf57SBgPt7KHc9/preview

[kumajaya]

And you can make a statement, SCADA 6 will ready with almost perfect bahasa Indonesia user interface 😀

[kumajaya]

To support language auto detection, we need to add language information to xml base like this:

<?xml version=”1.0″ encoding=”utf-8″ ?>
<ScadaDictionaries name=”English”>
<General>
<Culture>en-GB</Culture>
</General>
<!– ScadaCommon.dll –>
<Dictionary key=”Scada.Application”>
<Phrase key=”ProductName”>Rapid SCADA</Phrase>
<Phrase key=”ServerAppName”>Server</Phrase>
<Phrase key=”CommAppName”>Communicator</Phrase>
.
.
</ScadaDictionaries>

[kumajaya]

Hi, Xml Content Translator use Google translate API to automate translate base language to target language. Even the translation results not always perfect but quite useful to speed up translation task, we can manually review and edit the results directly on the application after. This app can track online base language and sync to our translation target locally, remove the missing content and add the new one. You can continue to update the base language as you need and I can start translate it right now.

Original app show all Xml node attributes as translation base, not as we expected and can’t translate multi line words. That’s why a modification needed.

[kumajaya]

Support both SCADA 5 and 6 language files:
https://github.com/kumajaya/XmlContentTranslator/releases/download/1.11.2/XmlContentTranslator.zip

[kumajaya]

Download XML Content Translator for SCADA 6:
https://github.com/kumajaya/XmlContentTranslator/releases/download/1.11.1/XmlContentTranslator.zip

…and be happy translate SCADA 6 to your own language!

[kumajaya]

Administrator server stats will inform you about server status.

[Author]

Posts