Ocpp, possible to send heartbeat signal?

[Jonas S]

Hello

Would it be possible, maybe through websocket? to send heartbeat command to ocpp backend? 
What I'm really after is to use a energy meter and send consumption to the backends Load managment but if I could mange to figure out just the heartbeat function I should be able to get the rest working by my self


json script for heartbeat response:
{
    "$schema": "http://json-schema.org/draft-04/schema#",
    "id": "urn:OCPP:1.6:2019:12:HeartbeatResponse",
    "title": "HeartbeatResponse",
    "type": "object",
    "properties": {
        "currentTime": {
            "type": "string",
            "format": "date-time"
        }
    },
    "additionalProperties": false,
    "required": [
        "currentTime"
    ]
}



/Jonas

[admin]

We're looking into OCPP at the moment. Examples will be posted when ready.

[admin]

See attached code for OCPP v1.6 client example.

[Jonas S]

See attached code for OCPP v1.6 client example.

Cool. Thanks

[pioneersteffen]

We're looking into OCPP at the moment. Examples will be posted when ready.

Many thanks, looks promising! Do you see a difference to using it with OCPP 2.0?

[admin]

The base protocol is the same but the command structure is different. Meaning this example won't work with 2.0 without modifications.

[pioneersteffen]

Thanks admin for the quick reply! Are you planning to supply also a template for OCPP version 2.0 in future?

[admin]

Attached v2.0 client example.

[pioneersteffen]

Many thanks for the prompt help!

[victor.back]

See attached code for OCPP v1.6 client example.

Thanks for sharing examples. 

I ran this in a Resident with the user.websocket and get 
arg1 string: ws connection failed
arg2 string: connection refused

tried it on an Easee chargebox.

[admin]

This example emulates a charger so LM acts as a client. Connecting charger to LM is a different thing.

[victor.back]

This example emulates a charger so LM acts as a client. Connecting charger to LM is a different thing.

Okey, but is it possible to connect a charger to LM via OCPP for doing a smart charging solution? 

Heres the developer doc from Easee
https://developer.easee.cloud/docs/ocpp-smart-charging

[admin]

Possible but we don't have a ready example at the moment. See this for Easee connectivity: https://forum.logicmachine.net/showthread.php?tid=3301

[victor.back]

Possible but we don't have a ready example at the moment. See this for Easee connectivity: https://forum.logicmachine.net/showthread.php?tid=3301

Okey thank you!

[domotiqa]

Is there any solutioon to take information from EV CHARGING Expert SCHNEIDER HMIBSC...

For example take the total/zone consumsion of evlink.... I know we can communicate modbus to the evlink (but I have 20 evlink). I was looking for a solution to interface with the SE EV HMI.
Do you know it ?
thanks

[FatMax]

Is there any solutioon to take information from EV CHARGING Expert SCHNEIDER HMIBSC...

For example take the total/zone consumsion of evlink.... I know we can communicate modbus to the evlink (but I have 20 evlink). I was looking for a solution to interface with the SE EV HMI.
Do you know it ?
thanks

The EV Charging Expert does not expose that information in the API they developed for the EVCE.

You are better off requesting the info over modbus tcp.

[domotiqa]

ok
I ssaw that we can provide ocpp server on the EV but not yet implemented on LM I guess
I didn't know there was an API

when you say modbus ip you mean to the evlink not the EVCE, cause I didn't find any modbus register for it, only for the evlink station

[FatMax]

ok
I ssaw that we can provide ocpp server on the EV but not yet implemented on LM I guess
I didn't know there was an API

when you say modbus ip you mean to the evlink not the EVCE, cause I didn't find any modbus register for it, only for the evlink station

Yes, I mean polling the EVlinks via modbus TCP.

[hocine]

hello  

Is there any information about OCPP protocol support?

THX

[Daniel]

For the last two years we didn't see any demand from OCPP as all EV chargers did support modbus or other way of communications. Due to this and many versions of the protocol we did freeze any development on this.