OCPP (7) 썸네일형 리스트형 43 4.9. Status Notification 4.9. Status Notification Charge Point —- Central System Status Notification.req(connectorld, errorCode, status, [timestamp], [info], [vendorld], [vendorErrorCode]) StatusNotification.conf() Figure 20. Sequence Diagram: Status Notification A Charge Point sends a notification to the Central System to inform the Central System about a status change or an error within the Charge Point. The following.. 42 4.8. Start Transaction NotApplicable, Unknown, RST, RTS, SRT, STR, TRS and TSR. see section Standard Configuration Key Names & Values for more information. The EXPERIMENTAL optional format field specifies whether the data is represented in the normal (default) form as a simple numeric value ("Raw"), or as "SignedData", an opaque digitally signed binary data block, represented as hex data. This experimental field may b.. 41 4.7. Meter Values 4.7. Meter Values Charge Point ---- Central System MeterValues.req(connectorld, meterValue, [transactionId]) MeterValues.conf() Figure 18. Sequence Diagram: Meter Values A Charge Point MAY sample the electrical meter or other sensor/transducer hardware to provide extra information about its meter values. It is up to the Charge Point to decide when it will send meter values. This can be configure.. 40 4.5. Firmware Status Notification / 4.6. Heartbeat 4.5. Firmware Status Notification Charge Point ---- Central System Firmware Status Notification.req(status) Firmware Status Notification.conf() Figure 16. Sequence Diagram: Firmware Status Notification A Charge Point sends notifications to inform the Central System about the progress of the firmware update. The Charge Point SHALL send a FirmwareStatus Notification.req PDU for informing the Centr.. 39 4.3. Data Transfer / 4.4. Diagnostics Status Notification 4.3. Data Transfer Charge Point ---- Central System Data Transfer.req(vendorld, [messageld], [data]) Data Transfer.conf(status, [data]) Figure 14. Sequence Diagram: Data Transfer If a Charge Point needs to send information to the Central System for a function not supported by OCPP, it SHALL use the DataTransfer.req PDU. The vendorld in the request SHOULD be known to the Central System and unique.. 38 4.2.1. Transactions before being accepted by a Central System This includes cached messages that are still present in the Charge Point from before. When the Central System responds with a Boot Notification.conf with a status Accepted, the Charge Point will adjust the heartbeat interval in accordance with the interval from the response PDU and it is RECOMMENDED to synchronize its internal clock with the supplied Central System's current time. If the Central.. 37 4. Operations Initiated by Charge Point / 4.1. Authorize / 4.2. Boot Notification 4. Operations Initiated by Charge Point 4.1. Authorize Charge Point —- Central System Authorize.req(idTag) —-- Authorize.conf(id TagInfo) Figure 12. Sequence Diagram: Authorize Before the owner of an electric vehicle can start or stop charging, the Charge Point has to authorize the operation. The Charge Point SHALL only supply energy after authorization. When stopping a Transaction, the Charge P.. 이전 1 다음
