Practical guides for CSMS teams — OCPP simulator comparisons, testing strategies, and protocol deep dives.
Happy-path tests tell you the system works. Invalid scenario tests tell you it won't break in production. Here is what to test — and how SimIt makes each scenario reproducible.
Read article →AC chargers top out around 22 kW. DC fast chargers go from 50 kW to 350 kW. The difference matters for CSMS billing, smart charging profile limits, and how a simulator needs to behave.
Read article →A multi-connector charge point can run two or more sessions simultaneously. Testing this concurrency in your CSMS — session isolation, meter tracking per connector, smart charging across connectors — requires a simulator that handles it correctly.
Read article →MeterValues is how a charging station reports energy delivery to the CSMS. Static dummy values hide a class of billing and SOC bugs that only surface when the simulator meters realistically.
Read article →Unit tests cannot catch OCPP protocol bugs — you need a live charging station to connect. A REST-driven simulator makes OCPP integration tests viable in any CI pipeline.
Read article →A CSMS is the backend that every EV charger talks to over OCPP. It authorizes sessions, tracks energy, controls power limits, and manages hundreds of stations remotely. Here is how it works and how teams test it.
Read article →When a charging station has a hardware or software problem, it tells the CSMS via a StatusNotification error code. Your CSMS needs to handle each one correctly — and testing that requires fault injection.
Read article →Authorization in OCPP has multiple layers: online CSMS lookup, local authorization list, and authorization cache. The interactions between them — especially offline — are a common source of hard-to-reproduce bugs.
Read article →Smart charging lets a CSMS control how much power each charger draws. SetChargingProfile is the command that makes it work. Here is how the profile model works and how to test it.
Read article →OCPP is not a REST API — it is a persistent WebSocket protocol. Understanding the connection URL, message format, and reconnect behaviour is essential for CSMS developers and simulator users.
Read article →OCPP 1.6 is still the most widely deployed version. OCPP 2.0.1 is the future. Understanding the differences — device model, transaction messages, and security — is essential for CSMS developers supporting both.
Read article →A technical comparison of OCPP simulator options for CSMS teams: open-source tools versus managed SaaS, covering protocol support, deployment complexity, scale, and maintenance.
Read article →An OCPP simulator is software that speaks the OCPP protocol exactly like a real charging station — without any hardware. Here is what it does and why every CSMS team needs one.
Read article →External coverage
Read the launch note for SimIt's OCPP 2.0.1 simulator support, including TransactionEvent lifecycle, multi-EVSE scenarios, smart charging, device model behavior, and security handlers.
Read on LinkedIn