1

Hi, I have a problem with my delta. every couple of prints it just stops at a random height, none of the error messages showing, it doesn’t start the cooldown and thinks it’s printing but nothing is moving. Last time I left printer over night it stood still for 17h.

dsc_0116.jpg
dsc_0116.jpg3840×2160 2.5 MB

2

I know those feet!

How are you printing? SD card, USB?

3

I have had a problem like this but I don’t know if it is the same. In my case it was caused by the USB cable getting loose, causing a communication error. normally this is automatically fixed by the controller because the printer does not acknowledge the data but this time it did not. Somehow the printer received an unknown command and crashed partially but did not show any warning, the screen showed it was still printing but i was not. The temperature overshoot with more than 20°C and did not show any warning. I tried using the emergency stop and disconnecting the printer but nothing worked, even not the reset button on the printer. The strange thing is that the elapsed time did increase and temperatures were still shown correct. I disconnected power and reset the printer and now it is printing fine. To prevent this problem I upload all files to SD and print from SD.

I just remember I once had this problem with an other printer. It stopped randomly after some hours. That printer did not have a buffer for the data from USB and did not receive enough data to keep going and just stopped printing. Also here: print from SD

4

I’m printing from SD card. For me, it’s at correct temperatures and showing elapsed time like it was printing but motors are not moving. For the owl (file that came with the printer) it stopped at the same height. Could it be that slicer made a mistake in code ?

5

Hi Zrale,
if it stopped at the same point maybe it’s a gcode problem … please make a new gcode.

6

We are having a similar problem. We are printing a prosthetic socket file on a DeltaWASP 20x40. We create the .stl file in a program called Omega, then create the g-code in Slic3r. We set all the print settings in Slic3r, then export the g-code onto the SD card that came with our DeltaWASP printer. We insert the SD card into the printer and print the stl file.

The print proceeds normally until at some point the extruder just stops moving. The extruder is not clogged. The display on the printer screen still says, “printing”. All the temperatures look normal. This has happened at 27%, 30%, 45%, and 60%.

We have successfully printed the same g-code from the same SD card on a different printer (makerbot Z18). We have successfully printed the files from the manufacturer (Aria the dragon) off the same SD card on our printer.

We have tried resetting the printer to manufacturer’s settings. We have tried restarting the printer and re-leveling the bed. The printer continued to stop inexplicably (at different points) even after we did these things.

Any suggestions would be much appreciated.

7

Exactly the same problem. I send mail to WASP waiting for the answer.

8

@constantino_1. If it were a problem with the gcode, would the file be able to print ok on a different printer? We printed our same gcode file on a Makerbot z18 and the print completed successfully.

9

if it so … is not gcode … but i don’t know what

10

Hi! I have the same issue here…

I am printing with a Delta Wasp, by sd card. Just start to print and most times it suddenly stops… always at different percentages… seems to be no correlation…

Tried to stop it and save, but nothing happens… the printer just says “saving”… Tried to resurrect it, it moves, it goes to the point, and then stops there…

Don’t know if this could be related but, after it stops, if I navigate through the display menu and try to get into the sd card, it doesn’t see what’s inside!

Has ANYONE solved this issue?!

11

We finally fixed it by:

a. Using a different SD card (ordered brand new one)

b. Plugging into the wall outlet directly (we were plugged into a lab bench outlet)

Not sure which of these actually fixed it (I suspect the SD card). We will be testing each solution individually over the next couple weeks to figure that out definitively.

Hope this helps.