Smart Grid Applications Overview > Smart Operations Solution > AMI Integration > Optional Configurations > Configure WCF client to connect to the AMI Event Service - 09/2010 Revision of 61968-9 |
Beginning with 10.0.1 SP1, Responder AMI supports the CreatedEndDeviceEvent operation in the 09/2010 revision of 61968-9 EndDeviceEvent message profile.
The following is sample configuration for a WCF client connecting to the Responder AMI Event Service. Note that the client should use the basicHttpReceiveEndDeviceEventsService endpoint for SOAP 1.1 messages or wsHttpReceiveEndDeviceEventsService for SOAP 1.2. Also note that you must replace ‘localhost’ with the IP:port of your server hosting the Responder AMI Event Service.
09/2010 Revision of 61968-9 |
Copy Code
|
---|---|
<system.serviceModel> <bindings> <basicHttpBinding> <binding name="EndDeviceEventService_basicHttpBinding" /> <binding name="ReceiveEndDeviceEventsService_basicHttpBinding" /> </basicHttpBinding> <wsHttpBinding> <binding name="EndDeviceEventService_wsHttpBinding"> <security mode="None" /> </binding> <binding name="ReceiveEndDeviceEventsService_wsHttpBinding"> <security mode="None" /> </binding> </wsHttpBinding> </bindings> <client> <endpoint address="http://localhost/Miner.Smartgrid.EventService/EndDeviceEventService.svc/basicHttpEndDeviceEventService" binding="basicHttpBinding" bindingConfiguration="EndDeviceEventService_basicHttpBinding" contract="IEndDeviceEvent" name="EndDeviceEventService_basicHttpEndpoint" /> <endpoint address="http://localhost/Miner.Smartgrid.EventService/EndDeviceEventService.svc/wsHttpEndDeviceEventService" binding="wsHttpBinding" bindingConfiguration="EndDeviceEventService_wsHttpBinding" contract="IEndDeviceEvent" name="EndDeviceEventService_wsHttpEndpoint" /> </client> </system.serviceModel> |
The following event codes are supported in the 09/2010 revision of 61968-9 interface:
Event Code | Maps To |
3.26.1.185 | Power Down |
3.26.9.216 | Power Up |
3.31.6.68 | Disconnected |
3.31.6.42 | Connected |
1.19.1.32 | Communication Down |
1.19.17.34 | Communication Down |
1.19.17.33 | Communication Up |
6.25.1.85 | Partial Power |
3.33.1.44 | Disconnected |
3.33.1.77 | Disconnected |
3.33.1.152 | Disconnected |
3.33.1.184 | Disconnected |
3.33.1.219 | Disconnected |
3.33.1.257 | Disconnected |
3.33.1.263 | Disconnected |
For the 09/2010 revision of 61968-9 interface, the following is a sample message:
Copy Code
|
|
---|---|
<?xml version="1.0" encoding="utf-16"?> <CreatedEndDeviceEventInput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <CreatedEndDeviceEvent> <Header> <creationDateTime xmlns="http://www.iec.ch/TC57/2010/schema/header">2010-08-03T19:03:22.7786684-06:00</creationDateTime> <verb xmlns="http://www.iec.ch/TC57/2010/schema/header">EndDeviceEvents</verb> </Header> <Payload> <EndDeviceEvent xmlns="http://www.iec.ch/TC57/2010/schema/EndDeviceEvent"> <category>3.26.1.185</category> <createdDateTime>2010-08-03T19:03:32.7786684-06:00</createdDateTime> <Assets> <mRID>testtags1</mRID> </Assets> <status> <dateTime>2010-08-03T19:03:22.7786684-06:00</dateTime> <value>DeEnergized</value> </status> </EndDeviceEvent> </Payload> </CreatedEndDeviceEvent> </CreatedEndDeviceEventInput> |
You can copy and save the contents of the wsdl file from the EndDeviceEvent.wsdl help topic.
You can copy and save the contents of the .xsd files from the 09/2010 Revision .xsd Files help topic.