[Mikhail]

Periodically I do similar tests. I should repeat them.
That’s funny, but a few years ago SCADA-Web run stable on IE for days. And Chrome supported Silverlight 🙂
I think that the cause of memory leak is reloading frames within web page. This approach is outdated and will be changed to REST API.

[Mikhail]

Shouldn’t apply delay in case of any error too?

I think that you did is enough.

Where can I get it?

It will be included in the next version. In case we found the workaround I think you shouldn’t update Communicator. But if you wish, I can send it by email.

[Mikhail]

As I realized the most fast communication if UDP is used directly for a serial converter without virtual port and C:\SCADA is ignored by anti-virus system.

[Mikhail]

Without a delay Communicator tries to write in the loop. So CPU become loaded.
I will add the fix in the core of Communicator.

Does the connection repair automatically or you need to restart Communicator?

[Mikhail]

I have an idea:
set Delay after request cycle parameter of the communication line to 100
Please write about the result

[Mikhail]

Unfortunately, write method is very simple:

        public override void Write(byte[] buffer, int offset, int count, 
            CommUtils.ProtocolLogFormats logFormat, out string logText)
        {
            try
            {
                SerialPort.DiscardInBuffer();
                SerialPort.DiscardOutBuffer();

                try
                {
                    SerialPort.Write(buffer, offset, count);
                    logText = BuildWriteLogText(buffer, offset, count, logFormat);
                }
                catch (TimeoutException ex)
                {
                    logText = CommPhrases.WriteDataError + ": " + ex.Message;
                }
            }
            catch (Exception ex)
            {
                throw new InvalidOperationException(CommPhrases.WriteDataError + ": " + ex.Message, ex);
            }
        }

It drops on SerialPort.Write, where SerialPort is standard .NET class.
Probably serial port driver causes CPU load.
Does your converter support direct connection as TCP client or TCP server without virtual port?
For instance, Moxa NPort converter works correctly if connection is lost.

[Mikhail]

Is there any known memory leakage that could make this?

Chart component uses JavaScript and web service. JavaScript has auto memory management and should work correctly. Let’s compare with other browsers. Close all other pages except chart.

[Mikhail]

Hi,
Is the only chart web page is open? I mean do you close the main web form with scheme or table view?

When you test the same with IE and Chrome please write about the result.

[Mikhail]

Please, post a part of the communication line log when this situation occurs.
If you stop communication line (from context menu), CPU load become low?

[Mikhail]

Hello,

communicator not taking over the CPU.

Sorry, I didn’t catch what the error is?

[Mikhail]

Please download Rapid SCADA again and update SCADA-Web application. Is it possible to just overwrite the files from ScadaWeb.zip

[Mikhail]

I observed this also, is there a reason it starts up minimised to the tray?

Let me think about it 🙂

[Mikhail]

Are the requested files here C:\SCADA\ScadaWeb\config\ ?
Do use use default installation directory C:\SCADA ?

[Mikhail]

The beta version of the new schemes will be released in the summer 2016. In the first time it will support the existing format of schemes. SVG will be supported a bit later. Bootstrap is used. New components such as gauges will be added in the same time as SVG.
Thank you for your patience 🙂
In Chrome:

[Mikhail]

Hello,
It is collapsed to a tray icon after start. Look for it in the right botton corner of your desktop.

[Author]

Posts