Closed Uffel3 closed 9 months ago
(@danyill assisting Maik)
In the attached we cannot see the Communications structure for the control block within the publisher plugin.
This appears to be because it does not support the ServerAt directive.
ServerAt
We were looking to see the communications addressing information (for the GSE) within the publisher communication for the Ctl control block.
GSE
Ctl
Attached is an example file:
SEL-411L-2.zip
And a screenshot of the publisher plugin:
The control block of Ctl is in the S1 AccessPoint, however the GSE is within the P1 ConnectedAP
AccessPoint
ConnectedAP
This plugin needs to following the ServerAt directive to allow finding the GSE within P1:
<AccessPoint desc="Process Bus" name="P1"> <ServerAt apName="S1" /> <Services> <ClientServices goose="true" sv="true" /> </Services> </AccessPoint>
@danyill wrote something for this which may be useful but undoubtedly needs careful review.
https://github.com/danyill/oscd-tp-multicast-naming/blob/9daa65ed3e9ab37c9bc23c5d88638ef0f6790af2/oscd-tp-multicast-naming.ts#L339-L372
We can simply swap in: controlBlockGseOrSmv from https://github.com/OpenEnergyTools/scl-lib/blob/main/tControl/controlBlockGseOrSmv.ts into
controlBlockGseOrSmv
https://github.com/OpenEnergyTools/oscd-publisher/blob/a765f5ddeaa339d2dfc997bbf18a094961fb1fa0/editors/gsecontrol/gse-control-element-editor.ts#L74-L86
I can do a PR if you would like @JakobVogelsang
(@danyill assisting Maik)
In the attached we cannot see the Communications structure for the control block within the publisher plugin.
This appears to be because it does not support the
ServerAt
directive.We were looking to see the communications addressing information (for the
GSE
) within the publisher communication for theCtl
control block.Attached is an example file:
SEL-411L-2.zip
And a screenshot of the publisher plugin:
The control block of
Ctl
is in the S1AccessPoint
, however the GSE is within the P1ConnectedAP
This plugin needs to following the
ServerAt
directive to allow finding theGSE
within P1:@danyill wrote something for this which may be useful but undoubtedly needs careful review.
https://github.com/danyill/oscd-tp-multicast-naming/blob/9daa65ed3e9ab37c9bc23c5d88638ef0f6790af2/oscd-tp-multicast-naming.ts#L339-L372