Create ICD files for generic devices: HMI, RTU, Switch, GPS

[DiegoGasca]

The listed devices are not often required or available in SCD files, but they are useful for StationScout/Guard, so include a button to add these new elements should be cool

[JakobVogelsang]

Thank you for your contribution. We will take that in the roadmap. However, this feature will be part of the communication mappings epic that will contain connecting Reports story. Until then please import these specific IED types from an .iid, .icd.

[BurTah00]

and also would be great if we use "OMICRON" Test Device .icd file as a template for generic test devices to be added as a client. Note: it is the official iid once prepared by developers but format can be changed to icd, doesn't create problem.

OMICRON_Test Client.zip

[ca-d]

@BurTah00 We're currently considering including your feature wish in our ROADMAP.md document. Could you expand a bit on the use case so we can see whether we can find a solution to it that's generic enough to be of interest to others?

Would using a central https://github.com/com-pas/compas-scl-data-service be an option for your use case?

[Sander3003]

To try CoMPAS: https://demo.compas.energy/ Please note that this is a shared database. With CoMPAS you can put HMI, RTU, Switch, GPS as an ICD file in the database and import them when needed.

[BurTah00]

The idea is having a repository of well-known or generic device library consist of .icd files and depending on the project import them to further engineer. It doesn't have to be clients but client files are generic enough without so many changes depending on their firmware like IEDs.

[Sander3003]

Sounds like a good idea. The CoMPAS database can the repository. The icd files need to be created.