I am very excited by this announcement. Great work Duet!

@dc42 Awesome news, thank you and congrats to Louis as well!

Hi All,

For the Bear Duet project we will have a single repository for on our GitHub with release that contains all the necessary files and configurations for installing Duet RRF and PanelDue to our Duet Mini 5+ board. I am doing a GitHub action script to automate the release creation (gather files from Duet GitHub release, make our own splash screen, create a draft release and upload all necessary files to the draft release).

I have noticed that filenames are changing between the releases and this makes the automation script more difficult and it might be more prone to errors. This makes me thing that the RRF and PanelDue firmware release are made manually and I am wondering if automating this process would be possible in the future. This would reduce risks of human error, reduce time needed to make the release and make it more consistent over time.

I would be very happy to help with this however, I might not be the best person as I am new to Duet RRF and have not tried to build it myself yet.

@mfs12 Don't hesitate if you need help

@jay_s_uk awesome thank you

@owend Sorry for my late answer, thanks I better understand now

@apak just seeing your project now, very nice

@owend thanks for your help. Any reason why you want to get the current instead of machine position like with move.axes[].machinePosition ?

@dc42 We are very interested to have this feature as well . This is not only a security feature but also reduce chances for people to have their hotend clogging, avoid some part like shroud deforming because there is no airflow or simply reduce energy consumption. Even for an advanced user there will always be a day where you forgot about it.

If not possible, could you give us a little bit more details on how to implement this with daemon.g?

For info, this is how my draft release looks like on GitHub after the automatic creation

@mfs12 Don't hesitate if you need help

@mfs12 It is not published yet but here is the create release GitHub action script I am currently using to create the release:
create_release.yml.txt

I have an external script to create the zip files and for now the splash screen creation isn't done yet. You need to rename the file as .yml

@mfs12 That is awesome to head, thanks for that work. So yes for PanelDue we can use GitHub actions, it is using docker and you can specify the OS as well if you like.

@oliof Ah yes that would be great too. This can probably be handled as two separate tasks but I agree it would make sense. Moving to cmake is probably a lot of work.