Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wipe tower interferes with print object when arrange all objects is used #3806

Open
photodude opened this issue Mar 9, 2020 · 18 comments
Open
Assignees

Comments

@photodude
Copy link
Contributor

photodude commented Mar 9, 2020

Version

Build: PrusaSlicer-2.1.1+win64-201912101512
and
Build: PrusaSlicer-2.2.0-rc2+win64-202003071138

Operating system type + version

Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 10 (build 18363), 64-bit edition
Total RAM size [MB]: 34,307MB
OpenGL installation
GL version: 4.6.0 NVIDIA 441.87
Vendor: NVIDIA Corporation
Renderer: GeForce GTX 1070/PCIe/SSE2
GLSL version: 4.60 NVIDIA

3D printer brand / version + firmware version (if known)

BIBO2 Stock model with 5015 part cooling blower and PEI sheet build surface
BIBO MFG provided stock based on Marlin 1.0.0 shaqFoo Ditto printing fork firmware

Behavior

When a multi-extruder object has a wipe tower and the "arrange all objects is used the wipe tower can end up interfering (overlapping) the print object.

  • Steps needed to reproduce the problem
  1. multi extruder print (in my case a 2 color print for dual extrusion)
  2. turn on wipe tower
  3. press the "arrange all objects
  4. observe wipe tower interfering with the object
  • Expected Results
    Wipe tower should be positioned at a location near but not overlapping the print object.
  • Actual Results
    the wipe tower often overlaps the object
  • Screenshot
    Capture3

printer configuration can be found in my Github Repo or the open PR #3804
https://github.com/photodude/BIBO2-PrusaSlicer

Project file
wipe tower before using arrange all object
bulbasaur_dual_detail.zip
wipe tower after arrange all objects
bulbasaur_dual_detail_wipeTower_interferance.zip

@lukasmatena
Copy link
Collaborator

This should be already fixed in 2.2.0-rc2.

@lukasmatena
Copy link
Collaborator

Actually, the arrange function accounts for the wipe tower since 2.0.0, so it's not something that was fixed recently. Something is clearly wrong, but I have no clue what it is. I didn't manage to reproduce the issue (at least not on Linux). We will try to reproduce and fix it.

@peymon
Copy link

peymon commented Mar 20, 2020

I can confirm, I have the same issue. Had it since 2.2.0 RC3. It has not been fixed in RC5.

@tamasmeszaros
Copy link
Contributor

Hi @peymon ! Please, could you send a 3mf where the issue occurs? I could not reproduce with @photodude 's project files.

@tamasmeszaros tamasmeszaros self-assigned this Mar 20, 2020
@peymon
Copy link

peymon commented Mar 20, 2020

Hi @tamasmeszaros,

The issue occurs regardless of the model. I just reproduced it using the Prusa Beer Opener and attached it for you here. Please note that I am using the Mac version: 2.2.0-rc5+-202003191653. But I have had this issue since rc3. I have not tested it on previous builds.

PrusaBeerOpener

PrusaBeerOpener.3mf.zip

@bubnikv
Copy link
Collaborator

bubnikv commented Mar 20, 2020

I am not able to reproduce this issue with PrusaSlicer 2.2.0-rc5 either. To be sure, I tried on both Windows 10 and OSX Catalina.

@peymon
Copy link

peymon commented Mar 20, 2020

I tried to make a gif of the problem. See attached, please.

PrusaSlicerProblem

@photodude
Copy link
Contributor Author

@bubnikv I'm guessing it requires having the wipe tower selected when arrange is selected.
Which of the 2 project files I uploaded did you try?

@bubnikv
Copy link
Collaborator

bubnikv commented Mar 21, 2020 via email

@bubnikv
Copy link
Collaborator

bubnikv commented Mar 21, 2020

I was not able to reproduce the issue with PrusaSlicer 2.2.0-rc5 with any models provided. However these are my hints:

The wipe tower has two states:

  1. G-code not generated yet, thus the size of the wipe tower is not know yet and the wipe tower block shows the two zigs.
  2. G-code generated, the wipe tower size is known and the rear wall of the wipe tower is rendered flat without the two zigs.

The animated gif by #3806 (comment)
shows a wipe size was known. I was thinking maybe the issue could be that the arrangement will invalidate the wipe tower from state 2) to 1), but it does not, as just moving the objects around does not change the amount of wipe (this assumption may be no more valid after PrusaSlicer 2.2.0 path planning change though).

The wipe tower position is stored in the Print preset. This is not optimal, it is a heritage of the Slic3r PE impelmentation we did before we had 3MFs. I would expect that the wipe tower could jump back to the position stored in the Print preset if some messages indicating the wipe tower position inside PrusaSlicer were delivered in a wrong order. But this does not seem the case here either.

@bubnikv
Copy link
Collaborator

bubnikv commented Mar 22, 2020

By the way, do you guys have background processing enabled?

@photodude
Copy link
Contributor Author

@bubnikv I do not have background processing enabled.
Capture

@photodude
Copy link
Contributor Author

photodude commented Mar 22, 2020

@bubnikv This is what I got with a dual extrusion calibration target, background processing enabled, and wipe tower using auto arrange. Clicked on bed before auto arrange to deselect everything. 2.2.0-rc5 BIBO dual printer, 0.15 print profile with wipe tower
Capture

before
wipe_tower_error_before_Dual_Extruder_Calibration_Target.zip

after arrange
wipe_tower_error_after_Dual_Extruder_Calibration_Target.zip

@photodude
Copy link
Contributor Author

@bubnikv I have discovered the replication step that was missing, =D
happens only when "auto center parts" is enabled.

Seems there is a missing, or incorrect, collision check for the wipe tower when "auto center parts" is enabled.

with the before project uploaded above and "auto center parts" is enabled there is an issue (see image in post above), but disabling "auto center parts" keeps the wipe tower positioned without collision with the model.
Capture
Re-enabling "auto center parts" causes the issue again.

@bubnikv
Copy link
Collaborator

bubnikv commented Mar 22, 2020 via email

@peymon
Copy link

peymon commented Mar 22, 2020

@photodude, genius! Indeed without auto-center, the issue is no longer there.

@photodude
Copy link
Contributor Author

photodude commented Mar 29, 2020

@bubnikv When "auto-center" is removed will it be replaced with an "auto-arrange"?
It would be nice for models to auto-arrange when first placed on the print bed, then let me adjust positions as I see fit.

@photodude
Copy link
Contributor Author

@bubnikv ::face-palm:: ... I see you already said that auto-arrange on first add is coming and I forgot to reread before commenting... sorry.

@rtyr rtyr added the AutoCenter label Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants