Setting up Duet for a diy 3d printer
-
Hi everybody.
I'm working on a 3d printer, it dual z axis with endstop micro switches, X and Y axis are hopefully sensorless... I on the other hand have no background in programing what so ever. The thing is i'm having hard time homing my Y and X axis from a random position. Can please someone take a look at my nonsense and push me at the right direction.
-
Please post some more details.
What are the motors? Do you know the specs?
What kind of printer kinematics?
Send M122 in the gcode console and post the results here so we can see which Duet board and firmware you are using.
Post your config.g and homing macros so we can see what it's currently trying to do.@4thddoughnut said in Setting up Duet for a diy 3d printer:
The thing is i'm having hard time homing my Y and X axis from a random position.
What does this mean? What commands are you sending and what exactly happens? What were you expecting to happen?
-
at the moment i'm using anet a8 motors except on the x axis i have a wantai motor , because i'm cheap, and the Psu is 12 volt. both z axis motors have endstop switches. Right now i'm fooling around with macros for homing x and y axis to prepare the code for actual homing commands.
The config.g looks like this; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2:4 E3 ; Set Z motors on drives 2 and 4
M671 X-43.0:309.0 Y137.5:137.5 S4 ; Set the Z motor relative locations
;M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z400.00 E100.00 ; set steps per mm
M566 X600.00 Y600.00 Z18.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z100.00 E10000.00 ; set accelerations (mm/s^2)
M906 X700 Y400 Z500 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0:250 Y0:215 Z-0.1:205
;M208 X-5.5 Y-10 Z0 S1
;M208 X-33 Y-10 Z0 S1 ; set axis minima
;M208 X230 Y206 Z190 S0 ; set axis maxima; Endstops
;M574 Z1 S1 ; set active high endstops
M574 Z1 S1 P"zstop+e1stop" ; configure active-high endstops for low end on Z via pins zstop and e1stop
M574 X Y S3 ; set endstops controlled by motor stall detection
M915 X Y R0 F0
; Z-Probe
;M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
;M557 X20:200 Y20:200 S40 ; define mesh gridM122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L4MSJ-6J1FA-3S46R-TS3YP
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72480 of which 72 recycled
Never used RAM 16068, free system stack 173 words
Tasks: NETWORK(ready,212) HEAT(blocked,366) MAIN(running,449) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:10:08 ago, cause: software
Last software reset at 2021-03-23 11:04, reason: User, GCodes spinning, available RAM 16068, slot 2
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 28.3, current 28.8, max 29.2
Supply voltage: min 12.3, current 12.5, max 12.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 5000, standstill, SG min/max 0/232
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
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-23 11:14:45
Cache data hit count 741516237
Slowest loop: 29.38ms; fastest: 0.17ms
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.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 13005ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 3, completed moves 3, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 = -1 -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: 63.75ms; 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 84:f3:eb:ea:b2:80
WiFi Vcc 3.39, reset reason Power up
WiFi flash size 4194304, free heap 26344
WiFi IP address 192.168.0.26
WiFi signal strength -46dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
x homing macro
M400
M913 X70 Y70 ; drop motor current to 70%
M400 G91; relative positioning
G1 H2 Z10 F12000 ; lift Z relative to current position
G1 H1 X-320.5 F10000 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F12000 ; go back a few mm
G1 H1 X-320.5 F7000 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-10 F6000 ; lower Z again
G90 ; absolute positioning
M400
M913 X100 Y100 ; return current to 100%
M400 - WiFi -
-
all is good, separate axis homing is now all good, guess i had to take a break from this
... but now i have to figure out how the homeall.g should look like for my particular printer. -
well, for the start of an endless beginning here are my homing files.
homey.g homex.g homez.g homeall.gWould be super helpful if someone could take a look and give some advice. since i'm working on this project with determination and frustration hand in hand, i'm not willing to give up on it any time soon
-
Glad you figured it out. The homing files look ok.
