Closed eriksven closed 1 year ago
Not really something, that needs to be added here, just an idea: a helper script creating these .csv from a "life" system is probably easy to do: Give it a list of VSS paths, and it can depending on metadata, subscribe current value for sensors and current&target value for actuators while writing a CSV file. (Don't forget to flush on Ctrl-C :) ). But just an idea for the future
I updated the branch for the CSV-provider, @erikbosch and @SebastianSchildt could you please have another look.
The idea of having a script to generate the CSV-files from a life system is good. To me this is beyond the scope of this PR but I will have look into it for a further PR.
This PR adds a provider which reads VSS signals from a given CSV-file and replays this data and the changes over time to an instance of the kuksa.val databroker.