RepRapFirmware 3.01-RC6 released

chas2706

In a previous post somewhere I read that @ DC42 does not have Duet 3 with SBC so based on this how can new firmware be released if the owner of firmware does not have the hardware?

JoergS5

@chas2706 He is not the only person developing and testing the firmware. The software for SBC Raspi DSF has even a different owner Chris Hamm.

Danal

Correct. DC42 is the primary (but not only) author of the firmware for the Duet Board itself, and is the lead engineer for the company, and a principal owner of the company.

Chrishamm is the primary developer for Duet Web and for Duet Software Framework on the Pi. I do not know his other relationships to the company. Chris has the hardware to test D3+Pi.

And... anyone can open a "pull" request, it is the nature of github. So there are somewhere between 7 and a dozen other contributors. Probably not all that relevant to our discussion here.

percar

I just installed 3.01 RC6
I have run into a couple of issues and I'm not sure if it is the firmware or the web control...I also updated it to 2.1.0

I have a load filament Macro and when I tried to use it it did not function...it is pretty simple the extruder was up to temperature
M83
G92 E0
G1 E1200 F3000
G1 E200 F10
Also on the same note if I try to press the extrusion control from DWC it does not work either but the funny thing is that if you do it on panel duo it does work.
on the tools block when extruders and bed are on and you go to the control all and press turn everything off...that does not function
It will work if you change the set all active temperatures and set all active temperatures to some other value then back to 0 again

A Former User

@chas2706 said in RepRapFirmware 3.01-RC6 released:

In a previous post somewhere I read that @ DC42 does not have Duet 3 with SBC so based on this how can new firmware be released if the owner of firmware does not have the hardware?

i get thats its frustrating when things go pear shaped; and I don't have an explanation as to why I was able to downgrade to a specific version but you were not - however it does suggest something being amiss with your setup.

if you still have a backup sd card, I would encourage you to make a copy and then try that with my suggestions for restoring the RRF firmware which is on the sd. there really is no reason that shouldn't give you the same combination of apt packages and rrf firmware as you had when you made the backup.

arhi

seem to be working on duet2eth but when I upload Duet2CombinedIAP.bin in the system tab it shows uploading forever, never finishes?!

Marco Bona

I updated the DWC to 2.1.0, but I haven't noticed any changes.
Yesterday I tried to make a couple of prints but the layer screen remained with the same problem I had.
It always hangs on the second layer and the statistics are wrong.
This morning I try to start the print and see if something has changed.
I'll update you as soon as possible.
Thanks

dc42

I'm sorry that there are some issues with upgrading to the new RRF/DWC/DSF. There have been many major changes, especially to DSF and DWC which now support almost the full object model.

Here's a summary of issues we are aware of with upgrading to RRF 3.01-RC6, DWC 2.1.0 and DSF 1.3.0.

DWC issue: extrude/retract buttons greyed out when they shouldn't be. Workaround: if you need those buttons, use DWC 2.0.7.
DWC issue: when you click on a heater in the Fault state there is a new dialog that allows you to reset the fault; but the heater fault reset doesn't work.
Upgrading RRF+DSF+DWC on Duet 3 with attached RPi does not always go smoothly.
DSF issue: laser and magnetic filament monitors without a filament present switch are not handled. Workaround: add 1 to the filament monitor type (M591 P parameter) to say that a filament present switch is present, and put a jumper across the filament present switch pins to simulate the presence of filament.

We are preparing a new DWC release (2.1.1) to address #1 and #2, and a new DSF release (1.3.1) to address #4. Chrishamm will provide new instructions to address #3. I will then lock this thread and we will start two new threads: one for issues users are having using the new release on Duet 3 + SBC, and one for other users.

gruen

for me work this to upgrade my sbc:

apt remove duetsoftwareframework duetcontrolserver duetsd duettools duetwebserver duetwebcontrol reprapfirmware

and install with

apt install duetsoftwareframework duetcontrolserver duetsd duettools duetwebserver duetwebcontrol reprapfirmware

Marco Bona

@droftarts, I send you the DWC screen, as you can see nothing has changed since the previous build.

The only doubt is that there is something at the beginning of the file that creates some noise.

M117 Preparing            ;write Preparing
G4 S2                     ;delay 2 seconds
M140 S60                  ;set bed temperature and move on
M141 S0                  ;set heated chamber temperature and move on
M104 T0 S195              ;wait for the extruder to reach desired temperature
M107                      ;start with the fan off
G28                       ;home all axes
T0                        ;select tool 0
G1 X-23 Y-24 F10000       ;go to the center of bed
G1 Z10 F1000              ;E go to Z10
M107 P0                   ;turn off leds
G30 X-23 Y-24 S-2 H1.915  ;probe current position and ajust Z offset
G1 Z40 F1000              ;E go to Z40
M106 P0 S1                ;turn on leds
T0                        ;reset current tool
M584 P4                   ;apply custom setting
G1 X-87 Y160 F10000       ;go to X-87 Y160
M117 Spray print adhesive ;write Spray print adhesive
G4 S2                     ;delay 2 seconds
M226                      ;pause
M190 S60                  ;wait for the bed to reach desired temperature
M109 S205                 ;wait for the extruder to reach desired temperature
G1 U130 F10000            ;go to U130
G92 E0                    ;reset the extruder position
G1 X-137 E25 F500         ;move to X-137 and extrude 25mm of feed stock
G92 E0                    ;reset the extruder position
G1 E-4 F5000              ;retract 4mm
G1 X-187 F500             ;go to X-187
G1 Y165 F500              ;go to Y165
G10                       ;retract
G1 X-137 F500             ;go to X-137 and clean nozzle
G1 XO Y0 U0 F10000        ;go to X0 Y0 U0
M584 P3                   ;apply custom setting
G21                       ;metric values
G90                       ;absolute positioning

M117 Print starting       ;write Print starting
G4 S2                     ;delay 2 seconds
G92 E0                    ;reset the extruder position
G1 E4 F500                ;unretract 4mm
G11                       ;unretract

I am attaching the file to verify.
HA_Rudder.gcode

droftarts

@Marco-Bona can you confirm you’re using the latest firmware and DWC versions? Shown on System tab of DWC. I have not had a chance to test if the layer time problem is fixed.

Ian

Marco Bona

@droftarts, I confirm, I am using DWC 2.1.0, I have updated to RRF3.01 RC6 and DuetWiFiServer 1.23.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.01-RC6 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2020-04-03b3

tobias_munich

@dc42 thanks for your clear statement. have a nice weekend.

ChrisP

@dc42
I've just stumbled across another odd error.
I had just started a print but a bit of purge material got caught on the head so I paused the print (I have a hardware button and use the input to trigger a pause using M581).

On first press of the button, all motion stopped instantly but the pause script (below) wasn't executed. I pressed the button again and the notification to say that the print had been paused be external trigger showed but the head still didn't move out of the way.

; Pause macro file
M83			; relative extruder movements
G1 E-3 F2500		; retract 3mm
G91			; relative moves
G1 Z10 F5000		; raise nozzle 10mm
G90			; absolute moves
G1 X0 Y110 F5000	; move head out of the way of the print

I then pressed Emergency Stop on the web interface at which point the web interface said it was tying to reconnect, but it never came back to life. I tried moving the axis by hand to move the hot nozzle off the print but all the axis motors were sitll powered and holding. I took the following dump fron the DCS service log on the SBC:

Apr 04 11:25:18 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:25:28 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:25:38 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:25:46 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:25:50 starttex DuetControlServer[360]: [info] Selected file /opt/dsf/sd/gcodes/Test Parts/20x20x10 8dia hole.gcode
Apr 04 11:25:50 starttex DuetControlServer[360]: [info] Starting file print
Apr 04 11:25:50 starttex DuetControlServer[360]: [info] File: Optional macro file start.g not found
Apr 04 11:25:50 starttex DuetControlServer[360]: [info] Executing nested macro file pre_print.g on channel File
Apr 04 11:25:51 starttex DuetControlServer[360]: [info] Executing nested macro file homeall.g on channel File
Apr 04 11:25:51 starttex DuetControlServer[360]: [info] Executing nested macro file homez.g on channel File
Apr 04 11:25:54 starttex DuetControlServer[360]: [info] File: Finished macro file homez.g
Apr 04 11:25:54 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:25:54 starttex DuetControlServer[360]: [info] Executing nested macro file homex.g on channel File
Apr 04 11:25:55 starttex DuetControlServer[360]: [info] File: Finished macro file homex.g
Apr 04 11:25:55 starttex DuetControlServer[360]: [info] Executing nested macro file homey.g on channel File
Apr 04 11:25:59 starttex DuetControlServer[360]: [info] File: Finished macro file homey.g
Apr 04 11:26:01 starttex DuetControlServer[360]: [info] File: Finished macro file homeall.g
Apr 04 11:26:01 starttex DuetControlServer[360]: [info] Executing nested macro file tfree0.g on channel File
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] File: Finished macro file tfree0.g
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] Executing nested macro file tpre0.g on channel File
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] File: Finished intermediate macro file tpre0.g
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] Executing nested macro file tpost0.g on channel File
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] Executing nested macro file config.g on channel File
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] File: Finished macro file config.g
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] File: Finished macro file tpost0.g
Apr 04 11:26:02 starttex DuetControlServer[360]: [info] Executing nested macro file tfree0.g on channel File
Apr 04 11:26:03 starttex DuetControlServer[360]: [info] File: Finished macro file tfree0.g
Apr 04 11:26:10 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:26:18 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:26:26 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:26:35 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:31:16 starttex DuetControlServer[360]: [info] File: Finished macro file pre_print.g
Apr 04 11:31:17 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:31:18 starttex DuetControlServer[360]: [info] Executing nested macro file purge.g on channel File
Apr 04 11:31:18 starttex DuetControlServer[360]: [info] File: Finished macro file purge.g
Apr 04 11:31:18 starttex DuetControlServer[360]: [info] Executing nested macro file wipe.g on channel File
Apr 04 11:31:20 starttex DuetControlServer[360]: [info] File: Finished macro file wipe.g
Apr 04 11:31:25 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:31:33 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:31:42 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:31:50 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:32:00 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:32:10 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:32:18 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Restarting transfer because the number of maximum retries has been exceeded
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Restarting transfer because the number of maximum retries has been exceeded
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Restarting transfer because the number of maximum retries has been exceeded
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)
Apr 04 11:32:18 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x7222, got 0x7aaa)

I pressed the reset button on the Duet3 (by the power LEDs) and everything came back to life. I've since tried to recreate the issue, but can't unfortunately as yet.

The printer has been running solidly for days, so I'm not inclined to believe its a hardware or other setup issue at the moment.

update:
I've not just had it crash randomly mid-print. Web interface becomes unresponsive and service logs are full of:

Apr 04 12:03:53 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x92b3, got 0x23e3)
Apr 04 12:03:53 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x92b3, got 0x23e3)
Apr 04 12:03:53 starttex DuetControlServer[360]: [warn] Bad data checksum (expected 0x92b3, got 0x23e3)
Apr 04 12:03:53 starttex DuetControlServer[360]: [warn] Restarting transfer because the number of maximum retries has been exceeded

I also seem to be getting lots of this. Which is confusing as I don't have the macros page open on anything...?

Apr 04 12:02:45 starttex DuetControlServer[360]: [info] Aux: Running code from firmware 'M20 S2 P0:/macros' on channel Aux

chrishamm

@ChrisP It looks like you have a PanelDue connected to your Duet 3 and that is not fully supported yet while the Duet 3 is operating in SBC mode. At present the only transmitted command from the firmware to DSF is M20 which you can see in the logs. So I suggest don't use the PanelDue for anything else than pausing prints (not resuming) or emergency stops in SBC mode until support for PanelDue has been fully implemented.

Can you share the output of M122 if you are certain the firmware reset unexpectedly?

ChrisP

@chrishamm
You are absolutely correct that I have a PanelDue connected I hadn't anticipated that this could be part of the problem since i'ts been connected since it has always been connected to the Duet3 from the first time I set it up over a few weeks ago. I was aware that it had limitations but have kept it there as an easy way to view teh temperatures and print progress - I don't use it for anything onther than displaying info currently. With previous firmwares / DCS it's been operating fine. That said, I'll take the advice and remove it for now.

Is there a was that I can issue M122 and grab the result from the Pi as when the crashed happen, the web interface becomes totally unresponsive and requires me to press the hardware reset on the Duet3 to bring things back to life?

edit: I will unplug the PanelDue, power cycle and try the print again.... I'm only running test prints currently to ensure the system is stable... clearly not quite ready for a proper print yet

chrishamm

@ChrisP It sounds like there is a problem in DCS and I'll be happy to look into it. To obtain some debug info, please connect to your Pi via ssh, run sudo journalctl -u duetcontrolserver -en 100 --no-pager, and share the output you get.

PS: It's fine to leave the PanelDue attached but be aware that most file-related commands will not work as expected.

A Former User

@ChrisP said in RepRapFirmware 3.01-RC6 released:

Is there a was that I can issue M122 and grab the result from the Pi as when the crashed happen

log in using ssh and do echo M122 | sudo /opt/dsf/bin/CodeConsole should work if DuetControlServer is still running, if that is not the case, you'll need to connect to the Duets micro USB port and use it as a serial console.

ChrisP

@chrishamm said in RepRapFirmware 3.01-RC6 released:

@ChrisP It sounds like there is a problem in DCS and I'll be happy to look into it. To obtain some debug info, please connect to your Pi via ssh, run sudo journalctl -u duetcontrolserver -en 100 --no-pager, and share the output you get.

Thanks for the help. I'm running this as a test machine anyway, so I'm happy to test anything on it if it'll help move forward. Here's the log from a fresh boot (with PanelDue disconnected):

-- Logs begin at Thu 2019-02-14 10:11:59 GMT, end at Sat 2020-04-04 12:33:27 BST. --
Apr 04 12:28:50 starttex systemd[1]: Started Duet Control Server.
Apr 04 12:28:52 starttex DuetControlServer[350]: Duet Control Server v1.3.0
Apr 04 12:28:52 starttex DuetControlServer[350]: Written by Christian Hammacher for Duet3D
Apr 04 12:28:52 starttex DuetControlServer[350]: Licensed under the terms of the GNU Public License Version 3
Apr 04 12:28:54 starttex DuetControlServer[350]: [info] Settings loaded
Apr 04 12:28:55 starttex DuetControlServer[350]: [info] Environment initialized
Apr 04 12:28:55 starttex DuetControlServer[350]: [warn] Downgrading protocol version 2 to 1
Apr 04 12:28:55 starttex DuetControlServer[350]: [warn] Incompatible firmware, please upgrade as soon as possible
Apr 04 12:28:55 starttex DuetControlServer[350]: [info] Connection to Duet established
Apr 04 12:28:55 starttex DuetControlServer[350]: [info] IPC socket created at /var/run/dsf/dcs.sock
Apr 04 12:28:55 starttex DuetControlServer[350]: [info] Executing system macro file config.g on channel Trigger
Apr 04 12:28:56 starttex DuetControlServer[350]: [warn] Deprecated firmware detected, please update it in order to use DSF
Apr 04 12:28:56 starttex DuetControlServer[350]: [warn] Deprecated firmware detected, please update it in order to use DSF
Apr 04 12:28:57 starttex DuetControlServer[350]: [info] Trigger: Finished system macro file config.g
Apr 04 12:31:48 starttex DuetControlServer[350]: [info] System time has been changed
Apr 04 12:32:05 starttex DuetControlServer[350]: [info] Flashing IAP binary
Apr 04 12:32:05 starttex DuetControlServer[350]: [info] Flashing RepRapFirmware
Apr 04 12:32:11 starttex DuetControlServer[350]: [info] Verifying checksum
Apr 04 12:32:14 starttex DuetControlServer[350]: [info] Firmware update successful
Apr 04 12:32:14 starttex DuetControlServer[350]: [fatal] Abnormal program termination
Apr 04 12:32:14 starttex DuetControlServer[350]: [fatal] SPI task faulted
Apr 04 12:32:14 starttex DuetControlServer[350]:    System.Exception: Invalid protocol version 2
Apr 04 12:32:14 starttex DuetControlServer[350]:    at DuetControlServer.SPI.DataTransfer.ExchangeHeader() in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 1130
Apr 04 12:32:14 starttex DuetControlServer[350]:    at DuetControlServer.SPI.DataTransfer.PerformFullTransfer(Boolean mustSucceed) in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 157
Apr 04 12:32:14 starttex DuetControlServer[350]:    at DuetControlServer.SPI.Interface.Run() in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 744
Apr 04 12:32:14 starttex DuetControlServer[350]: [fatal] SPI task faulted
Apr 04 12:32:14 starttex DuetControlServer[350]:    System.Exception: Invalid protocol version 2
Apr 04 12:32:14 starttex DuetControlServer[350]:    at DuetControlServer.SPI.DataTransfer.ExchangeHeader() in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 1130
Apr 04 12:32:14 starttex DuetControlServer[350]:    at DuetControlServer.SPI.DataTransfer.PerformFullTransfer(Boolean mustSucceed) in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 157
Apr 04 12:32:14 starttex DuetControlServer[350]:    at DuetControlServer.SPI.Interface.Run() in /home/christian/duet/DuetSoftwareFramework/src/DuetControlServer/SPI/Interface.cs:line 744
Apr 04 12:32:14 starttex systemd[1]: duetcontrolserver.service: Succeeded.
Apr 04 12:32:19 starttex systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
Apr 04 12:32:19 starttex systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 1.
Apr 04 12:32:20 starttex systemd[1]: Stopped Duet Control Server.
Apr 04 12:32:20 starttex systemd[1]: Started Duet Control Server.
Apr 04 12:32:20 starttex DuetControlServer[1513]: Duet Control Server v1.3.0
Apr 04 12:32:20 starttex DuetControlServer[1513]: Written by Christian Hammacher for Duet3D
Apr 04 12:32:20 starttex DuetControlServer[1513]: Licensed under the terms of the GNU Public License Version 3
Apr 04 12:32:21 starttex DuetControlServer[1513]: [info] Settings loaded
Apr 04 12:32:22 starttex DuetControlServer[1513]: [info] Environment initialized
Apr 04 12:32:22 starttex DuetControlServer[1513]: [info] Connection to Duet established
Apr 04 12:32:22 starttex DuetControlServer[1513]: [info] IPC socket created at /var/run/dsf/dcs.sock
Apr 04 12:32:22 starttex DuetControlServer[1513]: [info] Executing system macro file config.g on channel Trigger
Apr 04 12:32:26 starttex DuetControlServer[1513]: [info] Trigger: Finished system macro file config.g

chrishamm

@ChrisP Thanks, please run that when DSF becomes unresponsive. So far nothing unusual in this excerpt.