Solved inductive end stop intermittently triggered
-
Hi,
I'm new to the world of rep rap and having some difficulty. I have a chinese 1325 router with rotary axis thats been running on mach 3 for years and I decided it was time to upgrade. I got a duet 3 xd and rpi4 to convert this machine. I have the duet up and running and accessible through the dwc which is really cool. My first issue is with endstops,
it has omron TL-Q5MC1-Z on all axis
and wired them the same way they were wired to the old controller 24v and 0v coming directly from the power supply and the 5v signal going to input pins. When I test with a meter they are showing 5v on the input wire and when tripped the led on the sensor comes on and shows 0v on the wire, Great right.........but in the dwc i have the endstop monitor add on installed and they are all triggering on and off randomly. Here's my config file.; Configuration file for RepRapFirmware on Duet 3 Main Board 6XD
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Sun Jul 07 2024 12:19:31 GMT-0500 (Central Daylight Time); General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"duet 3" ; set hostname
M911 S19.8 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss; Network
M551 P"monkeys" ; set UI password; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout; External Drivers
M569 P0.0 S0 R0 T5:5:10:0 ; driver 0.0 goes forwards and requires an active-low enable signal (Z axis) ;;;*** changed from s1 to s0
M569 P0.1 S1 R0 T5:5:10:0 ; driver 0.1 goes forwards and requires an active-low enable signal (X axis)
M569 P0.2 S1 R0 T5:5:10:0 ; driver 0.2 goes forwards and requires an active-low enable signal (Y axis)
M569 P0.3 S1 R0 T5:5:10:0 ; driver 0.3 goes forwards and requires an active-low enable signal (Y axis)
M569 P0.4 S1 R0 T5:5:10:0 ; driver 0.4 goes forwards and requires an active-low enable signal (A axis); Axes
M584 X0.1 Y0.2:0.3 Z0.0 A0.4 ; set axis mapping
M350 X16 Y16 Z16 A16 I0 ; configure microstepping without interpolation
M92 X104.3160419 Y104.3160419 Z400.1476923 A320 ; configure steps per mm
M208 X0:1900 Y0:2570 Z0:340 A0:99999 ; set minimum and maximum axis limits
M566 X1200 Y1200 Z1200 A1200 ; set maximum instantaneous speed changes (mm/min)
M203 X1800000 Y1800000 Z360000 A240000 ; set maximum speeds (mm/min)
M201 X600 Y600 Z300 A200 ; set accelerations (mm/s^2); Kinematics
M669 K0 ; configure Cartesian kinematics; Probes
M558 K0 P8 C"io1.in" H5 F120 T6000 ; configure unfiltered digital probe via slot #0
G31 P500 X0 Y0 Z0.7 ; set Z probe trigger value, offset and trigger height; Endstops
M574 X1 P"!io3.in" S1 ; configure X axis endstop
M574 Y1 P"!io4.in" S1 ; configure Y axis endstop
M574 Z1 P"!io5.in" S1 ; configure Z axis endstop
M574 A1 P"!io2.in" S1 ; configure A axis endstop; Spindles
M950 R3 C"vfd" Q3000 L60:20000 ; configure spindle #3; Lasers
;M452 C"io4.out" F500 R255 S0 ; configure Laser port; Tools
M563 p0 r3 ; create tool #0
M568 P0 ; set initial tool #0 active and standby temperatures to 0C; Miscellaneous
M453 ; select CNC mode
T0 ; select first toolthanks in advance for any insight you guys might have.
i have issues with the fulling vfd too but i assume that should go in another post
-
@dwak in DWC 3.5.2 you don't need the end stop monitor plugin anymore as the functionality is built-in. For the floating end stop signal, I'd try enabling the input pull-up by pretending a
^before the!ioX.inin your endstop definition. -
thanks, I had tried that previously but just put it back in and get the same results
; Endstops
M574 X1 P"^!io3.in" S1 ; configure X axis endstop
M574 Y1 P"^!io4.in" S1 ; configure Y axis endstop
M574 Z1 P"^!io5.in" S1 ; configure Z axis endstop
M574 A1 P"^!io2.in" S1 ; configure A axis endstopRecording 2024-07-08 071616.mp4
as for the native endstop monitor, I could not find it, maybe I just wasn't looking in the right place, or maybe it has something to do with being configured for cnc? Dunno, but a native monitor of all IO pins like that would be hugely beneficial in troubleshooting.
thanks for your time!
-
I don't think I mentioned that the sensors themselves have an led indicator that lights when they are tripped and that the leds are not indicating being tripped but the dwc does if that makes sense. If I trip them manually they dwc shows a steady indication that they are tripped but when they are not activated the dwc shows random tripping of the sensors. I hope I'm explaining that well. The above video demonstrates what the dwc is indicating and when I go to home all the machine doesn't go to the endstops before thinking its homed.
-
@dwak in DWC 3.5.2 the background of the axis name turns green when the end stop is triggered.
<>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>
-
Is it possible your wiring is picking up interference?
-
not sure which screen you are referring to but I have clicked through all the tabs and am not seeing that on any of the pages even with the A axis manually triggered. I am content with the add on for now as long as its not causing a problem.
-
@Phaedrux
that sounds like a logical possibility, the cables for the inductive sensors are shielded, but there is a short pigtail connecting them to 24v and gnd that is not shielded, I'll try to find a shielded cable to replace that pigtail or a ferrite and give it another go. -
@dwak said in inductive end stop intermittently triggered:
not sure which screen you are referring to but I have clicked through all the tabs and am not seeing that on any of the pages even with the A axis manually triggered. I am content with the add on for now as long as its not causing a problem.
It's the main dashboard page where the X Y Z position is shown. When an endstop triggers the background of the X Y Z changes color.
-
does not change color for me
-
Can you check your firmware and DWC versions?
-
Electronics
Diagnostics
Product Short Name Version
Duet 3 MB6XD MB6XD 3.5.2
Duet Software Framework DSF 3.5.2
Duet Web Control DWC 3.5.2 -
@dwak
added a shielded cable to power the endstops, no change
changed power supply out just as a poke in the dark, no change -
@dwak
I noticed in the video that the z probe indicator alternates between 1000 and 0, not sure what exactly this number indicates but I assume that this is indicitive of the same problemRecording 2024-07-08 071616.mp4 -
update:
first the history.......when i started to get this duet set up I purchased an "identical" inductive sensor so i could mock up my machine before I committed to the change over. in the mock up the sensor worked perfectly so i proceeded with the install.I just disconnected my z end stop and connected the new test sensor in its place, and it functioned properly. its not installed on the machine just hanging loose.
now I guess I need to figure out what that's telling me.
i guess as a next step i will replace one of the existing sensors with the new one and see what I get.
the cable runs on this machine are pretty long and i want to think that I could be getting some EMI, but the cables are shielded and they did work with the previous mach 3 controller, and the indicator lights on the sensors are fuctioning as expected ( led turns on when it approaches a metal object ) so I'm a little stumped. need a diode? why is the Z probe flashing in the dwc? (z probe is just a 3v supplied brass pad the tool touches off on)any other suggestions would be appreciated.
thank you all for your time and expertise
-
@dwak said in inductive end stop intermittently triggered:
z probe indicator alternates between 1000 and 0
The value of 0 to 1000 indicates the trigger status of the probe. So it's picking something up.
-
update:
i grounded the shielding on the offending cables and now I only have the issue with the y axis, so I have ordered some ferrites to see if i can eliminate the remaining noise.
-
Well got the endstops working on my own.
for anybody having similar issues,
I grounded the shielding on all the endstop and z probe cables and after ordering a trifield meter to test for efi, I moved the duet and pi to a more shielded location with some metal between them and the stepper motor transformers.hope this helps someone in the future.
an aluminum, case for the duet would probably be a good idea,Wonder if a 3d printed case from some ferromagnetic fillament would work for shielding.
the duet seems to be more sensitive to noise than my old controller was
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
