EV Charging Station Integration

ปัญหา

Chargers added to a car park can overload the building supply, yet the BMS and energy system have no visibility of charging power or charger faults.

ภาพรวมโซลูชัน

MILESGO gateways collect data from EV chargers (Modbus interface or charging platform API), electricity meters, run/stop and fault dry contacts over Modbus TCP / Modbus RTU, and deliver it to the energy management system, the BMS, third-party platforms (HTTP API) as BACnet/IP / MQTT. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

EV chargers (Modbus interface or charging platform API)
electricity meters
run/stop and fault dry contacts

Protocol path

Modbus TCP / Modbus RTU → BACnet/IP / MQTT

Implementation checklist for the project manager

Charger data comes from each charger’s Modbus interface, its energy meter or the charging platform’s API; confirm what each model exposes (OCPP is not handled by the gateway).
Where equipment only offers a vendor API or cloud, confirm access rights, data rate and costs with the vendor before design.
Record CT ratios, meter IDs and multipliers in the point table; wrong multipliers are the usual cause of billing errors.
Commission in read-only mode first; enable write / control points only after the client approves each one.
Issue an IP address plan and VLAN / firewall rules with the client’s IT team before installation.
Keep OT networks segregated and use VPN for remote access instead of opening ports to the internet.

Project deliverables

Signed point table and protocol mapping
Gateway configuration files and backups
IP address plan and network drawing
FAT and SAT test records
As-built documentation and operator training

สถาปัตยกรรมระบบ

Field layer: EV chargers (Modbus interface or charging platform API), electricity meters, run/stop and fault dry contacts, connected over Modbus TCP / Modbus RTU. Edge and integration layer: MILESGO protocol gateways and edge controllers, mounted on DIN rail in existing panels, polling each device, time-stamping values and buffering them locally. Upper layer: the energy management system, the BMS, third-party platforms (HTTP API), which receives the data as BACnet/IP / MQTT. Remote access for maintenance runs over VPN rather than open internet ports.

องค์ประกอบของระบบ

Field devices: EV chargers (Modbus interface or charging platform API), electricity meters, run/stop and fault dry contacts
Edge / integration: MILESGO protocol gateways and edge controllers
Upper systems: the energy management system, the BMS, third-party platforms (HTTP API) (BACnet/IP / MQTT)
Tools and commissioning: Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

ความสามารถด้านซอฟต์แวร์และ AI

Load and consumption forecastingอยู่ในแผน
Consumption baseline and deviation alertsอยู่ในแผน

ขั้นตอนการส่งมอบ

1
Site survey and point list
Inventory devices, protocols, register maps, panel space, power and network paths.
2
Design and point table sign-off
Map every point to the target protocol and system; agree it with the client and the upper-system contractor.
3
Configuration and FAT
Build the gateway configuration off site, simulate it and test against the signed point table.
4
Installation and wiring
Mount gateways on DIN rail, wire RS-485 / I/O / Ethernet, apply the IP plan.
5
SAT and alarm tests
Verify values against local readings, test every alarm and command end to end.
6
Handover and support
Hand over configuration backups, point table and as-built documents; train operators.

คุณค่าสำหรับลูกค้า

Consumption visible by area, system and time period
One view of all subsystems instead of separate vendor consoles
Alarms reach the right person by SMS, email or messaging apps
Consumption attributable by tenant, department or cost centre

โซลูชันอื่นใน Energy & Power

บอกเราเกี่ยวกับโครงการของคุณ

ส่งโปรโตคอล จำนวนจุดข้อมูล และระบบปลายทางมาให้เรา ทีมฝ่ายขายและวิศวกรรมจะตรวจสอบทุกคำขอ

ปรึกษาโครงการของคุณ