So nun einen Powered USB Hub dran. Wird noch schlimmer.
Mesg:16:42:52.230: Dtr: true Rts: true
Mesg:16:42:52.238: Connection started
Mesg:16:42:52.238: Printer reset requested - emergency:false
Mesg:16:42:52.238: Dtr: false Rts: false
Mesg:16:42:52.260: Dtr: true Rts: true
Recv:16:42:53.382: Connection verified by:start
Recv:16:42:53.382: Printer reset detected:start
Recv:16:42:53.382: start
Recv:16:42:53.382: echo:Marlin 1.0.0
Send:16:42:53.382: N1 M110
Recv:16:42:53.386: echo: Last Updated: Oct 5 2022 20:25:05 | Author: Version DEV
Recv:16:42:53.386: Compiled: Oct 5 2022
Recv:16:42:53.390: echo: Free Memory: 2041 PlannerBufferBytes: 1232
Recv:16:42:53.390: echo:Stored settings retrieved
Recv:16:42:53.390: echo:Steps per unit:
Recv:16:42:53.394: echo: M92 X80.00 Y80.00 Z400.00 E510.00
Recv:16:42:53.394: echo:Maximum feedrates (mm/s):
Recv:16:42:53.398: echo: M203 X300.00 Y300.00 Z40.00 E50.00
Recv:16:42:53.398: echo:Maximum Acceleration (mm/s2):
Recv:16:42:53.398: echo: M201 X9000 Y9000 Z100 E10000
Recv:16:42:53.402: echo:Acceleration: S=acceleration, T=retract acceleration
Recv:16:42:53.403: echo: M204 S3000.00 T3000.00
Recv:16:42:53.411:
echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate
(mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s),
Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
Recv:16:42:53.415: echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
Recv:16:42:53.415: echo:Home offset (mm):
Recv:16:42:53.415: echo: M206 X0.00 Y0.00 Z-11.75
Recv:16:42:53.415: echo:PID settings:
Recv:16:42:53.418: echo: M301 P12.07 I1.11 D32.93
Recv:16:42:53.713: echo:SD card ok
Recv:16:42:53.742: ok
Send:16:42:53.750: N4 M115 ; Get firmware capabilities and info
Recv:16:42:53.759:
FIRMWARE_NAME:Marlin Ultimaker2; Sprinter/grbl mashup for gen6
FIRMWARE_URL:http://github.com/Ultimaker PROTOCOL_VERSION:1.0
MACHINE_TYPE:Ultimaker EXTRUDER_COUNT:1
Recv:16:42:53.759: ok
Send:16:42:53.759: N5 M220 S100 ; Speed multiplier 100%
Recv:16:42:53.762: ok
Send:16:42:53.762: N6 M221 S100 ; Flow multiplier 100%
Recv:16:42:53.766: ok
Send:16:42:53.766: N7 G92 E0
Recv:16:42:53.770: ok
Send:16:42:53.770: N8 G90
Recv:16:42:53.775: ok
Send:16:42:53.775: N9 M82
Recv:16:42:53.779: ok
Send:16:42:53.779: N10 G21 ; Use mm as unit
Recv:16:42:53.783: ok
Send:16:42:53.783: N11 M114
Recv:16:42:53.787: X:0.00Y:0.00Z:0.00E:0.00 Count X: 0.00Y:0.00Z:0.00
Recv:16:42:53.787: ok
Send:16:42:53.787: @echo Some printers don't implement timing, but can cause unexpected execution based on file name.
Mesg:16:42:53.787: Some printers don't implement timing, but can cause unexpected execution based on file name.
Send:16:42:53.787: @echo By triggering unknown command here we block it for real usage.
Mesg:16:42:53.787: By triggering unknown command here we block it for real usage.
Send:16:42:53.787: @echo So please ignore unknown command if it appears now.
Mesg:16:42:53.787: So please ignore unknown command if it appears now.
Send:16:42:53.787: N12 M75
Recv:16:42:53.791: ok
Send:16:42:53.791: N13 M77
Recv:16:42:53.795: ok
Send:16:42:53.795: @getIP
Send:16:42:53.795: N14 M114
Recv:16:42:53.799: X:0.00Y:0.00Z:0.00E:0.00 Count X: 0.00Y:0.00Z:0.00
Recv:16:42:53.799: ok
Send:16:42:53.800: @startCodeProcessed
Send:16:43:07.261: @getip
Send:16:43:40.528: N61 M75 Platte Bandschleiffm
Recv:16:43:40.532: ok
Send:16:43:40.551: N62 M140 S90
Recv:16:43:40.556: ok
Send:16:43:40.561: Slow command added:M190 S90
Send:16:43:40.561: N64 M190 S90
Mesg:16:46:22.351: Connection closed by os during print ... trying reconnect for 10 seconds to continue ...
Offl:16:46:22.352: Ignored (offline):M73 P57 R3 Q57 S3
Mesg:16:46:22.979: Dtr: true Rts: true
Mesg:16:46:22.980: Connection continued
Mesg:16:46:26.991: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:26.991: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:26.991: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:26.991: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 5000
Mesg:16:46:26.991: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:46:30.997: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:30.997: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:30.997: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:30.997: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 5000
Mesg:16:46:30.997: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:46:34.999: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:34.999: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:34.999: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:34.999: Connection status: Buffered:12, Manual Commands: 1, Job Commands: 5000
Mesg:16:46:34.999: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:46:39.003: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:39.003: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:39.003: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:39.003: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:46:39.003: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:46:43.013: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:43.013: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:43.013: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:43.013: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:46:43.013: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:46:47.014: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:47.014: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:47.014: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:47.016: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:46:47.016: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:46:51.026: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:51.026: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:51.026: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:51.026: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:46:51.026: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:46:55.032: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:55.032: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:55.032: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:55.032: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:46:55.032: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:46:59.038: Warning: Communication timeout - resetting communication buffer.
Mesg:16:46:59.038: This means that a expected firmware response was not seen within the expected time.
Mesg:16:46:59.038: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:46:59.038: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:46:59.038: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:47:03.042: Warning: Communication timeout - resetting communication buffer.
Mesg:16:47:03.042: This means that a expected firmware response was not seen within the expected time.
Mesg:16:47:03.042: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:47:03.042: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:47:03.042: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:47:07.049: Warning: Communication timeout - resetting communication buffer.
Mesg:16:47:07.049: This means that a expected firmware response was not seen within the expected time.
Mesg:16:47:07.049: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:47:07.050: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:47:07.050: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:47:11.058: Warning: Communication timeout - resetting communication buffer.
Mesg:16:47:11.058: This means that a expected firmware response was not seen within the expected time.
Mesg:16:47:11.058: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:47:11.058: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:47:11.058: Buffer used:12 Enforced free byte:0 lines stored:1
Mesg:16:47:15.060: Warning: Communication timeout - resetting communication buffer.
Mesg:16:47:15.060: This means that a expected firmware response was not seen within the expected time.
Mesg:16:47:15.060: The typical reason is a communication error and print should continue after the communication reset.
Mesg:16:47:15.060: Connection status: Buffered:12, Manual Commands: 2, Job Commands: 8
Mesg:16:47:15.060: Buffer used:12 Enforced free byte:0 lines stored:1
Sysl:16:47:15.851: Your OS syslog contains these messages close to this disconnect that might help to understand:
Sysl:16:47:15.851: [ 121.528925] usb 1-1.3-port1: disabled by hub (EMI?), re-enabling...
Sysl:16:47:15.851: [ 121.529939] usb 1-1.3.1: USB disconnect, device number 4
Sysl:16:47:15.852: [ 121.836682] usb 1-1.3.1: new full-speed USB device number 5 using xhci_hcd
Sysl:16:47:15.852: [ 121.998068] usb 1-1.3.1: New USB device found, idVendor=2341, idProduct=0010, bcdDevice= 0.01
Sysl:16:47:15.853: [ 121.998099] usb 1-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sysl:16:47:15.853: [ 121.998117] usb 1-1.3.1: Product: Ultimaker 2.0
Sysl:16:47:15.853: [ 121.998133] usb 1-1.3.1: Manufacturer: Ultimaker BV (www.ultimaker.com)
Sysl:16:47:15.853: [ 122.013974] cdc_acm 1-1.3.1:1.0: ttyACM0: USB ACM device
Sysl:16:47:15.853:
checking bus 1, device 5:
"/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3.1"
(2)
Mesg:16:47:15.861: Connection closed by os.
Mesg:16:47:16.997: Dtr: true Rts: true
Mesg:16:47:17.000: Connection started
Mesg:16:47:17.000: Printer reset requested - emergency:false
Mesg:16:47:17.000: Dtr: false Rts: false
Mesg:16:47:17.022: Dtr: true Rts: true
Recv:16:47:18.142: Connection verified by:start
Recv:16:47:18.143: Printer reset detected:start
Recv:16:47:18.143: start
Send:16:47:18.143: N1 M110
Recv:16:47:18.147: echo:Marlin 1.0.0
Recv:16:47:18.147: echo: Last Updated: Oct 5 2022 20:25:05 | Author: Version DEV
Recv:16:47:18.147: Compiled: Oct 5 2022
Recv:16:47:18.151: echo: Free Memory: 2041 PlannerBufferBytes: 1232
Recv:16:47:18.151: echo:Stored settings retrieved
Recv:16:47:18.155: echo:Steps per unit:
Recv:16:47:18.155: echo: M92 X80.00 Y80.00 Z400.00 E510.00
Recv:16:47:18.155: echo:Maximum feedrates (mm/s):
Recv:16:47:18.159: echo: M203 X300.00 Y300.00 Z40.00 E50.00
Recv:16:47:18.159: echo:Maximum Acceleration (mm/s2):
Recv:16:47:18.163: echo: M201 X9000 Y9000 Z100 E10000
Recv:16:47:18.163: echo:Acceleration: S=acceleration, T=retract acceleration
Recv:16:47:18.167: echo: M204 S3000.00 T3000.00
Recv:16:47:18.172:
echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate
(mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s),
Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
Recv:16:47:18.176: echo: M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
Recv:16:47:18.176: echo:Home offset (mm):
Recv:16:47:18.179: echo: M206 X0.00 Y0.00 Z-11.75
Recv:16:47:18.179: echo:PID settings:
Recv:16:47:18.180: echo: M301 P12.07 I1.11 D32.93
Recv:16:47:18.474: echo:SD card ok
Recv:16:47:18.507: ok
Send:16:47:18.515: N4 M115 ; Get firmware capabilities and info
Recv:16:47:18.524:
FIRMWARE_NAME:Marlin Ultimaker2; Sprinter/grbl mashup for gen6
FIRMWARE_URL:http://github.com/Ultimaker PROTOCOL_VERSION:1.0
MACHINE_TYPE:Ultimaker EXTRUDER_COUNT:1
Recv:16:47:18.524: ok
Send:16:47:18.524: N5 M220 S100 ; Speed multiplier 100%
Recv:16:47:18.527: ok
Send:16:47:18.527: N6 M221 S100 ; Flow multiplier 100%
Recv:16:47:18.531: ok
Send:16:47:18.531: N7 G92 E0
Recv:16:47:18.535: ok
Send:16:47:18.535: N8 G90
Recv:16:47:18.540: ok
Send:16:47:18.540: N9 M82
Recv:16:47:18.544: ok
Send:16:47:18.544: N10 G21 ; Use mm as unit
Recv:16:47:18.548: ok
Send:16:47:18.548: N11 M114
Recv:16:47:18.552: X:0.00Y:0.00Z:0.00E:0.00 Count X: 0.00Y:0.00Z:0.00
Recv:16:47:18.552: ok
Send:16:47:18.552: @echo Some printers don't implement timing, but can cause unexpected execution based on file name.
Mesg:16:47:18.552: Some printers don't implement timing, but can cause unexpected execution based on file name.
Send:16:47:18.552: @echo By triggering unknown command here we block it for real usage.
Mesg:16:47:18.552: By triggering unknown command here we block it for real usage.
Send:16:47:18.552: @echo So please ignore unknown command if it appears now.
Mesg:16:47:18.553: So please ignore unknown command if it appears now.
Send:16:47:18.553: N12 M75
Recv:16:47:18.556: ok
Send:16:47:18.556: N13 M77
Recv:16:47:18.560: ok
Send:16:47:18.560: @getIP
Send:16:47:18.560: N14 M114
Recv:16:47:18.564: X:0.00Y:0.00Z:0.00E:0.00 Count X: 0.00Y:0.00Z:0.00
Recv:16:47:18.564: ok
Send:16:47:18.564: @startCodeProcessed
Send:16:47:32.031: @getip
