You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When try to add a PLC device, 4 yaml flies are needed and serval files should be edited accordingly.
But currently, the PLC configuration of different protocols are written in different yaml files.
Such as Siemens-S7 IP is written in plc-deviceshifu-deployment.yaml, for OPCUA IP is written in opcua_edgedevice.yaml, they are different type files.
I think users or developers may feel confused when facing this situation.
So, suggest to optimize the file organization, to unify the PLC configuration in the same type file, establish a unified specification, thus whenever add a PLC, we always know to change the same yaml file.
The text was updated successfully, but these errors were encountered:
When try to add a PLC device, 4 yaml flies are needed and serval files should be edited accordingly.
But currently, the PLC configuration of different protocols are written in different yaml files.
Such as
Siemens-S7 IP
is written in plc-deviceshifu-deployment.yaml, forOPCUA IP
is written in opcua_edgedevice.yaml, they are different type files.I think users or developers may feel confused when facing this situation.
So, suggest to optimize the file organization, to unify the PLC configuration in the same type file, establish a unified specification, thus whenever add a PLC, we always know to change the same yaml file.
The text was updated successfully, but these errors were encountered: