In OCPP 1.6, TransactionMessageRetryInterval applies to the following transaction-related messages:
- StartTransaction.req
- StopTransaction.req
- MeterValues.req
MicroOcpp applies this setting in the fetchFrontRequest() method of each connector type:
However, none of the above requests have an explicit timeout applied, causing them to use the default of 40s. This effectively limits the value of TransactionMessageRetryInterval to this same minimum, since this setting cannot be evaluated until the Request timeout expires.
To improve this, we could ensure that setTimeout on each new transaction request is updated using the current value of TransactionMessageRetryInterval, or possibly through a project build configuration value.
In OCPP 1.6,
TransactionMessageRetryIntervalapplies to the following transaction-related messages:MicroOcpp applies this setting in the
fetchFrontRequest()method of each connector type:However, none of the above requests have an explicit timeout applied, causing them to use the default of 40s. This effectively limits the value of
TransactionMessageRetryIntervalto this same minimum, since this setting cannot be evaluated until theRequesttimeout expires.To improve this, we could ensure that
setTimeouton each new transaction request is updated using the current value ofTransactionMessageRetryInterval, or possibly through a project build configuration value.