@msugar the last time we saw this error was some time ago, and it was caused by a particular antivirus program requesting very long filenames from the Duet because it assumed that the Duet might support OCSP (which it doesn't).
We changed the HTTP server in RRF 3.x some time ago to automatically return failure of the filename was longer than is sensible on a Duet. So upgrading to RRF 3.4.6 would get rid of the messages. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3 for an overview of the upgrade process.
@bernas Please post your config.g and response to sending M115 in the console. Also post your homeall.g and homez.g file, and pictures of your wiring at the Duet end and at the BLTouch.
M584 X0 Y1 Z2 E3 ; set drive mapping
...
M906 X2500 Y2100 Z1800 E1600 I30 ; set motor currents (mA) and motor idle factor in per cent
You are running driver 0 at 2.5A which is the maximum supported on your Duet 2. When running drivers at or near maximum current, fan cooling is required. Preferably, use a fan at the edge of the board, next to the VIN connector, to blow air across both sides of the board along the line of stepper drivers. See https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#cooling.
@Aitor The errors on printer 3 may indicate the SD card is failing, so try replacing that.
For printer 5, it may be the module is failing. Can you try reflashing the wifi firmware or even trying the new wifi beta firmware and see if it has any impact. If the SD card is old there as well, might be worth a change out.
@DariusR4 thats the SD card partition on the SD card in the pi.
What may be the case is that you're running an older version of the pi image that had logging turned on.
It may be worth backing up your config etc and flashing a new version of the image
@droftarts
From left to right the first two are Orange DuraMic PLA Plus and the third arrow is pointing to White Esun PLA+. Board is reinstalled. Taking it out (for a walk and cleaning) unfortunately did not solve the issue. Thanks again for pointing this out, without your keen eye and me blowing it on to a clean catch sheet I would have most likely not caught this.
@Phaedrux Puck.jpg
The part with the blue cap is the capacitive sensor, the part on the glass plate on the heatbed is the "puck/microswitch". Contact with the printhead triggers it...that works
@PXP11 I've made the build now, but my prototype is not ready, so I cannot test it. I posted you the binary, but I would prefer if I can test it next week before you damage something. I'll be out of office until Tuesday, then I can proceed.
The files are checked in in https://github.com/JoergS5/RepRapFirmware_robot
Duet 2 had compilation problems, I hope the memory is sufficient. => I can try to reduce the cache memory a bit more next week.
,...............Are the steps of the x-axis adjusted in the same way as with the extruder..........
No. Extruders are different because there are variables such as how far the teeth that grip the filament bight into it. With belts and pulleys, no such variables normally exist, so the calculated value based on known dimensions should be correct.