Rapid SCADA 6 Beta

Forum Home Forums Uncategorized Issues Rapid SCADA 6 Beta

Viewing 15 posts - 46 through 60 (of 82 total)
  • Author
    Posts
  • #10999
    Mikhail
    Moderator

    For the next beta update we should at least add historical and event reports. Currently the work is in progress.

    #11176
    Mikhail
    Moderator

    @123abc56, deadband logic is updated and will be included in the next release.

    #11180
    kumajaya
    Participant

    @Mikhail I just writing how to build SCADA 6 on VS Code in development section and I have to wait for a moderation? It wasn’t like that before.

    #11189
    Mikhail
    Moderator

    If a post contains a lot of hyperlink, it can be automatically blocked by the forum protection system. Sometimes, it’s more handy to provide a one link to Google document for example.
    I found and accepted your post.

    #11250
    Mikhail
    Moderator

    The scada_6.beta.10.zip update has been released. Download link in the beginning of the topic.
    What’s new:
    – Historical data and event reports
    – Fixed OPC UA client connection error
    The configuration database has been changed

    To update the configuration database:
    1. Add the ArchiveKind table to your projects by copying it from the project template of the Administrator app.
    2. Set the type of archives in the Archives table (optional).
    3. Upload the project for execution.

    If you encounter errors related to the installation package (for example, the required dll is missing), write to this topic. Please write functionality errors in separate topics indicating version 6.

    #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()
    #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 1 year, 6 months ago by kumajaya.
    #11254
    Mikhail
    Moderator

    System.IO.FileNotFoundException: Could not load file or assembly ‘PlgMain.Report

    Fixed. scada_6.beta.10.zip was updated.
    Thank you.

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

    This error message does not affect OPC UA. Discussion with OPC foundation is here.

    Communicator seems like not handle server restart nicely

    How to reproduce this issue?

    #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.

    #11272
    Mikhail
    Moderator

    While Server is restarting, connection errors in Communicator is a normal situation. Communicator reconnects when it’s possible.

    #11281
    kumajaya
    Participant

    Just a little worried because no confirmation after back connected.

    I found a glitch on mobile browser in portrait mode and found it the printer icon move down because no horizontal space left.

    #11296
    Mikhail
    Moderator

    Just a little worried because no confirmation after back connected.

    It would be good to improve logging.

    found it the printer icon move down

    Fixed. Will be included in the next release. Thank you.

    #11299
    victorlam
    Participant

    Hello,

    May I know if the version 6 (six) will be the official release by end of the year?

    #11301
    kumajaya
    Participant

    @Mikhail A good or a bad idea? https://drive.google.com/file/d/1utNnWR4-kXuTepxcD03yoQtjjSb-SbFF/preview

    – Partial PWA support
    – OS info on about page
    – User agent info on user profile

    #11306
    Mikhail
    Moderator

    Hello,

    May I know if the version 6 (six) will be the official release by end of the year?

    Yes, we plan to release it this year. The official release will be very close to the current beta version.

Viewing 15 posts - 46 through 60 (of 82 total)
  • You must be logged in to reply to this topic.