-
-
Notifications
You must be signed in to change notification settings - Fork 621
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
EN+: "Preparing" timeout before RemoteStartTransaction could be sent on long intervals #15752
Comments
The final reason why it jumps to "Finishing" state is an internal timeout of the charger waiting for a transaction to be started after vehicle connection (Available->Preparing) either by the user (RFID or Autostart) or by CS (RemoteStartTransaction).
So we need to find out why. Charger signaling itself looks good so far. What have you set for This value might be just too large for the internal transaction timeout trap. Can you please try to reduce it to Additionally please attach the output of |
@premultiply interval was set to 30 seconds, Found 10 seconds was too bouncy but this was quite some time ago when I did the initial setup. I have changed it to 10 can see how this goes tomorrow. Here is the output from
|
So tomorrow morning, The only thing in evcc is showing waiting for Authorisation which is a bit weird it's working! Here is the logs of the evse connecting something might be in here to show why it's saying asking for auth but of course it's charging. The other weird thing is why is the evse sending the
|
Correction on the 10 second interval, evcc is too bouncy once solar was above the minimum 6amps, will try 15 seconds restart evcc with interval setting changed and back to square 1 had to do the following to get working again
Also evcc has a warning about interval less and 30 seconds can lead to issues, 30 seconds worked pretty well it didn't need to be any quicker, the ocpp stuff shouldn't be doing commands for connection etc.. on the interval schedule. Or could just go back to 0.129.0 and it was perfect 🤷 |
So is it working now with the reduced interval or not? Log looks fine to me now. |
No I had to do the whole 6 step process in previous comment to get it working again and that is with a 15 second interval. Knowing what I know a guess to fix this would be upon preparing immediately just put charger into the suspended EVSE state. Then the usual interval should enable it if required. Don't wait for the interval loop to do that. |
Today the interval at 15 seconds I'm getting
it's oscillating because the interval is really too quick to get stable power measurements between the evse grid meter and solar inverter and if a household load switches on/off and a major adjustment is required in the evse for solar tracking this occurs. Lowering the interval to fix this isn't really a solution |
Sounds like your car consumes reactive power.
It shouldn't be. In this case: please contact vendor how charger can start session if it can't be started immediately. Also: it's totally unclear to me why this should have worked on 129. We were also using RemoteStart then and only did this in the regular intervals.
The log doesn't show any of that. What it shows is this, so there is still a different issue that needs be fixed:
|
Since there are more problems with this charger that do not seem contributable to evcc (#15552) I'm closing here. If there's an actual issue with evcc feel free to reopen. |
@andig there were a lot less problems before 0.130.0. I have gone back to 0.129.0 just turn EVSE on off and it started working no funny unplugging car etc required. |
Describe the bug
evcc is now unworkable when your ocpp evse decides to jump to finishing status upon plugging in
Prior to 0.130.0 evcc was quite happy to break ocpp spec and jump from Finishing back to SuspendedEVSE state (IE tell the evse to start charging!)
This happens even if the mode is set to min + solar or it's off (no solar) - I spent almost 1/2 hour trying to evcc into a working state this morning!
Only way to get going now seems to be to restart both the evse & evcc & unplug replug car! & make sure evcc is in min+solar or fast mode before plugging the car in! And not do this too quickly either otherwise evcc crashed see
Note this evse can't be set to free vend mode as this disables ocpp!
I have tried other combos to try and get going
relying upon vendors to fix issues is really a non starter, my only real option is evcc isn't fixed is to implement ocpp in node red and just connect this to evcc.
Steps to reproduce
Configuration details
Log details
What type of operating system are you running?
Linux
Version
0.130.6
The text was updated successfully, but these errors were encountered: