Enable endstops on a Duex5
-
I took voltage from Duex endstop + & - then I took signal from Duet endstop Z.
When Z is moving I get a led from Sunx when I put a screwdriver on it on Duet Zendstop the led comes on with red light. Z continues to move though.Sunx link http://www.clrwtr.com/PDF/SUNX/SUNX-GL-8U-Proximity-Sensors.pdf
With m119 I get a popup
Endstops - X at min stop. Y at min stop. Z at min stop. Z probe not stopped. -
These end stops are rated 12-24 but works with 5v as they are originals in my printer and runs well with 5 v.
-
any ideas? Some more to test?
-
Which particular model of the GL8 series are they?
-
Hi,
Its a Gl8h top sensing 3 wire model "normally open" -
Have you set up your M574 command and your homez.g and homeall.g files to tell the firmware that you are using an endstop for Z homing? See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer. Your files may be set up for Z homing using a Z probe instead, depending on where they came from.
-
Well I used the configurator to set it but I will go through it again.
Just to be on the safe side.. I connected black signal cable to the outer pin closest to usb port on Duet. Looking at schematics for Duet it looks like it should be the other way around.. but if I do that I get no led light on Duet.On Duet I have + brown cable and - blue cable.
-
Can confirm the wrong in the schematics now, just measured it and power is wrong in the Duet schematic.
-
I have M574 X1 Y1 Z1 S0
Had a M558 line active and put a rem in the front now, is that correct to rem that line and use the above for open and low homing?
If so I will test this now. -
Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sat Mar 04 2017 15:46:00 GMT+0100 (W. Europe Standard Time); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X370 Y250 Z280 S0 ; Set axis maxima; Endstops
M574 X1 Y1 Z1 S0 ; Define active low and unused microswitches
;M558 P1 X1 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; Define mesh grid; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y81 Z390 E189 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M143 S285 ; Set maximum heater temperature to 260C
M305 P0 T130600 B6084 C2.635903e-7 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M307 H0 P130.1, I0.213, D449.1; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C; Network
M550 Black Widow ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; Custom settings are not configured
-
Okay I have X homing as it should!
Y is homing in the wrong direction even though I did set it to low. Tried o change it to high incase there was a bug or something but it didnt work… It however stops if I put a screwdriver on the sensor so the sensor is communicating to the board correctly.. Its just the motor homing in the wrong direction despite being configurated as below.
; Endstops
M574 X1 Y1 Z1 S0 ; Define active low and unused microswitches
;M558 P2 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to modulated, the axes for which it is used and the probe + travel speeds
;G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
;M557 X15:355 Y15:235 S20 ; Define mesh gridZ does not stop with any metal on it but it still lights up on the board.
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0 + DueX5
Firmware Version: 1.17c (2017-01-14)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.14a -
Updated to 1.17e with no differance on homing
-
Y homing sorted out… works.
Now trying to fix Z
-
I would like to see how a Homez.g for a carthesian without probe looks like… Mine has a probe setting. Can anyone post one?
-
Did you read these yet
https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_files
If you home Z using a microswitch instead, then you can use a pattern similar to homex,g and homey.g. However, if you use a low-end homing switch that triggers a little before Z=0, then you can't use M208 to define the homing position, because it would prevent you moving below the trigger height. You can use a G92 command after homing instead. Here is an example, for the case where you have a low-end homing switch that triggers at Z=0.3mm:
G91 ; relative mode
G1 Z4 F200 ; raise head 4mm to ensure it is above the switch trigger height
G90 ; back to absolute mode
G1 X0 Y0 F2000 ; put head wherever you want it to be when you home Z (omit this line if it doesn't matter)
G91 ; relative mode
G1 Z-200 S1 F100 ; move Z down until the switch triggers
G90 ; back to absolute mode
G92 Z0.3 ; tell the firmware that we are at Z=0.3mm -
Seems like the configurator is putting out the wrong content, it does put out probe in homez even if probe was deselected.
Will read that link thanks, have a homez based on Y content now as a start and it works…
Just trying to understand how the files are built up and relates. -
I think I have it all figured out now.
Thanks for any assistance given.
Im sure I will find something more to ask about within short. -
Just like to remind DC42 to look at the error of the Duet 3.3v endstops signal and ground is not correct on schematic.. they need to switch place.
Configurator outputs probe even if probe in homez was deselected.
-
Just like to remind DC42 to look at the error of the Duet 3.3v endstops signal and ground is not correct on schematic.. they need to switch place.
Please provide a link to the particular diagram that you believe is wrong, and confirm whether you have a blue production board or a white pre-production board.
Configurator outputs probe even if probe in homez was deselected.
Thanks for that report. I'll check it out.
-
https://duet3d.com/wiki/Duet_WiFi_wiring_diagrams
My board is a 1.01
