Configuring Responder/Smart Grid
Configure WCF client to connect to the AMI Event Service - 61968-9 2nd Edition

Resource Center Home

Beginning with 10.0.3, Responder AMI supports the CreatedEndDeviceEvents operation in the 61968-9 2nd Ed. ReceiveEndDeviceEvents message profile. While the profile includes other operations, Responder AMI does not recognize them.

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.

61968-9 2nd Edition
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/basicHttpReceiveEndDeviceEventsService" binding="basicHttpBinding" bindingConfiguration="ReceiveEndDeviceEventsService_basicHttpBinding" contract="IEndDeviceEvents_Port" name="ReceiveEndDeviceEventsService_basicHttpEndpoint"/>
   <endpoint address="http://localhost/Miner.Smartgrid.EventService/EndDeviceEventService.svc/wsHttpReceiveEndDeviceEventsService" binding="wsHttpBinding" bindingConfiguration="ReceiveEndDeviceEventsService_wsHttpBinding" contract="IEndDeviceEvents_Port" name="ReceiveEndDeviceEventsService_wsHttpEndpoint"/>
  </client>
 </system.serviceModel>

The following event codes are supported in the 61968-9 2nd Ed. interface:

Event Code Maps To
3.19.17.85 Communication Down
3.19.17.33 Communication Up
3.23.74.85 Communication Down
3.23.136.85 Communication Down
3.23.17.85 Communication Down
3.23.17.68 Communication Down
3.23.17.42 Communication Up
3.26.25.85 Power Down
3.26.25.216 Power Up
3.26.0.85 Power Down
3.26.0.216 Power Up
3.26.126.85 Partial Power
3.26.134.85 Partial Power
3.26.135.85 Partial Power
3.31.0.68 Remote Disconnect
3.31.0.42 Remote Connected
3.12.0.257 Remote Disconnect

For the 61968-9 2nd Ed. interface, the following is a sample message:

Copy Code 
<?xml version="1.0" encoding="utf-16"?>
<CreatedEndDeviceEventsEvent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <CreatedEndDeviceEvents>
  <Header xmlns="http://iec.ch/TC57/2011/EndDeviceEventsMessage">
   <Verb xmlns="http://iec.ch/TC57/2011/schema/message">created</Verb>
   <Noun xmlns="http://iec.ch/TC57/2011/schema/message">EndDeviceEvent</Noun>
   <Timestamp xmlns="http://iec.ch/TC57/2011/schema/message">2012-01-06T08:21:30.8994639-07:00</Timestamp>
   <Source xmlns="http://iec.ch/TC57/2011/schema/message">TroubleMaker</Source>
  </Header>
  <Payload xmlns="http://iec.ch/TC57/2011/EndDeviceEventsMessage">
   <EndDeviceEvents xmlns="http://iec.ch/TC57/2011/EndDeviceEvents#">
    <EndDeviceEvent>
     <mRID>PWST065471</mRID>
     <createdDateTime>2012-01-06T08:21:30.8994639-07:00</createdDateTime>
     <Assets>
      <mRID>PWST065471</mRID>
     </Assets>
     <EndDeviceEventType ref="3.26.25.85"/>
     <status>
      <dateTime>2012-01-06T08:21:30.8994639-07:00</dateTime>
      <value>DeEnergized</value>
     </status>
     <UsagePoint/>
    </EndDeviceEvent>
   </EndDeviceEvents>
  </Payload>
 </CreatedEndDeviceEvents>
</CreatedEndDeviceEventsEvent>

Post-10.0.3, the treatment of IDs in Responder AMI changed for stricter compliance to 61968-9 2nd Ed. The following is an updated sample message for post-10.0.3 integrations:

Copy Code 
<?xml version="1.0" encoding="utf-16"?>
<CreatedEndDeviceEventsEvent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <CreatedEndDeviceEvents>
  <Header xmlns="http://iec.ch/TC57/2011/EndDeviceEventsMessage">
   <Verb xmlns="http://iec.ch/TC57/2011/schema/message">created</Verb>
   <Noun xmlns="http://iec.ch/TC57/2011/schema/message">EndDeviceEvent</Noun>
   <Timestamp xmlns="http://iec.ch/TC57/2011/schema/message">2012-01-06T08:21:30.8994639-07:00</Timestamp>
   <Source xmlns="http://iec.ch/TC57/2011/schema/message">TroubleMaker</Source>
  </Header>
  <Payload xmlns="http://iec.ch/TC57/2011/EndDeviceEventsMessage">
   <EndDeviceEvents xmlns="http://iec.ch/TC57/2011/EndDeviceEvents#">
    <EndDeviceEvent>
     <mRID>2b3232d5-4d3f-45c3-b2d7-56b440bf54f1</mRID>
     <createdDateTime>2012-01-06T08:21:30.8994639-07:00</createdDateTime>
     <Assets>
      <mRID>2b3232d5-4d3f-45c3-b2d7-56b440bf54f1</mRID>
      <Names>
       <name>PWST065471</name>
      </Names>
     </Assets>
     <EndDeviceEventType ref="3.26.25.85"/>
     <status>
      <dateTime>2012-01-06T08:21:30.8994639-07:00</dateTime>
      <value>DeEnergized</value>
     </status>
     <UsagePoint/>
    </EndDeviceEvent>
   </EndDeviceEvents>
  </Payload>
 </CreatedEndDeviceEvents>
</CreatedEndDeviceEventsEvent>

You can copy and save the contents of the wsdl file from the ReceiveEndDeviceEvents.wsdl help topic.

You can copy and save the contents of the .xsd files from the 61968-9 2nd Edition .xsd Files help topic.

The .xsd files must be saved in a separate sub-folder labled: xsd. The .wsdl file should remain in the parent folder.

 

 

Send Comment to ArcFMdocumentation@schneider-electric.com