When winding short lengths e.g. 5m it does not make sense
to use the entire winding width thus getting unnecessary
wide cable ring.
Determined some thresholds while testing and implemented
those to be applied at target length change automatically:
control:
- update winding width each time target length changes
guide-stepper:
- add function that returns dynamic winding width depending
on passed target length according to fixed thresholds
control:
- Add Button combination SET+PRESET1 to set winding width with potentiometer
- Add case and display output in that state
config: move config macros from guide_stepper to common config
guide-stepper:
- outsource config definitions
- add functions to get and set variable winding width
- add mutex
shutdown.cpp/hpp:
- repeatedly check supply voltage
- save value to nvs when dropping below threshold
- provide function to read lastPos from nvs
guide-stepper:
- auto-home considers stored last position in nvs
main:
- add new task shutDownDetection
config:
- slightly increase stepper speed
- guide-stepper:
- add queue to send commands to stepper-ctl task
- add function that tells stepper task to move to zero
- increase travel length full axis length 110
- control: move guide to zero at reset
- Cmake: enable colored output
- Add datasheets of VFD and stepper driver
- Change pins in config for stepper driver
- DISABLED LAMP (pin now used for stepper)
- update connection plan with stepper section and wiring
including the files in source file instead of header file fixed
'conflicting type' errors in idf macros when using newer version
ESP-IDF v4.4.4-148-g4c2afac355
- add macro variable STEPPER_TEST (config.hpp)
if set: only `task_stepper-test` is started (main.cpp)
- add file for stepper/guide related code (guide-stepper.cpp/hpp)
currently defines a task that simply moves the axis left to right
repeatedly with a speed defined by a potentiometer connected to ADC
GPIO34
