Updating DNP3 Analog Output Points

[Anonymous user]

Hi All,

Is it possible to get unsolicited updates for ClearSCADA DNP3 Analog Output points.

We have ClearSCADA communicating with a SCADAPack ES RTU. Setpoints are configured as generic DNP3 AO objects that are used in the RTU logic. There is also an OIP connected to the RTU via Modbus which can be used to adjust the setpoints locally. We want ClearSCADA to update when the point value changes. However, even though the point is configured as Class 1 with unsolicited events enabled and a small deadband it doesn't update in CS until a Class 0 poll occurs.

[AndrewScott]

ClearSCADA will update the point if the SCADAPack generates a DNP3 analog output event (group 42) when the point changes value. It sounds like no DNP3 event is being generated by the SCADAPack when the value changes. A comms log in ClearSCADA would confirm what is being received (or not) from the outstation.

Are other unsolicited events being reported by this outstation, is it just analog output events that aren't being reported?

Have you enabled unsolicited in the SCADAPack (see "DNP3 \ DNP3 Events" in SCADAPack E Configurator) and also enabled it in ClearSCADA (see "Enable Unsolicited Messages" in outstation properties)?

[Anonymous user]

All other analog points update correctly unsolicited or otherwise.

The Point Type in the SCADAPack is Derived and the DNP3 Static Object Type is g40v1.

The point Control Object in ClearSCADA is g41v1.

[AndrewScott]

It looks like ClearSCADA, the outstation and point are all correctly configured to generate a DNP3 event, so the question becomes, is an event being actually being generated by the outstation when the analog output value changes? A ClearSCADA comms log could be used to confirm whether or not an event is being sent by the outstation.

[Anonymous user]

Hi Andrew, there are events being generated by the RTU and received by SCADA but they are not being recorded by SCADA.

We are getting the following result from the driver logging:

Transport Header: FIR:1, FIN:1, Sequence:47

Application Control Field: FIR:1, FIN:1, CON:1, UNS:1, Sequence:10 Function Code: 130 - Unsolicited message Internal Indications: 32-bit Analog Input Change Event with Time (g32v3), Prefix: 2 - Index (2 octet), Range: 8 - Count of Objects (2 octet) , Count: 1

The number recorded in the driver log is correct but until there is an integrity poll the point in SCADA is not updated.

There does appear to be a mismatch between the event type in the log which is an Analog Input and the point configuration in SCADA which is an Analog Output.

[AndrewScott]

If the RTU is generating a DNP3 event for an analog input point then this will not update an analog output point in the ClearSCADA database as these are two different and unrelated points.

So the question is why is the RTU generating a g32v3 analog input event rather than a g42v3 analog output event for this derived analog point? I don't know if this is a configuration issue or a possible bug in the SCADAPack.

You might want to try asking about this in the SCADA & Telemetry Devices Forum for SCADAPack devices or raise a support ticket.

[BevanWeiss]

@Anonymous user  Can you please upload here your .RTU config?

You can strip out any sensitive info, but you need to leave in the Events Tab, and all the Point configuration.

I very much doubt this is a bug in SCADAPack firmware.

I think you've misled @AndrewScott with showing the g30 event section from ClearSCADA.

It's quite unusual to want to have g40 unsolicited messages.  I can envisage a reason for them, but are you sure you don't just want to use the ClearSCADA setting for 'Update Point Value on Success' on the Control Tab?

This way when ClearSCADA gets the ACK from the DirectOperate it will update the CurrentValue also.. which is normally good enough.

If you are indeed writing back to the Analog Output point within the SCADAPack (using an OPERATE instruction), then I can see why you may want the unsolicited, and I've not had issues with this in the past.