RemoteStartTransaction
RemoteTrigger CSMS->CP
Sent by the Central System to remotely start a charging transaction.
Quick Reference
Required Fields
idTag string(20) Identifier to use for the transaction
Optional Fields
connectorId integer Specific connector to use (omit for any available)
chargingProfile object Charging profile to use for this transaction
Example Payload
{
"idTag": "AABBCCDD",
"connectorId": 1
} Example Full Frame
[
2,
"msg-001",
"RemoteStartTransaction",
{
"idTag": "AABBCCDD",
"connectorId": 1
}
]
Format: [MessageType, MessageId, Action, Payload]
Overview
The RemoteStartTransaction command allows the Central System to initiate a charging session remotely (e.g., via mobile app).
When Received
- User requests charging start via mobile app
- Automated charging triggered by tariff schedules
- Integration with fleet management systems
Expected Response
The CP responds with:
status:AcceptedorRejected
What Happens After Acceptance
- CP authorizes using provided idTag
- CP starts transaction on specified or available connector
- CP sends StartTransaction message
- Normal charging session proceeds
Usage Notes
- If connectorId is omitted, CP selects an available connector
- Provided idTag is used for StartTransaction
- chargingProfile (if provided) defines power limits for this session
- CP must validate idTag locally or via Authorize
Best Practices
- Connector availability - Check connector status before sending
- Authorization - Ensure idTag is valid and authorized
- User feedback - Notify user of acceptance/rejection via app
- Timeout handling - Handle cases where CP doesn’t respond
- Charging profiles - Use profiles for smart charging and load management
Testing Tips
- Test with specific connectorId
- Test with omitted connectorId (auto-select)
- Test with unavailable connector to verify rejection
- Test with invalid idTag
- Test with chargingProfile included
Common Errors
GenericError
Cause: Connector already in use
Solution: Ensure connector is available before remote start
PropertyConstraintViolation
Cause: Invalid connectorId
Solution: Use valid connector ID or omit for auto-selection