Unsolved Motor issue, step forward and backward when change direction.
-
Hi all.
Suddenly I found this trouble printing some parts. The problem is the same like when a circle is printed with some kind of problem with tension in belts or similar.
This is what I found at printing:
First time I thought was a problem with belts or some of the printer parts, but when I look deeper, found that Y motor is doing a very strange movement when change direction of movement. This is what I found:
When the motor turns clockwise runs good, but just when change direction makes a little bump, don't know how to describe sorry.
I've dismantle the motor to see if there were a trouble inside, but it's in perfect conditions. In fact I decided to changed the motor by other one and the problem stills.
It doesn't matter if printed slow or fast, the same result come.I'm very angry, pissed off and tired about this issue.
If anyone could give me a hand...Thanks in advance.
Printer: Ultipaski (Ultimaker clone)
Motors: nema 17
Board: Duet3d 2.0 wifi - Firmware 3.0 -
Can you please post your config.g and the results of M122?
If you're on firmware 3.0 you should update to 3.1.1.
I do see the little hitch in movement. What commands are you sending to generate the movement?
-
Hi @Phaedrux.
This is the M122 results:
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S4-6J9FG-3SN6M-TVNZG
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 94088 of which 20 recycled
Exception stack ram used: 264
Never used ram: 8720
Tasks: NETWORK(ready,384) HEAT(blocked,1224) MAIN(running,1816) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:57 ago, cause: power up
Last software reset at 2020-10-29 18:52, reason: User, spinning module GCodes, available RAM 8472 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 16.5, current 23.1, max 23.5
Supply voltage: min 11.8, current 11.9, max 11.9, 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-10-30 17:59:16
Cache data hit count 311480769
Slowest loop: 7.06ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.6ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, 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, 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 82.44ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 84:0d:8e:b1:7d:76
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 4194304, free heap 22216
WiFi IP address 192.168.2.105
WiFi signal strength -46dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
And the config file:
As you said, this hitch, happened suddenly two days before, because until then and without making any changes to the firmware or anything, it worked perfectly, in fact, I was printing some figures of among us, perfect.
Thanks for your help.
- WiFi -
-
And you've tried with another motor? Another driver?
What commands are you sending to produce the movement?
-
Yes I've changed the motor by another one, new, and the same results appeared.
-
Does it happen on all drivers, or just one?
-
@Phaedrux Only in Y axis.
-
@Pasquk2
please reassign the y axis to another port and test againi.e
M584 X0 Y1 Z2 E3 ; set drive mapping
to
M584 X0 Y4 Z2 E3 ; set drive mapping -
Sorry for the delay.
I've changed the command but the Y axis doesn't move.
This is the error message from system: -
check your wiring.
did you plug in the cable into e1 on the board? -
Sorry, was not well connected. Is the problem when do things in the dark.
Trying now to print some circles and figures to prove all is ok.
I'll come back with results.Thanks.
-
I have problems now with the extruder. It does not extrude.
Left it for tomorrow. Too late for me. -
Today I've made a visual control printing test without filament and still produce the same hitch in the motor of Y axis.
-
to sum up.
you changed to driver on the duet to a different port -> no change
you changed the motor and its wiring -> no changedo you have pressure advance active?
did you try a differnet slicer?
-
@Veti said in Motor issue, step forward and backward when change direction.:
pressure advance active
Sorry, but, dont know what "pressure advance active" is. Where can I find it?
I've tried, simplify3d, repetier, prusaslicer and cura, and all get the same results.
-
@Pasquk2 said in Motor issue, step forward and backward when change direction.:
Sorry, but, dont know what "pressure advance active" is. Where can I find it?
https://duet3d.dozuki.com/Wiki/Pressure_advance
M572
-
If this must be in config.g file, I don't find it.
-
most of the time you put it the in the start g code of a file.
you can also just send M572 D0 in the console to query the current value
-
This is the result of m572 D0:
-
I'm going to erase all and reload the firmware again, begining from 0.