Inquiry about using the CSIP-AUS to test DER according to CSIP1.2 procedure.

[eamars]

Hello

First of all, thank you for your excellent work!

I'm currently working with an inverter company to support the CSIP-AUS interface, and I’d like to understand how the server can be used to implement tests that verify CSIP-AUS functionality for DERs.

Using Test 14.2.4 ALL-27: Disconnection of DER (DER-A) as an example, the procedure is as follows:

The test procedure shall be as follows:
(a) The utility server is to configure a DERControl with opModConnect = false and an immediate start.
(b) On the next poll of the utility server the client shall receive and start the new DERControl, by disconnecting all DER under its control.
(c) On the client’s next POST of DERStatus, bit 0 of genConnectStatus should be deasserted to reflect the disconnected DER.
(d) The utility server is to configure a DERControl with opModConnect = true and an immediate start.
(e) On the next poll of the utility server, the client shall receive and start the new DERControl by reconnecting all DER under its control. On next POST of DERStatus, bit 0 of genConnectStatus should be asserted to reflect the reconnected DER.

I'd like to understand:

1. Does the DER need to be registered with the server in the first place?
2. How to send a DERControl with opModConnect message to a given client? I don't see examples from postman collections https://github.com/bsgip/envoy/tree/main/postman.
3. What API should I call to read the DERStatus from the envoy?

I'd like to hear from you soon.

Thank you.

[joshvote]

Good question, more broadly speaking there is a (soon to be open source) tool for automating all these test interactions. It's currently under an internal alpha but the aim is to open it up to DERIAPITWG members next week. That will essentially use this server to implement the various test cases (and all you need to do is select the test case and point your client at the spun up server).

We're also aware of some missing bits to support some tests that are currently being developed (hopefully all sorted by the end of the week) #195

re: the referenced test case "Test 14.2.4 ALL-27" - What version of the client test docs are you referencing? I did a quick scan of the 1.0, 1.2 client test cases and SAHB218 and haven't managed to find a reference to it.

To your specific questions

1. A number of the test cases imply EndDevice registrations as a precondition (often including DERSettings and DERCapability being set to include max power + DOE capabilities). We've always interpreted as this happening "before" the actual test behaviour - whether this is a carry over from a previous registration/test or happening as part of the test setup isn't clearly described in the test case.
2. As of right now - it's not possible. That should be fixed in the next couple of days Settings for supporting CSIP-Aus 1.2 test cases #195
3. DERStatus can be accessed from the EndDevice.DERListLink which will always contain a single DER with links to DERStatus (and the other DER info entities). In the envoy implementation - it will have a fixed href in the form: /edev/$EDEV_ID/der/1/ders. As per 2030.5 you can PUT to that endpoint to update the DERStatus or GET to fetch the last value submitted.

[joshvote]

As a followup - we've had some changes come through on the admin server endpoints. There is now an endpoint for injecting DERControls (called site controls) that describe either a DOE or a connect/energize control. There will be a pass at updating the POSTMan collections in the very near future #217 but for now:

This is for the ADMIN server - The JSON API (not the CSIP-Aus server)

Send an array of (SiteControlRequest): https://github.com/bsgip/envoy-schema/blob/main/src/envoy_schema/admin/schema/site_control.py to /site_control_group/{group_id}/controls

In order to create/manage your SiteControlGroup (to get your group_id) you need to POST a SiteControlGroupRequest to /site_control_group

I've opened #217 to make this all a lot more clear.

[eamars]

Hi Josh

Thanks for your response, appologize for my late reply. I went on leave for the last two weeks and unfortunately I missed the presentation of the client test harness. My colleague Matthias just requested the slide from you to get me up on speed.

Speaking of the test case 14.2.4 ALL-27, I was referring to SA HB 218 v1.1, there are multiple versions of the documents floating around and appologize for the confusion. Below is the screenshot of the version I got:

#217 will be helpful for us to integrate the CSIP-AUS test into our existing AS 4777.2 functional test suite. I will close this issue once the postman API is updated.

Much appreciated for your feedback and awesome work.