Forum Home › Forums › Uncategorized Issues › Rapid SCADA 6 Beta
Tagged: Version 6 Beta
- This topic has 81 replies, 8 voices, and was last updated 2 years, 1 month ago by
Mikhail.
-
AuthorPosts
-
October 4, 2022 at 10:36 am #10999
Mikhail
ModeratorFor the next beta update we should at least add historical and event reports. Currently the work is in progress.
October 6, 2022 at 12:17 pm #11176October 6, 2022 at 3:19 pm #11180kumajaya
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.
October 7, 2022 at 11:15 am #11189Mikhail
ModeratorIf 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.October 12, 2022 at 2:40 pm #11250Mikhail
ModeratorThe 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 changedTo 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.
October 13, 2022 at 4:49 am #11251kumajaya
ParticipantStill 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()
October 13, 2022 at 5:16 am #11252kumajaya
ParticipantCan’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 2 years, 10 months ago by
kumajaya.
October 13, 2022 at 9:27 am #11254Mikhail
ModeratorSystem.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?
October 13, 2022 at 10:56 am #11256kumajaya
ParticipantYes, 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.
October 14, 2022 at 11:39 am #11272Mikhail
ModeratorWhile Server is restarting, connection errors in Communicator is a normal situation. Communicator reconnects when it’s possible.
October 14, 2022 at 2:04 pm #11281kumajaya
ParticipantJust 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.
October 17, 2022 at 11:34 am #11296Mikhail
ModeratorJust 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.
October 17, 2022 at 1:44 pm #11299victorlam
ParticipantHello,
May I know if the version 6 (six) will be the official release by end of the year?
October 17, 2022 at 3:15 pm #11301kumajaya
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 profileOctober 18, 2022 at 9:05 am #11306Mikhail
ModeratorHello,
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.
-
This reply was modified 2 years, 10 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.