ocpp/v1_6/message/data_transfer

OCPP 1.6 DataTransfer action.

Request/Response payload types with their OCPP-J codecs (request_to_json/request_decoder, response_to_json/ response_decoder). Transport-agnostic; the action-string mapping lives in ocpp/v1_6/dispatch.

Types

FieldTypeReqDescription
dataString
message_idString(max 50 chars)
vendor_idString(max 255 chars)

Schema: DataTransferRequest

pub type Request {
  Request(
    data: option.Option(String),
    message_id: option.Option(String),
    vendor_id: String,
  )
}

Constructors

FieldTypeReqDescription
dataString
statusDataTransferStatus

Schema: DataTransferResponse

pub type Response {
  Response(
    data: option.Option(String),
    status: data_transfer_status.DataTransferStatus,
  )
}

Constructors

Values

pub fn new_request(vendor_id vendor_id: String) -> Request

Construct a Request from its required fields, with every optional field set to None.

pub fn new_response(
  status status: data_transfer_status.DataTransferStatus,
) -> Response

Construct a Response from its required fields, with every optional field set to None.

pub fn request_decoder() -> decode.Decoder(Request)

Decode a Request from its OCPP-J JSON object, enforcing schema constraints.

pub fn request_to_json(value: Request) -> json.Json

Encode a Request to its OCPP-J JSON object.

pub fn response_decoder() -> decode.Decoder(Response)

Decode a Response from its OCPP-J JSON object, enforcing schema constraints.

pub fn response_to_json(value: Response) -> json.Json

Encode a Response to its OCPP-J JSON object.

Search Document