prusa3d_fw_3_1_1_rc2_b137 Issue  

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

Tried slicing with Simplify3D, something is wrong

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

The print stops, printer becomes unresponsive, but filament continues to pour out. Curious if this has to do with the Pi Zero W and Octopi

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

Are you printing with OctoPi on a Pi Zero W through the internal serial port?

If so I am having many similar errors. I don't think that serial interface is ready for prime time yet. See a bit of my log below where I am seeing something similar relatively soon into the print. I am back to straight printing off of SD for the time being.

Send: N4457 G1 X123.163 Y98.770 E0.65782*107
Recv: Error:checksum mismatch, Last Line: 4456
Recv: Resend: 4457
Recv: ok
Send: N4457 G1 X123.163 Y98.770 E0.65782*107
Recv: ok
Send: N4458 G1 X122.832 Y98.506 E0.01043*99
Recv: ok
Send: N4459 G1 X104.184 Y117.154 E0.65015*86
Recv: ok
Send: N4460 G1 X104.083 Y116.660 E0.01242*89
Recv: ok
Send: N4461 G1 X122.501 Y98.243 E0.64212*103
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: echo: too long extrusion prevented
Recv: ok
Send: N4462 G1 X122.169 Y97.979 E0.01043*102
Recv: Error:checksum mismatch, Last Line: 4461
Recv: Resend: 4462
Recv: ok
Send: N4462 G1 X122.169 Y97.979 E0.01043*102
Recv: ok
Send: N4463 G1 X103.989 Y116.159 E0.63384*92
Recv: ok
Send: N4464 G1 X103.902 Y115.652 E0.01269*81
Recv: ok
Send: N4465 G1 X121.822 Y97.732 E0.62478*108
Recv: Error:checksum mismatch, Last Line: 4464
Recv: Resend: 4465
Recv: ok
Send: N4465 G1 X121.822 Y97.732 E0.62478*108
Recv: ok
Send: N4466 G1 X121.471 Y97.488 E0.01053*111
Recv: ok
Send: N4467 G1 X103.818 Y115.141 E0.61548*95
Recv: Error:checksum mismatch, Last Line: 4466
Recv: Resend: 4467
Recv: ok
Send: N4467 G1 X103.818 Y115.141 E0.61548*95
Recv: echo:enqueing "G1 Z 10.650 E 0.000 F 800.000"
Recv: echo:enqueing "CRASH_DETECTED"
Recv: echo:enqueing "G28 X"
Recv: echo:enqueing "G28 Y"
Recv: echo:enqueing "CRASH_RECOVER"
Recv: G28, initial world coordinates: (254.795, -3.644, 10.650)
Recv: G28, initial physical coordinates: (254.430, -3.540, 10.355)
Recv: echo:busy: processing
Recv: echo:busy: processing
Recv: G28, final world coordinates: (0.365, -3.944, 10.212)
Recv: G28, final physical coordinates: (0.000, -3.540, 10.355)
Recv: G28, final mesh bed leveling: 0.149 0.149 0.126 0.080 0.010 -0.084 -0.200 0.182 0.194 0.184 0.152 0.097 0.020 -0.079 0.219 0.244 0.246 0.226 0.184 0.120 0.034 0.259 0.298 0.312 0.304 0.272 0.216 0.138 0.304 0.356 0.383 0.384 0.359 0.309 0.233 0.352 0.419 0.458 0.467 0.447 0.398 0.319 0.403 0.487 0.537 0.553 0.535 0.483 0.397
Recv: G28, initial world coordinates: (0.365, -3.944, 10.212)
Recv: G28, initial physical coordinates: (0.000, -3.540, 10.355)
Recv: G28, final world coordinates: (0.365, -4.404, 10.213)
Recv: G28, final physical coordinates: (0.000, -4.000, 10.355)
Recv: G28, final mesh bed leveling: 0.149 0.149 0.126 0.080 0.010 -0.084 -0.200 0.182 0.194 0.184 0.152 0.097 0.020 -0.079 0.219 0.244 0.246 0.226 0.184 0.120 0.034 0.259 0.298 0.312 0.304 0.272 0.216 0.138 0.304 0.356 0.383 0.384 0.359 0.309 0.233 0.352 0.419 0.458 0.467 0.447 0.398 0.319 0.403 0.487 0.537 0.553 0.535 0.483 0.397
Recv: echo:busy: processing

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

You are right. this seems to be a problem with Pi Zero W, I disconnected the Pi Zero and hooked it up to RPI3 and no issues occurred.

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

Did you look at this thread?
https://shop.prusa3d.com/forum/original-prusa-i3-mk3-f30/rpi-zero-octopi-working--t12432.html

perhaps those steps will solve your problem

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

looked at that as well, still having issues during the print.

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

Turn off crash detection. Crash detection in current firmware works only with SD card print.

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

I get the same issue with Octopi on rpi3 via USB, crash detected randomly that shows up in the terminal and then it just stops and keeps the hotend hot (not sure if it's still extruding, forgot to check), last test resetting the printer raised Z until it crashes in the endstops, another reset and it's responsive again.

Also turning off crash detection for now until I know what causes these and printong from octopi, if it's a fw bug or something else (belt tension seems ok, or bearing issue, not sure yet.)

The print stops, printer becomes unresponsive, but filament continues to pour out. Curious if this has to do with the Pi Zero W and Octopi

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

Thomas Sanladerer talked about a newer FW version, 138, in his video "Live: Unboxing the Prusa MK3!" on YouTube:

He had a lot of problems with version 137 and upgraded to 138 in the live stream.

But no link to 138 in the description... 😐

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

"But no link to 138 in the description... :|" An update would be nice...I don't care much for github...it always seems to be in disarray.

Re: prusa3d_fw_3_1_1_rc2_b137 Issue

Found the .hex file in the git repository: Firmware.ino.rambo.hex (build 138 (RC3))
Link: https://github.com/prusa3d/Prusa-Firmware/tree/MK3/Firmware

I'm not ready for testing - still building the MK3...