What’s the stance on RRF on none Duet boards?

jay_s_uk

@blacksheep99 we have a section on the forum as pointed out above but generally find it easiest to run our own discord server for support. Most support questions we get are around getting up and running as the process is different for us. No need to pollute this forum with things most duet users won't find useful

Blacksheep99

@zapta thanks, I had a ‘look’ but clearly not well enough. I posted from my phone so this will teach me to scroll more!

zapta

@jay_s_uk, are there RRF related resources (web sites, communities, forums, discord, etc) other than here?

I always wondered about the relationship between RRF and Duet3d. Is Duet3 the primary (or only) driver and maintainer of RRF or is it just a vendor that uses the RRF open source firmware with some adaptation for its boards as other board vendors do.

jay_s_uk

@zapta

We have our own set of wiki pages with instructions for using RRF with the boards we support https://teamgloomy.github.io/
We also have our own version of the configurator for generating the base files https://teamgloomy.github.io/Configurator
And then we run a discord server for day to day support https://discord.gg/uS97Qs7
We also have a facebook group but that doesn't see much action.

We have a partnership with Mellow/Flymaker supporting their boards etc, although this isn't a paid partnership and we would include other manufacturers boards where appropriate.

o_lampe

@zapta
RRF had only a small share on the 3d printer market. Marlin was the No1 firmware on RAMPS.
But then David came up with his branch of RRF for Delta printers. (first segmentation-free Delta kinematics)
It soon became the main-branch of RRF and the growing community helped to develop more usecases like laser-engraver/cutter and CNC. (we pushed David in these directions )
The hardware side of RRF was open from the beginning. Beside Duet0.6/0.85 there was RAMPS and RADDS, but the silent TMC drivers on Duet2 were a breakthrough for Duet3D boards. This and the easy way to change the setup (on SD-card instead of hardcoded in the MPU)

jay_s_uk

@zapta

I should add that Duet3D is the main driver of RRF.
We do have the odd feature that unique or implemented in a different way but thats mostly down to hardware differences.
We do submit any bugs or fixes we find back to Duet3D where possible

sinned6915

@blacksheep99 this has been discussed at length, many times over the years, both here and on reprap.org forums. if you do a bit of a searching you will see. I don't know if there IS an official position. Most people will say they justify the expense of the OEM hardware with the notion that part of the money goes towards RRF development, but I dont think anyone has proved that point.

dc42 has been very much supportive of ports to alternative hardware over the years. I think the first LPC port for 2.0.x was begun in 2017/2018, and he was instrumental to making that work. I think Tony did too. There was a LOT of work went into that to make RRF work on the limited hardware.

speaking for myself- as one who ran the then bleeding edge 2.0.x stuff on LPC boards there was no scorn or judgement from the main developers. they helped us get RRF running because I think the goal of expanding the collective userbase for RRF was more important than generating hardware sales.

I have printers that run on both OEM boards with expansion boards, and LPC based boards and expansion boards. The best comparison I could offer is think of it as an engine swap- you can stuff a V-8 into almost any car with varying amounts of adaptation, but its not nescessarily going to be a muscle car. Do you like the challenge of the mechanics or do yo want to drive?

Without a doubt, the OEM hardware is the most stable and reliable. You can convert an existing machine with an alternative board to run RRF but its not going to be the same. If you go into the adventure thinking you will save money by using alternative hardware- I think its a sense of false economy. You might spend 2/3 of what the equivalent OEM solutions are and end up with 75% of their funciton and ability. At the end of the day, its just not the same as the OEM hardware.

jay_s_uk

@sinned6915

Limitations were definitely the case with LPC port and still are an issue. For example, the LPC port won't be getting accelerometer support due to no floating point hardware.
The limitations on the STM port however are, as far as I'm concerned, non- existent. You'd be hard pressed to tell the difference without looking at the hardware.

zapta

@jay_s_uk said in What’s the stance on RRF on none Duet boards?:

For example, the LPC port won't be getting accelerometer support due to no floating point hardware.

What is the reason for that? There are for example M4 LPCs with floating point hardware and FP hardware is very common these days.

jay_s_uk

@zapta

the 1768/69 don't have it. And even if they did theres virtually 0 free ram to do anything.
They only have 64kb which is the same amount the duet 0.6/0.85 have

sinned6915

@jay_s_uk out of curiosity, what is the relative cost between say :

STM based board + SBC + display solution
vs.
Duet2 clone + display solution

so we can compare it to OEM?

zapta

@jay_s_uk said in What’s the stance on RRF on none Duet boards?:

the 1768/69 don't have it

Got this week two SKR 1.4 'turbo' for an upcoming Voron 2 build but now that you mentioned I checked and indeed they use a measly LPC1769, but still better than the 8 bit Prusa MK3.

The Voron uses Klipper so the heavy lifting computation is done on the SBC so so I expect good performance.

Do the Chineese manufactures upgrading now to STM32F4? E.g. the SKR pro and the FLY E3? Do they use STMicroelectronics chips or do they have local clones?

jay_s_uk

@sinned6915

STM

Wifi

The STM doesn't need an SBC to function.
The cheapest board is probably the SKR-RRF-E3 which can be had for around £30. It has built in 2209's and can't support an SBC. You can then use any one of the screens available, i.e. paneldue, fly scree, BTT TFT or 12864. So you could have a complete setup for around £40. It does however only have 4 drivers (there is an addon board that adds another 2 drivers which adds another £10 to the cost) but there are other boards that have 5 or more drivers (Fly-E3-Pro has 5 onboard, SKR 2 has 5 replaceable, Fly-CDYv2/SKR Pro have 6 replaceable, Fly-407ZG has 9 replaceable and SKR GTR + M5 has 11 replaceable).

For some of the boards an additional wifi adapter is needed which is around another £8.

We also don't currently offer any ethernet based boards, so if ethernet was required then an SBC setup would be needed.

SBC

To use an SBC, the boards require an additional set of adapters (you can roll your own), which are around £8-10.

Clones

The duet 2 wifi can be purchased for around £45 but you don't know what you're getting with those.

jay_s_uk

@zapta

I know fly/mellow uses original unused STM32F4 processors. Prices have also started to raise a lot recently.

We believe BTT is using secondhand STM32F4 processors (hence the slightly cheaper prices) but we can't substantiate that either way.

zapta

@jay_s_uk said in What’s the stance on RRF on none Duet boards?:

SKR 2 has 5 replaceable...

I am not sure what I think about the replaceable vs soldered. On one hand, the replaceable are easier to replace when something goes wrong but on the other hand the connector is another thing that can go wrong and overall it looks as a 'ghetto' design.

zapta

@jay_s_uk, the new rave in Chinese boards is the Fysetc Spider. STM32F446 with 8 replaceable TMC2209 for $60 shipped. It has 5V and 12V buck converters for external devices and marlin and klipper support, and got design input from the Voron dev team with the goal to replace the two SKRs. I don't see anything about a wifi dongle.

https://wiki.fysetc.com/Spider/

What's the process of getting RRF support for a new board like this? Is it typically done by the vendor or by the community?

EDIT: The wiki page says this: "As RRF firmware requires more than 512KB of Flash space, the Spider equipped with 446 cannot meet its requirements. So Spider has another version dedicated to running RRF firmware, which uses STM32F407VGT6 MCU."

jay_s_uk

@zapta that board won't get added in its current form.
They've chosen an MCU with only 512kb of flash and the firmware as it stands is already bigger than that for a wifi build
They are releasing a 407 version I believe. Lets just hope they choose the right processor

zapta

@jay_s_uk said in What’s the stance on RRF on none Duet boards?:

Lets just hope they choose the right processor

Just posted an EDIT. The RRF processor is STM32F407VGT6

jay_s_uk

@zapta thats the same processor used on the Fly-E3, E3-Pro, SKR-RRF-E3 and SKR 2.
The next challenge is getting the information for it or even getting a board for testing.

zapta

@jay_s_uk, when I click on Compatible Boards at https://www.reprapfirmware.org/ it shows only Duet3d boards.

Have you tried discussing with reprapfirmware.org owners (Duet3d?) having a more vendor neutral page that lists all boards?

The boundary between RRF and Duet3d is confusing to me.