Weird behaviour after first print
-
@martinnyhc is it a normally open or a normally-closed switch? A possible explanation is that you are using a normally open switch and you have run the wires close to the extruder motor cable, with no shielding between the two, so that the switch wire is picking up interference from the extruder motor cable.
Normally closed endstop switches and Z probes are much less susceptible to capacitive interference pickup. So if the switch has both NO and NC contacts, I suggest you change to using the NC contacts. If it has only NO contacts, then you can either shield the switch wire, or use M18 to disable the extruder motor before probing.
-
Whew....that had never come to my mind. The switch has NO and NC contacts. Before changing this (I have to put off the complete tool head) I'll try with disabling the extruder motor when using the probe.
Thanks!
-
Oh...and yes, wires are running close. The switch is connected to the tool board io0 beside the stepper port.
-
@martinnyhc said in Weird behaviour after first print:
Oh...and yes, wires are running close. The switch is connected to the tool board io0 beside the stepper port.
I would not normally expect it to be a problem when using a tool board, assuming the tool board is mounted on the print head, because the wires are so much shorter. But try the M18 test.
-
Just tried with M18 E0 but that doesn't change anything. Beside of that I observed the following after doing an emergency stop and moving the tool head up to deattach the probe:
https://drive.google.com/file/d/1xjToNHtGSHgUNfDPdsizFRtVbSMX8VJ_/view?usp=sharing
Very strange.
-
Just got "Error: Probe already triggered before probing move started" directly after switching off/on the printer. That was the first time.
-
@martinnyhc
Could get a bit tricky with a detached probe...then the cuircit is open.... -
I know t his is wokring for many many guys. And it already worked for me too
-
Hold on. Perhaps I've found the problem. DWC showed status 1000 when the probe is disconnected and 0 if connected. That should be the other way around. Changed C"^121.io0.in" to C"!^121.io0.in".
-
Since the change it goes to the probe points but not down to probe the bed at all.
I'm at my wits end.
-
That was bullsh****. All was properly installed. So I have no more ideas.
-
This is a detachable probe that must be docked, correct?
-
Yes, correct.
-
Maybe I found the problem. Just upgraded to 3.4-b2 to test input shaping and recognized that the accelerometer on the toolboard was not recognized. M122 B121 reported that no accelerometer could be found. Took the tool board from my other printer and it worked. Also currently it looks like the probe problems are gone. To be sure I'll test this a little bit more today.
-
Problem is still there
There is a new additional error message after the upgrade.
**Error: G32 has thrown an exception: [NullReferenceException] Object reference not set to an instance of an object.** Error: Probe already triggered at start of probing move -
And with G29 I now get
-
@martinnyhc There must be an exception or cancelled code somewhere in your bed.g which is why you get that exception. I've got a fix ready that will be included in 3.4-b3. Also you seem to call G29 without S parameter in mesh.g, which will invoke mesh.g over and over again until you get a stack overflow.
-
Yep, already fixed that. I need to do some further testing regarding the probe. In the meantime if did a fresh SBC install.
-
OK, spent the day with doing a clean SBC install (RRF 3.3.0) and rewriting all config files and macros. The main issue I have still persists. Gantry and bed leveling works like charm if it is the first print. As soon as a print finished or where cancelled and I start a new print it fails.
Fails means for example: The first thing of course is homing. Second thing is gantry leveling.
; bed.g ; called to perform automatic bed compensation via G32 if !move.axes[0].homed && !move.axes[1].homed && !move.axes[2].homed G28 ; home M558 K0 H10 F400 ; set trigger height M561 ; clear any bed transform M98 P"0:/macros/sys/undock_klicky_probe.g" ; undock clicky probe while iterations <=1 ; first pass G30 P0 X20 Y25 Z-99999 F9000 ; probe Z left front G30 P1 X20 Y320 Z-99999 F9000 ; probe Z left rear G30 P2 X330 Y320 Z-99999 F9000 ; probe Z right rear G30 P3 X330 Y25 Z-99999 S4 F9000 ; probe Z right front G1 H2 Z12 F2600 ; raise head M400 ; finish move, clear buffer M558 K0 H2.5 F200 ; trigger height to 2.5mm after first run while move.calibration.initial.deviation >= 0.003 ; Perform additional leveling if previous deviation was over 0.03mm. G30 P0 X20 Y25 Z-99999 F9000 ; probe Z left front G30 P1 X20 Y320 Z-99999 F9000 ; probe Z left rear G30 P2 X330 Y320 Z-99999 F9000 ; probe Z right rear G30 P3 X330 Y25 Z-99999 S4 F9000 ; probe Z right front G1 H2 Z12 F2600 ; raise head M400 ; finish move, clear buffer echo "Gantry deviation of " ^ move.calibration.initial.deviation ^ "mm obtained." G1 Z12 ; Raise nozzle M98 P"0:/macros/sys/dock_klicky_probe.g" ; dock clicky probe G28 ; Homing again for accurate Z offsetIt probes the four points for the first time, changes the probing height and probes for the second time. Suddenly it is just going to the probe points but don't lower Z to probe the bed.
Here's an archive of my complete config. I've spent so many days with this problem now and did everything which came to my mind, I'm definitely stuck and don't now what to do.
Help please!
Thanks in advance! -
Are there example configs from other voron users that use this probe?
Have you tested in standalone mode as a control?
