Topics created by Steppenleguan

@Phaedrux thanks for the help, I added the home sequence and its working fine now Also I had the drives in the wrong order so the compensation was wrong at first, too.

@Steppenleguan said in Independent dual z axis with endstops - z homing not working:

@knuxvomica no they don´t.
Current state: G28 homing failed , and nothing happens
Before with a homez.g: The axis lifts 5mm, moves down then passes! the endstops and hits my frame when I don´t emergency stop...

As you can see I am using the M564 command to test the axis movements in advance (which works fine) but obviously I don´t have any homing , i.e. no printing possible

M564 H0 ;move without homing

@Phaedrux said in Independent dual z axis with endstops - z homing not working:

Please post your full config.g
Homing Z should be as simple as a G1 H1 Z move to move the z axis such that the endstops are hit.

You need G1 H1 Z-700 at the end of your homeall.g to home the Z axis. The same would be needed in homez.g

@alankilian I might have found the problem.
I checked the resistances of the 5V signal wires
from the breakout board to the stepper drivers again and I found one cable that has infinite resistance.
It seems like it is one of the dir+- cables. So that would explain why the motor is running but cannot change its director.

At first I was expecting it to be the crimps or the connectors, but it appears that even with new crimps the cable is corrupted.

I'm checking in again in the evening and take a new cable, measure the resistances and hope that this solves to problem.

...Would be nice to add a sensor somewhere...

On a second thought, even the ability to connect external temp sensors (I2C?) and monitor them in the Web interface would be useful. For example, I can stick one to the MCU and another to the PCB near the hottest or typical driver.

@steppenleguan the fan fuse (F2) is for V_in I think the board can have a Problem you can try to measure ohmic if you have a connection between the 5V Fan connector to a other point which has 5V(switch off the board before). Here you can get the schematic from The board [https://github.com/Duet3D/Duet-2-Hardware/blob/master/Duet2/Duet2v1.04/Duet2_1.04b_Schematic.pdf](Duet schematic) on page six you can see the Power selector for V-Fan

@droftarts Sorry, here, the M122. The system is moving by now. I just left out the resistor on the PUL+ and it worked. The speed is a bit lackluster and the homing doesn´t yet work, but ill find out tomorrow. Up until now, thanks a lot for your help!
You will also find homeall.g and homez.g

M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later Board ID: 08DJM-9178L-L2MS8-6J9DJ-3S46S-TVHUN Used output buffers: 3 of 24 (20 max) === RTOS === Static ram: 23460 Dynamic ram: 73604 of which 24 recycled Never used RAM 14992, free system stack 191 words Tasks: NETWORK(ready,217) HEAT(blocked,322) MAIN(running,449) IDLE(ready,20) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:06 ago, cause: power up Last software reset at 2021-03-04 15:53, reason: User, GCodes spinning, available RAM 14992, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 8,8,8 MCU temperature: min 29.0, current 31.4, max 31.8 Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, standstill, SG min/max not available 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-04 19:58:05 Cache data hit count 79494073 Slowest loop: 7.99ms; 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 10.2ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, 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 = 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 assembling a command 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: 30.24ms; 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 98:f4:ab:d1:e4:90 WiFi Vcc 3.40, reset reason Turned on by main processor WiFi flash size 4194304, free heap 25784 WiFi IP address 192.168.2.125 WiFi signal strength -59dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0

Homeall

; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Feb 28 2021 15:17:04 GMT+0100 (Mitteleuropäische Normalzeit) G91 ; relative positioning M584 Z2 ; Split Z into 2 (Z+U) G1 Z250 U250 F2000 H1 ; Move up to 250mm in the +Z direction. S1 to stop if endstop is triggered G1 H1 X-805 Y-805 F3600 ; move quickly to X or Y endstop and stop there (first pass) G1 H1 X-805 ; home X axis G1 H1 Y-805 ; home Y axis G1 X5 Y5 F6000 ; go back a few mm G1 H1 X-805 F360 ; move slowly to X axis endstop once more (second pass) G1 H1 Y-805 ; then move slowly to Y axis endstop ; G90 ; absolute positioning G1 Z-2 U-2 F600 H2 ; Move 2mm in the -Z direction - (I'm not sure what S2 is for?) G1 Z+3 U+3 F100 H1 ; Move slowly 3mm in the +Z direction, stopping at the homing switch M584 Z5:6 ; Join U to Z again (pay attention to drive numbers used) G1 Z-5 F3000 ; Move back again 5mm in the -Z direction G90 ; Back to absolute mode ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning

Homez

; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Feb 28 2021 15:17:04 GMT+0100 (Mitteleuropäische Normalzeit) G91 ; Relative mode M584 Z2 ; Split Z into 2 (Z+U) G1 Z250 U250 F2000 H1 ; Move up to 250mm in the +Z direction. S1 to stop if endstop is triggered G1 Z-2 U-2 F600 H2 ; Move 2mm in the -Z direction - (I'm not sure what S2 is for?) G1 Z3 U3 F100 H1 ; Move slowly 3mm in the +Z direction, stopping at the homing switch M584 Z5:6 ; Join U to Z again (pay attention to drive numbers used) G1 Z-5 F3000 ; Move back again 5mm in the -Z direction G90 ; Back to absolute mode

It also says it couldn´t find 0:/filaments , does this mean i should add a folder on the SD card with that name?