RepRapFirmware 3.01-RC3 released

dc42

I've just released this at https://github.com/dc42/RepRapFirmware/releases/tag/3.01-RC3. As well as fixing bugs in RC2, it provides the following new features:

Additional 'daemon' GCode task, which repeatedly executes macro file daemon.g in the background (not yet available on Duet 3 with attached SBC, pending changes to DSF)
Support for some types of Z probe (unfiltered digital and BLTouch) attached to Duet 3 expansion and tool boards

See https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md for the upgrade notes.

Danal

On Duet 3, an emergency stop now tries to stop all CAN-connected expansion boards and tool boards

Yay!

Luke'sLaboratory

@Danal
That's what that was? I figured I was just dumb and had to power cycle every time -

Double Woohoo!

jens55

For a Duet2wifi, do I just need to upgrade the Duet2CombinedFirmware.bin file or do I need other stuff ?
I am running the web panel 2.0.7 code already.

Phaedrux

@jens55 said in RepRapFirmware 3.01-RC3 released:

For a Duet2wifi, do I just need to upgrade the Duet2CombinedFirmware.bin file or do I need other stuff ?
I am running the web panel 2.0.7 code already.

Yes, you'd need the combined firmware file, but you'll also need some IAP files from the 3.0 release first, if you haven't upgraded to rrf3 yet. So update to 3 first using the zip file. Then you should be good to go.

https://github.com/dc42/RepRapFirmware/releases/tag/3.0

jens55

@Phaedrux, thanks for confirming! I had already upgraded to 3.01-RC2 (I think). I installed the Duet2CombinedFirware.bin file and the web interface shows a successful upgrade. I haven't actually run anything on it but suspect it will be just fine.

tobias_munich

many thanks @dc42 works ...

Guyaros

I'm using Board: Duet WiFi 1.0 or 1.01
Running Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.03RC5 (2019-06-05b5)
Duet WiFi Server Version: 1.23
Duet Web Control 2.0.2

Printer is running perfectly, with no issues at all.

Should I consider upgrading to RRF3.01-RC3? What are the benefits?
What is the upgrade procedure?
In case I will upgrade to RRF3, is it possible to bind Heater E1 as a Fan output?

Thanks,

dc42

@Guyaros said in RepRapFirmware 3.01-RC3 released:

Printer is running perfectly, with no issues at all.

Should I consider upgrading to RRF3.01-RC3? What are the benefits?

I suggest you upgrade to either 2.05.1 or 3.01RC3. The main benefits of 3.01 are more flexible pin allocation, and conditions and loops in GCode and macro files; but upgrading from 2.x to 3.x is more complicated than upgrading to 2.05.1.

What is the upgrade procedure?

If you want to upgrade to 3.01 from 2.x then you must first upgrade to 3.0, and from there to 3.01. You will also have to make a lot of changes to your config.g file.

In case I will upgrade to RRF3, is it possible to bind Heater E1 as a Fan output?

Yes.

imrj

I cant get this to work for the life of me on a Duet3 1.0. I have tried with both M997 and via WebUI and it never upgrades the firmware even thou it says it is.....it keeps asking for a file i cant find named "Duet3iap_sd_MB6HC" and its not on your github.....I have renamed the "Duet3Firmware_MB6HC" to "Duet3iap_sd_MB6HC" and same result, nothing happens, it keeps showing the Beta12 firmware
am having an issue with OUT0 nozzle heater doesnt put any output to the heater, any clue as to why (is not the heater itself, works fine on another machine),.....

gtj0

@imrj
Try putting this file in /sys on your SD card:
https://github.com/dc42/RepRapFirmware/releases/download/3.01-RC1/Duet3_SDiap_MB6HC.bin

@dc42 It might be helpful if you included the IAP files in every release.

garyd9

@gtj0 said in RepRapFirmware 3.01-RC3 released:

@imrj
Try putting this file in /sys on your SD card:
https://github.com/dc42/RepRapFirmware/releases/download/3.01-RC1/Duet3_SDiap_MB6HC.bin

@dc42 It might be helpful if you included the IAP files in every release.

It's also confusing because the name of the duet3 IAP files changed from the early 3 betas to release. If someone purchases a new Duet3 board, it likely has one of those early pre-release versions of the firmware loaded. A user has to get the older IAP files on the SD card to upgrade to a more recent firmware, and then change to the newer IAP files.

For that, I'd suggest including the older IAP file (as well as the new one) with a note "needed for upgrading from XX and earlier."

A Former User

In all fairness the release has all the relevant files and instructions

https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-30

You should also upload the new IAP file for your system. You will need it when upgrading firmware in future. These files are called Duet2CombinedIAP.bin, DuetMaestroIAP.bin, Duet3_SBCiap_MB6HC.bin (for Duet 3+SBC) and Duet3_SDiap.bin (for Duet 3 standalone systems). Leave the old IAP files on your system, they have different names and you will need them again if you downgrade to older firmware.

And most users dealing with testing the unstable releases would either track down the files or just use bossa?

Phaedrux

I believe DC42 had mentioned the next full release will have all the files needed for a direct update.

CNCModeller

@dc42 said in RepRapFirmware 3.01-RC3 released:

I suggest you upgrade to either 2.05.1 or 3.01RC3. The main benefits of 3.01 are more flexible pin allocation, and conditions and loops in GCode and macro files; but upgrading from 2.x to 3.x is more complicated than upgrading to 2.05.1.

What is the upgrade procedure?

If you want to upgrade to 3.01 from 2.x then you must first upgrade to 3.0, and from there to 3.01. You will also have to make a lot of changes to your config.g file.

Hi All / @dc42
Unfortunately I think I've made a foolish error with my Duet 2 Ethernet... after upgrading to RRF3 (R3 zip then R3.01) I decided that I needed to spend much more time learning the new config commands so re-uploaded the 2.05 firmware, unfortunately (I think) I forgot that V3 uses a newer web interface and now I cant connect to the board via the web interface.

Is there any way for me to re-configure things on the SD card directly so I can get back to using my printer with 2.05 in the short term?

Also is polar config supported in RR3? I know I should have checked before upgrading but I am having a "hard of thinking" day. I only ask as the home files being called by the web interface for x appear to be the xhome rather than the radiushome file.

Any help would be much appreciated.

Many Thanks
Barry M

Phaedrux

@CNCModeller said in RepRapFirmware 3.01-RC3 released:

Is there any way for me to re-configure things on the SD card directly so I can get back to using my printer with 2.05 in the short term?

You can place the 2.05 firmware file on the SD card in the /sys folder, connect via USB terminal, and send M997 to flash the firmware.

While you've got the SD card in your PC, you can also replace the contents of the /www folder with the files from DWC 2.0.7 just to make sure it's all there.

CNCModeller

@Phaedrux said in RepRapFirmware 3.01-RC3 released:

@CNCModeller said in RepRapFirmware 3.01-RC3 released:

Is there any way for me to re-configure things on the SD card directly so I can get back to using my printer with 2.05 in the short term?

You can place the 2.05 firmware file on the SD card in the /sys folder, connect via USB terminal, and send M997 to flash the firmware.

While you've got the SD card in your PC, you can also replace the contents of the /www folder with the files from DWC 2.0.7 just to make sure it's all there.

Thanks @Phaedrux,
I'm thinking that the firmware is already installed so I'm hoping I just need to copy over the files to the WWW folder.

Fingers Xed!!!

Cheers
BPM

Phaedrux

@CNCModeller You can send M115 to see what firmware is actually flashed.

CNCModeller

@Phaedrux said in RepRapFirmware 3.01-RC3 released:

@CNCModeller You can send M115 to see what firmware is actually flashed.

Cool thanks for the heads up...

DaBit

That daemon-task runs always? Also when the printer is idle or off?

So, in theory I could use that to generate the desired chargepump signal, albeit at only 0,5Hz?