search

bigtreetech / BIGTREETECH-SKR-mini-E3

BIGTREETECH SKR-mini-E3 motherboard is a ultra-quiet, low-power, high-quality 3D printing machine control board. It is launched by the 3D printing team of Shenzhen BIGTREE technology co., LTD. This board is specially tailored for Ender 3 printer, perfectly replacing the original Ender3 printer motherboard.
2.02k stars 1.98k forks source link

Can't send file by esp3d. M28 command not working. SKR MINI E3 V.2.0 + TFT35 E3 V3.0 #382

Open Lotek213 opened 4 years ago

Lotek213 commented 4 years ago

Description

Can't send file by esp3d. M28 command not working. SKR MINI E3 V.2.0 + TFT35 E3 V3.0 Error:No Checksum with line number, Last Line: x (where x is a int value)

Steps to reproduce

  1. Upload file by ESP3D web interface (Upload to SD)
  2. Error:No Checksum with line number, Last Line: 1
  3. Printer stops working.
  4. I have to reset printer (off/on)

Expected behavior I expected that file should be send.

Actual behavior M28 command not working at all: Error:No Checksum with line number, Last Line: x (where x is a int value) M28 command create empty file.

Additional Information

All devices firmware are up to date. It is definitly problem with SKR MINI E2 V2.0 firmware, because ESP3D use M28 command to send (write) file,but it not workin on board firmware as deccribed. I also tried to print file 'test.gcode' (directly from SD on board using LCD mode): "M28 test.gc G28 M28" Behavior is the same. I also tried to connect printer by USB cable but it aslo not working. Virtual COM port are visible in OS but I can't connect printer using it. I guess that it is FW issue, but who know it could be also HW issue.

Best regards Michal

Lotek213 commented 4 years ago

I tried once again to connect printer by USB cable and it works (probably, I used broken cable). Then I tried to use M28 command with success - commands sequence: M28 test.g G28 M29 It created file 'test.g' with G28 command inside. So, I'm confused and I'don't know where is the issue, maybe in TFT35 E3 v3.0 firmware ? Any ideas what I should to test for investigate cause ?