V Minion attempting first print
Newly assembled V Minion with the default RatOS/Klipper setup. Updated RatOS and associated software to latest levels. SKR 2 flashed without issue, raspberry pi boots and loads Klipper/mainsail - no issues. MCU communication is fine. I've walked through all the basic calibration and axis motion checks, fans, everything appears good:
a. probe calibration completes and is repeatable using the PROBE command (completed the manual paper test portion as well) - z-offset sets to .240 automagically by the macro in printer.cfg
b. bed mesh calibration completes without issues
c. homing commands runs through all three axis without any bed collisions, etc.
d. PID temp calibrations for the bed and hot-end all complete without issue. temp control is great/stable on both elements.
e. all 3 end-stops (two switches and the probe) appear to be working as designed.
Slicer upload of a simple calibration cube works, klipper starts the print, runs through the initial bed/hotend pre-heats, gets to final temperature and then ... pushes the nozzle into the bed (at the front of the print surface) and starts to scrape along the + x-axis, hangs up and then I mash the emergency stop. After a firmware reboot, I can HOME just fine, etc. no bed collisions and the nozzle appears to be holding my PROBE/paper calibration settings just fine, etc.
I've tried manually setting a [probe]\z-offset of 1.240, -1.240, 1.724, etc. and it doesn't appear to be making any changes to the nozzle drag after a save/restart.
Any thoughts on what I'm missing here?
12 Replies
passive-yellow•2y ago
A Probe z offset can never be negative, also your numbers are very small, with an inductive Probe that sits 1mm above the Nozzle height you usually have a Offset of 3-5mm
How exactly are doing the paper test?
And how high is your Probe compared to the nozzle?
I've tried manually setting a [probe]\z-offset of 1.240, -1.240, 1.724, etc. and it doesn't appear to be making any changes to the nozzle drag after a save/restart.You prolly have a z-offset set in the klipper config section (it's saved by clicking the save button in the Z offset panel). Use the z-offset buttons to adjust your z-offset with a piece of paper so that z=0 touches the paper. Then hit save. Try again.
z-offset sets to .240 automagically by the macro in printer.cfgThere is no such macro But your slicer filament gcode (if you're using the default RR profiles) prolly has a line that sets the runtime gcode z offset to 0, so if that's what you've used so far, and haven't correctly saved it, then it'll disappear as soon as you start a print. 8mm inductive probes have a 2mm trigger distance, so if it's 1mm above the nozzle 0.8-1.2 i where you'd be at. 3-5 is bltouch territory a 12mm inductive probe with it's 4mm trigger distance is around 3.
passive-yellow•2y ago
yeah you are right of course, i have a 1,585mm Z-Offset in my Minion with SuperPinda
Yep that seems about right. The superpinda's also have a bit more trigger distance than the generic 8mm inductive probes (plose those fluctuate like crazy with heat).
adverse-sapphire•2y ago
ok guys - thanks for the responses and suggestions. I'll work on it a bit today and see if I can re-adjust it properly with the z-offset panel.
the probe is clone superpinda v2 from FYSETC, it's got a shorter barrel than the one that shipped with the kit.
If I can't get it going with the current suggestions, I'll post actual distances, etc. and some photos to make sure I have it installed correctly.
If I can't get it going with the current suggestions, I'll post actual distances, etc. and some photos to make sure I have it installed correctly.
There’s no “superpinda v2”. There’s a pinda v2 and it’s terrible 😅
The superpinda (and derivatives) are all made by Pepperl&Fuchs. There are no actual clones that work afaik.
adverse-sapphire•2y ago
Ok, I did a full RatOS reset on the pi, started from scratch. ran through the x/y-axis probe offset, z-axis probe calibration, etc.
Printer continues to home just fine and the PROBE command stops as expected right above the print bed, etc. Bed mesh calibration didn't have any issues either.
z-offset using the probe_calibration ended up at a -0.500, saved into the printer.cfg file by the save_config command following the calibration. Not sure why the system is saving it as a neg value if it can never be a negative value. Obviously I'm still missing something here in regards to z-offset with Klipper.
the printer is still dragging the nozzle along the x-axis at the start of a calibration cube print from SuperSlicer.
Uploaded screen shots of the print head for reference, and shots from the printer.cfg file and results of the probe calibration.
appreciate the help with what's most likely a problem between my keyboard and chair 🙂
adverse-sapphire•2y ago
Not sure why the system is saving it as a neg value if it can never be a negative value.It isn't. -0.500 is saved as 0.5. This is the difference between runtime gcode offset (applied to each gcode move) and probe z_offset. Just saw your last screenshot. That is most definitely wrong.. Not sure how that's possible. It should be 0.5. But -0.5 should put it further away from the bed, not closer. Ah i see from your TEST_Z report that it's actually going further up instead of down, that's why you're getting a negative z_offset. Something is definitely wrong here. Please check that your Z leadscrew/motor shaft coupler is properly tightened. Something must be slipping. Is your Z motor skipping steps?
adverse-sapphire•2y ago
Ok, took apart the z-axis spider coupler and put it all back together. checked for parallel, etc. - I did notice a small bit of the spool holder corner might have been rubbing on the rail carriage as it raised up to the same level as the spool holder so I moved it off to a different axis of the main pillar. z-axis rail is completely clear of any potential interference.
re-ran the probe-calibration, etc. and got a positive value.
after watching earlier video of the nozzle drag on my phone, I noticed that the "primeblob" portion of the print was pushing the probe out over the edge of the bed - I'm thinking this might be the cause of the nozzle getting driven down into the bed and scrapping the x-axis. Not sure why the "primeblob" is trying to push out past the bed boundary, etc. Are there any code adjustments to bring it back in towards the center of the bed? With that observation, I disabled the "primeblob" command in the printer.cfg file and on the next print, the print head moved perfectly into position and started layer printing. Now I have a second issue (lol). The LGX Lite extruder is not pushing filament out during the actual print cycle. It pushes filament out just fine if I heat up the hot end and a. manually rotate the gear to push filament out b. use the klipper extruder interface to test 50/25/10/5 mm filament "strings". works perfectly as far as I can tell - just not during layer printing. I verified that there's an air gap between the nozzle and the bed during the first layer so I know it's not rubbing the PEI bed, etc. During the layer print, the extruder gears are just "tweaking" clockwise/counterclockwise and not actually advancing filament. Any thoughts on this next issue with the extruder?
after watching earlier video of the nozzle drag on my phone, I noticed that the "primeblob" portion of the print was pushing the probe out over the edge of the bed - I'm thinking this might be the cause of the nozzle getting driven down into the bed and scrapping the x-axis. Not sure why the "primeblob" is trying to push out past the bed boundary, etc. Are there any code adjustments to bring it back in towards the center of the bed? With that observation, I disabled the "primeblob" command in the printer.cfg file and on the next print, the print head moved perfectly into position and started layer printing. Now I have a second issue (lol). The LGX Lite extruder is not pushing filament out during the actual print cycle. It pushes filament out just fine if I heat up the hot end and a. manually rotate the gear to push filament out b. use the klipper extruder interface to test 50/25/10/5 mm filament "strings". works perfectly as far as I can tell - just not during layer printing. I verified that there's an air gap between the nozzle and the bed during the first layer so I know it's not rubbing the PEI bed, etc. During the layer print, the extruder gears are just "tweaking" clockwise/counterclockwise and not actually advancing filament. Any thoughts on this next issue with the extruder?
passive-yellow•2y ago
It is normal for the Probe to be in the Air for the Primeblob, does not matter. At that Point Homing and the Bed Mesh has been done so the Probe is not used anymore.
For your second problem please check that the RatOS Macro in your printer.cfg and the Printer Settings tab in the Slicer are on the Value regarding relative Extrusion.
adverse-sapphire•2y ago
Ok, thanks everybody for the help!
Extrusion issue was fixed with the adjustment to the "variable_relative_extrusion" value - default config was set to false, when I flipped it to true (to match the setting in superslicer), the extruder started working during the print cycle!
Extrusion issue was fixed with the adjustment to the "variable_relative_extrusion" value - default config was set to false, when I flipped it to true (to match the setting in superslicer), the extruder started working during the print cycle!