5 hours ago, gr5 said:First and foremost, watch the leveling when it does the first two levelings - left and right core at the same spot. It's supposed to slowly move the bed until it touches the nozzle. One failure mode is that it stops before the bed touches the nozzle. Another is that it touches the nozzle and keeps going much too long afterwards.
1) Okay but what about this above.
2) And since you have the log file, do a grep for "peak" and "Preliminary" as shown here:
geo@geo-Wild-Dog-Pro:~/ultimaker/logs oct28 2020$ grep peak ultimakersystem-ccbdd3005b4c.5.7.2.boot0.log
Oct 29 00:13:45 ultimakersystem-ccbdd3005b4c python3[1166]: 2020-10-29 00:13:45,662 INFO probingController Found
peak @ 8.623
Oct 29 00:13:59 ultimakersystem-ccbdd3005b4c python3[1166]: 2020-10-29 00:13:59,315 INFO probingController Found peak @ 7.173
geo@geo-Wild-Dog-Pro:~/ultimaker/logs oct28 2020$ grep Preliminary ultimakersystem-ccbdd3005b4c.5.7.2.boot0.log
Oct 29 00:13:59 ultimakersystem-ccbdd3005b4c python3[1166]: 2020-10-29 00:13:59,507 INFO probeResultValidationStep Preliminary z offset for second nozzle: 1.45
Actually first search for "height difference between nozzles is too large" as that is the message that occurs right when the error happens. Write down the date and time and *then* search for "peak" and "Preliminary" and look to see if even the passing tests *almost* fail.
Recommended Posts
glx 27
I'm can't help with what exactly that value is, but I got 2.6 on my S5 (I honestly didn't run this anytime before now, so I don't have a clue).
Nearly always when I get that error it is wisps or small debris inside the printhead an/or a dirty front fan/build plate. Once I had a damaged wire in the back of the printhead (the red/white one).
Do you maybe have any electrical devices nearby thay may cause EMI problems?
Link to post
Share on other sites
SanneM 12
We are still working on fine tuning at what numeric value the sensor should be considered broken, so unfortunately the message is really vague at the moment
Why we did choose to show this message on the display already, is so that you can share the number with support
I expect that the message will have more clear feedback in 2 firmware updates from now, until then if you are experiencing issues with bed measurement please contact support and share this number with them
That said I can say that 2.6 is really good, and 44 or 35 definitely is reason to contact support if you have issues with bed measurement, as your print head circuit board might need replacement
Link to post
Share on other sites
gr5 2,239
There are so many things that can give you the same error message. First and foremost, watch the leveling when it does the first two levelings - left and right core at the same spot. It's supposed to slowly move the bed until it touches the nozzle. One failure mode is that it stops before the bed touches the nozzle. Another is that it touches the nozzle and keeps going much too long afterwards.
Another failure mode is that the lift switch isn't raising and lowering the right core. You might have to repair the print head or re run the lift switch calibration procedure (which takes less than a minute).
There may be electronic noise (obviously - discussed above).
There may be spring issues with the bed or a print core (basically you want the bed springs weaker than the nozzle springs but the bed springs can be somewhat stiffer and it still works fine because the entire cantilevering bends a bit also). And of course there can be something on the nozzle tip (usually not a problem as the leveling is done while the nozzle is hot).
Oh - and you can have two nozzles that are not the same "height" (where height is from the nozzle tip to the shiny steel angled part that sits in the metal "fork" of the print head). Tolerance here is 0.7mm. And you can have nozzles that are not seating properly into said fork.
Link to post
Share on other sites
dmanthei 1
Wow, thank you for all the helpful feedback everyone!
glx: The area where we keep the printer is free of other devices for at least a 4 meter perimeter. At the edge of that perimeter is a small office air handling unit on a different electrical circuit. Beyond that, it's 4 offices with laptops and desktop LCD monitors which likely share an electrical circuit, but these shouldn't be noisy devices. Would trying a surge protector or UPS help or hurt the situation?
SanneM: Thank you very much for providing your sensor value. I agree that's a significant difference and I assume this is a lower-is-better situation. I will contact support at this point.
gr5: All good points and I tried to consider each. I did a fresh calibration of the lift switch and that seems fine, though it also seemed fine before I did that calibration. I wondered about spring issues so I checked during another manual-levelling to ensure there was sufficient pressure in the build plate springs. They seem good. I have a spare (but used) AA 0.4 nozzle on-hand so I changed that out to see if it helped with respect to your nozzle height comment. Unfortunately it did not.
I did just grab the log files in preparation for contacting support. Now, I have no experience or knowledge of how to read a log file, but the file created during the capacitive sensor test was this:
Now again, I don't know what I'm looking at, but as an engineer I suspect the repeated "capdac 32767" lines mean a capacitive digital to analog converter input is reading 32767 which is the maximum value of a 16-bit signed value. That seems like a problem like an electrical short or accumulated static charge or something, but again I don't know...it just looks wrong to me. So hopefully support can help me out from here.
Thanks again everyone! You helped me determine my problem is not some silly operator error and actually warrants reaching out to support staff.
Link to post
Share on other sites