...
In this example the application shall handle I&M data on application side. For that it is necessary to change the configuration packet, to implement the "wirte write I&M indication" ,
the "read I&M indication" and the "reset to factory indication". For that the application needs a possibility to save information remanent in a flash.
...
In the GSDML the device developer need needs to give the information, which modul module has I&M data. Default in Below you see the default configuration in our PNS V5.1.0.4 device. I&M is, at the moment on , just configured for the DAP:
<VirtualSubmoduleItem ID="DIM 31" IM5_Supported="false" MayIssueProcessAlarm="false" SubmoduleIdentNumber="0x00003010" Writeable_IM_Records="1 2 3">
That means, I&M0 till 3 is supported. I&M4 till and 5 are not supported. Only the DAP Modul module has I&M Data.
It is possbile to use the Writeable_IM_Records="1 2 3 4" on a moduldifferent module. For example:
<VirtualSubmoduleItem ID="10byteinput" MayIssueProcessAlarm="false" SubmoduleIdentNumber="0x00000001" Writeable_IM_Records="1 2">
That means the DAP has now I&M0 till 3 and the 10 Byte Input modul module has it its own dataset for I&M0 till 2. In this case the application need to implement the Ithe I&M data handling needs to be implemented in your application, because the stack can only handle the default I&M data on the DAP.
4. Indications
Implement the packet handler Indications for
...
The stack does not know anything about the GSDML file. The stack needs first the first needs the information about supported I&M data. For that the stack sends, in startup, the
PNS_IF_READ_IM_IND with the parameter PNS_IF_IM_TYPE_IM0FILTER. That means the stack wants to get from the application the information which modul does modules do support their own I&M data.
The application can response with some flags to this stack request.
...