Printer stops before object is done.. and...

[dilmos]

I have on 3 different models (but not everything) had the printer head to stop moving before the object is complete... The head just stops in place and the temp stays the same, but it stops extruding filament.. and I have found an unfinished print with a blob right where it stopped. I have moved the SD card to another machine, and it will stop at the exact same place. This does not happen with every model I have sliced with S3D and it is at random times.. the last such instance was at 99%. CTC printers all 4 of them.. but the issue is on the sd card with the x3g file.. thank you.

[JoeJ]

Post the gcode and x3g files. That way someone else can try to print them and see if they have the same issue. I'm not sure i've ever heard of SD card prints stopping like that, but I suppose there could be a firmware bug that would cause it to stall.

[akruse12]

I have had the same problem. Here are the files. I hope someone can figure this out.

[JoeJ]

Hmm.. I don't see anything but G1 commands for the last 10% of the file until you get to the final ending script (cooldown and dropping bed). What exact line is it stopping on? If you send it through S3D's machine control panel, you can click on the Communication tab to see the last 50 or so commands that were sent right before the print stops. That would be helpful to know where exactly it is pausing.

[NanoBotAstronaut]

I've had a similar problem.
I'm using a CTC Makerbot Replicator Dual Clone with Sailfish 7.7.
Connected via USB with a Baud rate of 115200.

I'm new to S3D and it's been tricky getting it to interface with my printer.
Temperatures and other parameters seem to be correctly set by S3D.
The first few layers will go down fine, then the machine stops mid-layer. The extruder stops extruding and the XY motors lock up.
Sometimes the motors will jitter as though they are trying to come back online.

It seems like S3D is having trouble keeping a consistent connection to the machine.

Any suggestions would be immensely appreciated!

//======================
// The following is:
// Communication output while printing a MarvinMartian test keychain leading up to print failure.

READ: d5
READ: 0181d2
SENT: d5209b4a06000044000000500000000000000000000000ed06000018a9ba383d000583
READ: d5018230
SENT: d5209b4a06000044000000500000000000000000000000ed06000018a9ba383d000583
READ: d50181d2
SENT: d5030a0002d6
READ: d50381d300c4
SENT: d5030a010212
READ: d503812100cc
SENT: d5030a001ee8
READ: d503814d00db
SENT: d5209b3b060000d200000050000000f7ffffff000000004c07000018f182c23f000520
READ: d5
READ: 0181d2
SENT: d5209b3a060000d80000005000000000000000000000006107000018620f823d000573
READ: d501
READ: 81d2
SENT: d5209b35060000fa00000050000000feffffff0000000058070000183a2eb93e00052e
READ: d501
READ: 81d2
SENT: d5209b34060000000100005000000000000000000000004f07000018fe57833d00055b
READ: d501
READ: 81d2
SENT: d5209b150600008c01000050000000f7ffffff000000002b070000188e3ec33f000538
READ: d5
READ: 0181d2
SENT: d5209b1306000091010000500000000000000000000000c406000018746f6c3d000590
READ: d501
READ: 81d2
SENT: d5209b0b060000af01000050000000feffffff00000000f906000018da54a63e0005c2
READ: d5
READ: 0181d2
SENT: d5209b0a060000b4010000500000000000000000000000c906000018becb6b3d000598
READ: d5
READ: 0181d2
SENT: d5209bec0500000c02000050000000faffffff00000000f306000018453a7d3f0005b1
READ: d5
READ: 0181d2
SENT: d5209bea050000100200005000000000000000000000005f07000018db952d3d0005de
READ: d50181d2
SENT: d5209be20500002502000050000000ffffffff00000000cf0600001810a8763e000589
READ: d5
READ: 0181d2
SENT: d5209be10500002902000050000000000000000000000040070000180976303d000537
READ: d5
READ: 0181d2
SENT: d5209bc40500006d02000050000000fbffffff00000000b906000018df304a3f0005bd
READ: d50181d2
SENT: d5209bc1050000720200005000000000000000000000007706000018f675773d000501
READ: d50181d2
SENT: d5209bb30500008f02000050000000feffffff00000000b306000018f01aad3e000575
READ: d5
READ: 0181d2
SENT: d5209bb0050000940200005000000000000000000000007706000018f675773d00058b
READ: d5
READ: 0181d2
SENT: d5209b720500000203000050000000f8ffffff000000005f060000180698ac3f000587
READ: d5
READ: 0181d2
SENT: d5209b6e05000009030000500000000000000000000000a806000018773fa83d000502
READ: d50181d2
SENT: d5209b560500002c03000050000000fdffffff000000002506000018734eea3e00050b
READ: d5
READ: 0181d2
SENT: d5209b5105000033030000500000000000000000000000be050000188722a73d0005ee
READ: d5018230
SENT: d5209b5105000033030000500000000000000000000000be050000188722a73d0005ee
READ: d50181d2
SENT: d5209b100500008503000050000000faffffff00000000c205000018fa5f8e3f000544
READ: d501
READ: 81d2
SENT: d5209b0d0500008a03000050000000ffffffff000000001d060000180ad9823d0005cb
READ: d501
READ: 81d2
SENT: d5209bf6040000a303000050000000feffffff000000007505000018762cb73e0005c1
READ: d5
READ: 0181d2
SENT: d5209bf2040000a7030000500000000000000000000000e804000018b95d823d00055c
READ: d501
READ: 81d2
SENT: d5209bbd040000dc03000050000000fcffffff0000000039050000183aec4a3f000575
READ: d5
READ: 0181d2
SENT: d5209bb8040000e103000050000000ffffffff000000000405000018fd669f3d0005ae
READ: d5
READ: 0181d2
SENT: d5209b99040000fc03000050000000feffffff000000008705000018674ee03e000544
READ: d50181d2
SENT: d5209b930400000104000050000000ffffffff00000000fd05000018fa3da03d000546
READ: d50181d2
SENT: d5209b300400004a04000050000000f9ffffff00000000e705000018a8b4a73f000527
READ: d501
READ: 81d2
SENT: d5209b280400005004000050000000ffffffff00000000bf05000018e9aade3d00058d
READ: d50181d2
SENT: d5209bf60300006e04000050000000fdffffff000000005d0600001855161d3f000512
WARNING: Device unplugged while connected to port
Total build time: 4.55 minutes

[andrewk72]

That error doesn't have anything to do with S3D. That means that the serial connection that is managed by the OS was broken. This usually either means the firmware reset itself (which breaks the serial connection), the electronics are going bad (could be either computer USB port or printer electronics), or the cable could also be physically damaged or potentially even unplugged by accident.

But there's nothing the software can do if this happens. So you should look at the other areas I mentioned above.

[savaget]

I was having the exact same problem with my Lulzbot Taz 5.
My solution was to buy a class 10 SD card and the problem was solved.

Problem was that Lulzbot ships with a lower class SD card.

Hope this helps you.

TS