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

problem with the calibration menu tabs #1325

Closed
erathos77 opened this issue Jun 17, 2021 · 8 comments
Closed

problem with the calibration menu tabs #1325

erathos77 opened this issue Jun 17, 2021 · 8 comments
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@erathos77
Copy link

Describe the bug
When the included calibration objects are generated from any calibration tabs, it shows an inappropriate alert in the 3D view window:

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'any calibration menu tab'
  2. Click on "generate" in the help window
  3. go to the 3D view window
  4. See error: Alert at the bottom of the window
    "Error:
    An object outside the print area was detected
    Resolve the current problem to continue slicing."

Desktop (please complete the following information):

  • OS: macOs 10.13
  • Version [e.g. 2.3.56.5],

Additional context
Despite of this no such other object is visible in the window, and the calibrations perform well from the gcode.
Maybe intruders in the included calibration stl files ?

@kevenwyld
Copy link

All of the calibrations are created using amf files, not stl. I have noticed that when opening amf files from FreeCAD where I create most of my models, they are imported into superslicer off of the build plate and I get this error. Then I have to click Arrange from the tool bar to center it.

I had always assumed this was a FreeCAD export issue but I just tried this with one of the amf files from a calibration directory and it does the same thing:
Screenshot_2021-06-17_16-27-54

I wonder if when you click generate it imports the amf file and then positions it so for a brief moment it's outside the bounds of the build plate?

@supermerill
Copy link
Owner

yes.

@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Jun 17, 2021
@liftbag
Copy link

liftbag commented Jun 18, 2021

Seems solved with the MacOS nightly 364.

@supermerill
Copy link
Owner

supermerill commented Jun 18, 2021

be careful to not write the '#', as github will think that you want to link to an issue.

@liftbag
Copy link

liftbag commented Jun 18, 2021

be careful to not write the '#', as github will think that you want to link to an issue.

Understand.

@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Jun 26, 2021
@falo2k
Copy link

falo2k commented Jun 29, 2021

I just ran into this in the latest release when trying to drop a pair of Voron cubes for the dimensional accuracy test.

@liftbag
Copy link

liftbag commented Jul 1, 2021

I just ran into this in the latest release when trying to drop a pair of Voron cubes for the dimensional accuracy test.

I can confirm. In my case it happens because the cube is positioned at the end of the axes instead of in the center of the bed.

@supermerill
Copy link
Owner

supermerill commented Jul 2, 2021

Somone updated the voron calibration cube. I didn't checked if it was correctly at 0,0...
Will change that

@supermerill supermerill added bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build and removed fix is live in the last release Please download /build the last release and try to reproduce. problem labels Jul 2, 2021
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

5 participants