question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Ocpp1.6 soap request to central system

See original GitHub issue

Hi one and all,

After a small testing with a mock-up soap (xml) request (from pole to CentralSystem) I noticed that I’m not quite sure what’s the correct form of an Ocpp1.6 soap request. Especially how the soap headers and namespaces should be set. I think that the request below is close the right form, but, do you have any comments?

Of course it could be also so that implementations in the poles could differ slightly. In case message form below is about the right one the library needs a little fix to handle it, I could make a PR for that.

B.r. Antti

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ns="urn://Ocpp/Cs/2015/10/">
   <soap:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
      <ns:chargeBoxIdentity>Pole1000</ns:chargeBoxIdentity>
      <wsa:MessageID>1001001</wsa:MessageID>
      <wsa:From><wsa:Address>http://localhost:12345</wsa:Address></wsa:From>
      <wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address></wsa:ReplyTo>
      <wsa:To>http://localhost:8887</wsa:To>
      <wsa:Action>/Authorize</wsa:Action>
   </soap:Header>
   <soap:Body>
      <ns:authorizeRequest>
        <ns:idTag>tag200</ns:idTag>
      </ns:authorizeRequest>
   </soap:Body>
</soap:Envelope>

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
lahnaojacommented, Feb 20, 2018

Unit test should be fine now.

0reactions
lahnaojacommented, Feb 21, 2018

Ok, thanks.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Open Charge Point Protocol 1.6
System for two cases: 1. a Charge Point requesting authentication of a card and sending charge transaction status,. 2. Central System requesting a...
Read more >
Open Charge Point Protocol SOAP 1.6, OCPP-S 1.6 ...
The purpose of this document is to give the reader the information required to create a correct interoperable OCPP SOAP implementation ...
Read more >
OCPP 1.6, Protocols, Home - Open Charge Alliance
FUNCTIONALITIES. OCPP 1.5; Both SOAP and JSON versions; Smart Charging support for load balancing and use of charge profiles; (Local) list management support ......
Read more >
Open Charge Point Protocol SOAP 1.6, OCPP ... - DocPlayer.net
OCPP1.6J means we are talking about a JSON/WebSockets implementation of 1.6. ... BootNotification If the SOAP connection to the Central System is lost, ......
Read more >
Not getting the required SOAP request XML - Stack Overflow
Provided the prefixes match up with the xmlns declarations on the Envelope element, then it is valid XML and therefore valid SOAP so...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found