Connection issue with 3.5-rc2
-
@e4d The panel of the temperature graph looks odd to me. Perhaps try to disable your ad-blocker (if any) and if that doesn't help, open the dev tools via F12 and check the JS Console for errors.
-
@chrishamm my adblocker is already disabled, here's the output of the dev console on 3 differents browser Chrome, Opera and Edge :
index.ts:420 TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'. at window.Node.appendChild (vue-fragment.esm.js:1:4055) at window.Node.insertBefore (vue-fragment.esm.js:1:3770) at Object.insertBefore (vue.runtime.esm.js:6311:16) at updateChildren (vue.runtime.esm.js:6800:29) at patchVnode (vue.runtime.esm.js:6913:21) at updateChildren (vue.runtime.esm.js:6787:17) at patchVnode (vue.runtime.esm.js:6913:21) at VueComponent.patch [as __patch__] (vue.runtime.esm.js:7081:17) at v._update (vue.runtime.esm.js:3769:25) at VueComponent.ne (vue.runtime.esm.js:3875:16)
-
@e4d Okay, the new version 3.5.0-rc.3 should have a bug fix for this error message, although I don't think it's the reason why DWC stays in "Connecting". Can you try to upgrade your SBC using
apt update
/apt upgrade
and check if that helps? -
@chrishamm thanks for the release, the error message is fixed in the dev console on the browser.
The connection issue was still there sadly. I identified that the issue is caused by the line
M141 H5
If I have it in the config.g file, impossible to connect and when I comment it I can connect on the board as usual. If I comment it on the config, power up and then write "M141 H5" in the console it goes on connection screen.
Is it a known bug or something new ? I can't figure out how to have the control on the heated chamber without using M141 to declare it. Is there a workaround or do you plan a bug fix soon ?
-
@e4d Is there any way you could provide a minimal config.g that lets you reproduce this problem? I just put
M141 H5
in my config.g and after a restart my machine came up as expected. -
This config let us reproduce the problem :
; Duet 3 Configuration File G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M669 K1 ; Set Core XY mode ;Bed M308 S0 P"0.temp0" Y"thermistor" A"Bed" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"0.out0" T0 Q10 ; create bed heater output on out0 and map it to sensor 0 M307 H0 R0.605 K0.237:0.000 D2.36 E1.35 S1.00 B0 ; enable PID mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S215 ; set temperature limit for heater 0 to 215C ;Chamber M308 S5 P"1.temp0" Y"pt1000" A"Chamber" T100000 B4725 C7.06e-8 ; Set thermistor M950 H5 C"1.out2" T5 ; Chamber heater M950 P17 C"1.out3" ; Chamber heater fan M307 H5 B0 S1.00 ; Bang bang tuning M141 H5 ; Define heated chamber M143 H5 S75 ; Set temperature limit for heater 5 to 70C M570 H5 P999999 T50 ; configure heater fault on H4
To test this I did :
- Put this config with "M141 H5" commented
- Access the DWC in Chrome browser
- Execute "M141 H5" in the console
- Refresh the webpage
-
@e4d Thanks! I could reproduce and fix it. The fix will be included in the next DWC version, so probably 3.5.0 stable.
-
@chrishamm thank you for your quick inputs on my issue. Do you have any timeline on the release of 3.5 stable ? I can't use an heated chamber in the meantime ?
-
-
-
@chrishamm it works well on my machines, thank you again for your time on my issue