#UBL results not 0

1 messages · Page 1 of 1 (latest)

wicked rapids
#

If I run UBL on my ender 3 pro and output results to pronterface, I get a mesh that has +0.15 and -0.10 etc. but for some reason my tronxy x5sa gives me only values at +2.95-3.15 kind of thing. anyone know why?

As I'm having issues with the first layer sticking, which I think is because of this weird problem. It used to give me the expected results before, I don't know what's changed since then. Thinking it's to do with z offset or something 🤔

Also both printers have inductive probes which should be mounted roughly 1.2mm above the nozzle. yet I need to set z nozzle offset to like -6.5mm on the tronxy to stop it from printing in the air, and the ender 3 has basically 0 on z offset..? in the firmware, nozzle_to_probe is set to 1 on the ender 3 pro and -1.2 on the tronxy

fading timberBOT
#
AI Help

It sounds like there may be a discrepancy in the settings or calibration between your two printers causing the differences in the mesh output from UBL. Since you suspect the first layer adhesion issues might be related to this, here are a few steps to troubleshoot:

  1. Check the bed leveling process on both printers to ensure they are calibrated correctly.
  2. Verify that the Z offset values in the firmware for both printers are correctly set according to the probe distance from the nozzle.
  3. Make sure the firmware settings for the probe offset are accurately entered to prevent printing issues.
  4. Validate the height at which the inductive probe is actually triggering; it's possible that the physical setup might be slightly different on each printer.
  5. Double-check the G-code generated by your slicer to ensure that the nozzle height is properly adjusted based on the offset values.

If you're still experiencing issues, consider reaching out to the manufacturer or an online community...

WARNING: This response is AI generated and may contain errors.
wicked rapids
#

example of what I should be getting on my tronxy, which is what the ender gets

image.png
#

and then this is what I get on the tronxy

image.png
#

(it comes out the same way with the spaces and that, it's just been condensed so I can use a bed mesh visualiser)