donovan6000 / M33-Fio

The ultimate OctoPrint plugin
GNU General Public License v3.0
125 stars 38 forks source link

Print "fails" after first layer #121

Closed ra100 closed 8 years ago

ra100 commented 8 years ago

After first layer is done, head starts to move very slowly to FR corner, still extruding. stl+gcode: pin.zip

donovan6000 commented 8 years ago

I'm printing it right now. At layer 5 so far and I'm not experiencing any problems. Are you able to repeat this issue?

I'm really starting to think there's something wrong with M3D's V2016012501 firmware. Even M3D's tech support is now recommending that people downgrade to their V1.4.0.7 software which includes their V2016010812 firmware. I'll probably include that firmware in the next version of M3D Fio unless M3D release a new update in that time.

ra100 commented 8 years ago

Interesting, I tried it with 2 different models, this is result of first print, I didn't watch it and canceled print after 10 minutes or so. I'll just try flash firmware and run full calibrantion, as I see there is also external bed height calibration now. So at least I'll try that and report back. img_20160325_100338

ra100 commented 8 years ago

Seems everything is fine again. It was maybe just some glitch in my system.

ra100 commented 8 years ago

Seems like problem is with Wave Bonding, now I tried again with wave bonding, and again, after first layer of raft, head started to move to FR. And it also didn't seem like there were any "waves". log020160325.zip

donovan6000 commented 8 years ago

What other settings do you have enabled/disabled? I'm trying to recreate it, but I only got a successful print. The log does show that it moved into the FR corner from commands inserted by the pre-processors, so this is definitely the pre-processors fault.

Do you also expirence this issue in M3D Fio's V0.30.2 release? The only thing I've changed about the pre-processors since releasing that version was making sure that all commands have feedrates. I don't really think that would cause this though since the printer is already internally be using the last commands's feedrate if the current command doesn't have one.

ra100 commented 8 years ago

Now I noteiced, that Volume setting is somewhat weird. Shouldn't it be 109x113x116? And I didn't try wave bonding for some time (it's probably not even worth it while printing on glass) so I'll have to try older version and try printing again.

screenshot-192 168 150 12 5000 2016-03-26 09-55-28 screenshot-192 168 150 12 5000 2016-03-26 09-55-51 screenshot-192 168 150 12 5000 2016-03-26 09-58-19 screenshot-192 168 150 12 5000 2016-03-26 09-58-55 screenshot-192 168 150 12 5000 2016-03-26 09-59-11

ra100 commented 8 years ago

Same result with 0.30.2

donovan6000 commented 8 years ago

M3D Fio dynamically changes the dimensions of the M3D printer profile, micro_3d, whenever the boundaries of the printable region change. That happens when changing the external bed height or changing the external bed expands printable region setting, so that makes the dimensions in the printer profile always equal to the size of the lowest boundary. The only thing I've noticed that actually uses the printer profile dimensions is OctoPrint's G-code viewer to size the grid, so it's purely aesthetic.

I'm able to get the same unexplained slow FR movements when using wave bonding with all your settings. Turns out that there was an issue with the wave bonding and thermal bonding pre-processors where incrementing a layer counter could get messed up by the 'Use GPIO' and 'Mid-print filament change layers' settings. It should be fixed now.

ra100 commented 8 years ago

I've had time to test it just now. And it works nice, and it makes "waves". Thanks for fixing it.