UMO / UMO+ Firmware
- Amedee
- Reactions:
- Posts: 599
- Joined: February 15th, 2016, 11:10 am
- Location: Brussels, Belgium
- 3D Printer(s): UMO / UMO+
- Contact:
Re: UMO / UMO+ Firmware
I was thinking of saving the LED brightness in the preferences...
... But we could go from 0 to saved settings with a fade-in
... But we could go from 0 to saved settings with a fade-in
- Neotko
- Reactions:
- Posts: 1142
- Joined: February 7th, 2016, 7:02 pm
- Location: Madrid
- 3D Printer(s): UMO+ x2.5
- Contact:
Re: UMO / UMO+ Firmware
Ohh that could be so sweet!
- Amedee
- Reactions:
- Posts: 599
- Joined: February 15th, 2016, 11:10 am
- Location: Brussels, Belgium
- 3D Printer(s): UMO / UMO+
- Contact:
Re: UMO / UMO+ Firmware
Done!
(In the experimental branch, which has been pulled on the build system as well)
(In the experimental branch, which has been pulled on the build system as well)
- Neotko
- Reactions:
- Posts: 1142
- Joined: February 7th, 2016, 7:02 pm
- Location: Madrid
- 3D Printer(s): UMO+ x2.5
- Contact:
Re: UMO / UMO+ Firmware
Woohoo. Gonna test right away!
- Neotko
- Reactions:
- Posts: 1142
- Joined: February 7th, 2016, 7:02 pm
- Location: Madrid
- 3D Printer(s): UMO+ x2.5
- Contact:
Re: UMO / UMO+ Firmware
Hahahaha this it's brilliant men, literally!
Amedee for president!
So sweet.
Just a question, I suppose that after changing the led power I needed to save settings to eprom right? Or does it write it as soon as you change the led number? Just to know because my instinct was to just store settings.
Tested on my 3 machines, works like a charm.
Amedee for president!
So sweet.
Just a question, I suppose that after changing the led power I needed to save settings to eprom right? Or does it write it as soon as you change the led number? Just to know because my instinct was to just store settings.
Tested on my 3 machines, works like a charm.
- Amedee
- Reactions:
- Posts: 599
- Joined: February 15th, 2016, 11:10 am
- Location: Brussels, Belgium
- 3D Printer(s): UMO / UMO+
- Contact:
Re: UMO / UMO+ Firmware
Yes indeed, you need to save
- drayson
- Reactions:
- Posts: 254
- Joined: February 15th, 2016, 5:04 am
- Location: Graz, Austria
- 3D Printer(s): UMO with mods :-)
Re: UMO / UMO+ Firmware
Yesterday I tied the filament runout sensor
It detects and initiates M600 as it should, moves to a safe position and restracts, but the interestingly when new filament is loaded, it wont´move the filament to the nozzle again...
Has anybody of ou the same issue?
Amedee, maybe you could take a look...
It detects and initiates M600 as it should, moves to a safe position and restracts, but the interestingly when new filament is loaded, it wont´move the filament to the nozzle again...
Has anybody of ou the same issue?
Amedee, maybe you could take a look...
- Amedee
- Reactions:
- Posts: 599
- Joined: February 15th, 2016, 11:10 am
- Location: Brussels, Belgium
- 3D Printer(s): UMO / UMO+
- Contact:
Re: UMO / UMO+ Firmware
What do you mean? I am not sure to understand...drayson wrote:but the interestingly when new filament is loaded, it wont´move the filament to the nozzle again...
Is it:
- Extruder won't work after the swap?
or
- Extruder is not pushing the filament to the nozzle before restarting? (If this is the case, afaik the UMO does not do that, you have to ensure it is ready to print)
or
- something else?
- drayson
- Reactions:
- Posts: 254
- Joined: February 15th, 2016, 5:04 am
- Location: Graz, Austria
- 3D Printer(s): UMO with mods :-)
Re: UMO / UMO+ Firmware
It´s this one. so you mean that I have to prime the nozzle manually. Ok, that sounds logical as the FW does not know the position of the filament.Amedee wrote:- Extruder is not pushing the filament to the nozzle before restarting? (If this is the case, afaik the UMO does not do that, you have to ensure it is ready ?drayson wrote:but the interestingly when new filament is loaded, it wont´move the filament to the nozzle again...
Sorry, my fault/misunderstanding.
- Amedee
- Reactions:
- Posts: 599
- Joined: February 15th, 2016, 11:10 am
- Location: Brussels, Belgium
- 3D Printer(s): UMO / UMO+
- Contact:
Re: UMO / UMO+ Firmware
Yes, the expected behaviour should be:
- Retract 2mm (Or value from the E parameter)
- Lift Z 10mm (Or Z value)
- Move 'home' (Or X/Y values)
- Retract 10cm (or L value)
- Wait until filament is changed
- Move back to original X/Y
- Move Z back on the print
- Push 2mm (Or E value -- set back pressure in the bowden)
- drayson
- Reactions:
- Posts: 254
- Joined: February 15th, 2016, 5:04 am
- Location: Graz, Austria
- 3D Printer(s): UMO with mods :-)
Re: UMO / UMO+ Firmware
Thank you for explaination - helps a lot as I thought first I made a mistake in my settings.
I also tried to use the filament sensor code as a base for my "stop button" but it seems that just replacing enquecommand_P(PSTR(FILAMENT_RUNOUT_SCRIPT));" in marlin_main.cpp
by
enquecommand_P(PSTR(lcd_sdcard_stop()));
had not the expected impact
As more I´m playing around with programming as more I think I learned the wrong (mechanical engineering) in school
I also tried to use the filament sensor code as a base for my "stop button" but it seems that just replacing enquecommand_P(PSTR(FILAMENT_RUNOUT_SCRIPT));" in marlin_main.cpp
by
enquecommand_P(PSTR(lcd_sdcard_stop()));
had not the expected impact
As more I´m playing around with programming as more I think I learned the wrong (mechanical engineering) in school
- martin-bienz
- Reactions:
- Posts: 172
- Joined: February 22nd, 2016, 2:42 am
- Location: Switzerland
- 3D Printer(s): Ultimaker Original, prusa i3 mk2
Re: UMO / UMO+ Firmware
Guys, I don't want to interupt your discussion, just a quick question
When my UMO is printing and I issue an M600 (serial), is this what happens also? Or is this only with Amedee special FW?
When my UMO is printing and I issue an M600 (serial), is this what happens also? Or is this only with Amedee special FW?
- Amedee
- Reactions:
- Posts: 599
- Joined: February 15th, 2016, 11:10 am
- Location: Brussels, Belgium
- 3D Printer(s): UMO / UMO+
- Contact:
Re: UMO / UMO+ Firmware
Right
enquecommand add a GCode command in the execution queue -- so you can only add GCode.
lcd_card_stop() is not GCode, it is a call to a function.
The C language is very powerful, but it allows you to do almost anything without too much checking with very unexpected results
enquecommand add a GCode command in the execution queue -- so you can only add GCode.
lcd_card_stop() is not GCode, it is a call to a function.
The C language is very powerful, but it allows you to do almost anything without too much checking with very unexpected results
- Amedee
- Reactions:
- Posts: 599
- Joined: February 15th, 2016, 11:10 am
- Location: Brussels, Belgium
- 3D Printer(s): UMO / UMO+
- Contact:
Re: UMO / UMO+ Firmware
What I described above is exaclty what M600 is doing. The filament detection just enqueues an M600.martin-bienz wrote:Guys, I don't want to interupt your discussion, just a quick question
When my UMO is printing and I issue an M600 (serial), is this what happens also? Or is this only with Amedee special FW?
Although I have some plans to improve this, I have not touched the M600 handling, so it is still 'standard', which means you can only restart the print with a click on the controller. You cannot restart remotely
- martin-bienz
- Reactions:
- Posts: 172
- Joined: February 22nd, 2016, 2:42 am
- Location: Switzerland
- 3D Printer(s): Ultimaker Original, prusa i3 mk2
Re: UMO / UMO+ Firmware
Thank you.
Which makes sense, I guess.Amedee wrote: You cannot restart remotely