Quick start
This guide explains how to start a virtual charger on the IoT service platform and debug against your backend.
Why this project exists
In charging-stack development, relying on physical chargers and real load for every test wastes a lot of time. This project provides protocol-level simulators so you can exercise common protocols between a “charger” and your platform without real hardware.
Supported protocols
| Simulated debugging | Simulated load test | |
|---|---|---|
| YKC 1.6 | Yes | Yes |
| OCPP 1.6-J | Yes | No (planned) |
1.1 Create a virtual device profile
Open Virtual device → Virtual device config, add a profile, and choose YKC1.6 or OCPP1.6-J.
Profile fields
| Field | Description |
|---|---|
| Protocol | YKC1.6 (YKC 1.6) or OCPP1.6-J (OCPP 1.6 JSON) |
| Connector count | Number of simulated connectors |
| Firmware version | YKC 0x01 program version; OCPP BootNotification.firmwareVersion |
| Pile type | Fast vs slow (affects SoC and YKC BMS-related reporting) |
| Working current | Reported current after charging starts |
| Working voltage | Reported voltage after charging starts |
| Working temperature | Reported temperature after charging starts |
| Full charge time | Auto-stop delay for remotely started sessions |
1.2 Create a virtual device
Open Virtual device → Virtual device management, add a device, and set device ID, server IP, server port, protocol, and device profile.
For OCPP, also set the server path.
1.3 Debug UI
Click the device name in the list to open the detail page.
When disconnected, click Start to launch the first virtual device according to the profile.
Simulate plug / unplug:
At the bottom of the page you can subscribe to live traffic:
