I have two vehicles that I regularly connect to my smartevse v3 charger using the latest software. A BMW works very well with smartevse, I have not had any issues. But our Ford Kuga does not like the way the smartevse works.
With some persuation I can charge the Ford Kuga but almost all sessions end up in error. And connecting the Kuga to the cable must be done in a certain order or the charge will not start. If I connect the cable before the smartevse is active the Ford will error and only continue by disconnecting the cable first, then enable smartevse and connect. Only then the charge will start. As soon as I disable the smartevse while it is connected the Ford will error.
In order to diagnose the Ford issues I have a raspberry pi which uses telnet to log all smartevse messages to syslog. If any one needs this functionality just install screen and start a new session. In this session start the command:
telnet 192.168.1.10 | logger -t smartevse
now put the session in the background, you can then look at syslog file while messages are collected.
My setup uses a separate p1 monitor and the API is used to send the L1/2/3 values to the smartevse. And I have a fixed cable outside my house, I use a switch to disable or enable the smartevse
When I look at all the messages, I found that last night at 03:48 there was a State change from B to B1 because the API had a timeout, for 30 seconds there was no P1 information. The state change to B1 also disconnects the contactor, even when the car is not charging. I think the Ford Kuga does not like the power being disconnected.
Any thoughts on what to do to further diagnose and maybe solve the situation?
Anyone with experience on charging Ford Hybrid vehicles?
Any help appreciated. Very happy with the hardware and software!
I have two vehicles that I regularly connect to my smartevse v3 charger using the latest software. A BMW works very well with smartevse, I have not had any issues. But our Ford Kuga does not like the way the smartevse works.
With some persuation I can charge the Ford Kuga but almost all sessions end up in error. And connecting the Kuga to the cable must be done in a certain order or the charge will not start. If I connect the cable before the smartevse is active the Ford will error and only continue by disconnecting the cable first, then enable smartevse and connect. Only then the charge will start. As soon as I disable the smartevse while it is connected the Ford will error.
In order to diagnose the Ford issues I have a raspberry pi which uses telnet to log all smartevse messages to syslog. If any one needs this functionality just install screen and start a new session. In this session start the command:
telnet 192.168.1.10 | logger -t smartevse
now put the session in the background, you can then look at syslog file while messages are collected.
My setup uses a separate p1 monitor and the API is used to send the L1/2/3 values to the smartevse. And I have a fixed cable outside my house, I use a switch to disable or enable the smartevse
When I look at all the messages, I found that last night at 03:48 there was a State change from B to B1 because the API had a timeout, for 30 seconds there was no P1 information. The state change to B1 also disconnects the contactor, even when the car is not charging. I think the Ford Kuga does not like the power being disconnected.
Any thoughts on what to do to further diagnose and maybe solve the situation?
Anyone with experience on charging Ford Hybrid vehicles?
Any help appreciated. Very happy with the hardware and software!