Z Axis behaving strangely
-
so, my have a Tronxy X5SA carcas which I upgraded with a Duet 3 as motherboard. That process wasn't without difficulties but I am really happy with the result. I think the board worked wonderfully for the past 3 months. However, since a week or so something strange appeared. Out of nowhere one of the Z steppers (its a dual z setup) started to sometimes turn in the wrong direction. No changes where made to the config file (for the Driver part) and it sometimes happens mid homing. This makes the platform skew until it creates enough pull to stop the platform from moving, paired with a horrible noise obviously. I thought it was part of the home all protocol, but I have come to find that skipping homing and trying to move it manually also endures the same faith.
I switched the stepper cables, to test if it was due to the steppers, but this just moves the problem over to the other side. I'm afraid it's with the driver... any way to test / fix it?
-
@yellow said in Z Axis behaving strangely:
I switched the stepper cables, to test if it was due to the steppers, but this just moves the problem over to the other side.
Do you mean you swapped the stepper cable from one z motor to the other and it followed the cable?
Can you please post your config.g and homing files as well as the results of M122 and M98 P"config.g"?
-
Do you mean you swapped the stepper cable from one z motor to the other and it followed the cable? Yes
Can you please post your config.g and homing files as well as the results of M122 and M98 P"config.g"?
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
Board ID: 08DJM-956L2-G43S8-6JKD2-3S06N-1A2UDUsed output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 154572
Dynamic ram: 161908 of which 64 recycled
Exception stack ram used: 296
Never used ram: 76376
Tasks: NETWORK(ready,84) ETHERNET(blocked,444) HEAT(blocked,1108) CanReceiv(suspended,3824) CanSender(suspended,1484) CanClock(blocked,1428) TMC(blocked,216) MAIN(running,4532) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 21:18:49 ago, cause: software
Last software reset at 2021-05-31 17:31, reason: User, spinning module GCodes, available RAM 76168 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 33.4, current 34.1, max 34.7
Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Driver 0: standstill, reads 33076, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 33078, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 33078, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 33078, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 33079, writes 14 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 33079, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-06-01 14:49:50
Slowest loop: 4.73ms; fastest: 0.21ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== 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
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 5.79ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages sent 306917, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 76729348ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
M98 P"config.g"
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 508C[no clue what this does... Haven't had an issue with overheating, just saying]
- Ethernet -
-
If it follows the cable, replace the cable..
The over-powered heater warning is just a warning telling you how hot it expects your heaters are capable of reaching in a runaway failure condition.
-
@phaedrux I wanted to test this but the problem seems to have resolved itself, but a new one arose (probe isnt triggering properly). As I do not believe it is totally gone but I'm not able to test it properly I'm going to try to fix that, try to update some wires just because I can, and get back to this if it shows up again....
I love this hobby
