Orion triggers during tuning but not when Z homing
-
post your homeall and homez.
also check the status manually with
https://duet3d.dozuki.com/Wiki/Gcode#Section_M119_Get_Endstop_Status -
; homeall.g
; called to home all axes
;
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-305 Y-305 F6000 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-305 F6000 ; home X axis
G1 S1 Y-305 F6000 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-10 F360 ; move slowly to X axis endstop once more (second pass)
G1 S1 Y-10 F360 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X140 Y135 F6000 ; move quickly to centre of bed
G30 ; home z; homez.g
; called to home the Z axis
;
G91 ; relative positioning
G1 Z10 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
G1 X140 Y135 F6000 ; move quickly to centre of bed
G30 ; home z -
@Foden said in Orion triggers during tuning but not when Z homing:
please post the M119 without manually triggering it and one with.
-
M119 reports the same leaving the orion alone and when manually man-handling it to get it to trigger - which is odd as the lights do change
11:53:34 AMEndstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped
11:53:14 AMEndstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stoppedAlso when tuning the red light is full on the blue is off. Once it starts to home the red light is only about 30-40% and the blue stays off all the time
-
Also, if relevant
Firmware Version: 2.03 (2019-06-13b2)
WiFi Server Version: 1.22
Web Interface Version: 1.22.6 -
please post a picture of the wiring on the duet and the piezo.
-
@Foden said in Orion triggers during tuning but not when Z homing:
Also when tuning the red light is full on the blue is off. Once it starts to home the red light is only about 30-40% and the blue stays off all the time
That's because you have enough vibration when homing to cause the sensor to oscillate right on the edge of the trigger value. It's a lot easier for human eyes to detect red than blue so it's a lot harder to see the blue LED flashing. Try tweaking the adjustment pot just a "touch" and see if you can dial it in.
Also how is the Orion mounted? If you're using a custom mount it's possible that the mount it too tight or that the part that holds the hotend is too rigid.
-
@Veti Will grab photos but will be later on
-
@gtj0 No, there's a very obvious difference in the light and the blue is completely out. I can see the blue even when its only barely flickering. Will try to grab photos of the difference with the red led too
Appreciate the assist, will be back later with photos
-
Do you have it connected to the Z Probe input and not the Z End Stop input? It won't work as a probe on the end stop input.
-
I haved similar issue.... Was the heat skin fan, that vibrantes and cause false poaitives
Try with fans powered off
-
@peirof I saw that as well, just after I fitted my Mosquito hot end. The tiny little 25mm fan they use was not balanced in any way and caused so much vibration that I could see the trigger LED flickering all the time. Of course, this lead to false triggering when probing and made it impossible to produce a levelling map.
I cured the vibration by printed an adapter and replacing the 25mm fan with a 30mm fan from my E3D V6.
However, if vibration was causing the OP's problem, he would be seeing error messages about the probe triggering prematurely. It won't stop the probe from triggering.
-
-
First image is printer idle or during tuning, second is during homing - see difference in the red light intensity. Blue light decided to appear during second photo but does not trigger
-
@peirof Thanks, it's not fan vibration on this one. Likely to be PEBCAK though
-
@Foden YIKES - way bigger than i expected
I setup the BLTouch originally and then moved to the Precision PCB then the Orion. Never got the Piezo to be reliable so switched back to the BLTouch. The Orion setup was done so long ago it's probably a PEBCAK issue - just can't see it until it's pointed out in public i guess
I like the RJ45 easy swap-out setup - as it means i can usually carry on if i break something or it wears out. Makes for easier testing/modding too
-
What are the blue and blue/white wires which are connected to the left two pins of the Z-probe header?
From your notes, the Orion does not seem to be connected to the Z-probe header. Therefore, it won't work.
-
Yeah it does look like it's not connected to anything at all. Hmmm. Somehow I switched into a mobile layout. Gimme a sec.
That was weird.
Anyway, the green signal wire from the sensor should be on terminal 5 on the RJ45 break out board (white/blue) and the black ground wire to terminal 4 (blue/white). The red wire (3.3v) on terminal 3 will be the white/green wire but I can't see where that's connected on the Duet.
Anyway for reference, those breakout boards go like this...
1 white/orange 2 orange/white 3 white/green 4 blue/white | Yes, these are reversed. 5 white/blue | 6 green/white 7 white/brown 8 brown/white -
Doc is a revised version, showing BLTouch and Piezo
Cable colours depend on the cabling standard used B or A - B being the preferred
For the Piezo the blue & blue/white wires aren't used. They are only used when i have a BLTouch in play
On the 50pin expansion pin 1 is voltage and pin 2 is ground. gtj0 has found the issue, the signal wire is in the wrong place - voltage and ground should be OK though
Also fighting a cold and some hideous gastro thing which makes this all the more fun!
Thanks for all the help - will take another look
Update - correct - i'm pushing "5v to it rather than +3.3 so need to change that too
-
@Foden Giving up for today and going to bed
From the spec the Orion can cope with 3.3 - 5v so guess it could stay on current 5v pin.
Will play more tomorrow, i hope
Thanks again
