ocpp icon indicating copy to clipboard operation
ocpp copied to clipboard

Documentation how CALL messages are handled

Open OrangeTux opened this issue 5 years ago • 5 comments

Currently the docs are lacking proper documentation about how routing of CALL messages work, how to use the @on() and @after() decorator should be used and how the route map is build.

OrangeTux avatar Dec 03 '19 09:12 OrangeTux

Do you people had an example that implement all the operations initiated by the charge point for ocpp1.6?. In chapter 4 of the Specifications it says that the operations initiated by the charger point are:

  1. Authorize.
  2. Boot Notification.
  3. Data Transfer.
  4. Diagnostics Status Notification.
  5. Firmware Status Notification.
  6. Heartbeat.
  7. Meter Values.
  8. Start Transaction.
  9. Status Notification.
  10. Stop Transaction.

eugenio-tesio avatar Jul 27 '20 23:07 eugenio-tesio

No, we don't have open source implementation of that in this repo.

OrangeTux avatar Jul 28 '20 07:07 OrangeTux

So there is no way to send a start/stop command to the charger using this repo?

Bej-Technologies avatar Jan 25 '24 12:01 Bej-Technologies

No, that's not a correct statement. It's perfectly feasible to send a RemoteStartTransaction or RemoteStopTransaction from the CSMS to a charger. See for example this comment.

OrangeTux avatar Jan 25 '24 20:01 OrangeTux

Perfect! I think I just misunderstood your last comment. Now we have it up and running here, thank you for clarifying

Bej-Technologies avatar Jan 26 '24 07:01 Bej-Technologies