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
guide-stepper:
- fix deadlock when editing winding width
- fix behaivor when windingWidth is set to 0 (disable guide)
control:
- add dead time to prevent setTarget when exiting setWindingWidth with buttons
- fix typo and conditons
- increase max winding width
- optimize display text
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
- outsource global variables and objects
- move from config.hpp to global.cpp / hpp
- rename config.hpp, thus change all includes
- re-arrange includes -> in source files instead of header
- optimize / make function comment titles more consistent
- optimize comments overall
- add several temporary files to gitignore
- fix unused variable compiler warnings
Adjust some parameters while testing cable guide with new Reel V2.2.2
Guides quite well with current setup, calculated diameter (layer heights)
matches quite good now
- 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
- prevent hard stops (no decel ramp) when target changes while
decelerating already (overshoot and move back)
- optimize/adjust stepper-test mode, add macro for test with single switch
Note: tested the current state, works quite well. very rarely crashes
probably dude to race conditions in isr?
- Add waitForStop function to custom stepper driver
- use that function in guide-stepper to ensure stepper actually was at
max/min position before dir change
- move stepper config e.g. speed accel steps... from stepper.cpp to
config.h
- uncomment and rework code in guide-stepper.cpp (for traveling the
stepper based on encoder) to work with new custom driver instead of
previous library
Note currently in STEPPER_SIMULATE_ECNODER mode (use button as encoder),
see macro
- add functions
setSpeed (mm/s)
setTargetPosMm
- add macros and function to define and convert variables to actual units
speed in mm/s instead of unknown
abs pos in mm instead of steps
- simplyfy isr code
new driver works well while testing with one button with debug output
- small changes to isr function that made it fully functional!
- add stepper debug task
- minor optimizations necessary
Partially implemented stepper driver as planned in diagram
works partially (reset button toggles distances)
major issues though - wip
needs debugging and testing
basic task for controlling the stepper
(no accel / decel etc)
works at current speed settings but long moves trigger watchdog
so dropped this idea and using timer as before
Some adjustments to make it work
- fix direction change (temporary)
- fix isr initial start
See notes in stepper.cpp
Todo:
- fix crash after accelerating
- add initial speed (takes long to accelerate from 0
-
- Add stepper driver code from scratch
- Remove / comment out code that used DendoStepper library
- Test custom driver with buttons (guide-stepper.cpp)
untested limited features
- decrease home speed
- invert direction in stepper test and home function due to changed
wiring
- stretch travel steps calculation to multiple steps and variables for
better overview and debugging
- prevent partial steps from being lost -> fixes rounding issue
TESTED: works in general, but steper movement is too jerky. Also there
is a Hardware issue: When VFD/motor is on the steper does not work
properly -> 50ohm pullup near stepper driver fixed this
- optimize some variable and macro names
- change/add function that travels guide certain steps
- stepper task: - calculate steps depending on encoder steps
- move steps if at least 1 step possible
- prepare poti modifier
-> untested
- 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
While testing the setup
Optimizations of problems noticed while testing the setup:
- mount too weak
- only very slow speeds relevant
- less distance required
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
