PROMEGA Duet Firmware 3.0 G Code Update

flynhawaiian

I was wondering if anyone with a promega has done the G-Code update for firmware 3.0 on the duet. If so is it possible someone could let me know what to do or share the files with me?

I'm just getting started with my promega (been in the box since April 2020), and I would like to get it going for printing.

Phaedrux

The biggest hurdle there is that the promega config files are pretty convoluted with lots of nested macro calls, so it's not easy to replace with a fresh config. But it also means it's pretty difficult to go through and manually update all the macros for RRF3 syntax.

flynhawaiian

Do you think it's better to just go back to the 2.0 firmware and not deal with it?

I would love to get this promega working so I could print with it. Just took it out of the box a few days ago finally.

I'm not sure if M3D is helpful or if they are quiting as a company or what specifically.

Phaedrux

Well you very got a few options.

Stick with 2.05.1 and us the stock configs. No problem with that.

Try to update the configs manually yourself line by line to update the things that have changed

Find someone who's already done the update and use their configs

Try and get a simplified rrf3 config working without all the complicated nested macros. It's just a printer after all. There's nothing super proprietary about their configs other than being needlessly complicated.

flynhawaiian

Would love to find someone who did the updates, and use their files. Do you know if the company has gone under?

Phaedrux

I have no idea.

ktapper

Company is still around to my knowledge. But I have a promega that has been pretty converted. The basics of the CoreXY G-Code should work for most part need to make changes to the endstops on the Z. config.g

I recommend reading the RRF3 differences and get Pin calls at the bottom for the Maestro
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview

If you do what I did...I did one line at time looking up in the Overview if it changed..if it did followed the write up if not moved to the next line. All the M98 calls just need " " around the file name for it to work again. I would recommend pulling the data back to the main config and get rid of some of the calls.