Motors working then chatter before and after homing...

wingtip

Phaedrux

That is indeed strange that movement after M564 S0 H0 works fine, but homing behaves strangely. One thing that occurs to me is that it could be resonance due to the speed of the homing moves compared to the normal travel moves.

In the gcode console, can you send M122 and M98 P"config.g" and post the results here?

wingtip

M122
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F2MS4-7JKD6-3SN6K-9GU4G
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73376 of which 76 recycled
Never used RAM 15168, free system stack 115 words
Tasks: NETWORK(ready,169) HEAT(blocked,200) MAIN(running,449) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:45:14 ago, cause: power up
Last software reset at 2021-03-03 20:03, reason: User, GCodes spinning, available RAM 15168, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 22.2, current 29.6, max 30.0
Supply voltage: min 11.6, current 12.0, max 12.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max 0/319
Driver 1: position 1600, standstill, SG min/max 0/7
Driver 2: position -2000, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max 0/320
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-03-03 22:39:09
Cache data hit count 3286832726
Slowest loop: 25.80ms; fastest: 0.21ms
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 1.6ms, write time 79.8ms, max retries 0
=== Move ===
DMs created 83, maxWait 634476ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 51, completed moves 51, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 40], 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 = 0 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 186.63ms; fastest: 0.00ms
Responder states: HTTP(0) 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.25
WiFi MAC address bc:dd:c2:89:a2:58
WiFi Vcc 3.43, reset reason Power up
WiFi flash size 4194304, free heap 21168
WiFi IP address 192.168.1.7
WiFi signal strength -58dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Phaedrux

Can you also post your homeall, homex, and config.g as they are right now so we're all looking at the same code?

I notice in the video that when you are jogging it around it's with very short small moves. Have you tried longer distance moves yet?

wingtip

@Phaedrux said in Motors working then chatter before and after homing...:

M98 P"config.g"

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

Error: Temperature reading fault on heater 1: sensor open circuit

homex.g

home x is the only one im using at the moment.

Phaedrux

@wingtip said in Motors working then chatter before and after homing...:

i up'd the current from 1amp (1000mah) to 1.2amp (1200mah) and no change

What is the max rated current for the motors?

wingtip

@Phaedrux said in Motors working then chatter before and after homing...:

Can you also post your homeall, homex, and config.g as they are right now so we're all looking at the same code?

I notice in the video that when you are jogging it around it's with very short small moves. Have you tried longer distance moves yet?

unfortunately at the moment i cant due to the huge mess lol... but months ago i was running it the full distance of 800mm no issues

wingtip

@Phaedrux said in Motors working then chatter before and after homing...:

@wingtip said in Motors working then chatter before and after homing...:

i up'd the current from 1amp (1000mah) to 1.2amp (1200mah) and no change

What is the max rated current for the motors?

Ill have to check as they came from openbuilds.com but from the config file you gave me they are now down to 800 mah and still chatter before and after homing..

fcwilt

Re-posting of your homeX.g file

; homex.g
;
; generated by RepRapFirmware Configuration Tool v2.1.1 on Sun Nov 03 2019 09:32:23 GMT-0500 (Eastern Standard Time)
;
G91                      ; relative positioning
G1 H2 Z5 F6000           ; lift Z relative to current position
G1 H1 X-805 F400         ; move quickly to X axis endstop and stop there (first pass) S1 checks for endstop hit
G91
G1 H2 X5 F1800           ; go back a few mm
G1 H1 X-10 F360          ; move slowly to X axis endstop once more (second pass) H1 checks for endstop hit
G92 X0
G90
G1 H2 Z-5 F2000          ; lower Z again
G90                      ; absolute positioning

fcwilt

@fcwilt said in Motors working then chatter before and after homing...:

Comment out the Z axis commands, move Z clear with the jog buttons, and try homing again.

Frederick

Phaedrux

I'm curious if longer moves would actually work jogging around because the short back off move in homex does seem to work ok as do the short jogging moves. If the motor current is too low there may be some back emf issues on long moves since the motors have to spin fairly fast due to being lead screw based.

Also, unrelated to the current problem, but will become a problem in the future when you try to use Z. The last Z move you have G90 setting it to absolute positioning and then telling it to go Z-5. Which is not what you want. You want to be using relative moves with G91 so that Z-5 lowers the z axis back down by 5mm.

G90
G1 H2 Z-5 F2000 ; lower Z again

wingtip

@Phaedrux said in Motors working then chatter before and after homing...:

@wingtip said in Motors working then chatter before and after homing...:

i up'd the current from 1amp (1000mah) to 1.2amp (1200mah) and no change

What is the max rated current for the motors?

checked, they are rated to 1.68 amps

fcwilt

@Phaedrux

Given that the chatter is at the beginning and the end perhaps we are hearing the Z axis?

Frederick

wingtip

@fcwilt said in Motors working then chatter before and after homing...:

@fcwilt said in Motors working then chatter before and after homing...:

Comment out the Z axis commands, move Z clear with the jog buttons, and try homing again.

Frederick

i can comment them out but cant jog it, as stated z motors arent plugged in right now.

Phaedrux

M92 X400.00 Y80.00 Z400.00 E420.00              ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00            ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00        ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00            ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30                   ; set motor currents (mA) and motor idle factor in per cent

I'm assuming you're using the config.g I posted earlier, these values may not be perfect for your setup.

For the motor currents lets set them to 1400ma which is 80% of the rated max and see if it makes any difference.

M92 X400.00 Are we sure your X axis is 400 steps per mm?

Let's reduce the max speed, jerk, and accel for X as well.

Let's try these

M203 X3000
M201 X300
M566 X300
M906 X1400

wingtip

@Phaedrux said in Motors working then chatter before and after homing...:

M92 X400.00 Y80.00 Z400.00 E420.00              ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00            ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00        ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00            ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30                   ; set motor currents (mA) and motor idle factor in per cent
I'm assuming you're using the config.g I posted earlier, these values may not be perfect for your setup.

For the motor currents lets set them to 1400ma which is 80% of the rated max and see if it makes any difference.

M92 X400.00 Are we sure your X axis is 400 steps per mm?

Let's reduce the max speed, jerk, and accel for X as well.

Let's try these

M203 X3000
M201 X300
M566 X300
M906 X1400

Will input these right now.....

fcwilt

@wingtip said in Motors working then chatter before and after homing...:

i can comment them out but cant jog it, as stated z motors arent plugged in right now.

Well since the chatter occurs at the beginning of the homing and the end but the homing itself works fine the only difference between you jogging X and the homing file is the Z axis commands and they appear at the beginning and end of the homing file.

Thus my suggestion to see if they are the source.

Frederick

Phaedrux

Also, just to eliminate the file, you can send the homing commands manually line by line in the console. The important ones being.

G91 ; relative positioning
G1 H1 X-805 F400 ; move quickly to X axis endstop

wingtip

Ok... I have some good news and some bad news lol..... The good news is you guys are awesome and have saved me from losing my mind.

The bad news is im a stupid idiot.... The chatter is in fact coming from the one z motor that is connected. I had forgotten that one z motor was plugged into the duet board while the 2nd z motor is plugged into the duex expansion board. I only unplugged the ribbon cable of the expansion board to eliminate everything on it, thus forgetting the one z motor on the main board. and im going to guess that i have a crossed wire from the breakout boards to where it finally connects to the board causing the non moving motor.....

i feel like an idiot... as i said in my first video that was the only thing i had changed lol... so i should be able to bump all the speeds and current to the x motors back to where they were if i want... And now fix the z motors and finish the install of the probe.

Phaedrux

Makes perfect sense knowing that and watching the homing again.

Glad we could figure it out. And on the plus side, your config is a lot simpler now on RRF3. No more U and V axis and all that non-sense.