Transportation & InfrastructureS69
EV Bus Charging Infrastructure
ปัญหา
Depot chargers, transformers and building loads share one grid connection, and without live data the depot risks peak charges or buses not charged by morning.
ภาพรวมโซลูชัน
MILESGO gateways collect data from EV chargers (Modbus interface or charging platform API), electricity meters, transformer temperature and tap monitors, power quality analysers over Modbus TCP / Modbus RTU, and deliver it to the energy management system, third-party platforms (HTTP API), the utility SCADA (IEC 104 / IEC 61850) as MQTT / OPC UA / IEC 60870-5-104. 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
- transformer temperature and tap monitors
- power quality analysers
Protocol path
Modbus TCP / Modbus RTU → MQTT / OPC UA / IEC 60870-5-104
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).
- Any set-point control of PV or storage must follow the grid-connection requirements; start with monitoring only.
- Record CT ratios, meter IDs and multipliers in the point table; wrong multipliers are the usual cause of billing errors.
- Where equipment only offers a vendor API or cloud, confirm access rights, data rate and costs with the vendor before design.
- Commission in read-only mode first; enable write / control points only after the client approves each one.
- Define an alarm matrix (priority, recipient, escalation) and test every alarm end to end at SAT.
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, transformer temperature and tap monitors, power quality analysers, 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, third-party platforms (HTTP API), the utility SCADA (IEC 104 / IEC 61850), which receives the data as MQTT / OPC UA / IEC 60870-5-104. Remote access for maintenance runs over VPN rather than open internet ports.
องค์ประกอบของระบบ
- Field devices
- EV chargers (Modbus interface or charging platform API), electricity meters, transformer temperature and tap monitors, power quality analysers
- Edge / integration
- MILESGO protocol gateways and edge controllers
- Upper systems
- the energy management system, third-party platforms (HTTP API), the utility SCADA (IEC 104 / IEC 61850) (MQTT / OPC UA / IEC 60870-5-104)
- Tools and commissioning
- Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools
ความสามารถด้านซอฟต์แวร์และ AI
- Load and consumption forecastingอยู่ในแผน
ขั้นตอนการส่งมอบ
- 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
- Abnormal conditions seen early, before they become failures
- One view of all subsystems instead of separate vendor consoles
- Consumption attributable by tenant, department or cost centre
โซลูชันอื่นใน Transportation & Infrastructure
บอกเราเกี่ยวกับโครงการของคุณ
ส่งโปรโตคอล จำนวนจุดข้อมูล และระบบปลายทางมาให้เรา ทีมฝ่ายขายและวิศวกรรมจะตรวจสอบทุกคำขอ
ปรึกษาโครงการของคุณ