Posts made by com3

undefined

@gloomyandy thanks a lot, that worked!!

undefined

I so I tried the stuff I found in other posts:
sudo apt-get update
sudo apt-get upgrade

and:
sudo apt update
sudo apt upgrade duetsoftwareframework

thats currently the situation here:


pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e
Sep 10 10:37:40 duet3 systemd[1]: Failed to start Duet Control Server.
Sep 10 10:37:40 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Sep 10 10:37:40 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Sep 10 10:37:40 duet3 systemd[1]: Stopped Duet Control Server.
Sep 10 10:37:40 duet3 systemd[1]: Starting Duet Control Server...
Sep 10 10:37:40 duet3 DuetControlServer[2552]: Duet Control Server v3.3.0
Sep 10 10:37:40 duet3 DuetControlServer[2552]: Written by Christian Hammacher fo
Sep 10 10:37:40 duet3 DuetControlServer[2552]: Licensed under the terms of the G
Sep 10 10:37:41 duet3 DuetControlServer[2552]: [info] Settings loaded
Sep 10 10:37:41 duet3 DuetControlServer[2552]: [info] Environment initialized
Sep 10 10:37:41 duet3 DuetControlServer[2552]: [warn] Restarting transfer becaus
Sep 10 10:37:41 duet3 DuetControlServer[2552]: [fatal] Could not connect to Duet
Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Failed with result
Sep 10 10:37:41 duet3 systemd[1]: Failed to start Duet Control Server.
Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Sep 10 10:37:41 duet3 systemd[1]: Stopped Duet Control Server.
Sep 10 10:37:41 duet3 systemd[1]: Starting Duet Control Server...
Sep 10 10:37:41 duet3 DuetControlServer[2565]: Duet Control Server v3.3.0
Sep 10 10:37:41 duet3 DuetControlServer[2565]: Written by Christian Hammacher fo
Sep 10 10:37:41 duet3 DuetControlServer[2565]: Licensed under the terms of the G
Sep 10 10:37:42 duet3 DuetControlServer[2565]: [info] Settings loaded
Sep 10 10:37:42 duet3 DuetControlServer[2565]: [info] Environment initialized

Is there a way to extract all the sys files and macros (did not find anything on the SD-Card)? I could at least reflash it without losing everything

undefined

Hey,

I recently updated my Duet 6hc+SBC from 3.2.2 to 3.4, or at least I tried.
After the update I´ll get an error message "Failed to connect to duet, please check your connections".

Checking with USB and 115 I´ll get follwing message

SENDING:M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.0beta3 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-08-24 13:58:02

journalctl -fu duetcontrolserver returns:

pi@duet3:~ $ journalctl -fu duetcontrolserver
-- Logs begin at Fri 2021-09-10 09:17:01 BST. --
Sep 10 10:02:44 duet3 DuetControlServer[851]: [warn] Restarting transfer because                                                                                                  the Duet received a bad response (header)
Sep 10 10:02:44 duet3 DuetControlServer[851]: [fatal] Could not connect to Duet                                                                                                  (Invalid protocol version 6)
Sep 10 10:02:44 duet3 systemd[1]: duetcontrolserver.service: Failed with result                                                                                                  'protocol'.
Sep 10 10:02:44 duet3 systemd[1]: Failed to start Duet Control Server.
Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=                                                                                                 100ms expired, scheduling restart.
Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j                                                                                                 ob, restart counter is at 10.
Sep 10 10:02:45 duet3 systemd[1]: Stopped Duet Control Server.
Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Start request repea                                                                                                 ted too quickly.
Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Failed with result                                                                                                  'protocol'.
Sep 10 10:02:45 duet3 systemd[1]: Failed to start Duet Control Server.

sudo journalctl -u duetcontrolserver -e returns:

pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e
Sep 10 10:02:43 duet3 DuetControlServer[838]: [info] Environment initialized
Sep 10 10:02:43 duet3 DuetControlServer[838]: [fatal] Could not connect to Duet
Sep 10 10:02:43 duet3 systemd[1]: duetcontrolserver.service: Failed with result
Sep 10 10:02:43 duet3 systemd[1]: Failed to start Duet Control Server.
Sep 10 10:02:43 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Sep 10 10:02:43 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Sep 10 10:02:43 duet3 systemd[1]: Stopped Duet Control Server.
Sep 10 10:02:43 duet3 systemd[1]: Starting Duet Control Server...
Sep 10 10:02:44 duet3 DuetControlServer[851]: Duet Control Server v3.2.2
Sep 10 10:02:44 duet3 DuetControlServer[851]: Written by Christian Hammacher for
Sep 10 10:02:44 duet3 DuetControlServer[851]: Licensed under the terms of the GN
Sep 10 10:02:44 duet3 DuetControlServer[851]: [info] Settings loaded
Sep 10 10:02:44 duet3 DuetControlServer[851]: [info] Environment initialized
Sep 10 10:02:44 duet3 DuetControlServer[851]: [warn] Restarting transfer because
Sep 10 10:02:44 duet3 DuetControlServer[851]: [fatal] Could not connect to Duet
Sep 10 10:02:44 duet3 systemd[1]: duetcontrolserver.service: Failed with result
Sep 10 10:02:44 duet3 systemd[1]: Failed to start Duet Control Server.
Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Sep 10 10:02:45 duet3 systemd[1]: Stopped Duet Control Server.
Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Start request repea
Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Failed with result
Sep 10 10:02:45 duet3 systemd[1]: Failed to start Duet Control Server.

Upgraded DCS to 3.3, still not working.


pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e
Sep 10 10:37:40 duet3 systemd[1]: Failed to start Duet Control Server.
Sep 10 10:37:40 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Sep 10 10:37:40 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Sep 10 10:37:40 duet3 systemd[1]: Stopped Duet Control Server.
Sep 10 10:37:40 duet3 systemd[1]: Starting Duet Control Server...
Sep 10 10:37:40 duet3 DuetControlServer[2552]: Duet Control Server v3.3.0
Sep 10 10:37:40 duet3 DuetControlServer[2552]: Written by Christian Hammacher fo
Sep 10 10:37:40 duet3 DuetControlServer[2552]: Licensed under the terms of the G
Sep 10 10:37:41 duet3 DuetControlServer[2552]: [info] Settings loaded
Sep 10 10:37:41 duet3 DuetControlServer[2552]: [info] Environment initialized
Sep 10 10:37:41 duet3 DuetControlServer[2552]: [warn] Restarting transfer becaus
Sep 10 10:37:41 duet3 DuetControlServer[2552]: [fatal] Could not connect to Duet
Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Failed with result
Sep 10 10:37:41 duet3 systemd[1]: Failed to start Duet Control Server.
Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Sep 10 10:37:41 duet3 systemd[1]: Stopped Duet Control Server.
Sep 10 10:37:41 duet3 systemd[1]: Starting Duet Control Server...
Sep 10 10:37:41 duet3 DuetControlServer[2565]: Duet Control Server v3.3.0
Sep 10 10:37:41 duet3 DuetControlServer[2565]: Written by Christian Hammacher fo
Sep 10 10:37:41 duet3 DuetControlServer[2565]: Licensed under the terms of the G
Sep 10 10:37:42 duet3 DuetControlServer[2565]: [info] Settings loaded
Sep 10 10:37:42 duet3 DuetControlServer[2565]: [info] Environment initialized

So it seems like the firmware update was succesful, but DCS is now on the wrong version or broken? How can I fix this (ideally without reflashing everything)?

undefined

@fcwilt The biggest problem is the first tool which all the other offsets are applied relatively to. It would just be soooooo easy saving that damn zero point instead of fuzzing around with g-code. Just start a print, check if it´s fine, adjust it if not, save and forget it. And other people think the same about it:

https://forum.duet3d.com/topic/16328/baby-stepping-can-it-or-can-it-not-be-permanent

https://forum.duet3d.com/topic/1226/baby-steps-z-offset

https://www.reddit.com/r/ender3/comments/a4sx14/how_to_save_babystepping_z_values/

https://reprap.org/forum/read.php?415,879905

Also Klipper, Marlin and Repetier offer that feature since years. But as I said, i´ll try to script it.

undefined

@fcwilt Every. Single. Time. someone asks here for a useful solution someone comes along and washes it away by saying the printer is trash.

"The only time I need to use baby-stepping (don't like that name) is when I am trying to rush a print and heat related changes have not stabilized."

That is great for you but I am printing 24/7 with eight toolchanging printer resulting in 32 Extruders which I need to set up and calibrate. I know this is an extreme but it really is a problem (especially after nozzle change) literally any other firmware has a simple solution for. But with duet it is not possible? Come on.

I will try to hack it toghether as a macro and will share it here if it works.

undefined

@deckingman I understand that but anyone who uses their Duet for 3D Printing (which should be like 95% right?) would profit from this very simple feature every single day of usage.

undefined

@phaedrux I really need to say that the reulctancy to implement this feature properly is really bugging me. The solution you are proposing is none because you still need to fuzz with the start Gcode and/or G31 to get a very very basic thing done. I mean seriously why the hesitancy to add a simple "save offset button" to the interface? (It could then write it as whatever gcode, doesn´t matter) but adding an offset to every print, or fuzzing with start g-code just to set this very simple value is a total nogo for productive use with several operators. I love Duet but it´s things like this which make me think of switching.

This feature has been requested so many times over the years and each time someone ends the discussion with use this or that g-code as if it would be the same OP, me and many others were askingfor, but it´s just not.

undefined

Im not too shure that it´s my network as I got multiple duets running and only one is particular problematic. But ofc it still could be an issue. However, I need some hardware to rule out this potential problem.

@dc42 It seems like it doesn´t matter if it´s idle or not

undefined

Just tried it without success, everything is now on 3.2 but the issue remains

//edit: had to upload it multiple times because of the connection loss

undefined

Hey there!

Ive been using multiple printer with Duet Wifi and had occasional connection issues. So I switched to the lan version for the latest Printer in hope it would improve stability but it actually got worse. The problem are frequent short disconnections (.5-2 times per minute) which make it super hard to use the printer at all.

I tried multiple Web Control Versions: 2.0.7, 2.0.4, 2.1.7 and 3.1 without any noticable improvement.
Both Duet Wifi and Duet 2 Lan are hooked to a router with fixed IP

Does anyone share this problem or has an idea how it could be fixed?

	=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet Ethernet 1.02 or later + DueX5
Board ID: 08DLM-996RU-N8PS4-6J9DA-3SD6M-TVU3N
Used output buffers: 1 of 24 (24 max)
=== RTOS ===
Static ram: 30516
Dynamic ram: 93388 of which 0 recycled
Exception stack ram used: 248
Never used ram: 6920
Tasks: NETWORK(ready,640) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3676) IDLE(ready,156)
Owned mutexes:
=== Platform ===
Last reset 00:04:18 ago, cause: power up
Last software reset at 2021-01-14 14:52, reason: User, spinning module GCodes, available RAM 6560 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 3.2ms, max retries 0
MCU temperature: min 31.0, current 31.2, max 31.6
Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2021-01-14 15:06:54
Cache data hit count 434684016
Slowest loop: 10.27ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = 0 -1 -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 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 ===
Slowest loop: 23.08ms; fastest: 0.04ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
Interface state 5, link 100Mbps full duplex