Prioritized tasks related to this project/repository, and to the very specific custom builds/hardware.
See here and here for the documentation on VSCode's GitHub integration.
-
Auto-generate/update README.md to include a Markdown table with names, explanations and links to every single matrix build (see here)
-
Try disabling
SQUARE_WAVE_STEPPING
, as it's disabled in BTT by default (enabled in Marlin/Creality by default) -
Try disabling
SDCARD_CONNECTION
, since this should cause the board itself to figure out the correct SD card connection -
Try lowering
ENCODER_PULSES_PER_STEP
from4
to3
or2
, as the stock Creality DWIN display's rotary encoder seems to not register when changing direction and a single step is produced, requiring an additional step to register (must be a bug, but not sure where/why or if it's actually a hardware fault or not) -
Try enabling
ADAPTIVE_STEP_SMOOTHING
to see if it works fine with it enabled (most BTT boards recommend or require it to be disabled) -> Must be enabled, otherwise probes like the BL-Touch will fail at random -
Try enabling
ENDSTOP_INTERRUPTS_FEATURE
to see if it works fine with it enabled (most BTT boards recommend or require it to be disabled) -> Currently have this enabled, but yet to see if it's causing issues or not -
Try enabling
SPEAKER
with the BTT display, as it should then be able to display tones at different frequencies etc. -
Switch our software to use baud rate of 115200 again, as the higher baud rate is unnecessary (I feel like?)
-
Update Cura to match our new/default speeds, acceleration etc.
-
Calibrate flowrate (may need other calibrations first!)
-
Recalibrate linear advance and configure in firmware (likely needs other calibrations first!) -> We currently use a K value of 0.15
-
Install filament sensor and adjust firmware values for the sensor/filament length
-
Recalibrate retraction and enable/configure firmware retraction (remember to enable in Cura also)
-
Probing position is never at the cented of the bed, X seems okay but Y is way too far in the positive numbers
-
Implement an easy way to run these builds locally in Docker (I guess with
act
we could still do that, but it's still a bit buggy) -
Implement BTT TFT35 (E3 V3.0) display support (with dual mode?), possibly also enabling
BTT_TFT35_SPI_V1_0
? (see here, here and most importantly here)- Enable and configure
CUSTOM_MENU_MAIN
,CUSTOM_MENU_CONFIG
,CUSTOM_USER_BUTTONS
with the BTT display
- Enable and configure
-
Research/implement MPC builds (#4)
-
Research/implement
DIRECT_STEPPING
- Try a different language, especially with the BTT TFT (eg.
LCD_LANGUAGE
set tofi
instead ofen
)
-
Test
TEMP_STAT_LEDS
with a Neopixel RGB LED strip to change colors based on the current temperatures -
Implement PSU control support
-
Implement Neopixel RGB LED support with
NEOPIXEL_LED
(WARNING: See the notes about mosfets and power handling first!) -
Implement automatic patch file generation for the entire repository (#3)
-
Test various "easter eggs" like games in the firmware (with the BTT display running in LCD mode)
-
Try enabling
POWER_MONITOR_CURRENT
andPOWER_MONITOR_VOLTAGE
(#error "POWER_MONITOR_CURRENT requires a valid POWER_MONITOR_CURRENT_PIN."
)