ender 5 plus
i am working on an ender 5 plus with a duet wifi
but I have a problem
when I am home x, y I cannot go to the minus position only the plus position
but am already at end stops (right rear)
i'm still figuring out files
and independent z axes (P2 left z axes: P4right z axes)
Take a look at the following posts.
If you go through the steps outlined in those posts an identify where 0,0 should be, and then where the endstops are located physically and configured correctly in M574 then you can check motor direction so that -x goes to the left and -y goes to the front. Then the direction of the homing moves may need to be changed to move the correct direction to the endstops.
If you still can't figure it out, post your config and homing files.
I have been busy with it continue to have problems
the M569 drivers the driver rotation is good,
when i home x,y go to the good rotation right back corner
home x, y i can move them after when amhomeall.g send M564 S 0
home z is problems ;G28 Z
Error: Z probe already triggered at start of probing move
home all same problem first home x,y,z send m564
then i can do the home all axis
sorry for me bad english i translate with google translate
Post your config.g as well.
With 0,0 in the front left corner does -x go to the left and -y go to the front?
What firmware version are you using? Can you post the results of M122 as well?
in config.g I have M208 on x0 y0
home x, y is going in the right direction, but no response after home should send M564 S0
then I can move axes in dwc -x left and -y forward
Firmwareversie: 2.03 (2019-06-13b2)
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N8PS4-7JKFA-3S86L-9BABN
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93688 of which 0 recycled
Exception stack ram used: 452
Never used ram: 11252
Tasks: NETWORK(ready,468) HEAT(blocked,1236) MAIN(running,3744) IDLE(ready,160)
=== Platform ===
Last reset 01:51:45 ago, cause: power up
Last software reset at 2020-07-28 10:13, reason: User, spinning module GCodes, available RAM 11300 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 3.3ms, max retries 0
MCU temperature: min 34.3, current 34.5, max 34.8
Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/193
Driver 1: standstill, SG min/max 70/406
Driver 2: standstill, SG min/max 0/428
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max 0/428
Date/time: 2020-07-28 13:32:11
Cache data hit count 4294967295
Slowest loop: 75.94ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 167, MaxWait: 324808ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 35, completed moves: 35, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 200.39ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.23
WiFi MAC address 84:0d:8e:ad:73:9d
WiFi Vcc 3.42, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24904
WiFi IP address 192.168.178.19
WiFi signal strength -75dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
You should update your firmware to 2.05.1
Upload this zip file as is (do not extract it) to the /sys folder
i just updated to
Firmwareversie: 2.05.1 (2020-02-09b1)
home z is problems ;G28 Z
Error: Z probe already triggered at start of probing move
What type of Z probe are you trying to use?
Your homeall is setup to use a probe and then the endstop, which is not ideal. You also should not need to have a U axis at all. Your maxima is set to negative values and your endstops aren't configured for the right location.
Try making the following changes to your config.g homeall.g and homez.g files. You can copy and paste my text over yours.
; Configuration file for Duet WiFi (firmware version 2.03) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Fri Jul 03 2020 20:35:09 GMT+0200 (Midden-Europese zomertijd) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Ender 5+" ; 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 S0 ; physical drive 0 X M569 P1 S0 ; physical drive 1 Y M569 P2 S0 ; physical drive 2 Z LEFT M569 P3 S0 ; physical drive 3 EXTRUDER 0 M569 P4 S0 ; physical driver 4 Z RIGHT M584 X0 Y1 Z2:4 E3 ; Driver 0 For X, 1 for Y, Z=2:4 ; Motor remapping for dual Z M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80 Y80 Z1600 E105.00 ; set steps per mm M566 X900 Y900 Z60 E300 ; set maximum instantaneous speed changes (mm/min) M203 X180000 Y180000 Z1200 E12000 ; set maximum speeds (mm/min) M201 X600 Y600 Z60 E1000 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 I20 ; 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 X333 Y350 Z400 S0 ; set axis maxima ; Endstops M574 X2 Y2 S0 ; set active low and disabled endstops M574 Z1 S2 ; Set active high endstops ; Z-Probe M558 P1 H5 F300 T6000 B1 ; disable Z probe but set dive height, probe speed and travel speed G31 P500 X0 Y-45 Z0.855 ; Set Z probe trigger value, offset and trigger height M557 X60:300 Y30:300 S30 ; define mesh grid ; Heaters M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0 M143 H0 S100 ; set temperature limit for heater 0 to 120C M305 P1 T500000 B4723 C1.196220e-7 R4700 ; set thermistor + ADC parameters for heater 1 M143 H1 S300 ; set temperature limit for heater 1 to 300C ; Bed adjustment screw locations ;M671 X316:316:46:46 Y295:35:295:35 ; mark leveling screws at (316,295) (316,35) (46,295) (46,35) ; Fans M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off (part cooling) M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on (hotend) M106 P2 H100:101 T45:55 L0.3 ; set fan 3 value, pmw signal intersion and frequency. thermostatic control is turned on (case fan) ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 U0 ; 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 M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0
; homeall.g ; called to home all axes G91 ; relative positioning G1 H2 Z2 F6000 ;lower bed 2mm G1 H1 X355 Y355 F3000 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X-5 Y-5 F6000 ; go back a few mm G1 H1 X355 Y355 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X175 Y175 F6000 ; move to center of bed G30 ; lower head, stop when probe triggered and set Z to trigger height G1 X10 Y10 Z10 F6000 ; move Z to Z=1
With this new config file and homeall test to make sure the motors are still going in the correct direction. -x to the left, +x to the right, -y to the front, +y to the back. If the direction isn't like that you will need to reverse the motor direction in M569 for either axis.
M569 P0 S0 ; physical drive 0 X
M569 P1 S0 ; physical drive 1 Y
Once the machine is homing correctly with the probe you can then move on to doing bed tilt correction using this method.
i am using the DC42's IR sensor for z switch / probe
i am going to try your files from config.g and home files
This post is deleted!
now it works home is right back corner
- goes left + goes right
home = x330 y350
0,0 left front corner
Ok good, that sounds correct now.
Is the probe working?
probe works with height .
now I can find out further with homez.g
thanks for the quick responses
For your home Z, I would change it to just home the Z axis with the probe. Then use G32 which calls bed.g to do the tilt correction as described in the link I provided above. You'll need to add M671 command to your config.g that defines the position of the lead screws and then configure bed.g to probe at two locations close to the lead screws. The link describes it in more detail.
I've been working on the Bed leveling with multiple independent Z motors
Bed adjustment screw locations
M671 X-20: 370 Y0: 0 S2; leadscrew locations
(if this is correct left x-20/y200 right x350(max)/y200)
M561; clear any bed transform
G30 P0 X5 Y165 Z-99999; probe near a leadscrew left
G30 P1 X325 Y165 Z-99999 S2; probe near a leadscrew right
but after G32 only the left drops and does not rise after a few tries this is the result
Leadscrew adjustments made: -0.571 0.573, used points 2, deviation before 0.470 after 0.000
Leadscrew adjustments made: -0.320 0.350 , points used 2, deviation before 0.275 after 0.000
M98 P "0: / macros / G32 HOME"
Leadscrew adjustments made: -0.193 0.182, points used 2, deviation before 0.154 after 0.000
after each g32 left sinks and tilts the bed
what am I doing wrong?
Please post your entire config.g
Which Z motor driver is on which side of the bed? The order of the driver needs to match the order of the points to probe.
You must use the M671 command to define the X and Y coordinates of the leadscrews. The M671 command must come after the M584 command and must specify the same number of X and Y coordinates as the number of motors assigned to the Z axis in the M584 command; and these coordinates must be in the same order as the driver numbers of the associated motors in the M584 command. The M671 command must also come after any M667 or M669 command.
Can you post a video of it in action?
I try to uploud the movie but the files are too big
dropbox, or google drive, box, onedrive, youtube, vimeo, something like that.
oke i go try
Are you using a macro called G32 HOME? Or are you using just G32 (which calls bed.g)?
i tried both normal G32 (bed.g) and macro G32 same settings as bed.g