I have had the same kind of issue with 1.19.2, 1.19 is correct.

I had issues when I was running my bed compensation routine and I had it too when I was printing,
I always finish by being disconnected of the web interface when I print and I cannot reconnect to it.

The print continue without issue until it's done so it doesn't affect it

The only way to get back access to the web interface is by powering off / on the board,

I'll give another try to 1.19 soon.. with the 1yr old twins, time is missing

David,, I just downgraded back to 1.18.1 and everything is fine, no more unexpected reset

I ran the macro again and this time it failed just after its completion.

M122
=== Diagnostics ===
Used output buffers: 3 of 32 (6 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19beta4 running on Duet WiFi 1.0
Board ID: 08DAM-999TL-NL5T8-6J1DA-3SJ6P-T55BJ
Static ram used: 20356
Dynamic ram used: 95876
Recycled dynamic ram: 2552
Stack ram used: 1304 current, 3804 maximum
Never used ram: 8484
Last reset 00:00:13 ago, cause: software
Last software reset reason: User, spinning module Network, available RAM 7824 bytes (slot 0)
Software reset code 0x5001, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min -270.2, current 16.6, max 17.1
Supply voltage: min 11.2, current 11.6, max 11.7, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-06-03 09:31:52
Slowest main loop (seconds): 0.004088; fastest: 0.000030
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== 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
Code queue is empty.
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19-beta1
WiFi MAC address 5c:cf:7f:1b:3c:b8
WiFi Vcc 3.10, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39736
WiFi IP address 192.168.1.101
WiFi signal strength -63db
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

David,
I've flashed beta 4 yesterday on my corexy and the board is resetting by itself without any known reason.
Yesterday the printer reseted during a print that was running for less than 5 minutes and this morning I was running my bed compensation macro and it crashed again.

this is the m122 output.

M122
=== Diagnostics ===
Used output buffers: 3 of 32 (5 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19beta4 running on Duet WiFi 1.0
Board ID: 08DAM-999TL-NL5T8-6J1DA-3SJ6P-T55BJ
Static ram used: 20356
Dynamic ram used: 95876
Recycled dynamic ram: 2552
Stack ram used: 1304 current, 3804 maximum
Never used ram: 8484
Last reset 00:00:13 ago, cause: software
Last software reset reason: User, spinning module Network, available RAM 8484 bytes (slot 4)
Software reset code 0x5001, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0040080f, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min -270.2, current 16.4, max 16.7
Supply voltage: min 11.2, current 11.4, max 11.7, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-06-03 09:17:31
Slowest main loop (seconds): 0.004786; fastest: 0.000030
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== 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
Code queue is empty.
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19-beta1
WiFi MAC address 5c:cf:7f:1b:3c:b8
WiFi Vcc 3.11, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39864
WiFi IP address 192.168.1.101
WiFi signal strength -63db
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

@c310:

i got the inductive sensor LJ12A3-4-Z / BX . it needs 12v for operation.
http://3dtoday.ru/upload/blog/a06/797ea2c00b20a65725d6247ac01f7aba.png

As written in documentation, i put in 10k and 30k resistors.

http://3dtoday.ru/upload/blog/880/797ea2c00b20a65725d6247ac01f7aba.png

however, Z-probe connector duetwifi has only +3.3 volts pin and sensor does not work.

From where on the board i can take +12 volts for sensor so that sensor works and board is alive ?
perhaps there are other sensors allowing 10mm distance and +3.3 volts supply?

please advise!

I've the same kind of sensor (setup). I've wired the 12v input to the duet board power supply input (if you are using 12v…) .. any source of 12v will do the job.
Black and signal wire have been connected to one of the endstop connector. I don't remember which one and I don't have access to the printer right now

The important part is to make sure that your resistences lower the voltage to 3.3v to safely connect it on the endstop connector

@Sabagmn:

Just bought one of those from your early bird special.
Looking forward to trying it.
Planning on using that on a Hypercube Evolution that I am in the process of building.
Thanks for putting in the time and effort needed to develop such a product, and still making it easily available to everyone!

Sandro

@DjDemonD:

Couple of fresh results.

These are with a 20mm "Piezo20" module I am hoping to be able to sell soon, on a kossel XL.

This is the moving head test
Bed probe heights: -0.004 0.001 0.001 0.001 0.001 0.001 0.001 0.001 0.001 0.006 0.001 0.006 0.006 0.006 0.001 0.001 0.001 0.006 0.001 0.006 0.001 0.006 0.006 0.006 0.001, mean 0.003, deviation from mean 0.003

This is the stationary probing test:
Bed probe heights: 0.001 0.001 0.001 0.001 0.001 0.001 0.001 -0.004 -0.004 -0.004 0.001 0.001 -0.004 -0.009 -0.009 -0.009 -0.009 -0.004 -0.009 -0.009 -0.004 -0.004 -0.004 0.001 -0.004 0.001 -0.004 -0.004 -0.004 -0.004 -0.004 -0.004 -0.004 -0.004 -0.004 -0.004, mean -0.003, deviation from mean 0.003

Same here… I'll install it on my custom coreXY... I hope to get it soon

Thank you guys.. I report that I've the same behavior for m290. I guess tomasf explaination make sense

David,
I have an issue with this firmware version on my coreXY.

When I move my axes (X, Z and Y) everything looks fine

When I execute homeall it seems that the endstop logic is reversed or something else, i'm not able to home. I revedted to beta1 and it's fine.

Thanks

Hi,
I'm using the Auber Instruments MGR-1DD80D100 that DC42 recommend on the wiki and I've nothing to say about it.
It does its job perfectly, beside an almost imperceptible vibration caused by switching that doesn't affect anything.
I use it with the makerfarm 12v heatbed 12x12in