Endstops not stopping external drivers on the expansion header
-
Is there anywhere I can send this Ethernet board to have it repaired?
-
Bear in mind that when you map axis drivers using M584, that does not map endstops. You must still use the XYZ endstop inputs on the Duet.
-
It was, I know it is a board issue. I swapped to my wifi board that I was saving for a different printer and it works fine. The only thing I changed was the board, I even swapped the sdcard so it was running identical settings and firmware. I don't want a free repair I will gladly pay to have it done, but just don't know of anyone qualified to send it to.
-
I don't see how it can be a hardware problem. Please can you try the latest release (1.20.1RC2) and if that has the same problem, share your config.g and homing files.
-
Sure give me a day or two to switch the boards around. in advance these are my config.g and home files.
; Configuration file for Duet Ethernet (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Mon Dec 25 2017 21:58:57 GMT-0500 (Eastern 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
M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X673 Y673 Z694.29 S0 ; Set axis maxima; Endstops
M574 X1 Y2 Z2 S1 ; Set active high endstops
M558 P1 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X30 Y-5 Z1.74 ; Set Z probe trigger value, offset and trigger height
M557 X90:630 Y43:603 S30 ; Define mesh grid
M584 X5 Y6 Z7:8:9 ; three Z motors connected to driver outputs 2, 5 and 6
M671 X336:94:652.5 Y613:53:53 S30 ; leadscrews at rear left, front middle and rear right; Drives
M569 P3 S0 ; Drive 3 goes backwards
M569 P4 S1 ; Drive 4 goes forwards
M569 P5 S0 ; Drive 5 goes forwards
M569 P6 S0 ; Drive 6 goes forwards
M569 P7 S0 ; Drive 7 goes forwards
M569 P8 S0 ; Drive 8 goes forwards
M569 P9 S0 ; Drive 9 goes forwards
M584 X5 Y6 Z7:8:9 E3:4 ; Apply custom drive mapping
M350 X16 Y16 Z16:16:16 I0 ; Configure microstepping without interpolation
M350 E16:16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z400:400:400 E476.5:476.5 ; Set steps per mm
M566 X800 Y800 Z400:400:400 E120:120 ; Set maximum instantaneous speed changes (mm/min)
M203 X8000 Y8000 Z2500:2500:2500 E1200:1200 ; Set maximum speeds (mm/min)
M201 X1800 Y1800 Z700:700:700 E250:250 ; Set accelerations (mm/s^2)
M906 X2000 Y2000 Z2000 E800:800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 X150 ; Set thermocoupler remapped 150
M143 H1 S400 ; Set temperature limit for heater 1 to 400C
M305 P2 X151 ; Set Thermocoupler remapped 151
M143 H2 S400 ; Set temperature limit for heater 2 to 400C; 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
M563 P1 D1 H2 ; Define tool 1
G10 P1 X89.40 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
M912 P0 S-7;*** Networking - Enable for both WiFi and Ethernet boards.
M552 S1 ; Turn network on;*** Ethernet networking: Adjust the IP address and gateway in the following 2 lines to suit your network
M552 P0.0.0.0 ; (0 = DHCP)
M554 P192.168.1.255 ; Gateway
M553 P255.255.255.0 ; Netmask; Fans
M106 P3 T20 H100
M563 P0 D0 H1 ; tool 0 uses extruder 0, heater 1 (and fan 0)
M563 P1 D1 H2 F2 ; tool 1 uses extruder 1, heater 2 and fan 1 2; homeall.g
; called to home all axes
;; Relative positioning ; uncomment this line to lift the nozzle after homing
G91
; Course home Z
G1 Z725 F2500 S1
; Course home X
G1 X-675 F8000 S1
; Course home Y
G1 Y675 F8000 S1; Move away from the endstops
G1 X5 Y-5 F400
G1 Z-5 F400; Fine home X
G1 X-10 F400 S1
; Fine home Y
G1 Y10 F400 S1
;fine home Z
G1 Z10 f400 S1; Absolute positioning
G90 -
also the firmware is 1.20.1RC2
-
I don't know if this might be relevant but when I changed my CoreXY to XYUV, after mapping the drives I had to move the axes maxima to a position in the gcode file that was after the M584 command. I see in the config.g that your M208 is before the M584.
Also this from the Wiki might be relevant.
"Assigning a drive using M584 does not remove its old assignment. Therefore, if you assign a drive that defaults to being an extruder drive, you should also assign the extruder drives explicitly as in the above example. Failure to do so may result in unexpected behaviour".
Edit. That's big printer BTW!
-
Ok so I switched back to the Ethernet and used the same SD card and verified that the firmware is the undated one and when homing the endstops do not trigger the motors to stop. I even swapped the min and max codes so the max comes first and still the same. Not sure what the deal is.
-
Please try disconnecting the endstop switches from the Duet. As you have configured them to be active high, this should make them all read as if triggered. Then try to home X or Y when it is not already in the home position. Does the motor move towards the homing switch, or not?
-
It moves to towards the switch. But they should not be moving at all. This is why I link it is the board. With my WiFi board the printer runs perfect. If I bypass the external drivers and the encoder and run them from the main board they operate as intended. It is only when using the breakout board for external drivers.
-
As soon as I have shipped the prototype laser filament sensors, I'll try to replicate your configuration and see if I can reproduce the fault.
-
I can ship you the board if you want.
-
I don't see how it can be a fault with the board. It is firmware that reads the endstop inputs and stops the motors when they are triggered during a G1 S1 move.
One other user reported a similar problem, but it appeared to go away when he changed his config file.
-
Would it be worth the time if I completely erased the board and re-flashed it via usb?
-
You could try it, but that rarely solves anything. OTOH you could try installing different firmware versions, e.g. 1.18.2, 1.19.2, 1.20 and 1.20.1RC2
-
I need to run my printer so I am going to put my WiFi board back in but I will make a bench test for it and keep trying things.
-
I have put your config.g and homing files on a Duet Ethernet on the bench, and I have been unable to make the problem occur. As soon as I trigger the X homing switch, the X homing button changes from orange to blue. The only difference I can see is that I don't actually have any external drivers connected to the expansion connector. I have the internal 5V regulator enabled.
I am wondering whether with the external drivers connected, the voltage on the 5V and/or 3.3V rail is dropping too low, and that is causing the problem.
Please can you do the following tests:
1. Confirm that when you try to home, triggering the X homing switch does not change the X homing button from orange to blue (as well as not stopping motion).
2. In DWC, go to the Machine Properties page and check that endstops 0 and 1 are showing as not triggered. Then use the "Send GCode" box to send G28. When the X and Y homing switches are triggered (but the motors do not stop), do they show as triggered on the Machine Properties page?
3. If you try to home with the external drivers disconnected, when you press the X homing switch, does the homing button still fail to change from orange to blue?
-
Just when I thought I killed the last hornet finally getting the 2130 to cooperate (more like me to cooperate) I have this same endstop issue while using the expansion port. I will try the above suggestions and report my findings. I have the latest 2.0FW
