Closed sahabulh closed 3 months ago
@activeshadow can you try to run this MRE to verify that it works properly. Feel free to clean it up as well. I can then pull and test one final time before merging.
We should also have a plan, as a follow-on, on engaging with the community for both MaEVe and EVerest so that they can be handled through configuration file changes and not require modifications to the code. I can certainly facilitate this, although I think @sahabulh should lead the effort since he did all the work 😄
also, @sahabulh which use cases does this work for? Does it work for AC 15118-2 EIM (the non-PnC dropdown) or only for PnC? It would be good if you would fill in the expected results, similar to https://github.com/EVerest/everest-demo/issues/35#issuecomment-2023837531 so that we can verify whether we get the same results while trying to reproduce
also, @sahabulh which use cases does this work for? Does it work for AC 15118-2 EIM (the non-PnC dropdown) or only for PnC? It would be good if you would fill in the expected results, similar to https://github.com/EVerest/everest-demo/issues/35#issuecomment-2023837531 so that we can verify whether we get the same results while trying to reproduce
Okay, I will post it when I get back home.
We should also have a plan, as a follow-on, on engaging with the community for both MaEVe and EVerest so that they can be handled through configuration file changes and not require modifications to the code. I can certainly facilitate this, although I think @sahabulh should lead the effort since he did all the work 😄
I don't know if OCSP can be turned off via configuration files. I couldn't find anything so I directly modified the code. But there might be other ways. I will create an issue and talk to the MaEVe devs.
There are two issues in this MRE. First, why does AC ISO 15118-2 drop-down option allow PnC? There is a separate option named AC ISO 15118-2 Plug&Charge. Second, it is charging now; the UI says "charging", the log says charging, but the power in the UI indicator stays at 0 kW. It doesn't go red and show 10+ kW. I will ask this in the same Zulip thread.
also, @sahabulh which use cases does this work for? Does it work for AC 15118-2 EIM (the non-PnC dropdown) or only for PnC? It would be good if you would fill in the expected results, similar to #35 (comment) so that we can verify whether we get the same results while trying to reproduce
AC 3ph 16A
and AC 1ph 32A
use EIM
and work with the RFID swipe.
AC ISO 15118-2
and AC ISO 15118-2 Plug&Charge
work and behave similarly. Both use PnC
.
DC ISO 15118-2
gets stuck at the waiting for auth
state. This is expected as we are using an AC config.
@sahabulh I meant with with logs like in my comment. You can use <details>
to make the logs expandable (like I did in those comments)
You can use
<details>
to make the logs expandable
Yeah, I know. I have done that before in the issues. Here you are:
Since @activeshadow and @jhoshiko are both unavailable, I have pulled @sahabulh's changes and tried to run them. However, I am not able to reproduce his results. When I try "AC ISO 15118-2 PnC" from the drop down, the EVerest manager gets stuck in
2024-04-02 02:58:27.494169 [INFO] evse_manager_1: :: CAR ISO V2G AuthorizationReq
2024-04-02 02:58:27.591404 [INFO] evse_manager_1: :: EVSE ISO V2G AuthorizationRes
2024-04-02 02:58:28.134989 [INFO] evse_manager_1: :: CAR ISO V2G AuthorizationReq
2024-04-02 02:58:28.233744 [INFO] evse_manager_1: :: EVSE ISO V2G AuthorizationRes
2024-04-02 02:58:28.775489 [INFO] evse_manager_1: :: CAR ISO V2G AuthorizationReq
2024-04-02 02:58:28.875015 [INFO] evse_manager_1: :: EVSE ISO V2G AuthorizationRes
2024-04-02 02:58:29.421546 [INFO] evse_manager_1: :: CAR ISO V2G AuthorizationReq
Before failing with
2024-04-02 02:58:31.358307 [ERRO] iso15118_charge void dlog_func(dloglevel_t, const char*, int, const char*, const char*, ...) :: Failed response code detected for message "Authorization", error: Response FAILED
@sahabulh are you sure these logs are from the MRE? Can you put in the exact command you used to run them? I don't see the SecurityProfile logs anywhere.
@sahabulh @activeshadow @jhoshiko ah this was just because the maeve image was not rebuilt, and so hadn't picked up the changes to ignore the OCSP. After deleting the existing maeve images, they were rebuilt, and the demo went to the correct charging status. However, the power drawn is still shown as 0W. @sahabulh I believe you said that this was a known issue that you were planning to fix....
Power draw shown as 0 is apparently due to an error with the EV simulator. https://lfenergy.zulipchat.com/#narrow/stream/417676-EVerest.3A-Cloud-communication/topic/Enable.20PnC.20with.20OCPP.202.2E0.2E1/near/430745417
Merging this now...