A self-hosted, lightweight implementation of a protocol server for cloud fast charging.

⚠️ This project is under development, please do not use in production environment. The original protocol can be viewed here

Concept

Quick Start

You can find latest release here.

Run it with:

./ykc-proxy-server

Flags

There are some flags to customize server's behavior without having to write a configuration file.

Example:

./ykc-proxy-server -servers 127.0.0.1:8080 -autoVerification true -autoBillingModelVerify true

supported server options:

Flag	Description	Default Value
host	host IP address	0.0.0.0
tcpPort	TCP server port	27600
httpPort	HTTP server port	9556
autoVerification	if enabled, the proxy server will automatically pass after receiving the login authentication message(01)	false
autoHeartbeatResponse	if enabled, the proxy server will automatically answer the heartbeat message(03) when it receives it	true
autoBillingModelVerify	if enabled, the proxy server will automatically pass after receiving the billing model verify message(05)	false
autoTransactionRecordConfirm	if enabled, the proxy server will automatically confirm the transaction record uploaded by device(3b)	false
messagingServerType	if you need to push device messages to other systems, modify this argument to specify the protocol (currently only HTTP and NATS protocol are supported)	http
servers	push endpoint (if there is more than one, separate them with commas)
username	username for message broker
password	password for message broker

Forward device messages to HTTP endpoints

If you start server with:

./ykc-proxy-server -servers 127.0.0.1:8080/charge/ykc/messages

The proxy server will forward the device messages to your endpoint. The proxy server will use your endpoint as prefix.

Taking the login authentication message (01) as an example, the proxy service will forward the message to http://127.0.0.1:8080/charge/ykc/messages/01.

Forward device messages to NATS

If you start server with:

./ykc-proxy-server -messagingServerType nats -servers nats://127.0.0.1:4222 -username user -password pwd

The proxy server will forward the device messages to your NATS server. The proxy server will use charge.proxy.ykc as the subject's prefix.

Taking the login authentication message (01) as an example, the proxy service will forward the message to charge.proxy.ykc.01.

Control device with REST API

see API list here -> REST API document

Build it yourself

git clone https://github.com/LLLLimbo/ykc-proxy-server.git \
&& cd ykc-proxy-server \
&& go build .

Currently supported messages

This is the current list of supported messages, you can find more detailed information here

帧类型码	帧类型码名称	数据传送方向	已支持
0x01	充电桩登录认证	充电桩->运营平台	✅
0x02	登录认证应答	运营平台->充电桩	✅
0x03	充电桩心跳包	充电桩->运营平台	✅
0x04	心跳包应答	运营平台->充电桩	✅
0x05	计费模型验证请求	充电桩->运营平台	✅
0x06	计费模型验证请求应答	运营平台->充电桩	✅
0x09	充电桩计费模型请求	充电桩->运营平台	✅
0x0A	计费模型请求应答	运营平台->充电桩	✅
0x12	读取实时监测数据	运营平台->充电桩
0x13	离线监测数据	充电桩->运营平台	✅
0x15	充电握手	充电桩->运营平台
0x17	参数配置	充电桩->运营平台
0x19	充电结束	充电桩->运营平台	✅
0x1B	错误报文	充电桩->运营平台
0x1D	充电阶段 BMS 中止	充电桩->运营平台
0x21	充电阶段充电机中止	充电桩->运营平台
0x23	充电过程 BMS 需求、充电机输出	充电桩->运营平台
0x25	充电过程 BMS 信息	充电桩->运营平台
0x31	充电桩主动申请启动充电	充电桩->运营平台
0x32	运营平台确认启动充电	运营平台->充电桩
0x33	远程启机命令回复	充电桩->运营平台	✅
0x34	运营平台远程控制启机	运营平台->充电桩	✅
0x35	远程停机命令回复	充电桩->运营平台	✅
0x36	运营平台远程停机	运营平台->充电桩	✅
0x3B	交易记录	充电桩->运营平台	✅
0x40	交易记录确认	运营平台->充电桩	✅
0x41	余额更新应答	充电桩->运营平台
0x42	远程账户余额更新	运营平台->充电桩
0x43	卡数据同步应答	充电桩->运营平台
0x44	离线卡数据同步	运营平台->充电桩
0x45	离线卡数据清除应答	充电桩->运营平台
0x46	离线卡数据清除	运营平台->充电桩
0x47	离线卡数据查询应答	充电桩->运营平台
0x48	离线卡数据查询	运营平台->充电桩
0x51	充电桩工作参数设置应答	充电桩->运营平台
0x52	充电桩工作参数设置	运营平台->充电桩
0x55	对时设置应答	充电桩->运营平台
0x56	对时设置	运营平台->充电桩
0x57	计费模型应答	充电桩->运营平台	✅
0x58	计费模型设置	运营平台->充电桩	✅
0x61	地锁数据上送（充电桩上送）	充电桩->运营平台
0x62	遥控地锁升锁与降锁命令(下行)	运营平台->充电桩
0x63	充电桩返回数据（上行）	充电桩->运营平台
0x91	远程重启应答	充电桩->运营平台	✅
0x92	远程重启	运营平台->充电桩	✅
0x93	远程更新应答	充电桩->运营平台
0x94	远程更新	运营平台->充电桩
0xA1	充电桩主动申请并充充电	充电桩->运营平台
0xA2	运营平台确认并充启动充电	运营平台->充电桩
0xA3	远程并充启机命令回复	运营平台->充电桩
0xA4	运营平台远程控制并充启机	充电桩->运营平台