Hi, I use a duet Wifi + Duex5 (RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5) and I have settled up a COREXYU with the following:

• 2 stepper to drive Y
• 2 independents X axis (X and U)
• 3 stepper to drive Z

Everything works well and I have successfully configured X homing, U homing, and Y homing (in this case I split the Y axis in Y and V using M584). I'm using the same logic when I home the Z axis, and in this case I split Z in Z, W, A axis, all with optical endstops. Endstops work properly (tested in the Machine specific tab).

So here the issue: when I perform homeZ, when an axis reach the endstop (I think is the asis A), the board run into a loop and get resetted. Here the event log.

Last reset 00:12:21 ago, cause: software
Last software reset at 2020-06-16 16:11, reason: Stuck in spin loop, spinning module GCodes, available RAM 10636 bytes (slot 0)
Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f80f BFAR 0xe000ed38 SP 0x20003234 Task 0x454c4449
Stack: 00445465 00444466 61000000 a5a5a5a5 00445465 a5a5a5a5 20003258 200030f8 00000002 200048d4 00037740 20004ce8 2000177c 20003258 20004ce0 00000004 200030d0 20001790 20003258 200030c8 00000001 200032b0 4e49414d

here how I run the z homing:

G91 ; relative positioning
M584 Z2 W7 A8 P7 ; split Z motor control to Z1, Z2, Z3
G1 H1 Z-310 W-310 A-310 F900 ; move Z down until the endstop is triggered
G1 H2 Z7 W7 A7 F360 ; go back a few mm
G1 H1 Z-310 W-310 A-310 F360 ; move Z down until the endstop is triggered
G1 H2 Z7 W7 A7 F360 ; go back a few mm
M584 Z2:7:8 P4 ; back to combined axes
G90 ; absolute positioning
G92 Z0 ; Tell the firmware where we are

Any idea on what could be the issue?

For the benefit of the forum let me share that the issue has been solved. I did as you suggested and I used shieded cables for the endstops. thanks to everybody for the support!

Hi, I did what you asked.

on launching diagnostic, here the result:

25/9/2020, 08:07:56: M122: === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SJ-6J1FL-3S86L-18XHF
Used output buffers: 3 of 24 (8 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93956 of which 108 recycled
Exception stack ram used: 544
Never used ram: 10752
Tasks: NETWORK(ready,764) HEAT(blocked,1176) DUEX(suspended,160) MAIN(running,3736) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:04:28 ago, cause: power up
Last software reset at 2020-09-23 12:05, reason: User, spinning module GCodes, available RAM 10976 bytes (slot 3)
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: 5.4ms, max retries 0
MCU temperature: min 25.3, current 34.1, max 34.1
Supply voltage: min 23.8, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/9
Driver 1: standstill, SG min/max 0/0
Driver 2: standstill, SG min/max 64/254
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max 0/35
Driver 6: standstill, SG min/max 0/0
Driver 7: standstill, SG min/max 54/203
Driver 8: standstill, SG min/max 48/209
Driver 9: standstill, SG min/max not available
Date/time: 2020-09-25 08:07:55
Cache data hit count 809711122
Slowest loop: 120.08ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 156, MaxWait: 145019ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 19, completed moves: 19, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 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: 136.59ms; fastest: 0.00ms
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 0
  WiFi firmware version 1.23
  WiFi MAC address ec:fa:bc:2d:df:20
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 25456
  WiFi IP address 192.168.1.237
  WiFi signal strength -44dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

25/9/2020, 08:08:48: M98 P"config.g": HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

Then I uploaded the file you sent to me, and now I have the WDC 2.0.7 and finlly I see all hotends!!! This menas that my version of WDC was not correct?

Your help has been great, thanks!!

Ciao,
Marco

@marco_76 said in Multiple z motors homing with firmware 3.3:

]

Solved!
I changed the names of the pins: exp.e2stop --> duex.e2stop
So now the sensors for Z are the following and it is working fine

M574 Z1 S1 P"zstop+duex.e2stop+duex.e3stop"

thanks,
Marco

@dc42 Thank you. The issue was in the pin to be inverted. I used "!exp.heater5" and not it's working again.

As always you are top starts in supporting the community.

@dc42 thanks. After some tentative I think I understood the logic. It's working fine for my double motors for the Y axis (see at the end of the post the new config.g), but I still have problems for the Z axis.

other tests I did:

• with M119 I tried with only Z1 sensor activated, only Z2, only Z3, all together. I get Z: at min stop only when Z1 is activated, and when all sensors are activated (but of course in this case also Z1 is activated)
• leds in the duex board are working fine, if I activate a sensor I see the led changing status
• the only difference between Z1 sensor is that this is connected to the duet board, while Z2 and Z3 sensors are connected to E2 endstop and E3 endstop of duex
• I'm using optic sensors for all axes

I tried to launch the Object Model Browser in DWC but it is returning all empty. See here:

M409
{
"key": "",
"flags": "",
"result": {
"boards": [
{}
],
"directories": {},
"fans": [
{},
{},
{},
{}
],
"global": {},
"heat": {},
"inputs": [
{},
{},
{},
{},
{},
{},
{},
{},
null,
{},
null,
{}
],
"job": {},
"limits": {},
"move": {},
"network": {},
"scanner": {},
"sensors": {},
"seqs": {},
"spindles": [
{},
{},
{},
{}
],
"state": {},
"tools": [
{},
{}
],
"volumes": [
{},
{}
]
}
}

Here the new config.g

; Drives
M569 P0 S0 ; physical drive 0 goes backwards(X1) (X)
M569 P1 S0 ; physical drive 1 goes backwards(Y1) (Y)
M569 P2 S1 ; physical drive 2 goes forwards (Z1) (Z)
M569 P3 S0 ; physical drive 3 goes backwards(E1)
M569 P4 S0 ; physical drive 4 goes backwards(E2)
M569 P5 S1 ; physical drive 5 goes forwards (X2) (U)
M569 P6 S1 ; physical drive 6 goes forwards (Y2) (V)
M569 P7 S1 ; physical drive 7 goes forwards (Z2) (W)
M569 P8 S1 ; physical drive 8 goes forwards (Z3) (A)

M584 X0 Y1:6 Z2:7:8 U5 E3:4 P4 ; set drive mapping (number of visible drivers P)
M350 X16 Y16:16 Z16:16:16 U16 V16 I1 ; configure microstepping with interpolation for axis
M350 E8:8 IO ; configure microstepping with no interpolation with extruders
M92 X200.00 Y200.00 Z4260.00 U200.00 E1900.00:1900.00 ; set steps per mm
M566 X1000.00 Y1000.00 Z10.00 U1000.00 E6.00:6.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z500.00 U12000.00 E2400.00:2400.00 ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z20.00 U1500.00 E120.00:120.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 U800 E400:400 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 U-23 S1 ; set axis minima
M208 X321 Y308 Z275 U298 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"
M574 Y1 S1 P"ystop+e1stop"
M574 U1 S1 P"e0stop"
M574 Z1 S1 P"zstop+exp.4+exp.9" ; set endstops for Z (zstop), W (exp.4), A (exp.9)

@dc42
I confirm that if I use M950 S0 C"exp.heater5" doesn't work. I tired with M950 S0 C"exp.heater5" Q500 and it's working but with the small movement again. I checked the tech specs of the servo and should operate at 50Hz.

Hi, I just upgraded the firmware from 2.05 -> 3.0 -> 3.3
I have a configuration with a double independent extruders and 3 independent motors for z axis. The three Z axis have endstops.

here the problem

I tied to changed the configuration based on the online guide, but I have a strange behavior:

• Z1 -> if I trigger manually the endstop of Z1 it stop. This stop. This is the only axis working as expected
• Z2 -> if I trigger manually the endstop of Z2 it doesn't stop
• Z3 -> it doesn't move in the direction of homing (but the motor works. I tested this moving up & down after running G92)

I tried M119 when all Z are still not homed, and here the result, where it looks like doesn't see endstops for Z2 and Z3 (axis W and A)
Endstops - X: at min stop, Y: at min stop, Z: not stopped, U: at min stop, V: at min stop, W: no endstop, A: no endstop, Z probe: not stopped

For simplicity I extract here only the Z axis part of config.sys and the the extract of Z in the homeall.g

OLD configuration, which worked well:

Config.g
M569 P2 S1 ; physical drive 2 goes forwards (Z1) (Z)
M569 P7 S1 ; physical drive 7 goes forwards (Z2) (W)
M569 P8 S1 ; physical drive 8 goes forwards (Z3) (A)
M584 X0 Y1:6 Z2:7:8 U5 V6 W7 A8 E3:4 P4 ; set drive mapping
...
M574 X1 Y1 Z1 U1 V1 W1 A1 S1 ; set active high endstops

Homeall.g
M584 Z2 W7 A8 P7 ; split Z motor control to Z1, Z2, Z3
G1 H1 Z-310 W-310 A-310 F350 ; move Z down until the endstop is triggered
M584 Z2:7:8 P4 ; back to combined axes

NEW configuration on firmware 3.3

Config.g
M569 P2 S1 ; physical drive 2 goes forwards (Z1) (Z)
M569 P7 S1 ; physical drive 7 goes forwards (Z2) (W)
M569 P8 S1 ; physical drive 8 goes forwards (Z3) (A)
M584 X0 Y1:6 Z2:7:8 U5 V6 W7 A8 E3:4 P4 ; set drive mapping
...
M574 X1 S1 P"xstop"
M574 Y1 S1 P"ystop"
M574 U1 S1 P"e0stop"
M574 V1 S1 P"e1stop"
M574 Z1 S1 P"zstop+exp.4+exp.9" ; set endstops for Z (zstop), W (exp.4), A (exp.9)

Homeall.g
G1 H1 Z-310 F350 ; move quickly to X axis endstop and stop there (first pass)

@dc42 I tired but using S0 it is not even moving. At least with P0 was doing small angle movements. any Idea?

Hi, I just updated my firmware from 2.05 to the latest version 3.3
I have a duet wifi + duex configuration and I'm now doing all required changes.

I'm using a servo which was working fine with the old configuration. It is attached to the duex PWM pins. Here changes I did:

OLD Config.g
M307 H5 A-1 C-1 D-1 ; Disable the 5th Heater to free up PWM channel 3 on the Duex board
NEW Config.g
M950 P0 C"exp.heater5" ; map 5th Heater or PWM channel 3 on the Duex board

with the old configuration, to move the servo from 0 to 180 degrees I was just using M280 P0 S0, or M280 P0 S90. Now it is still moving, but the servo doing very small movements (about 10 degrees).

My servo is an MG996R

Thanks for your help.

Marco

Dear duet community, I did a quick prototype which is supposed to speed up the calibration of my 2 independent nozzles (the lockdown is probably having bad effects on me :). I use a pi camera on the bed, looking up, and image recognition on raspberry to detect the position of the first nozzle vs the second one. So far I developed a web server on raspberry which is guiding me in a simple 2 min process in 4 steps. It is very accurate as I measure 0.05mm and more. I was thinking that would be even easier by automating all the process by sending gcode directly from raspberry to duet wifi, simulating how the DWC is doing when you put manual gcode. How can I do this?

Next step would be to add a load cell to compare z offset...

I landed to the slice engineering mosquito heater 50W and should be compatible with E3D V6 (22mm x 6mm) . This will drive 2A per heater. Thanks for your support.

Hi duet team,
I'm trying to print at >100mm/sec but when I'm exceeding 60mm/sec I see the temperature of the heater block dropping. I have a setup with a dual e3dv6. So I would like to upgrade to the volcano heater block and use the e3d 80w heater cartridges.

So here the question: Is the duet wifi able to handle 2X 80W heaters? I'm running it at 24V so should be 6.6A overall. Also, I'm managing the heater of the bed with a switch so no load on the duet wifi.

Thanks,
Marco