New in the Community? Get started here

Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Geo SCADA Expert Forum
Make the most of your remote operations with end-to-end solutions with Process Automation’s SCADA and Telemetry Solutions. With the challenges that remote sites present, reliable communications for remote operation, monitoring & management are vital in enhancing productivity and ensuring profitability.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Crewman

How to set quality to bad when Modbus is down?

Hello everyone.

 

I've noticed that my ClearSCADA (80.6914) don't write to archive value with bad qulity for modbus points when connection to modbus server is lost. 

 

Here I shut down modbus server and point has quality  "Last Known Value".

2019-12-11_15-34-03.png

 

And here it started again.

2019-12-11_15-42-25.png

 

But in Historic List there are only Good values.

2019-12-11_15-44-09.png

 

It's a problem. I need to see bad quality values in archive when connection was lost.

As a solution I can make for every modbus point a couple Internal point and a logic that will copy values with quality. This Logic will link quality in internal Point to Modbus Scaner Status. But maybe there is more easy way?

 

Also I've found interesting option in Advanced Modbus - Direct Outstation - Log Historic Value On Communication Failure. It sounds as that I need. I just can't make this advanced thing work.

14 REPLIES 14
Highlighted
Sisko

Re: How to set quality to bad when Modbus is down?

The general principles of Remote SCADA (unwritten!) are that historic data should only be logged if it came from the device (and the quality reflects what the device's opinion of the signal was - e.g. if it was from a connected instrument and the instrument failed).

 

However, the Advanced drivers support adding single historic values when devices fail. I do recommend you use Advanced drivers when available for the protocol you want for all sorts of reasons. 

Highlighted
Crewman

Re: How to set quality to bad when Modbus is down?

Oh, then I just need some help with Advanced.

 

I have a simple modbus slave simulator that runs on my local computer just for test. 

 

2019-12-11_17-54-37.png

 

With simple modbus driver i see it without any troubles. So I need to connect to it with advanced. As help says it means link Dircet Channel - Direct Outstation Set - Direct Outstation - Point.

 

1. My Direct Channel settings

2019-12-11_17-52-37.png

 

2019-12-11_17-53-46.png

2019-12-11_17-56-33.png

 

2019-12-11_17-57-38.png

 

2. My Direct Outstation Set settings

2019-12-11_17-58-55.png

 

2019-12-11_17-59-20.png

 

3. My Generic Direct Outstation settings

2019-12-11_18-00-39.png2019-12-11_18-01-34.png

 

Direct and PSTN - all checkboxes are off.

2019-12-11_18-03-31.png

 

4. And finally Generic Analog Input Point

 

2019-12-11_18-08-24.png

 

 So that I have now.

 

2019-12-11_18-06-16.png

2019-12-11_18-09-23.png

 

2019-12-11_18-10-09.png

 

2019-12-11_18-11-11.png

 

I just can't understand what's wrong. For example here is config for Simple Modbus that works (when InService is on).

 

1. Scaner

2019-12-11_18-13-10.png

 

2019-12-11_18-14-33.png

 

2. Analog Point

2019-12-11_18-15-32.png

 

Highlighted
Ensign

Re: How to set quality to bad when Modbus is down?

Your original issue, your historic list doesn't show any values recorded during the outage, so you will never see the "Last Known Value". The trend only updates connecting the last value, before the outage and the first value after the outage due to a setting. In the trend, you can change the point's "Trace Style" to Line, or Step Last. Step last will show the same flat line trace that you were seeing during the outage.

 

 

Unrelated. It is possible to pass the quality of a Modbus point to an internal point by connecting ModbusPointName.CurrentQuality to InternalPointName.PresetQuality via some logic. I do this regularly when I need to total together several flow rates or volumes but need to maintain the ability of the internal point to show the quality of the Modbus points to indicate when an outstation is out of communications where my Internal Total is displayed. 

 

 

Highlighted
Ensign

Re: How to set quality to bad when Modbus is down?

That all looks correct.

I even tried it on mine with a Modbus simulator.

You could try 127.0.0.1 instead of localhost

 

Make sure the Simple Modbus scanner is not in service at the same time. Maybe your simulator only supports one connection.

 

You can enable Comms Logging on the Channel and see if there is anything in the log to give you an answer to what the problem is.

 

Your Modbus simulator may also have logging. Mine does and I could see connection requests but then it closed the port. On the Channel, I forgot to set Modbus to TCP, it was still on RTU.

Highlighted
Crewman

Re: How to set quality to bad when Modbus is down?

Of course I switched off InService for Simple Modbus Scanner when tried Advanced. Modbus slave don't even see it's requests int it's log. I just don't understand why this thing doesn't work.

I keep in mind this model with AP (.CurrentQuality) -> IP (.PresetQuality) and it's the only way I see as solution. But my DB will double in size and there are more redundant work to do .

Highlighted
Sisko

Re: How to set quality to bad when Modbus is down?

Would you mind posting an sde export of the config?

Have you contacted support?

Highlighted
Crewman

Re: How to set quality to bad when Modbus is down?

No problem, these my two groups. am - Advanced Modbus, sm - Simple Modbus.

I though that problem is because my lack of understanding in reading help so didn't ask support still.

 

 

 

Highlighted
Ensign

Re: How to set quality to bad when Modbus is down?

The channel is out of service in "am.sde", unlike the screenshot above.

Once I put the channel into service this configuration works for me.

 

Given that the channel state is showing "Disconnected" it looks like the Advanced Modbus driver isn't actually running. You can check if the driver is running from the "General \ Modules" page of the Server Status tool on the main server, as well as starting and stopping the driver.


Andrew Scott, Lead Engineer, AVEVA
Highlighted
Sisko

Re: How to set quality to bad when Modbus is down?

Thanks Andrew - you beat me to it!

Note that the analogue point had a Retrieval Interval of 'Continuous' so the driver will be kept busy polling - choose a suitable interval to match what you need.

You also do not have a Scan Group (Confidence Interval), which may be as required. This interval 'guarantees' update of value/time/quality at this interval. Be very careful to set this at the slowest rate needed, as on larger systems you can impair performance.

Highlighted
Sisko

Re: How to set quality to bad when Modbus is down?

Example master and slave attached to this posting.

Highlighted
Crewman

Re: How to set quality to bad when Modbus is down?

Yap, I switched InService On/Off in advanced and simple, so it could happens in the export I gave. 

But I have found. It's just....License....

As I understand, I need SCADAPackModbus License, that I don't have. 

Configuration above will work with appropriate license very well.

 

Thank you very much for help guys. I'm really appreciate it. 

 

Ensign

Re: How to set quality to bad when Modbus is down?

If you're only using generic Modbus then you can just uninstall the unlicensed SCADAPack Modbus extension driver rather than obtaining a licence for it.


Andrew Scott, Lead Engineer, AVEVA
Highlighted
Ensign

Re: How to set quality to bad when Modbus is down?

I can confirm from my own system that even using Advanced Modbus, Generic Analog point with Scan Group (Confidence Interval) turned on, that no values are recorded in the Historic List while the Outstation is out of comms.

Highlighted
Crewman

Re: How to set quality to bad when Modbus is down?

Here is that I saw when cut off Modbus Slave and after enabled it.

 

изображение_viber_2019-12-12_13-42-40.jpg

 

Ih HL there are my national chracters but we see that one bad value is colored by violet.

 изображение_viber_2019-12-12_13-43-03.jpg

 

In Generic Direct Outstation enabled Log Historic Value on Communication Failure.