› ›

Smoothieboard and repetier

MariusMarius
in Questions & Answers

17:57:22.599 : "C:\Program Files\Repetier-Host\plugins\RepetierServerConnector\RepetierServerStarter.exe" start
18:05:04.713 : Repetier-Server successfully connected.
18:05:04.719 : M20
18:05:04.723 : M20
18:05:04.738 : Begin file list
18:05:04.738 : firmware.cur
18:05:04.738 : backup-firmware/
18:05:04.739 : M115
18:05:04.741 : M20
18:05:04.841 : documentation/
18:05:04.841 : drivers/
18:05:04.841 : source/
18:05:04.841 : software/
18:05:04.841 : models/
18:05:04.841 : readme.txt
18:05:04.841 : system volume information/
18:05:04.841 : config
18:05:04.842 : End file list
18:05:04.842 : Begin file list
18:05:04.942 : firmware.cur
18:05:04.942 : backup-firmware/
18:05:04.942 : documentation/
18:05:04.942 : drivers/
18:05:04.942 : source/
18:05:04.942 : software/
18:05:04.942 : models/
18:05:04.942 : readme.txt
18:05:04.942 : system volume information/
18:05:04.942 : config
18:05:04.942 : End file list
18:05:04.942 : Begin file list
18:05:04.942 : firmware.cur
18:05:04.942 : backup-firmware/
18:05:04.992 : documentation/
18:05:04.993 : drivers/
18:05:04.993 : source/
18:05:04.993 : software/
18:05:04.993 : models/
18:05:04.993 : readme.txt
18:05:04.993 : system volume information/
18:05:04.993 : config
18:05:04.993 : End file list
18:05:53.374 : Slic3r command:C:\Program Files\Repetier-Host\Slic3r\slic3r.exe --load "slic3r_settings.ini" --print-center 92.50,93.50 -o "composition.gcode" "composition.amf"
18:05:54.372 : <Slic3r> => Processing triangulated mesh
18:05:54.840 : <Slic3r> => Generating perimeters
18:06:03.305 : <Slic3r> => Preparing infill
18:06:04.938 : <Slic3r> => Infilling layers
18:06:06.249 : <Slic3r> => Generating skirt
18:06:06.253 : <Slic3r> => Generating brim
18:06:06.261 : <Slic3r> => Exporting G-code to composition.gcode
18:06:34.140 : <Slic3r> Done. Process took 0 minutes and 39.768 seconds
18:06:34.140 : <Slic3r> Filament required: 58732.6mm (141.3cm3)
18:08:10.413 : Slic3r command:C:\Program Files\Repetier-Host\Slic3r\slic3r.exe --load "slic3r_settings.ini" --print-center 92.50,93.50 -o "composition.gcode" "composition.amf"
18:08:11.579 : <Slic3r> => Processing triangulated mesh
18:08:12.035 : <Slic3r> => Generating perimeters
18:08:19.466 : <Slic3r> => Preparing infill
18:08:21.029 : <Slic3r> => Infilling layers
18:08:22.925 : <Slic3r> => Generating skirt
18:08:22.929 : <Slic3r> => Generating brim
18:08:22.937 : <Slic3r> => Exporting G-code to composition.gcode
18:08:51.037 : <Slic3r> Done. Process took 0 minutes and 39.458 seconds
18:08:51.037 : <Slic3r> Filament required: 58732.6mm (141.3cm3)
18:12:34.110 : B:42.0 /65.0 @255
18:15:57.117 : B:64.9 /65.0 @255
18:17:21.983 : Warning: Communication timeout - resetting communication buffer.
18:17:21.983 : Connection status: Buffered:28, Manual Commands: 2, Job Commands: 5000
18:17:21.983 : Buffer used:28 Enforced free byte:37 lines stored:1
18:17:21.983 : Printing layer 1 of 599
18:54:34.476 : Printing layer 2 of 599
19:11:12.271 : Printing layer 3 of 599
19:27:27.716 : Printing layer 4 of 599
19:30:11.579 : Printing layer 5 of 599
19:40:13.935 : Printing layer 6 of 599
19:50:26.037 : Printing layer 7 of 599
20:03:28.664 : Printing layer 8 of 599
20:06:08.455 : Printing layer 9 of 599
20:08:49.830 : Printing layer 10 of 599
20:11:17.405 : Printing layer 11 of 599
20:13:58.189 : Printing layer 12 of 599
20:16:40.957 : Printing layer 13 of 599
20:19:37.744 : Printing layer 14 of 599
20:23:14.718 : Printing layer 15 of 599
20:26:45.528 : Printing layer 16 of 599
20:30:12.795 : Printing layer 17 of 599
20:33:42.047 : Printing layer 18 of 599
20:37:08.422 : Printing layer 19 of 599
20:40:32.403 : Printing layer 20 of 599
20:44:01.610 : Printing layer 21 of 599
20:47:26.190 : Printing layer 22 of 599
20:50:46.696 : Printing layer 23 of 599
20:53:39.511 : Printing layer 24 of 599
20:56:03.884 : Printing layer 25 of 599
20:58:24.983 : Printing layer 26 of 599
21:00:45.174 : Printing layer 27 of 599
21:03:05.576 : Printing layer 28 of 599
21:05:23.731 : Printing layer 29 of 599
21:07:39.410 : Printing layer 30 of 599
21:10:03.786 : Printing layer 31 of 599
21:12:22.798 : Printing layer 32 of 599
21:14:41.891 : Printing layer 33 of 599
21:17:05.775 : Printing layer 34 of 599
21:19:20.651 : Printing layer 35 of 599
21:21:41.498 : Printing layer 36 of 599
21:23:55.331 : Printing layer 37 of 599
21:26:10.809 : Printing layer 38 of 599
21:28:31.158 : Printing layer 39 of 599
21:30:47.977 : Printing layer 40 of 599
21:33:00.566 : Printing layer 41 of 599
21:35:15.348 : Printing layer 42 of 599
21:37:32.168 : Printing layer 43 of 599
21:39:48.290 : Printing layer 44 of 599
21:41:58.646 : Printing layer 45 of 599
21:44:13.117 : Printing layer 46 of 599
21:46:23.728 : Printing layer 47 of 599
21:48:35.477 : Printing layer 48 of 599
21:50:45.045 : Printing layer 49 of 599
21:52:58.420 : Printing layer 50 of 599
21:55:05.940 : Printing layer 51 of 599
21:57:18.488 : Printing layer 52 of 599
21:59:31.721 : Printing layer 53 of 599
22:01:39.488 : Printing layer 54 of 599
22:03:51.243 : Printing layer 55 of 599
22:05:55.733 : Printing layer 56 of 599
22:08:07.177 : Printing layer 57 of 599
22:10:16.736 : Printing layer 58 of 599
22:12:25.896 : Printing layer 59 of 599
22:14:36.655 : Printing layer 60 of 599
22:16:45.566 : Printing layer 61 of 599
22:18:51.196 : Printing layer 62 of 599
22:21:00.063 : Printing layer 63 of 599
22:23:09.826 : Printing layer 64 of 599
22:25:12.819 : Printing layer 65 of 599
22:27:21.577 : Printing layer 66 of 599
22:29:25.822 : Printing layer 67 of 599
22:31:30.854 : Printing layer 68 of 599
22:33:37.498 : Printing layer 69 of 599
22:35:44.427 : Printing layer 70 of 599
22:37:46.929 : Printing layer 71 of 599
22:39:53.100 : Printing layer 72 of 599
22:41:55.252 : Printing layer 73 of 599
22:43:58.705 : Printing layer 74 of 599
22:46:07.260 : Printing layer 75 of 599
22:48:07.876 : Printing layer 76 of 599
22:50:09.387 : Printing layer 77 of 599
22:52:17.252 : Printing layer 78 of 599
22:54:33.671 : Warning: Communication timeout - resetting communication buffer.
22:54:33.671 : Connection status: Buffered:39, Manual Commands: 2, Job Commands: 5000
22:54:33.671 : Buffer used:39 Enforced free byte:39 lines stored:1
22:55:04.697 : Warning: Communication timeout - resetting communication buffer.
22:55:04.697 : Connection status: Buffered:48, Manual Commands: 2, Job Commands: 5000
22:55:04.697 : Buffer used:48 Enforced free byte:39 lines stored:3

Comments

  • MariusMarius
    Hi,

    I've changed from simply3d the latest version, because of prints hanging in the middle of the process (latest firmware and latest version on simplify3d).

    Now I'm on repetier with slic3r both on the latest versions and on a 10 hours print after 40 % Smoothieboard decide to hang because of comunications issues.

    Its getting a little bit annoying and I would like some sugestions.

    I'm attaching the report and the gcode.

    Thank you  
  • RepetierRepetier
    I assume you are printer over the server? In the server gui you can enable logging of prints. Your print form host ui does not contain the vital informations to analyse the problem. You need the full communication around the time where it happens.

    Since it says timeout it means the smoothieboard did not return a "ok" or it got corrupted through communication. In that case print would continue after a timeout, which assumes exactly this so it can continue which does not seem to happen hier except maybe at 18:17:21.983.

    The main question is do you have a hardware problem stopping communication or just a communication error that should recover.
  • MariusMarius
    The hardware problem is unlikely to exist. 
    My asumption is that there is a problem with the communication thus the error. the printing does not resume due to the fact that smoothieboard gets stuck. 

    But my question is why does this happen on the repetier and doesn't happen on the pronterface.

    I do like Repetier server more. 
  • RepetierRepetier
    A othe ruser had a similar problem with repetier host. When he activated ping pong mod ein printer setting it started to work. So maybe your buffer size does not match the one of smoothie and strange things happen. Try ping pong mode which is what pronterface uses.
  • neologneolog
    I got the same trouble with ping pong 
  • kr1sisskr1siss
    I know this is late, I had the same problem.  Ping Pong mode didn't fix it.  What did was lowering the buffer size.  I set mine to 24, I suspect it can go as high as 31 or 32, but since 24 works for me, I'm not touching it.  
  • RepetierRepetier
    Buffer size is also the longest command you can send. Not sur eif thi counts with ping pong a sit has only one command anyway.
Sign In or Register to comment.