𝙀𝙑𝘽 𝘾𝙝𝙖𝙧𝙜𝙞𝙣𝙜 Consolidates the global charging infrastructure  network at EV Charge Show! At EV Charge Show, #EVB unveils our flagship  products including the Floor-mounted 2 Guns AC/DC #EV Chargers. Wi

Define the stopping permissions for each charging session before a two-connector charger enters service. Starting one session should not leave the operator guessing whether the same card, app account or shared screen can stop another driver’s session. The required behaviour needs an explicit policy and a controlled test of the installed arrangement.

Keep ordinary session stopping separate from emergency controls and electrical isolation. They have different purposes. A successful app stop demonstrates a session action, not that the equipment is safe for maintenance.

Write down the roles and the intended permissions

Identify the driver, the charging-session credential, customer support and site administration. A credential might be an app account or a radio-frequency identification card, usually called an RFID card. It is evidence used for authorisation, not automatically a universal right to control every session at a cabinet.

Decide the intended rule for ordinary driver actions. For a public service, an operator may require a driver to control only their own session while designated support staff can intervene through an authorised process. A private fleet may have a different policy for shared vehicles and staff credentials.

Record what support staff are allowed to do, the reason they must capture and where their intervention is logged. Avoid granting full administrator access simply because an agent needs to help a customer stop charging.

Match physical labels to the session records

The public DC charger families listed by EVB include two-gun configurations in wall-mounted and floor-mounted arrangements. That makes the relationship between cabinet, connector and session a relevant operating question. The category listing does not establish a particular model’s stopping permissions.

Give each tested output a recognisable identifier and map it to the management-system record. If a shared screen says “left” and “right”, establish how that relates to the labels seen by a driver and by support staff.

The operator needs to know which session an action addresses. A correct permission applied to the wrong output can still interrupt another customer.

Test two sessions with different credentials

Use an operator-approved test arrangement with two identified sessions and separate test credentials. Define the expected result before attempting each ordinary stop action. Do not experiment on real customers’ sessions.

For each output, test the credential that started its session and an unrelated test credential. Then test the approved support process. Record whether the intended session stopped, whether the other session continued and which event the platform logged.

An illustrative public-site policy might expect the starting credential to stop its own session, the unrelated credential to be refused, and authorised support to stop a specified session with a recorded reason. These are proposed acceptance outcomes for that policy, not a statement of universal charger behaviour.

Include the shared screen and the platform

The local screen, app and support platform may expose different actions. Test each interface the service actually offers. An app result cannot establish what happens when someone uses a shared on-site control.

Where the Open Charge Point Protocol, or OCPP, is used, it connects a charging station to its management system. The protocol name alone does not prove how the installed software maps credentials, user roles and session commands. Capture the relevant charger and platform versions with the test record.

Keep emergency-control testing within the specialist commissioning procedure. Do not use an emergency control as an ordinary authorisation test or infer its full effect from a normal session stop.

Give customer support a precise intervention record

A useful support record identifies the site, cabinet, output and session, the requestor’s verified authority, the action, its reason and the observed outcome. Retain only the necessary personal information under the operator’s data-handling arrangements.

If a test exposes an unexpected stop or an ambiguous output selection, record the actual behaviour and assign it for correction before accepting that workflow. Do not change the expected result afterwards merely to match what the equipment did.

The result should be a clear service policy: who may stop which session, through which interface, with what evidence. That gives drivers a predictable experience and gives support staff a safe administrative boundary for helping them.