Hello, 

I am currently trying to solve an issue with automatization of GSD module parameter change.

Here is the example workflow: 

1. These are the parameters I am trying to change: 

2. I have already tried using Openness Explorer

3. But unfortunately I could not find a proper service that would provide the parameters in any way ... 

I have even tried to do it through CAX export/import where I have thought that the CAX workflow would work in this situation but unfortunately it seems that it does not work.

I have already tried to search these solutions here on the forum.

- https://support.industry.siemens.com/forum/cz/en/posts/copy-paste-%27module-parameters%27-of-a-decentral-io/267989

- https://support.industry.siemens.com/forum/cz/en/posts/openness-v14sp1-module-parameters-gsdml-and-download-to-device/293517

- Attributes of a GSD device in Openness - 293146 - Industry Support Siemens

but unfortunately these topics were not properly answered. 

Any help would be appreciated! 

Kind regards 

vformanek

 I have been investigating this issue for a while now. And yes comparing each property/attribute name is not that hard. But as can be seen on my post above, the Openness Explorer cant see the attributes that represent the parameters... What is weird is that I have even tried to import a safety device GSD and there only a few safety attributes are unlocked. My investigation has gone to that it could be an issue with versions since I am still using TIA V17. I will try with the newest TIA V19 since there are new features like: 

• Extended access to the hardware configuration

- source here: Sales and Delivery release of TIA Portal V19 - ID: 109821307 - Industry Support Siemens 

0_Einstein

Since it is for a device already added into the project using a GSD - and the available parameters unknown until runtime, will you not need to iterate over every property/attribute (presumably within a dictionary or hash table or the like), compare each property/attribute name with a given name until it is found, then assign your custom "value" to that property/attribute?

If it is not found, you may want to debug output what is found while iterating over the GSD-based module's components.

vformanek

 Hello, I am currently trying to solve the same issue. I have thought that the CAX export would work in this situation but it seems that it does not work. I know that it has been a while, but have you found any other solutions to this problem of automatic parametrization ? I am currently in the process of coding a C# tool for that so I would love to automatically change the module parameters since I have almost the same use case. I am for example familiar with Openness Explorer but I could not find anything usefull in the GSD deviceItems there. 

Kind Regards 

vformanek

Hi!

I don't have a copy of your specific GSD to test, but I have had success getting this to work with what looks to be a similar device structure.

On the DeviceItem invoke the GetService method with a GSDDeviceItem type then on the returned GSDDeviceItem object call the GetPrmData and SetPrmData methods to get this module parameter data out.

Finding the correct dsNumber and offsets took some trial and error and some digging into the GSD file itself, but it's doable.

Hopefully this helps?