kumajaya

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 141 total)
  • Author
    Posts
  • in reply to: Buid Rapid SCADA 6 on Visual Studio Code #11259
    kumajaya
    Participant

    I’m not familiar with VS. The compiler try to find .NetFramework v4.8:

    error MSB3644: The reference assemblies for .NETFramework,Version=v4.8 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks

    and add per https://github.com/Microsoft/dotnet/tree/main/releases/reference-assemblies instructions:

      <ItemGroup>
        <PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3" PrivateAssets="All" />
      </ItemGroup>

    fix it.

    in reply to: Buid Rapid SCADA 6 on Visual Studio Code #11257
    kumajaya
    Participant

    It’s normal because no object reference anywhere yet. In VS Code terminal type:

    dotnet build ScadaCommon.sln -c Release

    You will got your first error because of cross compiling Windows app on Linux, modify ScadaCommon.Forms.csproj like:

        <Copyright>Copyright © 2022</Copyright>
        <EnableWindowsTargeting>true</EnableWindowsTargeting>

    Run again dotnet build, you will got your second error. Edit ScadaCommon.Svc.csproj like:

      </Target>
      -->
      <ItemGroup>
        <PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3">
          <PrivateAssets>all</PrivateAssets>
          <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
        </PackageReference>
      </ItemGroup>
    </Project>

    Run dotnet build again, profit!

    in reply to: Rapid SCADA 6 Beta #11256
    kumajaya
    Participant

    Yes, I confirm without https endpoints, UAExpert not list https access anymore but Opc.Ua.Bindings.Https.dll still requested.

    To confirm communicator exception, you can watch ScadaComm.log while restart Scada server.

    in reply to: Rapid SCADA 6 Beta #11252
    kumajaya
    Participant

    Can’t create historical data and event reports because PlgMain.Report.dll not included in ScadaWeb.

    System.IO.FileNotFoundException: Could not load file or assembly 'PlgMain.Report, Version=6.0.0.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

    • This reply was modified 3 years, 3 months ago by kumajaya.
    in reply to: Rapid SCADA 6 Beta #11251
    kumajaya
    Participant

    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()
    in reply to: Buid Rapid SCADA 6 on Visual Studio Code #11248
    kumajaya
    Participant

    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
    in reply to: XML Content Translator for SCADA 6 #11247
    kumajaya
    Participant

    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.

    in reply to: XML Content Translator for SCADA 6 #11238
    kumajaya
    Participant

    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.

    in reply to: Buid Rapid SCADA 6 on Visual Studio Code #11237
    kumajaya
    Participant

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

    in reply to: Buid Rapid SCADA 6 on Visual Studio Code #11230
    kumajaya
    Participant

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

    mono ScadaSchemeEditor.exe

    in reply to: Buid Rapid SCADA 6 on Visual Studio Code #11228
    kumajaya
    Participant

    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 3 years, 3 months ago by kumajaya.
    in reply to: XML Content Translator for SCADA 6 #11224
    kumajaya
    Participant

    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>

    in reply to: XML Content Translator for SCADA 6 #11223
    kumajaya
    Participant

    Unmodified vs modified Xml Content Translator:

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

    in reply to: XML Content Translator for SCADA 6 #11222
    kumajaya
    Participant

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

    in reply to: XML Content Translator for SCADA 6 #11221
    kumajaya
    Participant

    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>

Viewing 15 posts - 31 through 45 (of 141 total)