X + Y NoT HoMiNg - Z is a BL Touch & IT IS Homing????!!!!!!!
-
undefinedAs the title of this post states the Z is a BL/3D Touch and it is in fact homing on command. However, the X & Y are not in fact homing regardless of my attempts to home said Axis????? When I do hit the command button "Home All" all of the axis will move simultaneously though they will ALL only move a couple two or three MM's, never make contact with any of their respective endstops, and then they will declare themselves "Homed?????" So what gives what is up with this here odd homing behavior???? Why will ALL of the axis move on the Home All command yet only move a mm or two maybe three IDK all I do know is that they never make contact with their respective endstop yet they will declare themselves "homed" when obviously they are not???? Please tell me I am not crazy and please I hope someone has a solution. I want things to work with RRF though Im already contemplating/considering moving over to Klipper coz it has been one issue after another with this RRF though Ill be perfectly honest the vast majority of the issues Ive encountered have been/are due to inexperience with RRF. All of my 3d hardware & fw experience is with the BTT SKR lineup particularly their SKR 1.4 Turbo of which I used to believe was "the board to get" that is until I learned of Duet3d and their "g code is everything" Philosophy along with ALL of the safety measures they bake into the hardware. I was settled on Duet3d and still am I just need to get past this hump of dealing with the "non homing/not hitting endstops/overall not working so great hump that I am on top of right now so anyways....... Okay that is all Ive got below you will find the applicable files that I am aware of thus far:
In accordance with the Testing Endstops publication from Duet3d the following m119 command was done when only the Duet 3 Mini 5+ was powered via USB coming from its SBC, a RPi 4b with only the D3M5+ being connected via USB:
10/8/2021, 9:32:10 PM m119 -- Endstops - X: at min stop, Y: at min stop, Z: not stopped, Z probe: not stopped
BTW the previous m119 command is NOT true as in the X and Y are not pressed up against their applicable endstops.......
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 08:23:52 GMT-0500 (Central Daylight Time)
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 08:23:53 GMT-0500 (Central Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F9600 ; lift Z relative to current position
G1 H1 X-415 Y-415 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F9600 ; go back a few mm
G1 H1 X-415 Y-415 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X-20 Y-9 F9600 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z5 F160 ; lift Z relative to current position
G90 ; absolute positioning
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 08:23:53 GMT-0500 (Central Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F9600 ; lift Z relative to current position
G1 H1 X-415 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F9600 ; go back a few mm
G1 H1 X-415 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F9600 ; lower Z again
G90 ; absolute positioning
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 08:23:53 GMT-0500 (Central Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F9600 ; lift Z relative to current position
G1 H1 Y-415 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F9600 ; go back a few mm
G1 H1 Y-415 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F9600 ; lower Z again
G90 ; absolute positioning; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 08:23:53 GMT-0500 (Central Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F9600 ; lift Z relative to current position
G90 ; absolute positioning
G1 X-20 Y-9 F9600 ; go to first probe point
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F160 ; lift Z relative to current position
;G90 ; absolute positioningLemme know guys and gals any help would be appreciated very much so as it is this is the only issue that I can tell as of right now that is holding me back from finally and I do mean FINALLY getting a print started and completed on this very much custom Anycubic Chiron!!!!!!!!!! Thanks!!!!!!!
-
@pickett said in X + Y NoT HoMiNg - Z is a BL Touch & IT IS Homing????!!!!!!!:
10/8/2021, 9:32:10 PM m119 -- Endstops - X: at min stop, Y: at min stop, Z: not stopped, Z probe: not stopped
BTW the previous m119 command is NOT true as in the X and Y are not pressed up against their applicable endstops.......You didn’t post your config.g or response to M115 (to show what board and firmware version you’re using), but most likely you need to invert the logic of the X and Y endstops. See https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Microswitch
We recommend you use the normally-closed contacts of the microswitches, which are generally the outside two connections on the microswitch, and set the signal polarity to active high (S1) in the M574 command. If for any reason you use normally-open microswitch contacts, then if you use RepRapFirmware 1.x or 2.x then you will need to set the signal polarity to active low (S0) in the M574 command, and if you are using RepRapFirmware 3 then you will need to use S1 but invert the polarity by putting a ! character at the start of the pin name in the M574 command.
Ian
-
- undefined@droftarts Thanks Ian for the response and in response to your response here is my response but will first respond with the requested response for an M115 command which is as follows:
10/9/2021, 2:17:55 AM m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-06-15 21:46:20, config.g;
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 08:23:52 GMT-0500 (Central Daylight Time); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Chiron_LRE" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display; Drives
M569 P0.0 S0 ; physical drive 0.0 goes backwards
M569 P0.1 S0 ; physical drive 0.1 goes backwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes backwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z400.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z600.00 E3600.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z200.00 E2500.00 ; set accelerations (mm/s2)
M906 X1000 Y1000 Z1450 E600 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X410 Y410 Z450 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io5.in" ; configure active-high endstop for low end on X via pin io5.in
M574 Y1 S1 P"io6.in" ; configure active-high endstop for low end on Y via pin io6.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
- undefined
M950 S0 C"io3.out" ; create servo pin 0 for BLTouch
M558 P9 C"io3.in" H5 F120 T9600 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X35 Y24 Z2 ; set Z probe trigger value, offset and trigger height
M557 X15:385 Y15:385 S20 ; define mesh grid
; Heaters
M308 S0 P"temp1" Y"thermistor" T98801 B4185 ; configure sensor 0 as thermistor on pin temp1
M950 H0 C"out1" T0 ; create bed heater output on out1 and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S160 ; set temperature limit for heater 0 to 160C
M308 S1 P"temp2" Y"thermistor" T98801 B4185 ; configure sensor 1 as thermistor on pin temp2
M950 H1 C"out2" T1 ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S320 ; set temperature limit for heater 1 to 320C; Fans
M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P0 C"Tool Fan" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency
M106 P1 C"Hotend Fan" S1 H1:0 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"out5" Q500 ; create fan 2 on pin out5 and set its frequency
M106 P2 C"Case Fans" S1 H1:0 T45 ; set fan 2 name and value. Thermostatic control is turned on
M950 F3 C"out6" Q500 ; create fan 3 on pin out6 and set its frequency
M106 P3 C"Bamboo Box Fan" S1 H-1 ; set fan 3 name and value. Thermostatic control is turned off; Tools
M563 P0 S"diy Volcano Hotend" D0 H1 F0 ; 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; Custom settings are not defined
; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool -
@pickett It harder to help with multiple threads being opened for the same issue:
https://forum.duet3d.com/topic/25374/all-axes-will-home-but-have-not-connected-any-endstops/24
I have locked the previous thread we can continue here.
Where we left off you had determined that you originally had your endstops wired as Normally Open, and the firmware configured for them to be normally closed. It looks like they are still wired Normally open if the M119 command is saying they are triggered when they are not. For now try changing the lines in config.g to the following:
M574 X1 S1 P"!io5.in" ; configure active-high endstop for low end on X via pin io5.in M574 Y1 S1 P"!io6.in" ; configure active-high endstop for low end on Y via pin io6.inThen test with M119:
Send M119 with the endstops not pressed. note the results
Press the X endstop and while its pressed, send M119, note the results
Press the Y endstop and while its pressed, send M119, note the results.post those three M199 outputs here.
-
@t3p3tony I didnt change or do anything with the X just yet as I had only wired the endstop up on the microswitch to the outer most wiring like the instructional said to. I apologize I know I stated last night or there abouts that I was certain that I had it wired correctly welp I guess I was wrong as I had the wires connected to the 2nd and 3rd "pins" of the micro switch when it should have been 1st and 3rd and left the 2nd alone. That was what I had just done to the Y microswitch and sure enough I started seeing results in its output whereas before no matter if I compressed the micro switch or not no change of status of any sort was noticed. Now I am seeing results. So anyways this last entry at 0456 am was when I had the microswitch compressed. THe entry before that was uncompressed and of course before that is the M119 results......
10/9/2021, 4:56:02 AM m119 Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped
10/9/2021, 4:52:13 AM m119 Endstops - X: not stopped, Y: at min stop, Z: not stopped, Z probe: not stopped
10/9/2021, 4:08:38 AM m574 s1
Endstop configuration:
X: low end switch connected to pin !io5.in
Y: low end switch connected to pin !io6.in
Z: low end Z probe -
@pickett ok so with the switches wired as you have them, if you are seeing M119 changing when you press the switches then tou can include the "!" or not in the M574 definition to make the logic correct.
