Documentation
¶
There is no documentation for this package.
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
Package api provides primitives to interact with the openapi HTTP API.
|
Package api provides primitives to interact with the openapi HTTP API. |
|
Package config provides support for configuring the system.
|
Package config provides support for configuring the system. |
|
Package handlers defines the interfaces implemented by handlers for OCPP messages and the types used when routing those messages.
|
Package handlers defines the interfaces implemented by handlers for OCPP messages and the types used when routing those messages. |
|
has2be
Package has2be defines handlers for processing Has2Be OCPP 1.6 extension messages.
|
Package has2be defines handlers for processing Has2Be OCPP 1.6 extension messages. |
|
ocpp16
Package ocpp16 defines handlers for processing OCPP 1.6 messages.
|
Package ocpp16 defines handlers for processing OCPP 1.6 messages. |
|
ocpp201
Package ocpp201 defines handlers for processing OCPP 2.0.1 messages.
|
Package ocpp201 defines handlers for processing OCPP 2.0.1 messages. |
|
Package ocpi implements the OCPI API for interacting with eMSPs (MOs)
|
Package ocpi implements the OCPI API for interacting with eMSPs (MOs) |
|
Package ocpp provides marker interfaces for types that are intended to be OCPP requests and responses.
|
Package ocpp provides marker interfaces for types that are intended to be OCPP requests and responses. |
|
ocpp16
Package ocpp16 contains types that represent each of the different OCPP 1.6 protocol messages.
|
Package ocpp16 contains types that represent each of the different OCPP 1.6 protocol messages. |
|
ocpp201
Package ocpp201 contains types that represent each of the different OCPP 2.0.1 protocol messages.
|
Package ocpp201 contains types that represent each of the different OCPP 2.0.1 protocol messages. |
|
Package server provides the implementation of the HTTP server components used by the manager.
|
Package server provides the implementation of the HTTP server components used by the manager. |
|
Package services defines pluggable services that are used to customize the processing of OCPP messages by the core handlers.
|
Package services defines pluggable services that are used to customize the processing of OCPP messages by the core handlers. |
|
Package store defines the interfaces to the persistent store.
|
Package store defines the interfaces to the persistent store. |
|
firestore
Package firestore provides an implementation of store.Engine using Google Firestore.
|
Package firestore provides an implementation of store.Engine using Google Firestore. |
|
inmemory
Package inmemory provides an in-memory implementation of store.Engine.
|
Package inmemory provides an in-memory implementation of store.Engine. |
|
Package sync provides support for synchronizing configuration changes to the charge stations.
|
Package sync provides support for synchronizing configuration changes to the charge stations. |
|
Package transport provides the interfaces that are used to communicate between the manager and the gateway and subsequently to the charge station.
|
Package transport provides the interfaces that are used to communicate between the manager and the gateway and subsequently to the charge station. |
|
mqtt
Package mqtt provides support for handling messages from the gateway and emitting messages to the gateway using MQTT
|
Package mqtt provides support for handling messages from the gateway and emitting messages to the gateway using MQTT |
Click to show internal directories.
Click to hide internal directories.