search

steve-community / steve

SteVe - OCPP server implementation in Java
GNU General Public License v3.0
774 stars 380 forks source link

How do I connect Elvi EVBox (22 kW) to SteVe? #549

Closed ashupani10 closed 3 years ago

ashupani10 commented 3 years ago

Hi,

I want to connect my EVBox to the SteVe backend. I followed the instructions as provided in the Github page.

For EVBox, I went to EVBox connect app --> Installer Mode --> Charging Management Platform --> Different backend URL --> ws://<..server address for SteVe..>/steve/websocket/CentralSystemService/<..chargebox ID..>/

However, I am not able to get a heartbeat on SteVe.

Could someone please help me out with this.

Thanks in advance

goekay commented 3 years ago

you probably do not have to add the chargebox id yourself. the station might add it itself. therefore, the url can be like: ws://<..server address for SteVe..>/steve/websocket/CentralSystemService/

ashupani10 commented 3 years ago

Thanks,

I will try it out. What should I expect to happen? Should the EVbox just pop up on SteVe?

goekay commented 3 years ago

as a starter, you should see the station under "number of connected charge points". additionally, "received heartbeats" and "connector status" pages should list the station (and its connectors) as well.

ashupani10 commented 3 years ago

Hi,

Thank you for the reply, however, the charger is not seen on SteVe. Could any of the following cause the problem?

  1. EVBox Elvi (22kW) might have updated firmware that is not supported by SteVe or vice-versa. (But this should not be the case right? as OCPP is an open protocol)
  2. So my test setup is just a powered EVBox, there is no connector or EV connected - see image attachment. Could that cause an issue? IMG_20210407_161116
followthebeast commented 3 years ago

@ashupani10 when you compile steve, you're just creating an internal web server in your machine (your server address for SteVe. : localhost). So to connect your EVBox Elvi, you must create a network environment where your charging station can communicate with steve web server. In short, I think that your setup is not good. I can tell you that i have the same issue with EVBox Elvi model because it only connects in wifi or 4g. Steve is working properly for charging station with ethernet connection if you have a local solution.

ashupani10 commented 3 years ago

Hi @followthebeast ,

Thank you for your reply. That is indeed something that I will work on. As you might have guessed, I am pretty new to all this stuff. It would be great if I could get some guidance (tutorials, sources) to set up such a network environment to connect the EVBox. I will also search on my end how to do the same.

Meanwhile, I had some other questions related to SteVe.

  1. I want to implement smart charging and dynamic power management algorithms through SteVe, Is it possible to implement such smart charging algorithms?
  2. If yes, what do think would be the response time of such a system? 10 - 15 seconds, less, more?

Thank you again for your continual support,

Warm regards,

Ashutosh

goekay commented 3 years ago

the issue looks like to be related to the station. unfortunately, i cannot help further in this regard.

I want to implement smart charging and dynamic power management algorithms through SteVe, Is it possible to implement such smart charging algorithms?

yes, ocpp supports smart charging. and steve implements this part of ocpp.

If yes, what do think would be the response time of such a system? 10 - 15 seconds, less, more?

response time of what? this question is too vague. it all depends on your context.

ashupani10 commented 3 years ago

@goekay, by response time what I mean is the following:

Suppose the car is already charging with a current of 14 amps and I want to reduce it to 10 A. I send a command through Steve. What do you think would be the time between sending the charging signal through Steve and actual drop of current in the physical system?

csamsel commented 3 years ago

@ashupani10 when you compile steve, you're just creating an internal web server in your machine (your server address for SteVe. : localhost). So to connect your EVBox Elvi, you must create a network environment where your charging station can communicate with steve web server. In short, I think that your setup is not good. I can tell you that i have the same issue with EVBox Elvi model because it only connects in wifi or 4g. Steve is working properly for charging station with ethernet connection if you have a local solution.

There is no reason why WiFi or 4G would not work with SteVe. It's like you said, a working network connection between the station and the Steve application is required. If that's a problem, i suggest asking someone with expertise in that area. Done wrong it could lead to security issues.

followthebeast commented 3 years ago

@ashupani10 when you compile steve, you're just creating an internal web server in your machine (your server address for SteVe. : localhost). So to connect your EVBox Elvi, you must create a network environment where your charging station can communicate with steve web server. In short, I think that your setup is not good. I can tell you that i have the same issue with EVBox Elvi model because it only connects in wifi or 4g. Steve is working properly for charging station with ethernet connection if you have a local solution.

There is no reason why WiFi or 4G would not work with SteVe. It's like you said, a working network connection between the station and the Steve application is required. If that's a problem, i suggest asking someone with expertise in that area. Done wrong it could lead to security issues.

Yes, i'm talking just about my little experience with steve. Tested with a charging station locally and it works perfectly fine.

@goekay, by response time what I mean is the following:

Suppose the car is already charging with a current of 14 amps and I want to reduce it to 10 A. I send a command through Steve. What do you think would be the time between sending the charging signal through Steve and actual drop of current in the physical system?

I think it depends of the charging station itself. For example, i have tested a Schneider Smart Wallbox, to clear and set a charging profile, it takes around 5 to 7 seconds.

ashupani10 commented 3 years ago

Hey Guys!

Thanks a lot! I got it connected!!

goekay commented 3 years ago

@ashupani10 i am closing this issue, since i consider it resolved after your comment.

jpaquete commented 2 years ago

Hey Guys!

Thanks a lot! I got it connected!!

Hello ashupani10, I am having problems connecting to an EVBOX charger also. It automatically concatenates the chargeboxid and I get PageNotFound - No mapping for GET /backend/wsjon/EVB-P20151773 from steve. Did you manage to solve this ?... Can you help ? Thx!!

axen2u commented 2 years ago

@jpaquete Check your URL Normally It should be like this if you're using JSON websocket ws://<ip>:<port>/steve/websocket/CentralSystemService/<Chargeboxid>

I found some boxes automatically adding (ex:- node-red-contrib-ocpp) chargerbox id at the end of the URL. In those cases just use ws://<ip>:<port>/steve/websocket/CentralSystemService

wlanrouter commented 1 year ago

Hey Guys!

Thanks a lot! I got it connected!!

Could you please describe your settings? What is the APN setting on the wallbox? What is platform management? What is the exact websocket address at the wallbox? With WallboxId at the end or not?

What must be done on SteVe to get a heartbeat?

Edit: Solved it. Platform adress at wallbox is (without ID!): ws://192.168.100.10:8080/steve/websocket/CentralSystemService APN at wallbox is unchanged: Something with tele2. It seems like it doesn't matter.

In the SteVe Webinterface>Log I had following entries: [ERROR] 2023-09-06 14:17:43,848 de.rwth.idsg.steve.ocpp.ws.OcppWebSocketHandshakeHandler (qtp6157254-392) - ChargeBoxId 'EVB-P21124229' is not recognize

I added the ChargeBoxId manually in SteVe Webinterface. Just the ID, all other fields (coutry, ZIP code, OCPP version) left empty. Afterwards it was listed in the SteVe Webinterface home screen.