Originally shared by René Jurack Look what a matt black beauty arrived today :)

@Rien_Stouten do some research and get back to us…

@Jeff_Para you’re in the wrong here – you really should re-read @Rien_Stouten 's original post. The beginning part of his post was obviously facetious/sarcastic.

Now I’m just waiting for Marlin 32-bit to be released :slight_smile:

Not only will I have a drop in upgrade for my hardware, but also a seamless upgrade for Marlin will be officially Marlin 32-bit.

@Panayiotis_Savva I second that!!

Backer number 69 here, looks like mine should come in tomorrow. Does is already have the firmware flashed?

Firmware is already on it, although I actually haven’t bothered to check what Ver it is. So far so good, things are different from Marlin so it’s a learning experience.

lol @ the marlin 32 bit comments. Why anyone would want to use that on a 32 bit controller baffles me.

@ThantiK ​, let’s not go down that route again…

Remain baffled until you try out Marlin.

@Jeremiah_Coley Firmware upgrades mean just putting a file on the uSD card and turning it on. Reflashing to change configuration is history because you can just change your configuration file, save and reset the board. Though I suppose you could already do something like that with EEPROM on your existing board.

@ThantiK
I’m very chllled actually :slight_smile: and I did not mean to imply that these boards are cheap . . …sorry.

@ThantiK - I guess why someone would use Marlin 32bit is familiarity and not liking change. Personally, I’ll be moving to Smoothieware when my Re-Arm comes in. That being said, and baring in mind that I’ve not physically used Smoothie as yet, configuration (which I’ve set up ready for the FB2020 it’s going in) isn’t really any different imo, it’s still a file you need to edit and learn what does what. In use, I couldn’t say as yet. For me I’d rather use a well established firmware over a new firmware, which could end up with bugs.

@Ax_Smith-Laffin I’ve been seeing your reference to FB2020, is that a FuseBox design that uses coreXY movement? If so, would you mind sharing your config? I’ve starting creating one for my D-Bot build, but I haven’t gotten very far and I’d like to compare against another coreXY config to make sure I’m not missing anything. Thanks!

@Ax_Smith-Laffin the problem with Marlin is that it’s not a “well established” firmware other than it existed longer. There are many hacks and other unfortunate garbage in Marlin. Smoothieware has been built from the ground up to ensure smooth timing between motor pulses, easy/flexible configuration, etc. It’s extensible, it’s well written, and 32 bit Marlin is Marlin in name-only. It’s less established than Smoothieware is, by far.

@ThantiK ​, that is where you are very wrong.

Marlin has been redesigned in many ways.

The hacks of the past are almost non-existant anymore.

There have been a few key people in the Marlin community that had brought the firmware forward in an excellent state.

I wish you would review the implementation of Marlin before saying it’s a hack…

I have personally developed a small part of Marlin and the people in the community are really vigilant in reviewing and improving the code.

Features such as LIN_ADVANCE, Bilinear bed leveling, BLTouch support, multi-lingual support, single nozzle support with multiple extruders (diamond hotend) and much much more is what makes Marlin great!

The people implementing these features are not hacking the code. They’re architecting and improving Marlin every minute they can.

Please stop knocking down a great piece of software.

32 bit will bring Marlin in line with new hardware, but certainly the features are rich and complete as you would expect from any Printer Firmware.

@ThantiK - not disagreeing with you there. I’ve only taken a look at Marlin 32bit briefly, and I’m no programmer (I can barely write a BASH script and I was a Linux SysEng) so I can only comment from an end user point of view.

@Geoffrey_Forest - You’re correct, the FB2020 is a Fusebox Derivative, however a lot of it has been designed from the ground up, I think currently all that’s Fusebox now is the Corner brackets and XY motor holders, everything else has either been modified or re-designed as I found the Fusebox parts flimsy as hell. My Smoothie config is here - https://www.dropbox.com/s/3mdmzwq6kde7my2/config?dl=0 - I cannot guarantee it will work as it’s not been tested due to my Re-Arm being part of the January batch.

@Panayiotis_Savva , have you ever thrown a controller with Marlin on a scope? Ever? Marlin does some dirty, nasty stuff with stepper motor timings in order to get a controller that is too slow to be able to move motors as fast as it does.

@Ax_Smith-Laffin Thanks! I just want something to compare mine with. I also saw the kickstarter posted some guides and reference material, including a sample configuration. So I’ve got a lot of guidance now.

@ThantiK That’s out of my technical knowledge boundaries.

Have you ever put Marlin on a scope?
If so, what was your findings?
What do you mean by nasty and dirty stuff?

@Panayiotis_Savva , Marlin - when faced with a CPU cycle shortage will simply double and quadruple steps. Without any appreciation for motor timing requirements. So you’ll get motor steps that are 80us apart, normally, but then 4 steps that are 6-8us apart bunched together then a 80us pause, then 4 more steps that are 6-8us together, etc.

Marlin doesn’t do like smoothie does, and keep motor steps equally spaced. This results in more noise, etc. This was done on the 8 bit controllers because they are not actually fast enough to do calculations between each step past a certain speed.

Marlin is inferior to Smoothieware, and why people are wasting man-hours on it is beyond me. It’s NIH syndrome at its finest…

Mine is stuck in Texas and I’m in Louisiana. Need to get home, want to try it out on an i3…