RemoteStopTransaction Returns Rejected

[sait1801]

Hi again,
I tried remote start and stop transaction via dashboard but I cannot stop charging because charger returns:
{ "status": "Rejected" }

What can be the reason for that ?

Thanks in advance

[ufocomp]

Hi! Make sure that you have entered a valid transaction number. If the command is sent to the emulator, it does not save the transaction number after reconnecting (rebooting).

[sait1801]

I tried it on a real charger without any charging profile payload. I tried numbers from 0 to 300 for transaction id, still none of them were accepted. The error for real charger is :
Transaction ID: 2, Response: {"error": {"code": 400, "message": "InternalError: No transaction with id '2' was found"}}

[ufocomp]

To stop the charging session, you must first start it. Please read sections "4.8. Start Transaction" and "5.11. Remote Start Transaction" an OCPP protocol v 1.6.

[sait1801]

I used the RemoteStartTransaction for starting charging and it worked. (I left ChargingProfile part blank). Then, tried to remotestoptransaction again. It didn't work. How will I know the TransactionID, without giving the ChargeProfile here :

Thanks, for the quick support 🙏

[ufocomp]

The charging profile has nothing to do with the number of the upcoming transaction.

5.11. Remote Start Transaction

Central System can request a Charge Point to start a transaction by sending a RemoteStartTransaction.req. Upon
receipt, the Charge Point SHALL reply with RemoteStartTransaction.conf and a status indicating whether it has
accepted the request and will attempt to start a transaction.

4.8. Start Transaction

The Charge Point SHALL send a StartTransaction.req PDU to the Central System to inform about a transaction
that has been started. If this transaction ends a reservation (see Reserve Now operation), then the
StartTransaction.req MUST contain the reservationId.
Upon receipt of a StartTransaction.req PDU, the Central System SHOULD respond with a StartTransaction.conf
PDU. This response PDU MUST include a transaction id and an authorization status value.

In other words, after you have sent a RemoteStartTransaction command to the charging station, it will request permission from the Central System to start a charging session, and if the decision is positive, the Central System will return the transactionId.

[ufocomp]

A charging session cannot be started on a physical station without workload. A car or a special workload simulation device must be connected to the charging station. Without workload, the charging station immediately completes the transaction. You can request the status of the connectors from the charging station by sending a Trigger Message command with the StatusNotification parameter.

[sait1801]

Sorry for the missing information, I connected simulation device to the charger, the problem happened while simulating the charging session

[sait1801]

This reason is solved because the charger that I tried did no thave setchargeoprofilehandler.