Duet 2 wifi CR10 end stops not working
-
@Smedley said in Duet 2 wifi CR10 end stops not working:
Now they go away from the switch a couple of inches.
That is the back off movement in the homing files. It still seems to think your endstops are triggered even when they are not.
Can you post a photo of the endstop switch itself? I'm assuming they are the creality endstop switches?
Posting M122 will let us verify your firmware version and hardware.
-
Perhaps a video to show what's going on? Sometimes being able to see the actual behaviour helps a lot.
-
@Phaedrux
I just put the X all the way from the switch. Hit home x it went to the switch move a way from the switch and the move back to the switch and did not stop. Basically it hit the switch and bounced and then went back to the switch and would not stop running the motor at the end stop. -
@Smedley the behaviour would be explainabe if you have firmware below 2.01 because then homing G1 H1 must be G1 S1 and H2 must be S2, but please make M122.
-
Please post the results of M122, your current config.g, and homeall.g
-
@Phaedrux
Ok I will. It is very flake. -
@Phaedrux
config.g no M122
homeall.g. no M122 -
What does that mean?
-
@Smedley he means please call M122 in the send g- code field. Some statistics are shown then. Please post them.
-
@Phaedrux
can not upload moves to large.If I start it from the middle it just runs to the switch and keeps going.
If I start at the far end it will run to the end switch and bounce and then come back to switch and keeps going.
-
@JoergS5
ok -
@JoergS5
If I run M112 I lose my connection.I can run M503 but not M112
-
M112 is reset.
M122 is diagnostic report.
-
@Phaedrux M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MS8-6J1FA-3SN6R-KSFLR
Used output buffers: 3 of 24 (16 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93184 of which 0 recycled
Exception stack ram used: 272
Never used ram: 11904
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:08:01 ago, cause: power up
Last software reset at 2020-07-28 19:05, reason: Heat task stuck, spinning module Platform, available RAM 11516 bytes (slot 2)
Software reset code 0x40a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x2000495c Task 0x4e49414d
Stack: 0044d797 00445546 6100f000 00000000 000004d9 00000000 00000000 43910000 41880000 3e178897 3e1cd04f bddcf905 3e3a3867 3e63939a 3e924c60 3c3ebcf3 397a8e49 c0a00000 00000000 60000010 20003258 20008a10 0044d797
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 36.9, current 37.4, max 37.5
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-07-28 19:19:06
Cache data hit count 1475307095
Slowest loop: 5.12ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 201.17ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi MAC address dc:4f:22:6e:6c:38
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23648
WiFi IP address 10.0.0.88
WiFi signal strength -62dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@Smedley please make some movement like homing etc before M122, because now you had the reset just before.
-
@Smedley
If I run any HOME command I have to do a EMERGENCE STOP. Is that resting M122 and not able to see the results.The end stop switches never stop the motor. I always have to use the emergency stop.
-
@Smedley I understand. I just wanted to see whether you have hiccups ( not you, your printer
)
This is when the printer looses steps. Your M203 X and Y values are high, please set to 6000 as a test.Another question is: on the photo a sensor is visible, is this an endstop? It looks like a capacitative sensor. Has it 2 or 3 wires? Some of those sensors need 6 volt, could you check the documentation? ( if you use it as endstop)
-
That is a microswitch.
The M203 I messed it up cannot get it back to the 500 it was set to.
-
If you physically move the print head to the farthest points from the endstop and then try to home all, does everything move towards the endstops?
Please post a photo of the actual endstop switch and double check your wiring is correct. Is it possible you've got the X endstop plugged into the Y spot or vice versa? Is it possible that in your splice job somehow the endstop has been shorted and so looks triggered?
-
@Smedley said in Duet 2 wifi CR10 end stops not working:
The M203 I messed it up cannot get it back to the 500 it was set to.
see if you have a more than one M203 line, espescially if you also have a config-override.g file.
and ignore the LEDs on the board, in duetwebcontrol go to the settings -> machine specific page and look at the end stop status as you manually trigger each one. if the status doesn't change when you actuate the endstops then they will not stop the motor either. as suggested above pay attention that it is the correct endstop status that changes.
if you've wired according to the slikscreen on the board the mapping between the driver and endstop indexes and letters should be as follows
x=0
y=1
Z=2
e0=3
e1=4
