| [sparkplug-wg] 回复: How to support SCADA to device command in a Non-Persistent Connection case |
|
Thanks Bryce for the reply.
Yes, for SCADA like Ignition, I think it give the user enough flexibility to add additional logic on the host side to achieve that, but for SCADA like Geo SCADA from Schneider there is not much we can do inside of the SCADA with limited script feature they
have (maybe need to implement a dedicated driver for our device but we may need to implement it again when the customer switch to another SCADA software).
I saw from the SparkPlug spec. and some public documents, there is a "store-and-forward" feature defined & implemented for the uplink messages from the field to the control room to overcome connection lost, but seems there is no such feature/definition that
handles the flow from host application to the field devices.
BR,
Jimmy
发件人: sparkplug-wg <sparkplug-wg-bounces@xxxxxxxxxxx> 代表 Bryce Nakatani via sparkplug-wg <sparkplug-wg@xxxxxxxxxxx>
发送时间: 2024年6月18日 23:20 收件人: The Sparkplug Working group <sparkplug-wg@xxxxxxxxxxx> 抄送: Bryc
BR,e Nakatani <bnakatani@xxxxxxxxxx>
主题: Re: [sparkplug-wg] How to support SCADA to device command in a Non-Persistent Connection case
Your understanding of Sparkplug is correct. There isn't a queuing of writes when a node is offline.
At the SCADA layer, you should be able to monitor the online status of the node. Should the node be offline, queue writes and when the node is online, release the writes.
On Mon, Jun 17, 2024 at 10:25 PM wang ge via sparkplug-wg <sparkplug-wg@xxxxxxxxxxx> wrote:
|