Printer stopped when Filament Lenght is 19999,7mm
in Bug Reports
Hello,
could Repetier have a problem with the filament length used? My printer always stopped when the filament length is 19999.7 mm. It doesn't matter which STL file I print.
![Image: https://forum.repetier.com/uploads/editor/0v/as5p1zwqj7x2.jpg](https://forum.repetier.com/uploads/editor/0v/as5p1zwqj7x2.jpg)
Syslog:
could Repetier have a problem with the filament length used? My printer always stopped when the filament length is 19999.7 mm. It doesn't matter which STL file I print.
![Image: https://forum.repetier.com/uploads/editor/0v/as5p1zwqj7x2.jpg](https://forum.repetier.com/uploads/editor/0v/as5p1zwqj7x2.jpg)
Syslog:
Feb 4 18:13:19 RepetierServer systemd-timedated[16362]: /etc/localtime should be a symbolic link to a time zone data file in /usr/share/zoneinfo/.
Feb 4 18:13:19 RepetierServer systemd[1]: Started Time & Date Service.
Feb 4 18:14:20 RepetierServer dbus[429]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service'
Feb 4 18:14:20 RepetierServer systemd[1]: Starting Time & Date Service...
Feb 4 18:14:20 RepetierServer dbus[429]: [system] Successfully activated service 'org.freedesktop.timedate1'
Feb 4 18:14:20 RepetierServer systemd-timedated[16396]: /etc/localtime should be a symbolic link to a time zone data file in /usr/share/zoneinfo/.
Feb 4 18:14:20 RepetierServer systemd[1]: Started Time & Date Service.
Feb 4 18:15:21 RepetierServer dbus[429]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service'
Feb 4 18:15:21 RepetierServer systemd[1]: Starting Time & Date Service...
Feb 4 18:15:21 RepetierServer dbus[429]: [system] Successfully activated service 'org.freedesktop.timedate1'
Feb 4 18:15:21 RepetierServer systemd-timedated[16431]: /etc/localtime should be a symbolic link to a time zone data file in /usr/share/zoneinfo/.
Feb 4 18:15:21 RepetierServer systemd[1]: Started Time & Date Service.
Feb 4 18:15:24 RepetierServer kernel: [24719.437271] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Feb 4 18:15:24 RepetierServer kernel: [24719.437381] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
Feb 4 18:15:24 RepetierServer kernel: [24719.515642] usb 1-1.2-port1: disabled by hub (EMI?), re-enabling...
Feb 4 18:15:24 RepetierServer kernel: [24719.515665] usb 1-1.2.1: USB disconnect, device number 5
Feb 4 18:15:24 RepetierServer kernel: [24719.516033] usb 1-1.2.1: failed to send control message: -19
Feb 4 18:15:24 RepetierServer kernel: [24719.516366] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
Feb 4 18:15:24 RepetierServer kernel: [24719.516413] ch341 1-1.2.1:1.0: device disconnected
Feb 4 18:15:24 RepetierServer kernel: [24719.815056] usb 1-1.2.1: new full-speed USB device number 6 using dwc_otg
Feb 4 18:15:24 RepetierServer kernel: [24719.948151] usb 1-1.2.1: New USB device found, idVendor=1a86, idProduct=7523
Feb 4 18:15:24 RepetierServer kernel: [24719.948165] usb 1-1.2.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Feb 4 18:15:24 RepetierServer kernel: [24719.948173] usb 1-1.2.1: Product: USB2.0-Serial
Feb 4 18:15:24 RepetierServer kernel: [24719.949262] ch341 1-1.2.1:1.0: ch341-uart converter detected
Feb 4 18:15:24 RepetierServer kernel: [24719.951099] usb 1-1.2.1: ch341-uart converter now attached to ttyUSB0
Feb 4 18:16:22 RepetierServer dbus[429]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service'
Feb 4 18:16:22 RepetierServer systemd[1]: Starting Time & Date Service...
Feb 4 18:16:23 RepetierServer dbus[429]: [system] Successfully activated service 'org.freedesktop.timedate1'
Feb 4 18:16:23 RepetierServer systemd-timedated[16471]: /etc/localtime should be a symbolic link to a time zone data file in /usr/share/zoneinfo/.
Feb 4 18:16:23 RepetierServer systemd[1]: Started Time & Date Service.
Feb 4 18:17:01 RepetierServer CRON[16485]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 4 18:17:24 RepetierServer dbus[429]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service'
Feb 4 18:17:24 RepetierServer systemd[1]: Starting Time & Date Service...
Feb 4 18:17:24 RepetierServer dbus[429]: [system] Successfully activated service 'org.freedesktop.timedate1'
Feb 4 18:17:24 RepetierServer systemd-timedated[16516]: /etc/localtime should be a symbolic link to a time zone data file in /usr/share/zoneinfo/.
Feb 4 18:17:24 RepetierServer systemd[1]: Started Time & Date Service.
Feb 4 18:17:30 RepetierServer dhcpcd[646]: eth0: Router Advertisement from fe80::3a10:d5ff:fe2a:813e
Feb 4 18:17:34 RepetierServer systemd[1]: Starting Session c2 of user pi.
Feb 4 18:17:34 RepetierServer systemd[1]: Started Session c2 of user pi.
Feb 4 18:17:35 RepetierServer systemd[1]: Starting Session c3 of user pi.
Feb 4 18:17:35 RepetierServer systemd[1]: Started Session c3 of user pi.
Comments
You should activate logging the print and see what the communication says.
Syslog also reveals an interesting line
Feb 4 18:15:24 RepetierServer kernel: [24719.515642] usb 1-1.2-port1: disabled by hub (EMI?), re-enabling...
reason is that linux disconnected USB which caused the print to abort assuming that is also the abort time which is not visible in your screenshot.
Does it always happen at same filament length regardless of the gcode or with same gcode at same position. In the latter case I would check what gcode gets executed there to see how that might cause the EMI ( I think it stands for electromagnetic interferrence). Commands affecting bed or heater are always a suspect here. You can test also in dry run mode if firmware supports it, then heaters would not interfere since it is not extruding and heating.