3D Printing Forum

Amedee wrote:I committed a couple of changes over the week-end

• @Neotko request to have the fan kickstart in the builder
• Removed PS_ON_PIN assignment for naked UMO (as reported by @drayson) -- as side effect it will remove the 'power off' option which does nothing in the controller menu!
• Fixed a Marlin bug related to auto.g files (for the ones still printing with SD-Cards )

Details in the commit log

Youuu rock men!

The fan kickstart it's online on the builder? Just wondering

Yes, in the experimental page

(I didn't test it myself, for the experimental branch I am relying a bit on you guys )

Cool, thanks! Fixes my annoying autoX.g bug

I'll test my fans tonight. S3D sets a 500 millisec pause to kickstarter them. Thankkkssss!!

Well tested kickstarter.

100-200 are almost like nothing, I would remove them. 300 only failed on me 2/6 and 400 worked perfectly 10/10 times. I would set as default a minimum of 400millisecs and I think 500 could be just perfect (ofc this depends on the fans) but I didn't 'fell' that 100-200-300 was enough for the fans to really get a nice spin.

The Motors current (I haven't test it yet) looks soooo sweet (menu and easy to understand).

Thanks for this @amedee best firmware ever!

Ohh men that auto.g bug it's the one you fixed? I stopped using auto.g exactly because of that!

It was so annoying that after a print was done sometimes it was going again for it. So it was because the sd was inserted after turning it on!

I'll start to make a new auto.g to make the leds fade at start

Neotko wrote:100-200 are almost like nothing, I would remove them. 300 only failed on me 2/6 and 400 worked perfectly 10/10 times. I would set as default a minimum of 400millisecs and I think 500 could be just perfect (ofc this depends on the fans) but I didn't 'fell' that 100-200-300 was enough for the fans to really get a nice spin.

Thanks for the feedback. I'll tweak the values in the builder -- I started at 100 because it is the default in the builder, but obviously I don't think either that a 1/10th of second pulse is enough to get a fan running.

Neotko wrote:Ohh men that auto.g bug it's the one you fixed? I stopped using auto.g exactly because of that!

It was so annoying that after a print was done sometimes it was going again for it. So it was because the sd was inserted after turning it on!

Hey, at least someone else who saw that!
Yes, it is a real Marlin bug --you only hit it if you boot without SD and the card with the first SD print has an auto.g file...
It is an edge case and as I don't think a lot of people are using the auto.g files it never came to light.

I'll do a couple of additional tests this week and then I'll merge all the experimental branch in the stable one. Some advanced features may not be fully tested, but I am confident nothing is broken in the core functionality.

Please forgive my ignorance, but what are auto.g files and what are they used for?

From Marlin Readme:

If you place a file auto[0-9].g into the root of the sd card, it will be automatically executed if you boot the printer. The same file will be executed by selecting "Autostart" from the menu.
First *0 will be performed, than *1 and so on. That way, you can heat up or even print automatically without user interaction.

I had no idea you could make a printer autostart like that.

Ah! Okay, I thought it is something that I saw once on a trade show where they had a g-code file that printed a small part, pushed it from the build platform with the extruder and then started printing another one.

Hi @amedee

I will like to ask an extra option.

Could we have the led startup (it's quite cute) um2 led turn on? I think it's on the um2 marlin

lcd_menu_startup()
{
lcd_lib_encoder_pos = ENCODER_NO_SELECTION;

LED_GLOW();

On the UltiLCD2

Or something very silly I know...

Can you elaborate?
I have no clue on what you are talking about
(I never used an UM2 )

Sure sorry. I never seen a um2 in live too XD but, because my um2.1 china board was flashed with um2 firmware, when I turned on the led lights made a fade from 0 to 100ish, and it's so cute. Also it's quite boring to turn the leds on everytime (but as much as before because you fixed the auto-gcodes).

https://ultimaker.com/en/manuals/130-calibration
Check the first animation from ultimaker. When turns on it fades from off to on at the startup.

Can't embed a mp4 but it's this:
https://s3.amazonaws.com/app-cdn.ultima ... _step1.mp4