-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPP 1.6 operation when status is Pending #478
Comments
This doesn't look like a bug. 6.4. BootNotification.conf of OCPP1.6 defines the following for the
The CS shall send another |
It depends on whether section 4.2. Boot Notification text (quoted above) overrides section 6.4's description in a table. |
"While in pending state, the following Central System initiated messages are not allowed: Some review of the latest code, is how to react on RemoteStart.req and RemoteStop.req in pending state? In the PR #421 there is no answer, and an error is issues on the outer protocol. Or is an answer to the RemoteStart/Stop.req legitime? |
@bWF0dGhpYXMK I was able to reproduce this with Steve. From my point of view the following behavior of EVerest is wrong:
The charging station should send "status": "Rejected" or a CALLERROR. Our propietary charging stack send a "Rejected" in this case. |
Recently the behavior regarding RemoteStart/Stop has been fixed in pull request #520 |
Hi, a review of the latest code, there is a PR #520 managing that case with an answer on Rejected. From the ocpp1.6, for me it is not clear what means not allowed, initially I thought on "no" answer, which is two edged. Because an on the RPC framework point of view you require at least an answer such as Call Error. It remains the clarification on ReserverNow.req, Reset.req, ... what behavior here is the most likely in the sense of the describtion. From this " The Central System MAY send request messages to retrieve information from the |
No, all CSMS initiated messages except RemoteStart/Stop during Pending state should be handled as in Accepted. The Pending state is intended to preconfigure the charging station before allowing to charge. Some charging stations apply config changes AFTER a reboot, so the CSMS must be able to reset the Charge point BEFORE finally accept it. So rejecting a reset request is a bad thing. Edit: From my point of view this bug can be closed because i don't see an issue anymore. |
Thank you for clarification, in terms of that, agreed the related PR is closed. Interesting hint concerning the Steve to be able to set the pending state, also as an answer. I was not aware of that... |
OCPP Version
OCPP1.6
Describe the bug
When the CS starts it sends a boot notification request. The CSMS may respond with a status of Pending.
OCPP 1.6 states:
If the Central System returns the Pending status, the communication channel SHOULD NOT be closed by either the Charge Point or the Central System. The Central System MAY send request messages to retrieve information from the Charge Point or change its configuration. The Charge Point SHOULD respond to these messages. The Charge Point SHALL NOT send request messages to the Central System unless it has been instructed by the Central System to do so with a TriggerMessage.req request.
The CS is resending boot notification requests which it shouldn't (no trigger message request received)
To Reproduce
configure CSMS to set "status": "Pending" in the boot notification conf and wait about 8 minutes.
Anything else?
No response
The text was updated successfully, but these errors were encountered: