[FEATURE]Data capture input

[black-top]

To use spare input for simple momentary switch to capture flow data. Use a simple algorithm to automatically sequence between set lift points, starting from first and after each capture jump to next. Maybe just use the simple sequence variable and just ++? Also, It will be good to have an indication on the main screen that data capture was successful and what lift point is currently active for data capture. Another option is that if the data capture works with the data graph screen open, no additional indication will be needed. In the future, we can just use data from an electronic micrometer for lift data. We have talked about it some time ago, but the project has evolved a lot since then, so probably it will not be so difficult to implement at this stage.

[DeeEmm]

Automation is one of the goals of the project, ultimately integrating the automated valve positioner along with the automated bleed valve to provide a 'hands-free' way to map flow versus lift. Just press 'go' and the system does the rest.

I will have a ponder on your suggestion as it is probably possible to implement full automation in several stages. A simple sequence as you suggest, and then later expand on this to include lift data or automated valve control.

At the moment I'm taking a bit of time out to finish some building work, but will return to the project soon.

I suspect that things will pick up shortly when the new PCB builds start to kick off.

[black-top]

No rush, I'm using the current setup quite often now, so just suggesting some improvements.

Maybe the current capture function can be modified to be triggered by an external switch at the spare input and a sequence function added to it.

Also related to this topic, after recording data at the last lift point, automatic file saving will be nice to have.

Another small thing, that graph and data files named "liftdata" "LiftGraph" can add the data and time to the file name? For example, "liftdata2025-04-21-08:36"

[DeeEmm]

All good. We still need to prioritise what features are to be worked on next.

There was a previous discussion about getting the current time and date from the network as the ESP32 does not have a realtime clock. The only issue with this method, is that it requires an internet connection. So, whilst definitely a possibility, would need to be implemented so that the user can enable or disable as required.

Automated file saving is relatively trivial, but again ideally needs to be enabled / disabled by the end user.