Mesh levelling stopping about halfway through G29

My BLTouch seems to be working, homes fine, but it can't complete a G29 mesh. It stops with the warning g29 Error: Probe already triggered before probing move started. If I immediately run G29 again, it starts fine but stops again usually at the same point about halfway through the mesh.. Any ideas?
billyd
billyd•344d ago
Increase horizontal_move_z: by 1 or 2mm. For example in your printer.cfg add:
horizontal_move_z: 6
horizontal_move_z: 6
To the user overrides section
sunny-green
sunny-green•344d ago
I... don't understand what that means sorry..
billyd
billyd•344d ago
Do you have a vcore3? With ratosv2
sunny-green
sunny-green•344d ago
VCore 3 with Duet 3..
billyd
billyd•344d ago
Ok well edit the printer.cfg file, like you did when you first set up the printer. Scroll down the file until you reach the user overrides section. Check to see if there is already a section under that that has [bed_mesh]. If it's not there add it. And under [bed_mesh] add the line: horizontal_move_z: 6 (like I show above) and save the printer.cfg file, and restart the firmware. That should fix your problem.
blacksmithforlife
blacksmithforlife•344d ago
Duet is RRF not klipper - so this isn't going to work
billyd
billyd•344d ago
Sorry! In that case you need to alter the z height of the hotend during the bed mesh operation so that it is higher than it is currently. (During travel between mesh points)
sunny-green
sunny-green•344d ago
The thing is, it probes fine up to a certain number of points, so I can't see how changing this will help..
billyd
billyd•344d ago
Perhaps that point in the bed is high enough to not allow the bed probe to trigger properly.
sunny-green
sunny-green•344d ago
Nope, it fails at different points randomly, some earlier some later.. I am currently trying running G29 S0.. Can you tell me what the S component is?
billyd
billyd•344d ago
Sorry that's all I've got. Not familiar with RRF or the Duet so I should have kept quiet lol. Hopefully someone will help you with a similar setup
sunny-green
sunny-green•344d ago
No worries, thanks for trying..
billyd
billyd•344d ago
G29 Mesh Bed Compensation (RepRapFirmware) RepRapFirmware: S0 (default if no S parameter) Probe the bed, save the height map in a file on the SD card, and activate the height map. The default folder for the height map file is /sys and the default file name is heightmap.csv. S1 Load the height map from file and activate bed compensation. The default folder and filename as for S0. S2 Clear the currently-loaded bed height map To define the grid, see M557. In RepRapFirmware 3.2 and later, G29 runs macro file mesh.g if it exists, otherwise it behaves like G29 S0. The mesh.g file can perform other actions (e.g. homing or tool selection) and then use G29 S0 to do the probing.
blacksmithforlife
blacksmithforlife•344d ago
maybe @oliof can help?
sunny-green
sunny-green•344d ago
He's on it,I believe..
sunny-green
sunny-green•344d ago
@billyd60 in RRF its all in G31 and M558
; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"io7.in" H6 F100 T12000 ; set Z probe type to bltouch and the dive height + speeds

G31 P500 X-32 Y-20 Z2.697 ; set Z probe trigger value, offset and trigger height
M557 X5:440 Y5:450 P7 ; define mesh grid
; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"io7.in" H6 F100 T12000 ; set Z probe type to bltouch and the dive height + speeds

G31 P500 X-32 Y-20 Z2.697 ; set Z probe trigger value, offset and trigger height
M557 X5:440 Y5:450 P7 ; define mesh grid
this looks, by and large correct, 2.7mm trigger height, 6mm dive height.
sunny-green
sunny-green•344d ago
I'm beginning to suspect faulty probe or wiring..
sunny-green
sunny-green•344d ago
@cairn4177 looking at Troubleshooting BLTouch (https://docs.duet3d.com/User_manual/Troubleshooting/BLTouch_troubleshooting) documentation, you may want to add 0.2sec settle time to the probe definition, so add R0.2 to your probe definition so it looks like M558 P9 C"io7.in" H6 F100 T12000 R0.2 (also see my comment about M501 in the #rrf-duet channel)
sunny-green
sunny-green•344d ago
Added the R0.2 but still no dice. Is it worth trying r0.4 ?
sunny-green
sunny-green•344d ago
only if your motion system really does not settle quickly. dive speed is already slow (F100) so I don't think if 0.2 helps 0.4 will anything in config-override.g?
sunny-green
sunny-green•344d ago
Nope..
sunny-green
sunny-green•344d ago
okay then I would point at wiring/loom since it seems to fail at the same point, it may be something is dragging on the wire.
sunny-green
sunny-green•344d ago
Yeah, going to take a look there.. Thanks! 🙂 Incidentally the Z Probe status in the Duet browser blinks pink 1000 very briefly on a few points before failing and remaining pink 1000. If this indicates anything in particular? OK, so I had an intermittent open circuit on the white wire to the BLTouch, and eliminating that solved the G29 failure, but... if it ain't one thing it's another, and now my Y axis endstop doesn't light up when tested, and when I home all or home Y seperately Y thinks it's already homed. I can bluff the machine into running by having the Y axis at zero at power-up, and accepting the false Y-home result, but this is obviously not ideal. What's the best way to test an endstop that doesn't light up?
sunny-green
sunny-green•344d ago
that also indicates bad wiring as they are normally closed
sunny-green
sunny-green•344d ago
By 'open' I just meant I removed the wiring ribbon and tested each wire. The white wire had a break somewhere, and when I replaced it the G29 fault wasn't repeated.
sunny-green
sunny-green•344d ago
yes I was talking about the endstop now you need to make sure the wiring is right since Duet changed the endstop pin order so you dont burn your input when you plug in the endstop flipped
sunny-green
sunny-green•344d ago
But this has worked fine for a long time. Nothing has changed.. Well, the thng that changed is the Y endstop light doesn't blink when you test it..
sunny-green
sunny-green•344d ago
that indicates some wiring issue or, rarely, a broken switch for a quick test you could unmount the y endstop, connect it to X endstop wiring, and see if it works there. If yes, its the wiring. if no, its the endstop
sunny-green
sunny-green•344d ago
Can I swap the X and Y wsitches to test?
sunny-green
sunny-green•344d ago
see above yes
sunny-green
sunny-green•344d ago
😀
sunny-green
sunny-green•344d ago
alright I need to grab 3 hours of sleep before flying back home
sunny-green
sunny-green•343d ago
Thanks friend! (disassembled and reassembled, works now. The dreaded 'intermittent fault'.. Today's Hassle: Heater 1 (hotend) not heating. Error: temperature rising too slowly.. must be wiring I guess..
sunny-green
sunny-green•340d ago
no you need to pid tune again I guess unless its not rising at all then its either the thermistor or heater
Want results from more Discord servers?
Add your server
More Posts
Issues w. extruder stepper (LDO-36STH20-1004AHG from lgx lite) since upgrade from RO2.0.0 to v2.0.1my stepper doesn´t work since the upgrade and reflashing the sd card. The stepper doesn´t react, no Strange Bed Level Test ResultHow can I fix this?belt shiftingOk..I have a odd issue that doesn't make any sense. I did a print almost 2 weeks ago and shut the prdouble peaks on YHi, did someone have such graph? Did you managed to fix it? Any ideas why is it so?Part Cooling Fan dauerhaft aktivSeit neuestem ist bei meinem Minion der Lüfter für die Bauteil Kühlung dauerhaft aktiv. Ich konnte lCan't equalize belt tensionI have such graph currently, if I try to tighten lower belt, my gantry moves out of square(when I moBed tilted after G34Hello everybody, Here is another mesh/homing problem. Maybe a really simple thing, but I don't get Extruder Heater not Heating at Expected RateI've gotten this error message 3 times in a row and I've noticed the temperature on the extruder seefan.cfg benötigtWie muss denn eine Fan.cfg aussehen, wenn ich bei Überschreiten einer vorgegeben Temperatur vom Mainprinting round tubesHaving trouble printing round stuff this is PETG and currently running 240c .15mm layer height. 2mm Extruder spinnt....Rest kommt. Strom braucht das LaptopStop services automaticallyHi guys, after updating to RatOS 2.0 my memory/CPU load (unfortunately only using a RPI Zero 2 W) haIs my rail eating itself?Just got around to lubricating my rails, left hand rail for the front and back axis (can't remember Belt grabber/adjuster broke. Replaced the adjuster but I have a new noise now.So while printing, I noticed a layer shift so I stopped printing and inspected. It turns out the bel4028 Lüfter an SKR2ich habe einen Artic Lüfter den Übergangsweise am Octopus betrieben habe übrig. Diesen wollte ich jUnregelmässige erste SchichtGuten morgen. Im internationalen Bereich hat mir niemand geantwortet, darum probiere ich es hier aucUnable to update RatOs repo after branch changeHello guys, I've tried upgrading my probe to unklicky and followed a blogpost which said to switch tOdd resonance shape on VC300What to do here? There's resonating sound from EVA, I've checked every screw and part, but nothing. Inconsistent first layerI have very weird behaviour on my first layer, which I can't seem to get right. What I have tried: Probleme bei der zweiten Schicht!Hallo habe einen Orbiter 2.0 verbaut und alles gemacht ESteps , PID Tuning usw und dann Probedrucke