Motors working then chatter before and after homing...
-
ugg, one thing at a time lol... Why would the motor/motors work fine then chatter before homing and after homing?
-
@wingtip said in Motors working then chatter before and after homing...:
Why would the motor/motors work fine then chatter before homing and after homing?
Video of the behaviour? Bad connection at the motor? binding?
I vaguely recall the previous thread where we got your dual X axis going. It's been a while though, and in the meantime it's gotten a lot easier to do with RRF3 as Veti says.
Since you are picking things up again almost with fresh eyes, it might be a good idea to go through the update to RRF3. It would simplify the homing process for multiple independent motors per axis greatly.
For motor mapping
M584 X0:3 Y1 Z2:5 U3 V5 E4
would become
M584 X0:3 Y1 Z2:5 E4For axis minima
M208 X0 Y0 Z0 U0 V0 S1
would become
M208 X0 Y0 Z0 S1For axis maxima
M208 X800 Y500 Z400 V400 U800 S0
would become
M208 X800 Y500 Z400 S0For x endstop
M574 X1 S0
would become
M574 X1 S1 P"!xstop+!e0stop"For y endstop
M574 Y1 S0
would become
M574 Y1 S1 P"ystop"You could use dual endstops for Z if you wanted, or just use the probe.
You no longer need the endstops defined for U or V.
In these commands you could remove the references to U and V entirely.
M350 X16 Y16 Z16 U16 V16 E16 I1 ; configure microstepping with interpolation M92 X400.00 Y80.00 Z400.00 U400.00 V400.00 E415.00 ; set steps per mm M566 X600.00 Y600.00 Z12.00 V12.00 U600.00 E120.00 ; set maximum instantaneous speed changes aka jerk speed(mm/min) M203 X7200.00 Y7200.00 Z180.00 V180.00 U7200.00 E1500.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 V20.00 U500.00 E10000.00 ; set accelerations (mm/s^2) M906 X1200.00 Y1200.00 Z1400.00 V1400.00 U1200.00 E1200.00 I30 ; set motor currents (mA) and motor idle factor in per centAnd the z probe, heaters, fans, tools, etc would need to be replaced as well.
Here's what the entire new config would look like.
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Mar 03 2021 15:26:56 GMT-0600 (Central Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M569 P4 S0 M569 P5 S1 M584 X0:3 Y1 Z2:5 E4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation 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 M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X230 Y210 Z200 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!xstop+!e0stop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B3950 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue T0For the homing files you can then remove the references to U and V entirely.
As for updating, If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
That will get your firmware and DWC up to date. -
ok i updated to the latest via your steps good sir. Next?
@Phaedrux said in Motors working then chatter before and after homing...:
Video of the behaviour? Bad connection at the motor? binding?
I did post a video in the original post. It's not a bad connection. Theres something different from normal movements and when its homed as you can see in the video.
EDIT: When i run the M115 it does say in the dwc its updated to the 3.2.2 but when i download the g files the top still says generated by RepRapFirmware Configuration Tool v2.1.1
also the panel due shows these errors:
m587 failed to add ssid to remembered list HTTP is enabled on port 80 FTP is desabled TELNET is disabled Error: M574 endstop type 0 is no longer supported. Use type 1 and invert the input pin instead. Error: M574 endstop type 0 is no longer supported. Use type 1 and invert the input pin instead.
WiFi module is connected to access point davet, IP address ********** -
@wingtip said in Motors working then chatter before and after homing...:
EDIT: When i run the M115 it does say in the dwc its updated to the 3.2.2 but when i download the g files the top still says generated by RepRapFirmware Configuration Tool v2.1.1
M115 is correct. The text in the config files is just telling you what version of the config tool was used to make the config originally.
@wingtip said in Motors working then chatter before and after homing...:
Error: M574 endstop type 0 is no longer supported. Use type 1 and invert the input pin instead. Error: M574 endstop type 0 is no longer supported. Use type 1 and invert the input pin instead.
This means you should use the config.g I posted above to get the correct syntax for RRF3.
@wingtip said in Motors working then chatter before and after homing...:
m587 failed to add ssid to remembered list
You have a command in your config.g to add the SSID to the wifi module, but you shouldn't. It only needs to be sent once and then it's saved in the module itself. So remove any M587 from config.g.
The rest is all normal.
-
I've uploaded the config file but not going to do anything yet till i ask a question. What should my home x and home all look like under this new version 3 stuff since i had it set to split the axis then rejoin them..?
Thank you for the assistance so far.
-
@wingtip said in Motors working then chatter before and after homing...:
What should my home x and home all look like under this new version 3 stuff since i had it set to split the axis then rejoin them..?
@Phaedrux said in Motors working then chatter before and after homing...:
For the homing files you can then remove the references to U and V entirely.
Since U and V don't exist anymore you only have to home them as if it was a single axis with a single motor. The main difference for RRF3 is that the endstops are defined to use 2 switches and it will continue to move the axis until both switches have been hit. It's much simpler than it was before.
-
-
@wingtip no. You wouldn't need m584 in the homing files at all and you would only need movement for x y z.
-
ok i tried to home x and immediately got an error something about a G1 S1 so i immediately shut down the power before it got to the end stops in case it wouldnt stop... here is my current home x settings
-
G1 S2 Z5 F6000
Change the S2 to H2 and any S1 to H1 in your homing files.
That is another change between RRF2 and RRF3. The S is now used for laser power. So H is now used for homing moves.
-
ok, its working using this new reprap 3 coding , HOWEVER, i still have the same issues. The motors move the gantry just fine. But the moment i hit home x, the motors chatter a few seconds, then move to home and after the second hit of the endstops it chatters again for a few seconds then stops... it only does it during homeing... any other time the motors move nice and quiet as they should.
Highly modified FT5 R1, ATX supply, mosfet w/silicone heat pad, bmg ext, TMC2600 drivers, and my custom quad z mod with 4 lead screws and custom cut new upper panels and bed, and using the dual z endstop mod. New project is 800x500x500z printer.
-
Video?
@wingtip said in Motors working then chatter before and after homing...:
The motors move the gantry just fine.
How are you moving the motors when it works if it's not homed yet?
Do the axis move ok by hand with the duet powered off? (do it slowly)
In the gcode console, can you send M122 and M98 P"config.g" and post the results here?
-
@Phaedrux said in Motors working then chatter before and after homing...:
Video?
@wingtip said in Motors working then chatter before and after homing...:
The motors move the gantry just fine.
How are you moving the motors when it works if it's not homed yet?
Do the axis move ok by hand with the duet powered off? (do it slowly)
M564 S0 H0 ; allows movement of non homed axis for testing, and yes the axis move fine with the duet powered off. let me take a short short video
-
@wingtip said in Motors working then chatter before and after homing...:
ok, its working using this new reprap 3 coding , HOWEVER, i still have the same issues. The motors move the gantry just fine. But the moment i hit home x, the motors chatter a few seconds, then move to home and after the second hit of the endstops it chatters again for a few seconds then stops... it only does it during homeing... any other time the motors move nice and quiet as they should.
Sounds like your endstops may not be working.
The G1 H1 commands specify a max distance they will move trying to reach the endstop. When the endstop activates the movement stops otherwise the movement may continue to the limit of the axis.
Unrelated to that you have a command in your config.g file M574 Z1 S2 - that is invalid and not needed all at the same time.
From the docs:
Snnn 1 = switch-type (eg microswitch) endstop input, 2 = Z probe (when used to home an axis other than Z), 3 = single motor load detection, 4 = multiple motor load detection (see Notes).
-
While im waiting for the video to render, the code for the z axis is irrelevant right now as i have them unplugged. As for the comment about the endstops. both end stops trigger and can be seen in the dwc changing states... also, why would the motor chatter before it even moves and gets anywhere near the endstop...? You will see in the video and maybe understand better.... just waiting for my slow computer to render this so i can upload it to youtube and wait for it to process it , then post the link here...
-
@wingtip said in Motors working then chatter before and after homing...:
While im waiting for the video to render, the code for the z axis is irrelevant right now as i have them unplugged.
I only mentioned it because the configurator often inserts that M574 Z1 S2 command even though it is incorrect.
why would the motor chatter before it even moves and gets anywhere near the endstop...?
It will certainly help to see the video. The only thing I have experienced like that affected all motor movements - not just homing.
Could you post the relevant homing file?
Thanks.
Frederick
-
-
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?
-
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
- WiFi -
-
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?
