Closed N1pp3 closed 3 years ago
For me it looks like you describe Autocharge and not Plug & Charge. Autocharge uses the CCS MAC address of the EV as the ID.
hey @N1pp3
sorry, your request flew under my radar, even though it was easy to implement. i added the logic with the commit above. feel free to test it and give feedback. i will merge it into master afterwards.
According to OCPP 1.6:
Therefore, message data elements of the IdToken class (including ParentId) MAY contain any data,subject to the constraints of the data-type (CiString20Type), that is meaningful to a Central System (e.g.for the purpose of identifying the initiator of charging activity), and Charge Points MUST NOT make any presumptions as to the format or content of such data (e.g. by assuming that it is a UID-like value that must be hex characters only and/or an even number of digits).
So my question is where does this limitation on SteVe come from?
So my question is where does this limitation on SteVe come from?
steve itself. i guess in the past we had some charging stations having troubles with more loose definitions of IdToken. therefore, we must have decided to limit what a human user can enter as idtag. currently, the characters are restricted to: Upper or lower case letters, numbers and dot, colon, dash, underscore symbols.
Thanks for the explanation
Hi!
Thanks for this amazing software!
We stared to play around with Plug & Charge and made it work whit Steve. But there is a smal problem.
We had to plug in the car and then add the vehicle ID from "Unknown Tags". Because of the limitations to add Colon (punctuation) in add new ID tag.
example: VID:00XXXXXXXXXX
So if you are able to remove the punctuation limitation it will be smother to add new ID.
We have tried it on Volvo and Audi and the issue is the same. We need to add VID: before ID, for it to recognize the vehicle.
The charger is hypercharger HYC 150.
Kind regards Jonas