RepRapFirmware 2.04RC4 released

dc42

UPDATE:

There is an intermittent problem when you upload to 2.04RC4 with CRC checking enabled. Sometimes the CRC calculation is not carried out, resulting in the calculated CRC being reported as zero and the upload failing. Uploading to RRF 3.0 beta11 or later with CRC checking enabled does not have this problem.
This issue is compounded by the fact that whenever you edit config.g, Duet Web Control first renames config.g to config.bak. So even though RRF 2.04 doesn't replace the original file until the upload has definitely succeeded, this renaming means that if you try to edit config,g and the upload fails because of the CRC calculation or any other error, the original config.g file is left renamed to config.bak.

chas2706

@dc42
In my case it is not intermitant it is guaranteed as long as crc checking is enabled.

wilriker

@chas2706 Have you already tried flashing the firmware again? There are very rare cases where flashing succeeds as a process but something was still going wrong. Usually flashing the firmware again (after a fresh download) helps then.

chas2706

@wilriker I just did an upgrade from 2.02RTOS.
Are you talking about just going through the upgrade process again or pressing the erase button and re-flash with 2.04RC4 ?

wilriker

@chas2706 There is no need to go the Erase-Reflash-Route. You can just redownload the firmware binary, upload it to the SD card and either run M997 manually or answer with yes if DWC asks you if you want to install the just uploaded firmware (if you do that via DWC).

chas2706

@wilriker OK cheers. I will do that and see if there is any improvement.

jdjeff58

@droftarts said in RepRapFirmware 2.04RC4 released:

@jdjeff58 The Maestro is a capable board; I have one! I haven't had any problems with updating firmware, but M3D did roll their own version of the firmware. It depends what version you were updating from, too; there are some caveats updating from old versions. Sometimes it's better to erase the board and upload new firmware via USB, as described here: https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_3

Have you got a link to where problems with this board are discussed? As far as Duet3D are aware, the problem seems to have been that the motors were not well matched to the board. I don't have any more details than that. If the PSU has died, is the machine still under warranty? I'd approach M3D and see what they say.

Ian

Hi Ian....the M3D Promega was an overall failure. It was poorly executed and it was cheaped out. Even with my limited experience, I was able to see where obvious corners were cut and shortcuts taken. Some of the more experienced guys were pointing out even more technical problems with the gantry, the motors, the idlers. M3D would ban people from the discord M3D.app for talking crap about the machine. (I at least give them credit for pioneering something as "banned for truth" has become pretty mainstream.) My contact from the user community told me (on the phone) this past week the M3D is all but shut down. As I said in one of my original posts that frustration peaked to the point of punching the print bed and likely surging the stepper driver(s). The machine along with the Promega community is pretty much dead. My contact bought 5 of their machines in hopes of boosting his production rates and he's stuck with a bunch of boat anchors. If you go on M3Ds' website they are selling the maestro for $99 all sales final. These people are the carnival that left town.

Mine was printing fine until I went and tried to update firmware and when I did it seemed like it wouldn't load the bedmesh as my prints were not level on the first layer. That was the final straw after all this screwing around with this horrible "project" Yes...it was not necessarily broke...although dual extruders were cut down to a single extruder, firmware painfully rolled back to 2.02beta (the only way I could get this thing to print successfully). So I was able to use it to print parts for my 2 Prusas....that by the way I built both from kits with an MMU2S on one of them and got them printing superbly from the start. Which is saying alot based on my experience level and comparing it to the stinking promega.

So the long answer to your question, the discord channel M3D was where all the noise was about the Maestro board. Testing was being done in the background proving numerous engineering mistakes/oversights/cheaping. These tests would either go ignored by M3D or just flat out lied about. The number of the screws used was cut in half and M3D came up with stupid excuses for having half the machine with open screw holes. Made the machine less rigid they said. They were explaining off all their cheaping out with some dumb explanation that made no engineering sense whatsoever. It needed a more powerful extruder motor as eventually someone fabricated a gearbox and later M3D sold a larger "upgraded" Stepper motor that yes...we had to pay $50 for. Anyway, even in my recent phone conversation, it was said to me that even the people at Duet were unhappy with M3D for one reason or another. And now I think I am hearing why.

So now that board and PS are burnt, I can either replace them and try to deal with the difficulty (at my current skill level) of setting up a new board, or shop around for a different printer. My contact told me to look into building a BLV Cube. Looks a little daunting based on what I've looked at so far. I need clear instructions for this stuff. So I'm still trying to sort out which direction I want to go.

Veti

my maestro is working like a charm. i did get it from a duet redistributor.

could it be that the boards sold by m3d where cheaped out on as well?

droftarts

@jdjeff58 Thanks for the backstory. Having worked for a number of manufacturers, I know how difficult it is to cope with dissenting voices, but also know that banning them is not really the answer. Being open, engaging with them, resolving problems and getting people back on your side is really the only thing to do.

@Veti No, according to @T3P3Tony it was M3D who asked Deut3D to develop and make the Maestro! So they are genuine Duet3D boards.

Ian

jdjeff58

@droftarts said in RepRapFirmware 2.04RC4 released:

@jdjeff58 Thanks for the backstory. Having worked for a number of manufacturers, I know how difficult it is to cope with dissenting voices, but also know that banning them is not really the answer. Being open, engaging with them, resolving problems and getting people back on your side is really the only thing to do.

@Veti No, according to @T3P3Tony it was M3D who asked Deut3D to develop and make the Maestro! So they are genuine Duet3D boards.

Ian

Ok...that's water under the bridge. Back on topic sort of....If I get a Duet 2 Ethernet, will it be the firmware in this thread that I would want to have installed on the board?

droftarts

@jdjeff58 said in RepRapFirmware 2.04RC4 released:

Ok...that's water under the bridge. Back on topic sort of....If I get a Duet 2 Ethernet, will it be the firmware in this thread that I would want to have installed on the board?

Yes. As this firmware has only recently been released, Duets in the supply chain will probably have older firmware, likely v2.03. However, updating should be simply a case of getting the board up and running on your network, then uploading the "Duet2CombinedFirmware.bin" from the firmware release https://github.com/dc42/RepRapFirmware/releases/tag/2.04RC4 via the 'System > Upload System Files' option. Once uploaded, the Duet will ask you if you want to install the firmware and restart.

Ian

jay_s_uk

@jdjeff58 You could build a jubilee printer

jdjeff58

@droftarts said in RepRapFirmware 2.04RC4 released:

@jdjeff58 said in RepRapFirmware 2.04RC4 released:

Ok...that's water under the bridge. Back on topic sort of....If I get a Duet 2 Ethernet, will it be the firmware in this thread that I would want to have installed on the board?

Yes. As this firmware has only recently been released, Duets in the supply chain will probably have older firmware, likely v2.03. However, updating should be simply a case of getting the board up and running on your network, then uploading the "Duet2CombinedFirmware.bin" from the firmware release https://github.com/dc42/RepRapFirmware/releases/tag/2.04RC4 via the 'System > Upload System Files' option. Once uploaded, the Duet will ask you if you want to install the firmware and restart.

Ian

Thanks IAN....good to know

jdjeff58

@jay_s_uk said in RepRapFirmware 2.04RC4 released:

@jdjeff58 You could build a jubilee printer

I appreciate that link jay. And having already looked at doing a BLV cube, I think I'm going to steer clear of these levels of DIY. At my current place on the learning curve, I really need kitted machines at the very least. That whole parts sourcing using a BOM (scratch builds) is just too daunting for me at this time.

Phaedrux

@jdjeff58 said in RepRapFirmware 2.04RC4 released:

@jay_s_uk said in RepRapFirmware 2.04RC4 released:

@jdjeff58 You could build a jubilee printer

I appreciate that link jay. And having already looked at doing a BLV cube, I think I'm going to steer clear of these levels of DIY. At my current place on the learning curve, I really need kitted machines at the very least. That whole parts sourcing using a BOM (scratch builds) is just too daunting for me at this time.

Perhaps consider a RailCore II. Comes as a kit or prebuilt.

Veti

@jdjeff58 said in RepRapFirmware 2.04RC4 released:

I really need kitted machines at the very least

there is also the upcomming prusa xl.
https://blog.prusaprinters.org/original-prusa-mini-is-here-smart-and-compact-3d-printer/

avaradus

@dc42 said in RepRapFirmware 2.04RC4 released:

@Adrian52, thanks for your report. Looks like output buffers are still being lost somewhere. I will look into it.

Hello!
I want to write about buffer overflow problems.
I looked at the code of the program OutputMemory.cpp
I saw that each buffer has a time of its creation whenQueued.
And there is a GetAge function to see the age of a busy buffer.
You must make the M122 command show Used output buffers and show GetAge age for each buffer.
Maybe then it will become clear in which cases these buffers accumulate and how to fix it