Jump to content

Difference between detected height of both PrintCores exceeds realistic values


Wisar

Recommended Posts

Posted · Difference between detected height of both PrintCores exceeds realistic values

Whats up with this message? Just started doing it out of the blue a couple days ago. Followed advice elsewhere on the forum about the distance from the build platform base plate to the bottom of the heated bed and still same error.

Printer is working fine in single extrusion mode but have not tried a dual extrusion print since the error manifested itself.

Help appreciated!

Will

  • Link to post
    Share on other sites

    Posted (edited) · Difference between detected height of both PrintCores exceeds realistic values

    It's the printers polite way off telling you the autolevel failed. If the detection fails it will stop before crushing your glass bed (I hope).

    Check if your nozzle and bed are clean. Think too much glue on the bed can already have a effect.

    Personally I just turned of autoleveling, mostly because it saves time.

    Edited by Guest
  • Link to post
    Share on other sites

    Posted (edited) · Difference between detected height of both PrintCores exceeds realistic values

    I manually level for single extruder prints and am fine with that though I still want auto leveling to work.  My print surface is sparkly clean and the bed is adjusted manually and is not far from the recommended clearances between the top of bottom plate and the bottom of the heated plate.  Yet the auto level fails and what is WORSE is that I just tried to do a two extruder print and IT FAILED!  Looks like bad extrusion.  The PLA side was just fine.

    Will

    Edited by Guest
  • Link to post
    Share on other sites

    Posted (edited) · Difference between detected height of both PrintCores exceeds realistic values

    More on the above.  I replaced the BB core with an AA core and the automatic leveling process worked.   So I swapped cores again...and the leveling process worked!  Even better my two material print with PVA is now well beyond where it had failed before........... :-o

    Edited by Guest
  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Hi Wisar,

    Is the auto leveling now always working for you? I just has my printer 4 days. Did a firmware upgrade on the setup. I'm on 3.5.3.20161221 version.

    I set it up to auto level before each print (really it takes a couple of minutes, less than 1% on some of my 18 hours prints) but it just keeps failing on the first auto level, every time.

    It was so bad that I basically cannot sent a job over the network, as the printer would fail the leveling and the job would be completed without printing. So I just disabled it for now.

    I manually leveled the bed at least 10 times now. I tried with the worm wheels in the lowest position, middle and upper. In non of the situations, auto leveling will complete successfully afterwards.

    Which firmware are you running?

    Can anyone comment on the real need for auto leveling. @Ultiarjan: did you just level it manually and redo it when needed?

    Regards,

    Richard

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Yes. I just level manually with a piece of ordinary copy paper. The bed is pretty stable. You hardly ever need to redo it.

    On my um2 it's not even needed after transporting it by car.

    I just have a preference for manual... also change material and cores manually... it's just quicker.

    But besides my preferences the auto functions should work ofc.

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Is the auto leveling now always working for you? I just has my printer 4 days. Did a firmware upgrade on the setup. I'm on 3.5.3.20161221 version.

    Which firmware are you running?

    Can anyone comment on the real need for auto leveling. @Ultiarjan: did you just level it manually and redo it when needed?

     

    I am running the current firmware, just updated last week, so whatever version that would be.

    I would be fine with manual leveling if I had not had the failed dual extrusion print in the midst of getting the message that I asked about at the start of this exchange.

    Interestingly, I just did an active level and it failed. This was on a build platform that I just manually leveled to perfection yesterday. So I heated the core that is in slot #2 and then wiped the tip of the nozzle and re-did the leveling. It worked. Might be worth a try.

    I would like to hear some thoughts from someone at Ultimaker!

    Will

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Yes, I had that too, the second time it is succesful, even without any wiping or so. But the problem is with when it automatically decides to auto level. I cannot use that feature as it basically means at a certain point the printer will auto level, fail and I have to go down to flights of step to acknoledge with a press on the front button.

    Better to completely disable the auto leveling then.

    I got a pointer to this message, will give that a try, even though I've been there and almost completely tightened the screws and tried. Maybe I tightened them too much.

    https://ultimaker.com/en/community/35700-auto-level-failure

    Cheers,

    Richard

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Interestingly, I just did an active level and it failed.  This was on a build platform that I just manually leveled to perfection yesterday.  So I heated the core that is in slot #2 and then wiped the tip of the nozzle and re-did the leveling.  It worked.  Might be worth a try.

    I would like to hear some thoughts from someone at Ultimaker!

     

    Hello Will,

    Let me shed some light on this. The message "Difference between detected height of both nozzles exceeds realistic values" is a check that verifies if the offset measured for both nozzles at each of the probe locations is within certain limits. That is: there is a minimum / maximum difference for height measured by the left (first) and right (second) nozzle.

    The logs should specify the probe location that would give the failure. For us at Ultimaker it would be interesting to get that data. It might provide information as to why it would be failing.

    Dumping the logs can be done using the Menu: System -> Maintenance -> Diagnostics -> Dump logs to USB

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Have the same problem.... maybe I send the printer back.,..

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Have the same problem.... maybe I send the printer back.,..

     

    You might want to do this first

    https://ultimaker.com/en/community/35700-auto-level-failure#featured

    That should remove the error

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    My scientific method in regards to working on this problem, frankly, sucked. The problem does seem to have gone away but I am not completely sure why as I changed more than one variable at a time. I did do the adjustment for the bed per the post recommended by neotko but did not find this to work. On one occasion I cleaned the nozzle on the BB print core and a subsequent auto level did work...but on another occasion, it did not. Then, somewhere along the line, I upgraded the firmware on the printer and, this is where the method broke down, I am pretty sure that I had an auto level failure after the upgrade, but would not swear to it in a court of law. So, at the moment I am working fine............!

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    For us at Ultimaker it would be interesting to get that data. It might provide information as to why it would be failing.

    Dumping the logs can be done using the Menu: System -> Maintenance -> Diagnostics -> Dump logs to USB

     

    I will 'def post logs if it occurs again...!
  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    I had that happen once. But when I did a manual leveling, it went away.

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Had mine delivered yesterday, fails 100% ungracefully. I can hear the z engine trying to crush the printhead and when in front, the plate clearly gets angled by the force.

    Not a good start. (I am not new to 3D print, I have been printing for several years and built and modified several printers),

    And yes, tried all by instructions/solutions, to no avail. I had to disable the auto leveling to get my first test print.

    So I figure from this thread that this is one fancy function to tick of the list of this premium printer as dysfunctional. I will see how it works in other areas, considering a return.

     

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values
    2 hours ago, RunTime said:

    Had mine delivered yesterday, fails 100% ungracefully. I can hear the z engine trying to crush the printhead and when in front, the plate clearly gets angled by the force.

    Not a good start. (I am not new to 3D print, I have been printing for several years and built and modified several printers),

    And yes, tried all by instructions/solutions, to no avail. I had to disable the auto leveling to get my first test print.

    So I figure from this thread that this is one fancy function to tick of the list of this premium printer as dysfunctional. I will see how it works in other areas, considering a return.

     

     

    Most often when the nozzle gets pushed inside the printhead during the active leveling (particularly right after arrival), it's because during your manual leveling, the springs got loosened too far. I've got a description, photos, and video here: https://ultimakernasupport.zendesk.com/hc/en-us/articles/115005705806-Why-Isn-t-My-Active-Leveling-Working- Tighten the springs (all of them), and it should be okay.

    • Like 1
    Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values
    7 hours ago, fbrc8-erin said:

     

    Most often when the nozzle gets pushed inside the printhead during the active leveling (particularly right after arrival), it's because during your manual leveling, the springs got loosened too far. I've got a description, photos, and video here: https://ultimakernasupport.zendesk.com/hc/en-us/articles/115005705806-Why-Isn-t-My-Active-Leveling-Working- Tighten the springs (all of them), and it should be okay.

    That was what happened on my new printer. I had followed your advice in another thread to get it set properly.

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    OK, admit being a bit grumpy...

    I tried lowering the plate to a maximum, it seems to have worked (at least once). Thank you all!

    My fault (?) was to assume that half way between maximum and minimum would be a good starting point (as an engineer that is).

    Now I have been struggling with Simplify3D that zeroes to negativ value (drive belt jumping) and to make PVA stick like PLA... an complete different story.

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Hey, new problems can make you a bit grumpy, eh?

     

    Why not try Cura? It is focused on the UM family of printers. Rocks on the UM3(X).

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Looks good indeed, I figure I will use both as sometimes a critical function or parameter is missing. My first was to adjust the support in areas where I needed to drop some extras in a hollow. I expect fin find use for both. Especially after years with Simple3D. Sad though that there are no direct connection over LAN/WiFi.

    By the way, I have not seen this mention anywhere. I often speed-cooled my previous machines prints by a freezer spary. I have now expanded the use to get things off the glass when it sticks to good (even after cooling down completely), some PLA that i use is really sticky.

    Just a firm short spray (-51C°) here and there and everything is easy to gently loosen without any damages. It even pops of by itself!

    Next test is to run the gizmos with support in the dishwasher....

     

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    I get this error at least 3/4 of the times I've tried to print over the last few months. It usually takes 3-4 tries to get it to pass the core height check. 

     

    The problem occurs during the first test it does (for core 2). It doesn't even try. It should take about 10 seconds for the bed to reach the nozzle (it does for the second check, for core 1), but instead it stops after just 1-2 seconds, when the bed is nowhere near the nozzle. Then it checks core 1, then the error. The nozzle and bed are clean. 

     

    It's very frustrating, especially because I'm usually only using one core, so height difference between the cores is irrelevant. I wish this test could be turned off. 

    • Like 1
    Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Same issue here. Doesn't even come close to touching when using Core 2. Then it touches off on Core 1 and throws the error. 

    Anyone find any sure ways to correct this?

    • Like 1
    Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values

    Yes, I have found that tightening all 3 bed screws until your fingers want to snap so the bed is very low. Then do manual leveling in maintenance and carefully follow instructions only touching what it tells you to touch (ie thumbs crew, or contols) what helped me is I printed a 1mm credit card with a small handle to use as a spacer for the exact 1mm needed, this solved my active leveling problem hope it does for you too.

    16072720879358881836875407495203.jpg

  • Link to post
    Share on other sites

    Posted · Difference between detected height of both PrintCores exceeds realistic values
    5 hours ago, GoguyT3d said:

    Yes, I have found that tightening all 3 bed screws until your fingers want to snap so the bed is very low. 

    No, you don't want to tighten your bed that far. The active leveling procedure is a tight balance between the tension of the bed springs and the sping inside the print core. The bed should be manually set at a height of 14mm, see the link in the post from @fbrc8-erin for a detailed description and procedure.

     

    Quote

    I printed a 1mm credit card with a small handle to use as a spacer for the exact 1mm needed,

    The correct height setting in manual leveling is 0.15mm. With a difference of 1mm there will be massive under extrusion for the first layer and poor bed adhesion.

    • Like 1
    Link to post
    Share on other sites

    Posted (edited) · Difference between detected height of both PrintCores exceeds realistic values

    Thats not what my printer told me. Turn the thumbs screw until the nozzle is 1mm away from the bed, then further adjust it with the calibration card. Worked for me, good luck.

    Edited by GoguyT3d
    Punctuation
  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...