Ok, in that case any wya i can increase login for you guys and try to reproduce the issue again?

i did the correction to the endstops mannually because in the configurator i have the choice of low and high end and that is what i did....maybe there is something i did nt do
now i home all axis ......
i copied all my previous mumbers to the new config and i m checking the behaviour of the printer

thanks for your assistance .....untill the next problem....

@Elvis0z I expect it will remain a mystery... but I am happy that it works for you now!

@lukas-aurarum try adjusting the H value in you M558 command that sets up the probe. I think default is 5mm. The z axis will travel an equal distance in the negative direction as the H value. So it will move 10mm before it gives up with the default of 5mm.

My solution involved two "beam break" detectors space 30 mm apart mounted on the frame (near Z min) and a 30 mm tall "blade" mounted to the bed that broke the beams.

Fast movement until the lower beam was broken, slower movement until the upper beam was broken.

This was on v2 until the setting (being able to specify the input being used for the Z end stop) that allowed it to work was removed. I think that setting is back in v3.

Frederick

so just -b wasn't sufficient as pr the documentation?

which version of bossac were you using?

I think I solved it by reflash it by usb and hopefully evrything looks okay for 3.1.1 now.
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93888 of which 44 recycled
Exception stack ram used: 284
Never used ram: 8876
Tasks: NETWORK(ready,384) HEAT(blocked,880) MAIN(running,1912) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:05:26 ago, cause: software
Last software reset at 2020-03-21 18:43, reason: User, spinning module GCodes, available RAM 9980 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 32.3, current 32.5, max 32.8
Supply voltage: min 1.6, current 1.6, max 1.7, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2020-07-05 16:08:33
Cache data hit count 579235577
Slowest loop: 5.95ms; fastest: 0.09ms
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 1.0ms, write time 0.0ms, 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 = -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 200.80ms; fastest: 0.08ms
Responder states: HTTP(2) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8

WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.23
WiFi MAC address bc:dd:c2:33:b9:4b
WiFi Vcc 3.29, reset reason Unknown
WiFi flash size 4194304, free heap 23704
WiFi IP address 192.168.2.20
WiFi signal strength -46dBm, reconnections 0, sleep mode modem
Socket states: 2 2 0 0 0 0 0 0

See https://forum.duet3d.com/topic/17395/duet3-3beta12-error-duet3iap_sd_mb6hc-bin-not-found

@Toby194 said in Problems with Tools and Heater:

There must be a mistake in the Config tool.

No sure about that. When I generated a config it did have extruder 0. M563 P0 D0 H1 F0 To change that you'd have to select a different drive for the extruder from the drop down.

Thank You! It works now fine 🙂

@Phaedrux That did it, thanks for the help.

@morf33 Please ask them to exchange under warranty. You can direct them to this thread as authorization.

@barbarossa-cologne said in True Auto Level 4ZAxis.NOT Working:

but that shouldn´t be the problem... the nozzle is running out of the heatbed area.

That might be right for the positiv side.
But as far as I know, the grid defenition of
M557 X15:650 Y15:650 S60 in combination with the probe offset X20 and Y100
would result in a movement of the nozzle to X-5 and Y-85, which is outside of the minium limit. So the points are not reachable....

Thanks!
A bit worried about updating, so I'll hold off for now (have some things to print) and do it when being without a printer is less of an issue.

And S has been superseded by H in RRF 3

@TypQxQ said in Error: Timeout while waiting for transfer ready pin:

I also got this error.
CoreXY Duet3 6HC +3HC

My best guess is that there was a power brownout or a transient of some sort (static discharge?).

post removed - starting a new thread

@baird1fa said in Duet 3 RRF3 BLtouch:

it bet that internally that pin4,5,and7 are the only ones able to do a servo signal.

🎖

https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview#Section_IO

I only checked that io3.in was able to analoge in, my bad!

@barbarossa-cologne

What @bearer said. Plus you can limit the maximum Z speed by editing the value in M203 in your config.g file. With short layer change moves, you'll never reach this speed unless it is set really low and you have very high accelerations.