RepRapFirmware 3.01-RC3 released

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?

dc42

@DaBit said in RepRapFirmware 3.01-RC3 released:

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?

You could run it faster than that if you use a loop within the daemon.g file.

imrj

@bearer bossa crashes on my Mac running Movaje, and i dont have a laptop w Windows, so I would have to rip out the board and uncable it all, trying to avoid that......
I tried the file "Duet3_SDiap_MB6HC.bin" that someone posted the link for but it still wont take, it says soemthing about in-app error (i notices is a really small file of 55k vs. the usual 550k or so).....I dunno this shouldnt be that difficult....help!!

DaBit

@dc42 said in RepRapFirmware 3.01-RC3 released:

You could run it faster than that if you use a loop within the daemon.g file.

I suppose I could, but as long as I do not have to interface with existing boards the frequency is not that important.

How do we prevent the daemon task from taking away too much processing from the main G-code pipe? Is an endless while() harmful? Or is all that handled by priority in RRF?

Anyway, nice addition that daemon task!
I could use the daemon task to monitor the heaters for faulting, generate a chargepump signal when OK, quit generating the chargepump and send an M81 when failing.

Danal

@imrj said in RepRapFirmware 3.01-RC3 released:

@bearer bossa crashes on my Mac running Movaje, and i dont have a laptop w Windows, so I would have to rip out the board and uncable it all, trying to avoid that......
I tried the file "Duet3_SDiap_MB6HC.bin" that someone posted the link for but it still wont take, it says soemthing about in-app error (i notices is a really small file of 55k vs. the usual 550k or so).....I dunno this shouldnt be that difficult....help!!

Do you have a Raspberry Pi?

The instructions for bossa on Pi are on the dozuki, just below the instructions for Winders (<=Texas edition of WIndows)

imrj

@Danal i do have plenty those, thanks, will give that a shot

droftarts

@imrj said in RepRapFirmware 3.01-RC3 released:

bossa crashes on my Mac running Movaje

See https://forum.duet3d.com/topic/11445/flashing-firmware-on-mac-os-x

Ian

dc42

@DaBit said in RepRapFirmware 3.01-RC3 released:

How do we prevent the daemon task from taking away too much processing from the main G-code pipe? Is an endless while() harmful?

If using your own loop, then I recommend that you include at least one G4 command in it with a reasonable length of delay.

dc42

@imrj said in RepRapFirmware 3.01-RC3 released:

I tried the file "Duet3_SDiap_MB6HC.bin" that someone posted the link for but it still wont take, it says soemthing about in-app error (i notices is a really small file of 55k vs. the usual 550k or so).....I dunno this shouldnt be that difficult....help!!

That's the new IAP file, used by RRF 3.0 and later to upgrade the firmware. It is not the firmware file itself, but it needs to be present in /sys when you want to upgrade the firmware using DWC or M997.

imrj

I understand, but even with it present and the firmware file, still does nothing, it says is updating the firmware, but it remains the same in M115 afterwards, stuck at 3.0B12

Phaedrux

@imrj Try updating to 3.0 first, with the zip file from that release. Then try updating to this release.