search

InsanityAutomation / Marlin

Optimized firmware for RepRap 3D printers based on the Arduino platform.
http://www.marlinfw.org/
GNU General Public License v3.0
451 stars 220 forks source link

CR-X (CRX_BLT_UBL_Fil_DW7) problem with serial connection and OctoPrint #154

Open LMS0815 opened 3 years ago

LMS0815 commented 3 years ago

Description

After updating my Creality CR-X from CRX_BLT_UBL_Fil_DW6.2 to CRX_BLT_UBL_Fil_DW7 OctoPrint is having issues connecting to the printer. Printing is impossible.

Steps to Reproduce

  1. Use CRX_BLT_UBL_Fil_DW7.hex
  2. Try printing with octoprint (PI B+ and Windows Installation same issues)

Additional Information

reverting to CRX_BLT_UBL_Fil_DW6.2 solves the problem.

alex-murphy commented 3 years ago

I upgraded my printer to 10SPro_BIL_DW7 from an old 6.x version today and I found Octoprint didn't connect using the previous working baud rate of 115200. Using 250000 did the trick for me. It's doing it's first print right now and seems OK so far.

LMS0815 commented 3 years ago

Thank you. I tried 250000 as well (Which was my default anyway) but no success.

LMS0815 commented 3 years ago

Just to be more precise. I can connect to the printer but I get a timeout if I am printing:

Send: N2 M420 S*84
Recv: echo:No SD card
Recv: //action:notification SD Init Fail
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N3 M105*36
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N4 M105*35
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N5 M105*34
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N6 M105*33
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N7 M105*32
No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Starting" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Connection closed, closing down monitor

Send: N2 M105*37
Recv: ok T:26.34 /0.00 B:27.81 /0.00 @:0 B@:0
Send: N3 M73 P0*84
Recv: ok N3 P7 B3
Send: N4 M73 P0*83
Recv: ok N4 P7 B3
Send: N0 M110 N0*125
Recv: ok N0 P7 B3
Send: N1 M117 Pre print bed/nozzle heating & UBL probe ...*22
Recv: //action:notification Pre print bed/nozzle heating & UBL probe ...
Recv: ok N1 P7 B3
Send: N2 M420 S*84
Recv: echo:No SD card
Recv: //action:notification SD Init Fail
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N3 G28 X Y*17
No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Starting" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Connection closed, closing down monitor

I get the error despite having an SD inserted or not, prior to communication issues. Recv: //action:notification SD Init Fail

alex-murphy commented 3 years ago

Since my last post - I'm now experiencing the same issue with no change to Octoprint or my CR10s. My logs look pretty much the same as yours LMS0815. I'll revert back to 6.2 later today I think.

LMS0815 commented 3 years ago

Seems printing from SD is as well not working with Version 7.0 on CR-X

alex-murphy commented 3 years ago

I'm having the same issues with 6.2 firmware as well. I can print files locally from octoprint but not from the SD-card. When printing from SD the printer starts the heating function then locks up which was the same issue as I experience in v7, then octoprint would timeout. Anyhoo, at least I can print :)

Additionally, when I try to print without Octoprint (ie: standalone directly from the SD card on the printer) and without the USB cable connected, I experience the same issue where the printer starts to heat then locks up.

I found this: https://www.thingiverse.com/groups/creality-cr10s-pro/forums/general/topic:42838 - I'll try to shorten my filenames can report back.

InsanityAutomation commented 3 years ago

Can you confirm if the rewritten file browser resolves the naming issues described as well as any changes to serial stability on 7.3? I have not been able to reproduce this kind of communication dropout here.

stooged commented 1 year ago

I upgraded my printer to 10SPro_BIL_DW7 from an old 6.x version today and I found Octoprint didn't connect using the previous working baud rate of 115200. Using 250000 did the trick for me. It's doing it's first print right now and seems OK so far.

you resolved the same issue i was having with the current firmware, the baud rate was the trick, thankyou.