Homing/Motor control Issues
-
@rich1351 Please post your homing files as code.
-
@theolodian here are the homing fileshomey.g homex.g homeall.g
it wouldnt post if i added them as code kept saying flagged as spam -
@rich1351 Yeah, I don't see any typos there. Sorry, beyond me.
-
Post your config.g please and Can you send M122 and M98 P"config.g" in the Gcode console in DWC and post the results?
-
config-spindle.g config-drives.g config-axes-limits.g config-axes-endstops.g config-axes-calibration.g config-axes.g config.g
ill have to upload the rest in another reply as it will only allow so many
The results from M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J9F0-3S86L-1V9LT
Used output buffers: 1 of 40 (22 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 91664 of which 0 recycled
Never used RAM 108768, free system stack 206 words
Tasks: NETWORK(ready,31.4%,212) ETHERNET(notifyWait,0.2%,126) HEAT(delaying,0.0%,405) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,7.4%,93) MAIN(running,60.8%,924) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:07:18 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 158
MCU temperature: min 25.1, current 25.7, max 26.0
Supply voltage: min 23.8, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/24/0, gc cycles 0
Driver 0: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 1: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 2: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 3: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 4: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Date/time: 2022-01-07 10:20:05
Slowest loop: 13.59ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
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 521, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 521/0/0
Tx timeouts 0,0,521,0,0,0 last cancelled message type 30 dest 127=== Network ===
Slowest loop: 13.77ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 2 of 8- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
The results from M98 P"config.g":
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Tool 49 not found - Ethernet -
-
remaining config files config-user-settings.g config-probe.g config-override.g config-network.g config-laser.g config_default.g
-
After some more testing I've swapped the x axis to driver 4 and all works as should no dropping out whatsoever so I have a feeling this board has a fault on driver 0 unless something in software is messing with driver 0
-
@rich1351 bump
-
Do you get any error messages when it's not moving? The description makes it sound like intermittent wiring issue. I don't see anything in your configs, but it's also very spread out so maybe I missed something.
-
@phaedrux no error messages, the readouts update as if it has moved. with just the change to driver 4 in config-axes.g and reversing the motor direction in config-drives.g it works flawlessly, ive tested it both ways with the routed wiring, and also made up a single motor wire to eliminate the other wiring and with both it acts exactly the same. I have spoken to ooznest where i purchased the board and they have advised it may be faulty but i need to get comfirmation from this forum to get the warranty claim sorted
Cheers
Rich -
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
