Duet dementia

droftarts

@Ethelred Sounds like a failing SD card. Connect via USB and send M122, and post the response. You should be able to test the SD card via USB too, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card

Backup the card to your PC. Then either reformat it, or replace it. Then copy the backup to the SD card and try again.

Ian

Ethelred

No joy - SDformatter. Copied full system back and exact same behavior.

Phaedrux

@Ethelred said in Duet dementia:

Copied full system back

To a new SD card, or the same one?

droftarts

@Ethelred said in Duet dementia:

M550 P# FOLLY ; Set machine name
...
M540 PBE:EF:DE:AD:FE:ED ; Set MAC address

That M550 command is wrong, and I don't know the effect of the format you have used. It should be M550 P"FOLLY".

M540 is also redundant, see https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m540-set-mac-address

On WiFi-equipped Duet boards (Duet 3 Mini 5+ WiFi and Duet 2 WiFi) the MAC address is unique and set on the WiFi Module so this command has no effect.

Please post the response to M122. Also the response to the SD card troubleshooting commands: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues

Ian

Ethelred

Reformatted old SD. Ethernet board. M122 and M39 appear ok to these old eyes.
console.txt

Phaedrux

Can you update your firmware/dwc/etc to 3.5.1?
https://github.com/Duet3D/RepRapFirmware/releases

droftarts

@Ethelred did you make the changes I suggested to config.g?

Ian

Ethelred

Changes made to config file as suggested and 3.5.1 update installed.
Strange behavior persists. !!!

Phaedrux

@Ethelred said in Duet dementia:

Reformatted old SD.

Do you have a fresh sd card to try?

Can you send M98 P"config.g" and report the results?

Ethelred

SD on the way - What would one do without Amazon ?

I'm in the dark as to "open file count", it's impact , and what to and how to mitigate it.

Phaedrux

@Ethelred said in Duet dementia:

Can you post your config-override.g?

Ethelred

@Phaedrux
Config-overide. Sorry to be so unresponsive but what with cleaning out and moving house priorities get confused. Hopefully new SD tomorrow.

O'RIDE.png

Phaedrux

@Ethelred said in Duet dementia:

Hopefully new SD tomorrow.

yes I'm curious to see if it makes a difference.

Phaedrux

Also, can you please post your tool change files if they exist?

tpre0.g tpost0.g

Can you upload the actual files as well for config.g, config-override.g, tool change files, etc?

Ethelred

@Phaedrux New, fast, big SD same behavior. No tpre0.g tpost0.g files.

I'm thinking a controller board glitch. Initial fail followed a perfect print with NO changes whatsoever. My problem (one of many) is that I'm electronically and software challenged. I'm tempted to buy a new board or take up golf.

config.g config-override.g

Phaedrux

Can you give a run down of the issues you're currently seeing?

Ethelred

Same as original post.. To recap
The printer homes normally. Don't know if thehoming offset leaves the nozzle in the correct location (no way to measure that). If, for example I command a simple G1 X100 the nozzle scoots away in an approximately 45 deg angle for perhaps 80-100mm and the Z ht looks to drop perhaps 20mm. If I reverse with a G1 X-100 it appears to return to the original position. Crazy.

droftarts

@Ethelred Because you have M501 at the end of your config.g, it's loading config-override.g:

; config-override.g file generated in response to M500 at 2024-02-17 17:01
; This is a system-generated file - do not edit
; Delta parameters
M665 L381.533:381.533:381.533 R214.834 H274.650 B140.0 X0.377 Y0.115 Z279.000
M666 X0.760 Y-0.369 Z-0.391 A0.00 B0.00
; Heater model parameters
M307 H0 R0.152 K0.097:0.000 D50.63 E1.35 S1.00 B0
M307 H1 R2.560 K0.469:0.016 D5.82 E1.35 S1.00 B0 V23.6
; Z probe parameters
G31 K0 P500 X0.0 Y-20.3 Z2.95
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

I think this bit must be causing problems:
M665 ... Z279.000

That's just wrong! It should be around zero, like the X and Y. Maybe calibration went wrong, and it's saved that. Try setting it to Z0, and/or redo the delta calibration and save it with M500, and see if it behaves after that.

Ian

Ethelred

Not so - M665H is the homing height distance from the bed in the case of a Delta printer.
Does no one think it just might be the Duet electronics? Are you monitoring this Mr. Crocker?

droftarts

@Ethelred I didn't say M665 H, I said Z! M665 Z is

Znnn Z tower position correction

See https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m665-set-delta-configuration

Definitely wrong!

Ian