Well done , similar to my DBot, but i've gone for the dual z motors. I like your print carriage \ cooling fan parts, have you published them anywhere ?

I tried a Titan Aero, but just couldn't get it to print nicely, so I've reverted to a normal Titan, combined with a Precision Piezo, which gives great prints.

It's by design of of the way IP networks operate.

When a device boots-up, if it has been given a static IP address, it will always use that address.

If it hasn't been given an address it will try and contact a DHCP server, which will give it an address, from a pool of address it has been configured for. Depending on your network configuration, but normally for home use, this will be the router that you use to connect to the internet, which unless you know how to make some advanced configuration changes, will be 'factory set' for the pool, to the local subnet of 253 possible hosts (computers).

So there are 2 ways to always get the same IP address:

1. Assign a static address in the DWC configuration, which could have knock on effects whereby the DHCP server tries to assign the same address to another device that connects to your network. this risk can be mitigated by assigning an IP address 'high-up' in the subnet range, e.g. if your IP address range is something like 192.168.1.1 through to 192.168.1.254, then assign an address in the 250's

2. Assign reservations on the DHCP server, such that when the MAC address of your DWC device requests an IP address it is always given the same address.

Try removing\comment out the

M574 Z1 S2 line, I found I didn't need it for my Precision Piezo z-probe , i.e.

M574 X1 Y2 S0 ; Set active low endstops

M558 P8 I1 R0.4 H5 T24000 F200 ; Set Peizo - P probe type, I Invert, R recovery time, H dive hight, T inter-probe-point speeds, F Probing Speed

DWC - Duet control web pages & sorry I should have taken in what you've written...

So I take it, that at the fourth point the probe hits the bed ??

FYI, as it looks like you are still on RRF2, if so, this was my setting for that version (which worked well)

M558 P8 I1 R0.5 H5 T24000 F250 A3 S0.08 ; Set Peizo - P probe type, I Invert, R recovery time, H dive hight, T inter-probe-point speeds, F Probing Speed, 3 Dives , S calculated difference

Thank You

It's by design of of the way IP networks operate.

When a device boots-up, if it has been given a static IP address, it will always use that address.

If it hasn't been given an address it will try and contact a DHCP server, which will give it an address, from a pool of address it has been configured for. Depending on your network configuration, but normally for home use, this will be the router that you use to connect to the internet, which unless you know how to make some advanced configuration changes, will be 'factory set' for the pool, to the local subnet of 253 possible hosts (computers).

So there are 2 ways to always get the same IP address:

1. Assign a static address in the DWC configuration, which could have knock on effects whereby the DHCP server tries to assign the same address to another device that connects to your network. this risk can be mitigated by assigning an IP address 'high-up' in the subnet range, e.g. if your IP address range is something like 192.168.1.1 through to 192.168.1.254, then assign an address in the 250's

2. Assign reservations on the DHCP server, such that when the MAC address of your DWC device requests an IP address it is always given the same address.

It's probably just my system, & I looked on the release notes, to see if there was anything, but....

I've had this occur on 3 occasions now, and only since updating to RC11, that the printer appears to be fully working, and can run everything from the Panel Due, but the web\network interfaces appear to have gone into a 'hibernation' state where no browser can connect, neither will the Duet respond a ping\telnet etc.

This appears to occur approx. 20 mins following a print, and the only way I can get back to a contactable system is either issue a 'STOP' command, on the Panel Due, or a power cycle.

No changes have been made to the Config files.

M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC11 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6J1F2-3SD6L-9JZHXUsed output buffers: 3 of 24 (20 max)
=== RTOS ===
Static ram: 28060
Dynamic ram: 93204 of which 44 recycled
Exception stack ram used: 256
Never used ram: 9508
Tasks: NETWORK(ready,176) HEAT(blocked,1228) MAIN(running,1828) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:02:46 ago, cause: software
Last software reset at 2020-05-04 20:32, reason: User, spinning module GCodes, available RAM 9212 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
MCU temperature: min 31.8, current 33.0, max 33.8
Supply voltage: min 24.2, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-05-04 20:35:00
Cache data hit count 305150093
Slowest loop: 146.97ms; fastest: 0.13ms
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 3.8ms, write time 44.9ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.0
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 233.11ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
Interface state active, link 100Mbps full duplex
=== DueX ===
Read count 0, nan reads/min

Thank you David, putting M143 after M140 sorted it, & I'll raise a new topic for the PanelDue G32 reporting issue.

Getting there, if I run my multi G32 macro from the PanelDue, I get the final 'run' output on the PanelDue, console window, but it is missing out the previous 6, and still no output in the DWC console window.

And I still can't Bed tune to 150 e.g.

21/04/2020, 14:47:25 M303 H0 P1 S150
Error: M303: heater 0 target temperature must be no hiher than the temperature limit for this heater (125.0C)

with my M143 setting way above the target (testing setup only)

; Bed
M308 S0 P"bedtemp" Y"thermistor" A"Bed" T105000 B4138 C0 ; 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
M143 H0 S180 ; set temperature limit for heater 0 to 180C
M307 H0 B1 ; enable bang-bang mode for the bed heater
M140 H0 ; map heated bed to heater 0
M144 S1 ; set bed 'Active'

Yes I have, i.e.
; Bed
M308 S0 P"bedtemp" Y"thermistor" A"Bed" T105000 B4138 C0 ; 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
M143 H0 S150 ; set temperature limit for heater 0 to 140C
M307 H0 B1 ; enable bang-bang mode for the bed heater
M140 H0 ; map heated bed to heater 0
M144 S1 ; set bed 'Active'

I re-flashed it & now its at least letting me get to 125, but I'd really like to get to 150.

As dc42 announced PanelDue 1.24, I've also updated my PD 5, but one thing I've noticed, and to be fair it was in earlier versions, but running a multi G32 macro from the PanelDue, runs everything ok, but where I'd like to see the output and changes, on the console of the PanelDue at least, but it also doesn't show in the console of a DWC which was already connected.

Have the default settings for Tuning the bed changed, as I'm trying to M303 the bed for 125 degrees, but it doesn't allow anything above 80 ??

@FelixH

A good starting point would be a flat bed, to this end I purchased a cast aluminium plate also known as 'aluminium tooling plate' 10mm thick, e.g. https://www.clickmetal.co.uk/aluminium-tooling-plate

It's not cheap, but you will get a guaranteed flat surface, and you'll need to use a better bed heater (I use SSR mains driven) with a different thermistor, unless you want to wait for the bed to heat...

I've just gone away from stick down PEI sheets, as they are a pain in the butt when trying to fix it to a 320x320 mm cast Aluminium sheet....

Instead I've gone for a "Two Trees" 310x310 mm magnetic removable spring steel, pei sheet... much much easier to work with, & when hot PETg sticks well, just have see how long it holds for.

D-Limonene, Iso-Propyl-Alcohol (IPA), or Evo-Stik Adhesive cleaner, take your pick....

Leave any of these to soak into the adhesive, the gently scrape with a plastic scraper