Well I'll be .... think of an adjective

This place is full of genius ... works ...

It's official - going senile ....

Still going to try the CURA and the 'modded' version, and ideamaker ....

Sorted - SSH route works a treat much appreciated.

It is probably best to earth bond the frame of any printer, not forgetting the bed as this deals with static electricity that is produced during operation, this allows it to sink to ground without going via your electronics.

I would not bond the frame to an isolated ground for this reason but a lot depends whether your power supply is an 'isolated' one or not - you may find its ground is already earth referenced if it isn't an isolated supply.

As for connecting cable shields / screens these really shouldn't be connected to an earth reference but bonded to the circuit ground. This topic could easily stray into RF generation and rejection and such, you absolutely must not ground a shield at both ends.

I think the part that many find difficult is that ground does not mean earth, ground is merely the reference point for the circuit itself, earth is something entirely different.

What is unfortunate is the standard of many low end PSU's, given the propensity of folk for seeking the cheapest they are likely to encounter some real nasty stuff that I believe isn't safe to use. I think a problem coming from this is that most people won't know how or be able to identify a poor PSU so 'erring on the cautious side is always preferred - if in doubt earth it.

My PSU for what it is worth is not part of, nor is it attached to the printer frame, yes my PSU chassis etc is grounded but it is not neutral referenced, so the AC it produces is floating and isolated. It is totally overengineered but that's the OCD in me.

(My PSU on the CoreXY is a Balluff BAE0003, on my Prusa I run a PULS SL20)

No complaints here, apology not needed, got into the RC stream, knew the risks, happy to help diagnose and fix.

I started work on a test plan but it is kind of hard to know what to test beyond normal user interraction, when things blow up as a result of previously functional code it is hard to know how to report it, harder to know the information needed to assist in the debug / analysis / remediation.

I find it frustrating and interesting - just sometimes it is more frustration - and even then more frustration at a lack of ability to trace through the fault.

Blunt question - Is it possible to seperate the apps such that loss of DCS does not prevent access to the web console, yes I know information won't be updating but a big red status flag 'No DCS Communication' or similar could be added. Make it possible to access diagnostic logs and still be able to edit .g files from the web gui. Possibly have some 'macro' to collect basic diagnostic information for submission.

I'm not a linux fan, I don't fully understand the code, I'm trying to understand, sometimes the frustration hits the keyboard.

You want me to do some tests just reach out, I think I'm getting pretty good at switching versions in and out, which is a big thank you to all that have stepped in and helped.

@jay_s_uk well I'll be - never had to do that before - but it worked - many thanks

Come now - you asked the questions, that's more than some do, so to say you know nothing is a little defeatist.

Electrickery is a subject that has it's share of complications for sure but nothing that can't be learned, you're aware enough to ask the correct questions so you do know something.

I'd keep the AC earth and DC grounds apart.

Power your DUET through a decent quality 12V or 24V DC Isolated power supply - Meanwell / Cosel aretwo brands that spring to mind that are pretty decent. Try to avoid the unknown cheapest you can find as it could be expensive in the long run.

I don't know that much about the CR10 and I'm not in Germany that often these days North or South, last trip was 4 years ago to Berlin.

What specifically is concerning you ? how do you power the CR10 currently ?

The way this week has gone so far you're not wrong ...

Just found this - just in case people thought moving air was easy ...

Why cooling fans are so hard, and some preliminary testing

Classic poor termination - keep those terminals tight - check regularly especially high current connections such as heaters.

No problem with OT, or jokes ... I can print the same part with 3 different slicers and the impact this has on the print quality / finish on the SAME printer is revealing. Slic3r and the Prusa offspring for instance put rubbish little dabs in places where a solid infil would make much more sense - added perimeters to overcome some of this nonsense. Simplify bridging is appalling, CURA lacks some finesse and is proving tricky to set up even using the same numbers from a successful profile in Slic3r ...

Could waffle all evening ... can already see a defect on the surface of a part that's printing - totally temperature related but if you get that bit correct the rest of the print suffers ....

@jay_s_uk well I'll be - never had to do that before - but it worked - many thanks

Updated the Raspberry Pi through usual route, All proceded normally except the reported version of the Web interface is 3.5.2 on the 'General' tab under settings.

There is also a warning about dissimilar software versions on the console "Incompatible software versions
The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors."

Done a forced re-install via the command line of the Pi and it says 3.5.3 is installed already then proceeds to overwrite 3.5.3 with 3.5.3 ...

I ran M997 S0 but that didn't do anything to resolve, I then took 3.5.3 direct from Github and manually wrote the version (extracted of course) to the SD card of the Pi.

No change - not sure what else to do now

Other than a mesh bed level every now an then I don't bother, you are limited to what you can do automatically anyhow depending on your bed mounts. Unless you use a kinematic mount the mount points are likely to be pretty rigid so offsetting the steppers could lead to binding. Once it is as level as you can get it mechanically it shouldn't change unless you abuse the machine / move it around etc - all depends how rigid things are, the more rigid you make it the more accurate things need to be.

The mesh bed level works slightly differently and attempts to compensate for bed inconsistencies - got to confess though I'm not entirely sure how Dave implements it.

Sounds like you did stuff right, you don't need G30, G30 simply tells the system to perform one probe. The previous poster is moving to the centre of his bed and probing he just has a macro to get there. I don't understand the G92 Z1 bit - G92 Z0 tells the system that wherever the nozzle is now in space that is Z=0. It is from that point that everything gets referenced for Z - no idea what G92 Z1 would do beyond telling the printer that the current nozzle position is exactly 1mm above the bed - pretty dangerous command if it is actually closer.

The nozzle shouldn't be at zero ever unless you deliberately put it there. The first height you see in status when laying down the first layer should be whatever your first layer height is - so what is it showing ?

You absolutely that the printer is correctly configured in the slicer - no Z offsets etc, absolutely sure that layer 1 isn't actually at 2.15 or something - the print is on the slicer bed when you slice it not elevated? - can you run preview in your slicer to see at what layer stuff appears.

Look for the first G1 Z in your print gcode - what does it say ? for a first layer of 0.15 the first G1 Z should be G1 Z0.150 or similar depending on your slicer.

Sorry if this all sounds a little basic but going for the complex first isn't always the best approach - if the printer can mesh level successfully and you seem to have a good trigger height I don't think it is the printer.

edit : Do not put G92 Z0 in ANY of your homing files - I think this is your problem.

You do not set Z using G92 when probing you use G30. G30 sets Z to the trigger height when it probes. You have no G30 ....

I think your homeall.g is messed up - there's no Z in there, your homez.g is also messed up -

This is my homez.g

; homez.g
; called to home the Z axis
G91 ; relative mode
G1 H2 Z4 F200 ; raise head 4mm to ensure it is above the Z probe trigger height
G90 ; back to absolute mode
G1 X152 Y152 F3000 ; put head over the centre of the bed, or wherever you want to probe
G30 ; lower head, stop when probe triggered and set Z to trigger height

my Homeall.g

; homeall.g
; called to home all axes
;

G91                     ; relative positioning
G1 H1 X-320 F1500 ; coarse home X
G1 X4 F360 ; move away from the X endstop
G1 H1 X-10 F250 ; fine home X

G1 H1 Y-320 F1500 ; coarse home Y
G1 Y4 F360 ; move away from the Yendstop
G1 H1 Y-10 F250 ; fine home Y

G1 H2 Z4 F200 ; raise head 4mm to ensure it is above the Z probe trigger height
G90                     ; absolute positioning
G1 X167 Y152 F2500 ; put head over the centre of the bed, or wherever you want to probe
G30 ; lower head, stop when probe triggered and set Z to trigger height

No worries, appreciated - you can always rely on users to do the unexpected. I never realy thought about the override file, never used it, suppose I should have realised what M501 actually did. It's one of those things you do early on then forget about - until it bites you .....

@chrishamm Confirmed - if I remove M501 the 'starting' becomes idle. if I add a config override but leave the M501 the starting becomes idle, it seems to be that the system expects to find a config override if M501 is used and gets stuck if it can't find it.

This is what impacts the status screen updating and the print going straight to 'complete' - I just verified it. The print however will continue and completes as it should.

@chrishamm I don't have an override file.

Journal contains nothing useful that I can see.

Dec 23 11:33:01 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:01 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/
Dec 23 11:33:01 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:01 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/
Dec 23 11:33:01 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0]
Dec 23 11:33:01 duet3 DuetWebServer[589]:       No endpoint found for GET request via /
Dec 23 11:33:01 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0]
Dec 23 11:33:01 duet3 DuetWebServer[589]:       No endpoint found for GET request via /
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       The file /index.html was not modified
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Server.Kestrel[34]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Connection id "0HM576Q0Q0EUL", Request id "0HM576Q0Q0EUL:00000001": the application aborted the connection.
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Sending file. Request path: '/index.html'. Physical path: '/opt/dsf/sd/www/index.html'
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request finished in 234.1646ms 304 text/html
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request finished in 234.1644ms 0 text/html
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/css/app.37435a82.css
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       No endpoint found for GET request via /css/app.37435a82.css
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       The file /css/app.37435a82.css was not modified
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request finished in 3.3812ms 304 text/css
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/js/app.166d29b4.js
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       No endpoint found for GET request via /js/app.166d29b4.js
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       The file /js/app.166d29b4.js was not modified
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request finished in 0.94ms 304 application/javascript
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/fonts/materialdesignicons-webfont.4187121a.woff2
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       No endpoint found for GET request via /fonts/materialdesignicons-webfont.4187121a.woff2
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/rr_connect?password=reprap&time=2020-12-23T11%3A33%3A1 application/json
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       The file /fonts/materialdesignicons-webfont.4187121a.woff2 was not modified
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       No endpoint found for GET request via /rr_connect
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request finished in 32.3736ms 304 font/woff2
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request finished in 12.2236ms 404
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/img/icons/favicon-32x32.png
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/img/icons/apple-touch-icon-152x152.png
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       No endpoint found for GET request via /img/icons/apple-touch-icon-152x152.png
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: DuetWebServer.Middleware.CustomEndpointMiddleware[0]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       No endpoint found for GET request via /img/icons/favicon-32x32.png
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Sending file. Request path: '/img/icons/favicon-32x32.png'. Physical path: '/opt/dsf/sd/www/img/icons/favicon-32x32.png'
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Sending file. Request path: '/img/icons/apple-touch-icon-152x152.png'. Physical path: '/opt/dsf/sd/www/img/icons/apple-touch-icon-152x152.png'
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request finished in 31.6052ms 200 image/png
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request finished in 31.6044ms 200 image/png
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/machine
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[5]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       CORS policy execution failed.
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[6]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Request origin http://10.100.254.252 does not have permission to access the resource.
Dec 23 11:33:02 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
Dec 23 11:33:02 duet3 DuetWebServer[589]:       Executing endpoint 'DuetWebServer.Controllers.WebSocketController.Get (DuetWebServer)'
Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
Dec 23 11:33:03 duet3 DuetWebServer[589]:       Route matched with {action = "Get", controller = "WebSocket"}. Executing controller action with signature System.Threading.Tasks.Task Get() on controller DuetWebServer.Controllers.WebSocketController (DuetWeb
Dec 23 11:33:03 duet3 DuetWebServer[589]: info: DuetWebServer.Controllers.WebSocketController[0]
Dec 23 11:33:03 duet3 DuetWebServer[589]:       WebSocket connected from ::ffff:10.100.0.4:52628
Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:03 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/machine/directory/0:%2Fmacros%2F application/json
Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
Dec 23 11:33:03 duet3 DuetWebServer[589]:       Executing endpoint 'DuetWebServer.Controllers.MachineController.GetFileList (DuetWebServer)'
Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Dec 23 11:33:03 duet3 DuetWebServer[589]:       Request starting HTTP/1.1 GET http://10.100.254.252/machine/file/0:%2Fsys%2Fdwc-settings.json application/json
Dec 23 11:33:03 duet3 DuetWebServer[589]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
lines 1-95/230 36%
pi@duet3:~ $ sudo journalctl -u duetcontrolserver
-- Logs begin at Wed 2020-12-23 01:17:01 GMT, end at Wed 2020-12-23 11:47:41 GMT. --
Dec 23 01:18:32 duet3 systemd[1]: Starting Duet Control Server...
Dec 23 01:18:34 duet3 DuetControlServer[398]: Duet Control Server v3.2.0-rc1
Dec 23 01:18:34 duet3 DuetControlServer[398]: Written by Christian Hammacher for Duet3D
Dec 23 01:18:34 duet3 DuetControlServer[398]: Licensed under the terms of the GNU Public License Version 3
Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] Settings loaded
Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] Environment initialized
Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] Connection to Duet established
Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] IPC socket created at /var/run/dsf/dcs.sock
Dec 23 01:18:35 duet3 systemd[1]: Started Duet Control Server.
Dec 23 01:18:35 duet3 DuetControlServer[398]: [info] Starting macro file config.g on channel Trigger
Dec 23 01:18:36 duet3 DuetControlServer[398]: [warn] M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 573C
Dec 23 01:18:36 duet3 DuetControlServer[398]: [warn] M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 341C
Dec 23 01:18:36 duet3 DuetControlServer[398]: [info] Finished macro file config-override.g
Dec 23 11:32:02 duet3 DuetControlServer[398]: [info] System time has been changed

@chrishamm it hasn't changed in a while now but it is attached here. config.g

Powered up this morning and still shows 'Starting' ...

Confirmed

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-RC1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956L2-G43S8-6JKD8-3SS6L-9B12H
Used output buffers: 1 of 40 (10 max)
=== RTOS ===

=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 63835/63835
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/1480-0
=== Duet Control Server ===
Duet Control Server v3.2.0-rc1