NT 100-XX-XX, NB 100-XX-XX with PROFIBUS Slave as basenet or subnet: allow manual input of "Configuration Data" which is not necessarily comprised of Hilscher Module IDs.

Components involved:

• netSLAVE DTM

Current behaviour:

1/ Drop NT 100-XX-XX;
2/ Page "Settings" -> select as "Primary network" - whatever protocol. Select as "Secondary network" - PROFIBUS-DP Slave (or vice versa, does not matter);
3/ Apply;
4/ Open the context menu -> Configuration -> PROFIBUS-DP Slave;
5/ Navigate to page "Configuration", scroll down the page where the field "Configuration data" is seen;
6/ Check the "Manual input" check box - the "Configuration Data" field becomes editable;
7/ Write in this field a valid non-Hilscher PROFIBUS configuration data. For example the ID of the Module 

• "Drive Profile Lexium 1" found in SE120B9D.GSD (Lexium 32M Profibus DP V1 GSD file V01.07 | Schneider Electric): C31919FD00FF.

8/ Click another control (causes KillFocus of this field) or click the "Apply" button.

Result: an error message appears "Invalid module id".
What we want to achieve: allow entering configuration data comprised of non-Hilscher modules. Check only whether this is a valid configuration data according to the PROFIBUS specification:

• PROFIBUS-Specification_Normative_Parts-8:1997, p. 736 - 738

PROFIBUS\PROFIBUS Specification EN 50170 Vol 2.pdf

Some explanations:

- The Configuration Data is an array of Module IDs. For example, using the CIFX DP/DPS slave, selecting "32 Words Out" and "8 Bytes In" modules achieves configuration data of: 80DF97.

- Currently, the Configuration Data is checked against the Hilscher Modules (C:\ProgramData\SYCONnet\PROFIBUS\GSD - HIL****.GSD files installed with SYCON contain only Hilscher Modules). We want to allow any valid configuration data.