Misleading bringup documentation

[bananen-republik]

Hello everybody,

in your bringup video you are showing how to start the simulator. I tried it the same way, with using "./afb-evcc/etc/binding-start-evcc.sh" but it always leads me to: "/home/admin/iso15118-simulator-rs Warning: To active tls support, PKI_TLS_DIR must be define (-p|--pki_tls_sim_dir) Fail: The scenario file must be define (-f|--scenario_file) Usage: -h|--help displays this text -d|--debug run the script in debug mode -i|--iface specify the network interface (default:"evcc-veth" or from env var IFACE_SIMU) -c|--scenario_uid specify the scenario uid (default:"evcc" or from env var SCENARIO_UID) -f|--scenario_file -s|--simulation specify the simulator mode (default:"injector" or from env var SIMULATION_MODE) -m|--simulation_conf specify the simulator conf (default:"/etc/default//binding-simu15118-evcc.yaml" if tls support or :"/etc/default//binding-simu15118-evcc-no-tls.yaml" if no tls support or from env var SIMULATION_CONF) -p|--pki_tls_sim_dir specify *.pem files directory (_client_chain.pem,_client_key.pem,_contract_chain.pem,_contract_key.pem) admin@TUX-EVSE:~/iso15118-simulator-rs$ ./afb-evcc/etc/binding-start-evcc.sh -i enp0s3 -s "

Even if i specify the interface it shows me the help page. What am I doing wrong? What configurations do i need to set?

[fulup-bzh]

Hi, --pki_tls_sim_dir should not be mandatory, exepct if you enforce TLS|PKI in your yaml config. Note that @ronan22 default config yaml require PKI, but he also provide a evcc-no-tls.yaml config.

Conclusion: either:

• edit or change simulator yaml.config with: evcc/etc/binding-start-evcc.sh -m .../binding-simu15118-evcc-no-tls.yaml to remove TLS|PKI definition (just comment all concerned lines)

• create development certificate with ./afb-test/certs/mkcerts.sh

  Note: from your your post, I understand that you started from source code. For quick start I recommend to start fro @ronan22 ready to use binary. @ronan22 could you please add in the readme the adequate comment for:

  • run without PKI
  • create development certificate at the right location.

[ronan22]

The script binding-start-evcc has been improve and some information has been add to the README file. You can update your package or use it from the source

@bananen-republik can you confirm you have a good configuration now?

[fulup-bzh]

Documentation was updated by Ronan. As we did not get any feedback, we expect the issue to be solved. Would you have more concern, feel free to open a new request.