RepRapFirmware 3.01-RC6 released

chas2706

@Danal said in RepRapFirmware 3.01-RC6 released:

Also, if you want to backup the entire Pi SD card to a windows PC without physically touching the card in the Duet+Pi, here is an outline of how to do that

I made the back up by taking out the sd card, inserting it in my pc and then using win32disk manager and I can verify that it works because while I was on the same RRF version I deliberately flashed a different sd card and re-installed using my backup. In the process I made lots of changes, backed them up and re- installed - all with success but when you "upgrade" the result is so different

Danal

@chas2706 said in RepRapFirmware 3.01-RC6 released:

I made the back up by taking out the sd card, inserting it in my pc and then using win32disk manager and I can verify that it works because while I was on the same RRF version I deliberately flashed a different sd card and re-installed using my backup. In the process I made lots of changes, backed them up and re- installed - all with success but when you "upgrade" the result is so different

The Duet board has flash that has the running firmware. It absolutely does have to be re-flashed to change the firmware release.

EVERYTHING else is on the SD card. That is the physical setup of a Raspberry Pi. I don't doubt what you are seeing, your symptoms. At the same time, if a backup SD card was taken before the upgrade, and that backup was properly restored (such as a physically different card with the prior copy being put in the Pi), then it is absolutely not possible that the files are somehow at a different level than the backup. Pi hardware does not have any other storage than the SD.

So again, I'm just a fellow user, trying to help improve understanding so that people don't get painted into corners... if DWC didn't regress to the level it was when the backup was taken, the the backup/restore procedure is the thing to fix for next time.

Danal

Wait a minute... "Win32 disk manager"??? That won't deal with the Unix partitions on that card. Will it?

A Former User

This ought be a passing problem for most people as a stable release becomes available that most people can actually use without being recommended to switch to the unstable list where stuff like this so to some degree is acceptable.

And for now; we can try to make the best of it.

A Former User

@Danal said in RepRapFirmware 3.01-RC6 released:

Wait a minute... "Win32 disk manager"??? That won't deal with the Unix partitions on that card. Will it?

indirectly; as in it'll do a bit for bit copy that will work unless you want to restore to a smaller sd card

(not sure if it applies to SD cards as it did with old harddrives, but I always leave a few megabytes unused to allow for X gigabyte from vendor A not being the same as X gigabyte from vendor B)

Danal

Are we talking about this:

A Former User

@Danal yaeh - dd for windows basically

Danal

Win32 disk imager has been known to copy portions of a card, and not copy other portions, in certain SD readers. Which makes it very difficult for other people to diagnose.

Personally, I would never use it. Balena etcher or SD Writer or...

Probably not what happened here; but something did happen to that backup. Some confusion.

chas2706

@Danal said in RepRapFirmware 3.01-RC6 released:

o again, I'm just a fellow user, trying to help improve understanding so that people don't get painted into corners... if DWC didn't regress to the level it was when the backup was taken, the the backup/restore procedure is the thing to fix for next time.

Thanks for your help danal. I really appreciate your input.
I am just so frustrated with the problems I am experiencing.

@Danal
Wait a minute... "Win32 disk manager"??? That won't deal with the Unix partitions on that card. Will it?

I am no Linux expert but I can confirm that win32 disk manager deals with the unix partitions because I have used it for many years on my rpi projects.
It was available for the rpi way before etcher or raspberry pi imager.

Danal

@chas2706 said in RepRapFirmware 3.01-RC6 released:

@Danal said in RepRapFirmware 3.01-RC6 released:

o again, I'm just a fellow user, trying to help improve understanding so that people don't get painted into corners... if DWC didn't regress to the level it was when the backup was taken, the the backup/restore procedure is the thing to fix for next time.

Thanks for your help danal. I really appreciate your input.
I am just so frustrated with the problems I am experiencing.

@Danal
Wait a minute... "Win32 disk manager"??? That won't deal with the Unix partitions on that card. Will it?

I am no Linux expert but I can confirm that win32 disk manager deals with the unix partitions because I have used it for many years on my rpi projects.
It was available for the rpi way before etcher or raspberry pi imager.

Yeah, I think we both mean "win32diskimager". That does work on complete SD cards. Although I have read where it can skip certain parts of cards on certain drives. Probably not what happened here.

And, yes, I understand the frustration. I was up until 2:30 last night doing a "five minute install" of LaTEX on an unrelated system... and had calls starting at 7 AM. I really should have walked away about 11 PM, but you get that "one more command and it has GOT to work" syndrome.

chas2706

@Danal said in RepRapFirmware 3.01-RC6 released:

Yeah, I think we both mean "win32diskimager

Sorry yes. My mistake!
Looks like I will just have to spend hours setting up my config again from scratch.
A lessen learnt - don't download from the "unstable list".
Again, thanks for you help.

A Former User

@chas2706 said in RepRapFirmware 3.01-RC6 released:

A lessen learnt - don't download from the "unstable list".

hopefully when 3.01 hits stable, there won't be a a reason to do so (which didn't quite hold true for 3.0)

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.