#help for my endstope

1 messages · Page 1 of 1 (latest)

lime pagoda
#

the issue is that when the endstop are unplug they got triggerd in x and y

bright forum
#

Please copy and paste the contents of the config.g file and M122 output rather than posting screen shots, that will make it much easier for folks to see how you have things set up.

inner spear
#

If Normally Connected(NC) endstops are unplugged they will trigger. This is normal and correct behavior. It the preferred method of wiring so that if you have a fault in the wire the printer will stop.

lime pagoda
#

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.4 (2022-10-20 16:19:01) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JTDG-3S46S-TAALT
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 152824
Dynamic ram: 67064 of which 200 recycled
Never used RAM 130512, free system stack 192 words
Tasks: SBC(resourceWait:,0.6%,484) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,259) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,334) TMC(notifyWait,8.0%,57) MAIN(running,91.4%,923) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:01:36 ago, cause: software
Last software reset at 2023-08-08 13:52, reason: User, Platform spinning, available RAM 130440, slot 1
Software reset code 0x0000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 133
MCU temperature: min 41.8, current 42.2, max 42.4
Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 11.9, max 12.0, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a, mspos 8, reads 34742, writes 0 timeouts 0
Driver 1: standstill, SG min n/a, mspos 8, reads 34743, writes 0 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 34743, writes 0 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 34743, writes 0 timeouts 0
Driver 4: standstill, SG min n/a, mspos 1, reads 34743, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 34742, writes 0 timeouts 0
Date/time: 2023-08-08 14:54:18
Slowest loop: 1.15ms; fastest: 0.06ms

#

=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 8, completed 8, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 2389, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 1327/0/0
Tx timeouts 0,0,1327,0,0,1062 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 15728/15728
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad08
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.37, max time between full transfers: 77.2ms, max pin wait times: 28.0ms/1.1ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 3224/532

#

; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.14 on Sun Nov 06 2022 17:02:14 GMT+0100 (heure normale d’Europe centrale)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CoreXY" ; set printer name
M669 K1 ; select CoreXY mode

; Drives
M569 P0.0 S0 ; physical drive 0.0 goes forwards
M569 P0.1 S0 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping
M350 X16 Y16 Z16 E128 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E741.00 ; set steps per mm
M566 X800.00 Y800.00 Z30.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z300.00 E1200.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E1500.00 ; set accelerations (mm/s^2)
M906 X1500 Y1500 Z1000 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent

M84 S30 ; Set idle timeout

; Axis Limits
M208 X-30 Y-30 Z0 S1 ; set axis minima
M208 X330 Y330 Z400 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin io1.in
M574 Y1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io2.in

#

; Z-Probe
M574 Z1 Z1 S2 ; set endstops controlled be probe
M558 P5 C"^!io3.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X30 Y30 Z4 ; set Z probe trigger value, offset and trigger height
M557 X30:330 Y30:330 P15 ; define mesh grid

; Heaters
M308 S0 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp1
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
;M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
;M307 H0 A215.5 C661.6 D5.8 S1.00 V11.6 B1
M307 H0 R0.187 K0.192:0.000 D1.89 E1.35 S1.00 B0
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp0
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency

#

M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 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
T0

#

@inner spear m119
Endstops - X: at min stop, Y: at min stop, Z: not stopped, Z probe: not stopped

#

the x is unplug and the y is plug

#

and even when i try to home x and y axis don't move

#

the head just stay where he is

halcyon sleetBOT
#

GG @lime pagoda, you just advanced to level 1!

lime pagoda
#

@bright forum do you need other logs or config ?

reef aurora
bright forum
#

@lime pagoda Do your endstops work when they are connected? Did you see the previous comment fro @inner spear :

If Normally Connected(NC) endstops are unplugged they will trigger. This is normal and correct behavior.  It the preferred method of wiring so that if you have a fault  in the wire the printer will stop.
lime pagoda
#

the components yes but i don't know in the software

reef aurora
#

You can either rewire them, or invert them in config.g using a ! eg
M574 X1 S1 P"!io1.in"

lime pagoda
#

@reef aurora i am gonna try

#

ok now it move but when he touch the end he doesn't stop

#

Error: G0/G1: insufficient axes homed

#

and i got this error

reef aurora
#

Looks like a TronXY X5S? I've got one of those!

halcyon sleetBOT
#

GG @reef aurora, you just advanced to level 2!

lime pagoda
#

x5SA

#

yes

reef aurora
#

It is better to test the endstop switches by sending M119 in the console, pressing the endstop switch, and sending M119 again to see if the state has changed.

#

Rather than smashing it against the frame by pressing Home All.

lime pagoda
#

found the problem when it works

#

i have inverted the two endstop thats why he didn't stop and with the ! everything is perfect

#

thank you every one

#

now i need some with the g32 and g29 cause it start outside of the bed

lime pagoda
#

@reef aurora i need some help on how to make correctly the bedleveling and config z axis

reef aurora
#

For Z axis with two motors, see https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_auto_levelling for changes to config.g.

Next, you need to make sure you Z probe works, as most of the following needs the Z probe. See https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_testing

Then, adjust the bed so it is level across the X axis, by turning the two Z motors by hand. Then you need to have a macro for manual 3-point bed levelling, see https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_manual_levelling. This allows you to adjust the bed using the bed adjustment screws to get the bed plane level with the XY plane. You can do this manually, by moving the bed up to the nozzle, and adjusting the bed plane, but a macro automates this process.

Then you can use the Z probe auto levelling to level the bed side to side (as you only have two Z motors), see the first link.

Finally, you can set up Bed Mesh Compensation, see https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_mesh_bed.

lime pagoda
#

ok i am gonna this