X-Git-Url: https://git.piment-noir.org/?a=blobdiff_plain;f=README.md;h=ad3f40a25a4a5ebae6cbfcc35d39d19027e5282a;hb=7edba9a79cf60b1d1113ec89f310788194ddb97a;hp=8ce209e59e8b06e25788b498af09e95162c9dbb5;hpb=38cc3b4ba35912552e88b0b8d2f16072a97b9b7f;p=e-mobility-charging-stations-simulator.git diff --git a/README.md b/README.md index 8ce209e5..ad3f40a2 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,7 @@ # [e-mobility charging stations simulator](https://github.com/sap/e-mobility-charging-stations-simulator) +[![CI worklow](https://github.com/SAP/e-mobility-charging-stations-simulator/actions/workflows/ci.yml/badge.svg)](https://github.com/SAP/e-mobility-charging-stations-simulator/actions/workflows/ci.yml) [![REUSE status](https://api.reuse.software/badge/github.com/SAP/e-mobility-charging-stations-simulator)](https://api.reuse.software/info/github.com/SAP/e-mobility-charging-stations-simulator) ## Summary @@ -34,10 +35,11 @@ brew install node ## Installation -Enable corepack if not already done: +Enable corepack if not already done and install latest pnpm version: ```shell corepack enable +corepack prepare pnpm@latest --activate ``` In the repository root, run the following command: @@ -49,7 +51,7 @@ pnpm install ## Initial configuration Copy the configuration template file [src/assets/config-template.json](src/assets/config-template.json) to [src/assets/config.json](src/assets/config.json). -Copy the authorization RFID tags template file [src/assets/authorization-tags-template.json](src/assets/authorization-tags-template.json) to [src/assets/authorization-tags.json](src/assets/authorization-tags.json). +Copy the RFID tags template file [src/assets/idtags-template.json](src/assets/idtags-template.json) to [src/assets/idtags.json](src/assets/idtags.json). Tweak them to your needs by following the section [configuration files syntax](README.md#configuration-files-syntax). @@ -76,7 +78,7 @@ The charging stations simulator's configuration parameters must be within the `s All charging station configuration templates are in the directory [src/assets/station-templates](src/assets/station-templates). -A list of RFID tags must be defined for the automatic transaction generator with a default location and name: `src/assets/authorization-tags.json`. A template file is available at [src/assets/authorization-tags-template.json](src/assets/authorization-tags-template.json). +A list of RFID tags must be defined for the automatic transaction generator in a file with a default location and name: `src/assets/idtags.json`. A template file is available at [src/assets/idtags-template.json](src/assets/idtags-template.json). **Configuration files hierarchy and priority**: @@ -142,7 +144,7 @@ But the modifications to test have to be done to the files in the build target d | ocppPersistentConfiguration | true/false | true | boolean | enable persistent OCPP parameters storage by charging stations 'hashId'. The persistency is ensured by the charging stations configuration files in [dist/assets/configurations](dist/assets/configurations) | | stationInfoPersistentConfiguration | true/false | true | boolean | enable persistent station information and specifications storage by charging stations 'hashId'. The persistency is ensured by the charging stations configuration files in [dist/assets/configurations](dist/assets/configurations) | | wsOptions | | {} | ClientOptions & ClientRequestArgs | [ws](https://github.com/websockets/ws) and node.js [http](https://nodejs.org/api/http.html) clients options intersection | -| authorizationFile | | undefined | string | RFID tags list file relative to src/assets path | +| idTagsFile | | undefined | string | RFID tags list file relative to src/assets path | | baseName | | undefined | string | base name to build charging stations id | | nameSuffix | | undefined | string | name suffix to build charging stations id | | fixedName | true/false | false | boolean | use the baseName as the charging stations unique name | @@ -181,11 +183,12 @@ But the modifications to test have to be done to the files in the build target d | firmwareUpgrade | | {
"versionUpgrade": {
"step": 1
},
"reset": true
} | {
versionUpgrade: {
patternGroup: number;
step: number;
};
reset: boolean;
failureStatus: 'DownloadFailed' \| 'InstallationFailed';
} | Configuration section for simulating firmware upgrade support. | | commandsSupport | | {
"incomingCommands": {},
"outgoingCommands": {}
} | {
incomingCommands: Record;
outgoingCommands?: Record;
} | Configuration section for OCPP commands support. Empty section or subsections means all implemented OCPP commands are supported | | messageTriggerSupport | | {} | Record | Configuration section for OCPP commands trigger support. Empty section means all implemented OCPP trigger commands are supported | -| Configuration | | | ChargingStationConfiguration | charging stations OCPP parameters configuration section | -| AutomaticTransactionGenerator | | | AutomaticTransactionGenerator | charging stations ATG configuration section | -| Connectors | | | Connectors | charging stations connectors configuration section | +| Configuration | | | ChargingStationOcppConfiguration | charging stations OCPP parameters configuration section | +| AutomaticTransactionGenerator | | | AutomaticTransactionGeneratorConfiguration | charging stations ATG configuration section | +| Connectors | | | Record | charging stations connectors configuration section | +| Evses | | | Record | charging stations EVSEs configuration section | -#### Configuration section +#### Configuration section syntax example ```json "Configuration": { @@ -211,9 +214,9 @@ But the modifications to test have to be done to the files in the build target d } ``` -#### AutomaticTransactionGenerator section +#### AutomaticTransactionGenerator section syntax example -Section type definition: +##### Type definition: ```ts type AutomaticTransactionGeneratorConfiguration = { @@ -230,7 +233,7 @@ type AutomaticTransactionGeneratorConfiguration = { }; ``` -Section example: +##### Example: ```json "AutomaticTransactionGenerator": { @@ -247,7 +250,7 @@ Section example: } ``` -#### Connectors section +#### Connectors section syntax example ```json "Connectors": { @@ -266,7 +269,8 @@ Section example: ... { "unit": "A", - "measurand": "Current.Import" + "measurand": "Current.Import", + "minimum": "0.5" }, ... { @@ -278,6 +282,46 @@ Section example: }, ``` +#### Evses section syntax example + +```json + "Evses": { + "0": { + "Connectors": { + "0": {} + } + }, + "1": { + "Connectors": { + "1": { + "bootStatus": "Available", + "MeterValues": [ + ... + { + "unit": "W", + "measurand": "Power.Active.Import", + "phase": "L1-N", + "value": "5000", + "fluctuationPercent": "10" + }, + ... + { + "unit": "A", + "measurand": "Current.Import", + "minimum": "0.5" + }, + ... + { + "unit": "Wh" + }, + ... + ] + } + } + } + }, +``` + ### Charging station configuration **dist/assets/configurations/\.json**: @@ -676,4 +720,4 @@ We as members, contributors, and leaders pledge to make participation in our com ## Licensing -Copyright 2020-2022 SAP SE or an SAP affiliate company and e-mobility-charging-stations-simulator contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/e-mobility-charging-stations-simulator). +Copyright 2020-2023 SAP SE or an SAP affiliate company and e-mobility-charging-stations-simulator contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/SAP/e-mobility-charging-stations-simulator).