DWC stays in "starting" status
-
I just installed a duet3 6HC board with raspberry 3 as SBC.
I've updated and upgraded from the SBC.
Nevertheless when I start the boards, the DWC stays in "starting" status, the DWC is responsive, but has nothing defined (no tool, no thermistor...)
I tried to put a command in the console, it never responds anything
I tried from the RPI and I have a message "[warn] Incompatible firmware, please upgrade as soon as possible" when starting DCS (although I can see from the console the firmware is 3.4.6)
I also tried to send M115 through CodeConsole, and I got nothing back...Any hint of something I may try to solve it ?
-
@Jerome IIRC there was an issue with that build and updating in SBC mode. You're best off bringing the board to 3.4.6 using bossa and then continue in SBC mode
-
@Jerome Try to send M997 and check if that helps.
-
undefined Jerome marked this topic as a question
-
Unfortunately M997 gives no answer in CodeConsole or directly in the console on DWC (looks like run forever)
If it may help here is the answer of journalctl -fu duetcontrolserver :
févr. 12 14:33:34 duet3 DuetControlServer[451]: Duet Control Server v3.4.6
févr. 12 14:33:34 duet3 DuetControlServer[451]: Written by Christian Hammacher for Duet3D
févr. 12 14:33:34 duet3 DuetControlServer[451]: Licensed under the terms of the GNU Public License Version 3
févr. 12 14:33:35 duet3 DuetControlServer[451]: [info] Settings loaded
févr. 12 14:33:36 duet3 DuetControlServer[451]: [info] Environment initialized
févr. 12 14:33:36 duet3 DuetControlServer[451]: [warn] Incompatible firmware, please upgrade as soon as possible
févr. 12 14:33:36 duet3 DuetControlServer[451]: [info] Connection to Duet established
févr. 12 14:33:36 duet3 DuetControlServer[451]: [info] IPC socket created at /run/dsf/dcs.sock
févr. 12 14:33:36 duet3 systemd[1]: Started Duet Control Server.
févr. 12 14:33:36 duet3 DuetControlServer[451]: [info] Starting macro file config.g on channel Trigger -
@Jerome what firmware version is on the mainboard? connect to it via USB and send M115
-
Connecting directly gives 3.0Beta12, obviously that's not what was expected. How come the RPI didn't update the firmware. I understood the apt dist-upgrade would have upgraded it, isn't it ?
-
@Jerome IIRC there was an issue with that build and updating in SBC mode. You're best off bringing the board to 3.4.6 using bossa and then continue in SBC mode
-
Thank you, that's what i've done, and now it works great
-
undefined Jerome has marked this topic as solved
