search

Thinkersbluff / DGUS-Reloaded_for_CR6-DWIN-SET_Component

Forks the Desuuuu DWIN T5UID1 touchscreen firmware, and refactors it for use on the CR6 T5L DWIN display . Must be used with the modified Klipper from https://github.com/Thinkersbluff/DGUS-Reloaded_for_CR6-Klipper_Component
GNU General Public License v3.0
22 stars 2 forks source link

Chronic shutdown problem on BTT SKR CR6 #23

Open Thinkersbluff opened 1 year ago

Thinkersbluff commented 1 year ago

Based on a sample of two printers, it appears that this DGUS Reloaded firmware will probably shutdown on the first Home X and the first Home Y, after startup. After that, it seems to run fine, until the next Klipper Restart or Firmware Restart, then the problem may repeat.

This problem does not occur when using any of the Creality boards, so is likely related to the TMC2209 UART mode. The specific issue is an error thrown by Klipper when trying to query the motor phase status. Possibly a race condition aggravated by the screen serial interface?

Klipper itself runs fine on that board, with DGUS Reloaded disabled.

h4x0rm1k3 commented 1 year ago

I've got a 'similar' issue in that when trying to go through the calibration menu it tries to home which causes the printer to throw an error 'homing failed due to printer shutdown' which then needs the printer to restart which can be done with the emergency restart button. The rest seems to work so far, it's just the calibration screen, Klipper seems to print fine otherwise as my printer was already setup with a printer.cfg file, my board is a SKR V1.4 Turbo with TMC 2209 drivers in UART mode.

Thinkersbluff commented 1 year ago

Sorry to hear that. My troubles were consistent on the BTT SKR CR6 board, which has the TMC2209 drivers in UART mode, but stopped completely after installing the Creality 1.1.0.3 ERA board, which has the TMC2209 drivers in standalone mode.

h4x0rm1k3 commented 1 year ago

It's certainly strange because the previous version worked perfectly so i'd have no idea what's changed in that respect. I have noticed one other small graphical issue where when printing and adjusting the Gcode z offset you can't see the + or - symbol and the numbers seem to be off slightly by 1 space so you can't see the + or -. It's not hugely important as you can see if it's + or - in Mainsail etc and i'll keep using this version of DGUS reloaded etc as it seems to be working fine apart from the issue in the configuration page's homing sequence and homing seems to work fine otherwise when using Mainsail, I haven't tested if it'd run ABL from Mainsail yet but don't see why it wouldn't.

Thinkersbluff commented 3 weeks ago

I did fix the z-Offset +/- sign display at a later release. See Issue #27