bump? still having this issue

Hey all,

I've just returned to my printer having finally got the right PSU.
I have the duet 085 with ethernet, and i had already done all my configurations, but now when i turn on the printer (hooked up to ethernet) the web interface is not loading at all, i simply get a 404 error.

I checked if it was recognized in the network via the router and it shows up there with the ip.
When i try connecting to the ip nothing loads. I have tried a different duet and the same issue occurs, also tried multiple sd cards.

I tried hooking up usb but it won't show up in devices at all so connecting trough usb was not possible for me either.

Does anyone know how to resolve this issue?
Let me know if you require more info.

Okay i have updated the firmware (just wondering is there another/newer version of dwc? running 1.22.6)
So far it seems like it keeps reading correctly, is there a way to keep checking if the sd card can be read every x seconds, without having to be constantly checking manually

For some reason it took a while for it to happen again, but here is the log from M122
This is with a different SD card (a new one from SanDisk) and the same happens.

=== Diagnostics ===
Used output buffers: 2 of 32 (21 max)
=== Platform ===
RepRapFirmware for Duet version 1.21 running on Duet 0.85
Static ram used: 44844
Dynamic ram used: 40964
Recycled dynamic ram: 208
Stack ram used: 1192 current, 5380 maximum
Never used ram: 6908
Last reset 00:02:13 ago, cause: power up
Last software reset at 2020-07-28 13:35, reason: User, spinning module GCodes, available RAM 6956 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00438000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 40.9, current 42.6, max 42.7
Date/time: 2020-07-28 15:54:00
Slowest main loop (seconds): 0.050156; fastest: 0.000104
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 10, completed moves: 10
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Free connections: 15 of 16
Free transactions: 23 of 24
Locked: 1, state: 4, listening: 0x20071bf8, 0x0, 0x0

Hi there,

I'm building a 3d printer using the duet 085 which i had still laying around, and am using the dwc too, i noticed though that it often happens that i get the error "can't read homex.g" for example, i then have to reset the machine for it to work correctly again.
Is this a hardware problem, or sd card problem or something else?

Also when using dwc it often has issues showing current states (for example having to refresh the page to see current temperatures) is there any cause/solution for this?

Yup my bad, it works now! (haven't tested with the newest version of Cura yet though)

okay, i changed the config to reflect this change, but still having the same issue, right now it also happened with the older cura's gcode.
It seems to not even be powered, might it help to include the extruder mapping in each M584?

EDIT: Never mind this comment, forgot to change my homing code, i'll be back after this!

I did some more testing, and a had a gcode made in the newer version of cura, because of the M106 command missing the P parameter, but it only fails on that motor with a file from this version of cura, before i used Cura 15.04.6 and in that version it doesn't have the problem with the motor

i do reassign the extruder in config.g at the end of the file

I'm currently only reassigning the axes in the homez.g file, and when I home manually everything is fine, only when i print a gcode it fails when homing.
Do i need to reassign the extruder everytime?