There really should be an unattended and repeatable build and preferrably CI for every software project. Does duet fw really require a ginormous interactive heap of Java to build?

My ender5 was down for a long time since the head got encased in plastic. I bought some new hotends and finally got it running again. Haven't had time to upgrade to v3 yet. I just want to get printing first.

A recursive GET followed by a git add/commit would give you a pretty nice rolling history along with backups.

Getting stiff and hard to start but not getting noisy does sound to me like contamination. I've noticed my hotend fan would really like to suck in any stray hair of filament hanging around the bed area. I expect dust will get in as well. Dust seems to be what usually kills fans in electronic devices. If they don't choke, then they may make it all the way to rattling old age.

Recursive wget (and probably curl, automated browsers and many download managers) would also work great with http. Almost certainly better since the protocol is far more sane than ftp. All that would be required is some url with an html page with one link per file. Or one page per directory for a whole tree.

Something that looks like the view you get when opening a directory or a web server served directory. Especially if you leave out sort columns or parent directory links so they don't need to be filtered out from the spider.

I finally found some time and energy to get back to the Ender. I had a few fans swapped, but otherwise things seem to work. I ran the PID tunings, leveled the bed and printed some small bits. First parts out of the Ender and Duet! It really is amazingly quiet for its movements but the full set of fans is still a lot of noise.

Next is figuring out parameters, pressure advance(?), speeds etc.

My PIDs ended up at: (edit: new therm values)

; Heaters
M307 H0 B0 S1.00                         ; Disable bang-bang for bed heater, set PWM limit
M305 P0 T98801 B4185 R4700               ; Set thermistor + ADC parameters for heater 0
M143 H0 S90                              ; Set temperature limit for heater 0 to 90C
M305 P1 T98801 B4185 R4700               ; Set thermistor + ADC parameters for heater 1
M143 H1 S230                             ; Set temperature limit for heater 1 to 230C

; Heater cal
; Heater 1 model: gain 355.8, time constant 112.4, dead time 5.0, max PWM 1.00,
; calibration voltage 24.1, mode PID, inverted no, frequency default
; Computed PID parameters for setpoint change: P11.2, I0.470, D39.5
; Computed PID parameters for load change: P11.

M307 H1 A355.8 C112.4 D5 V24.1 B0

; Bed cal
; Heater 0 model: gain 141.3, time constant 461.3, dead time 1.2, max PWM 1.00,
; calibration voltage 24.0, mode PID, inverted no, frequency default
; Computed PID parameters for setpoint change: P488.5, I20.825, D407.9
; Computed PID parameters for load change: P

M307 H0 A141.3 C461.3 D1.2 V24.0 B0

I presume that looks sane?

That's good. I'm aware of Eclipse and actually use it for some things in all kinds of strange versions. It's a fine tool for development, but not for builds or integration.

I've also seen so many compilers and tools get buried in licenses and obsoletion of platforms that it always lights up alarms to see some massive IDE been mentioned when something is supposed to get built.

There really should be an unattended and repeatable build and preferrably CI for every software project. Does duet fw really require a ginormous interactive heap of Java to build?

That looks like RJ-45 on the CAN? Is there a reason for such a large connector? I've used 4-pin RJ-11 in the past and that's already more than enough pins for CAN and would even carry a pair plus voltage and even ground if needed.

USB-C is indeed a minor nightmare unless you can get some sort of module for it with an interface chip and that would not be very cheap either way. Also, cables can be quite brittle unless you get very very good ones. Available functionality in full implementations is brilliant, of course.

I don't have much of a config yet. I might have managed to calibrate the extruder (E378.66) and fought with my network devices all day today. Maybe someone will have good answers if you can describe what the exact problem is.

I finally got everything back together and have enough configuration that homing, heating, cooling and all the other connections seem to be working.
Now I'll need to get on with calibrations and settings hunts and tests, but I'm hoping to have the printer back in running condition soon.

It is very cramped, but it's in there now. After this, I decided to flip the bottom cover so the fan is outside and drilled a hole for the fan wires. I'll need to print or otherwise make some blanking plates and plugs for the extra holes.