TC_054_CSMS — Trigger Message

TC_054_CSMS — Trigger Message

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 171.

Identification

Field	Value
Test case name	Trigger Message
Test case Id	TC_054_CSMS
System under test	Central System

Description

The Central System triggers a message from the Charge Point

Purpose

Check whether the Central System is able to trigger a message from the Charge Point.

Prerequisite(s)

The Central System supports the Remote Trigger feature profile.

Before (Preparations)

Configuration State(s):

• N/a

Memory State(s):

• N/a

Reusable State(s):

• N/a

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
2. The Charge Point responds with a TriggerMessage.conf	1. The Central System sends a TriggerMessage.req
3. The Charge Point sends a MeterValues.req	4. The Central System responds with a MeterValues.conf
6. The Charge Point responds with a TriggerMessage.conf	5. The Central System sends a TriggerMessage.req
7. The Charge Point sends a Heartbeat.req	8. The Central System responds with a Heartbeat.conf
10. The Charge Point responds with a TriggerMessage.conf	9. The Central System sends a TriggerMessage.req
11. The Charge Point sends a StatusNotification.req	12. The Central System responds with a StatusNotification.conf
14. The Charge Point responds with a TriggerMessage.conf	13. The Central System sends a TriggerMessage.req
15. The Charge Point sends a DiagnosticsStatusNotification.req	16. The Central System responds with a DiagnosticsStatusNotification.conf
18. The Charge Point responds with a TriggerMessage.conf	17. The Central System sends a TriggerMessage.req
[The following message will be sent if implemented.]; 19. The Charge Point sends a FirmwareStatusNotification.req	20. The Central System responds with a FirmwareStatusNotification.conf

Tool validation(s)

Charge Point side:

Step 2/6/10/14:

(Message: TriggerMessage.conf) The status is Accepted

Step 15:

(Message: DiagnosticsStatusNotification.req) The status is Idle

Step 18:

(Message: TriggerMessage.conf) The status is Accepted OR NotImplemented

Step 19:

(Message: FirmwareStatusNotification.req) The status is Idle

Central System side:

Step 1:

(Message: TriggerMessage.req) requestedMessage should be MeterValues connectorId should be <Configured ConnectorId>

Step 5:

(Message: TriggerMessage.req) requestedMessage should be Heartbeat

Step 9:

(Message: TriggerMessage.req) requestedMessage should be StatusNotification connectorId should be <Configured ConnectorId>

Step 13:

(Message: TriggerMessage.req) requestedMessage should be DiagnosticsStatusNotification

Step 17:

(Message: TriggerMessage.req) requestedMessage should be FirmwareStatusNotification

Expected result(s) / behaviour

Charge Point side:

• N/a

Central System side:

The Central System can request a message from a Charge Point and receive the requested message.