Bibi2 - Connection errors, failed prints


#1

I have a Bibo2, one of the supported devices. I’m using AstroBox on a Pi3. I’ve been unable to get past a few layers on any print…

I enabled the serial logs, and I see frequent CRC errors, line resends, and then ultimately - an odd event where the printer appears to request a line that hasn’t been sent yet. I have used different USB cables, and swapped USB ports on the Pi3, all with the same result.

I’ve built my .gcode files in Cura 3.2.1, also tried .gcode directly from thingiverse. If i use my gcode on the SD card, it prints fine.

Any ideas?

Error Example:

2018-03-23 21:49:51,621 - SERIAL - DEBUG - Send: N600 G1 F1800 X13.545 Y-7.484 E141.38616*17
2018-03-23 21:49:51,627 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:51,629 - SERIAL - DEBUG - Send: N601 G1 X13.475 Y-7.554*52
2018-03-23 21:49:51,736 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:51,738 - SERIAL - DEBUG - Send: N602 G0 F3600 X13.545 Y-6.918*82
2018-03-23 21:49:51,749 - SERIAL - DEBUG - Recv: ok T:220.6 /220.0 B:59.8 /60.0 T0:220.6 /220.0 T1:36.5 /0.0 @:53 B@:127
2018-03-23 21:49:51,751 - SERIAL - DEBUG - Send: N603 G1 F1800 X33.953 Y13.489 E142.82602*9
2018-03-23 21:49:52,629 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:52,634 - SERIAL - DEBUG - Send: N604 M105*37
2018-03-23 21:49:52,640 - SERIAL - DEBUG - Recv: Error:checksum mismatch, Last Line: 600
2018-03-23 21:49:52,643 - SERIAL - DEBUG - Recv: Resend: 601
2018-03-23 21:49:52,644 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:52,645 - SERIAL - DEBUG - Send: N601 G1 X13.475 Y-7.554*52
2018-03-23 21:49:52,646 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:52,647 - SERIAL - DEBUG - Send: N602 G0 F3600 X13.545 Y-6.918*82
2018-03-23 21:49:52,655 - SERIAL - DEBUG - Recv: Error:Line Number is not Last Line Number+1, Last Line: 600
2018-03-23 21:49:52,657 - SERIAL - DEBUG - Recv: Resend: 601
2018-03-23 21:49:52,659 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:52,660 - SERIAL - DEBUG - Send: N601 G1 X13.475 Y-7.554*52
2018-03-23 21:49:52,671 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:52,672 - SERIAL - DEBUG - Send: N602 G0 F3600 X13.545 Y-6.918*82
2018-03-23 21:49:52,680 - SERIAL - DEBUG - Recv: Error:Line Number is not Last Line Number+1, Last Line: 602
2018-03-23 21:49:52,682 - SERIAL - DEBUG - Recv: Resend: 603
2018-03-23 21:49:52,683 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:52,684 - SERIAL - DEBUG - Send: N603 G1 F1800 X33.953 Y13.489 E142.82602*9
2018-03-23 21:49:53,641 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:53,643 - SERIAL - DEBUG - Send: N604 M105*37
2018-03-23 21:49:53,651 - SERIAL - DEBUG - Recv: Error:Line Number is not Last Line Number+1, Last Line: 602
2018-03-23 21:49:53,654 - SERIAL - DEBUG - Recv: Resend: 603
2018-03-23 21:49:53,657 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:53,660 - SERIAL - DEBUG - Send: N603 G1 F1800 X33.953 Y13.489 E142.82602*9
2018-03-23 21:49:53,664 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:53,665 - SERIAL - DEBUG - Send: N604 M105*37
2018-03-23 21:49:53,674 - SERIAL - DEBUG - Recv: Error:Line Number is not Last Line Number+1, Last Line: 602
2018-03-23 21:49:53,676 - SERIAL - DEBUG - Recv: Resend: 603
2018-03-23 21:49:53,678 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:53,679 - SERIAL - DEBUG - Send: N603 G1 F1800 X33.953 Y13.489 E142.82602*9
2018-03-23 21:49:53,681 - SERIAL - DEBUG - Recv: ok
2018-03-23 21:49:53,682 - SERIAL - DEBUG - Send: N604 M105*37
2018-03-23 21:49:53,691 - SERIAL - DEBUG - Recv: Error:Line Number is not Last Line Number+1, Last Line: 604
2018-03-23 21:49:53,694 - SERIAL - DEBUG - Recv: Resend: 605
2018-03-23 21:49:53,696 - SERIAL - DEBUG - Changing monitoring state from 'Printing' to 'Error: Printer requested line 605 but no sufficient histo...'

#2

Your printer is having a hard time reading from the port. This rapid succession of errors and resend means that the printer isn’t reading what’s sent. Please read this: https://astroprint.zendesk.com/hc/en-us/articles/115001797403-Why-does-my-printer-disconnect-in-the-middle-of-a-print-


#3

Hi Tim_Chalk,

I also use the Bibo 2 and worked with the support team to get it added. My printer works just fine with Astrobox but I don’t use the online slicer instead I use Simplify3d for my slicing needs.Seeing that you can print via SD card just fine, I’m thinking the slicer is not the issue. As Daniel outlined there are a few things that could cause issues printing via astrobox as you are essentially printing via USB - so checking the link is a good first step. One other thing I would recommend trying if you have not done so already is updating your Bibo firmware to 3.0.1 - the old 2.x firmware that comes with the printer is a bit outdated and might cause USB printing issues.


#4

Thanks for the suggestions. I have updated to 3.0.1 firmware, I tried both “A” and “B” firmware versions, to try dropping the baud rate to 115200. I’m still getting the comms errors, unfortunately. Bibo support has suggested unplugging the LCD display to try to reduce interference - haven’t done that one yet, but we’ll see… I do think it’s clear that it’s my printer and not Astro though (or Octo, which also failed with comm errors).


#5

I’ve also heard from other members the wireless module on our Bibo is basically useless and causes interference as well. Pull the module out and see if that makes a difference.