Closed nahueld closed 2 months ago
The CS registration status on the CSMS is not 'Accepted' before the OCPP command trigger?
Yes, it is not accepted, it is in fact "Pending", according to OCPP :
The Central System MAY also return a Pending registration status to indicate that it wants to retrieve or set certain > > information on the Charge Point before the Central System will accept the Charge Point. 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.
We do:
I think the fix you've made should be moved into the 'BootNotificationResponse' handler. There's something wrong in there since 'startMessageSequence()' is not triggered by the event 'ChargingStationEvents.accepted'.
The CS event(s) emission code is only run at connexion opening, which is wrong. A proper fix is to either move that code into the BootNotificationResponse request handler, or a generic OCPP command event handler for boot notification command.
Please reopen if needed
Duplicate issue
Component
Simulator
Description
When triggering message BootNotification and its returning request Accepted, the emulator does not start the sequence of messages
Version
1.3.3
Node.js version
18
System
System: OS: macOS 13.6.4 CPU: (12) arm64 Apple M2 Pro Memory: 129.89 MB / 16.00 GB Shell: 5.9 - /opt/homebrew/Cellar/zsh/5.9/bin/zsh
Expected result
When the BootNotification result of a Trigger BootNotification is Accepted I expect the subsequent calls to be executed from the emulator, for example, StatusNotification
Actual result
Steps to reproduce
Attachments
Potential fix I'm using on my branch:
File:
OCPP16IncomingRequestService.ts