Flood of DiagnosticsStatusNotification status: "Uploading" about everest-core HOT 3 OPEN

Hi, thanks for bringing this up. I assume its not a problem with libocpp but with the user app of libocpp. Are you running a full EVerest? Do you have a custom implementation of the system interface running or do you use this system module?

from everest-core.

@Pietfried Thanks for the fast feedback. I think our problem is, that we don't know what is necessary to have a full EVerest. From my understanding we use the default system module from everest-core. I will try to get a confirmation for this. Sorry, if i opened the issue at the wrong place, but for me from tester perspective that's not easy to decide.

from everest-core.

@lategoodbye not a problem that it is opened up here, because it is OCPP related and indeed not easy to decide. I moved it to everest-core

The System module in everest-core serves as an example an at least needs some adjustments to be used in production. It uses some shell scripts to do the firmware update and log upload operations, but because these operations depend on the log location and update mechanism these scripts are just examples and could be modified to your requirements.

• diagnostics_uploader.sh (propably the bug you reported is inside here or in the System module code)
• firmware_updater.sh
• signed_firmware_downloader.sh
• signed_firmware_installer.sh.

For most production hardware we work with the system.yaml interface is overriden by a module that is custom to the target HW.

from everest-core.