Control Ultimaker 2 LEDs Via GCode?

[scottd 0]

Hi Everyone,

Long time lurker here. I am just curious if anyone knows how to control the LED lights on the Ultimaker 2 using GCode. I currently have my UM2 machines controlled with Octoprint and I would like to be able to send GCode commands to control the PWM of the LEDs during a USB print.

Thank you very much.

Scott

[Labern 775]

Using LED J15: Control it in G Code with M42 P13 SXXX where XXX is a value between 0 and 255. Use M42 P13 S0 to turn the leds off.

But I may be wrong.

[tinkergnome 927]

Using LED J15: Control it in G Code with M42 P13 SXXX where XXX is a value between 0 and 255.  Use M42 P13 S0 to turn the leds off.

But I may be wrong.

 

Actually LED_PIN is 13 on the UMO board and pin 8 (PH5) for the UM2...

...but never mind - the LED_PIN is the default for the M42 command.

You can omit the pin number and everything between

"M42 S0" and "M42 S255"

should work with every Marlin version out there...

[scottd 0]

Hey Labern,

Thanks for the info.  I am using Octoprint to send G Code commands to my printer and unfortunately, the M42 command on Pin 13 seems to be killing the connection to the printer.

I sent M42 P13 S0 to the printer and the LED turned off, so I thought I was good, but I just realized the connection has been killed and would need to be reconnected.  Any other commands I sent to the printer (i.e. M105), would get no response after that.

Is there a way to confirm that the LEDs are using Aux Pin 13?

Thanks again!

--Scott

Edited October 12, 2015 by Guest
Spelling

[scottd 0]

Actually LED_PIN is 13 on the UMO board and pin 8 (PH5) for the UM2...

...but never mind - the LED_PIN is the default for the M42 command.

You can omit the pin number and everything between

"M42 S0" and "M42 S255"

should work with every Marlin version out there...

 

Excellent.  I think my issue may be with Octoprint sending the commands.  If I send M42 S0 it will lock up the connection.  The LEDs do turn go off every time the connection breaks though.  

Very strange behavior.

Thank you,

--Scott

Edited October 12, 2015 by Guest

[scottd 0]

Can anyone confirm the M42 command works with the Ultimaker 2? If so, I will take a look at Octoprint as being the culprit of the behavior.

Thanks guys!

--Scott

[neotko 1,417]

It works. I use it on my umo+ (same board)

[scottd 0]

Thank you very much for the confirmation. I have opened an issue with OctoPrint to see what could be going on here. Thanks again everyone.

--Scott

[scottd 0]

It works. I use it on my umo+ (same board)

 

Which application are you using to send the G Code to your machine?

I just tried using Printrun to send the M42 S0 command and it failed and locked up the connection the same as it did with OctoPrint.

Any thoughts on what could be going on here? Maybe there is a difference between the UMO+ board and the UM2 board?

Can anyone test on an UM2?

Thank you,

--Scott

[neotko 1,417]

Which application are you using to send the G Code to your machine?

 

I use it on my auto0.g file on my umo+ it makes the lights to go on when the printer it's power on.

The M42 it's described on the Marlin for Ultimaker 2

https://github.com/Ultimaker/Ultimaker2Marlin/blob/master/README.md

Edited October 12, 2015 by Guest

[Labern 775]

 

Using LED J15: Control it in G Code with M42 P13 SXXX where XXX is a value between 0 and 255.  Use M42 P13 S0 to turn the leds off.

But I may be wrong.

 

Actually LED_PIN is 13 on the UMO board and pin 8 (PH5) for the UM2...

...but never mind - the LED_PIN is the default for the M42 command.

You can omit the pin number and everything between

"M42 S0" and "M42 S255"

should work with every Marlin version out there...

 

I just happened to be reading a post on using and UM2 for laser engraving so was a cut n paste from that article. But glad you corrected the mistake.

[scottd 0]

Has anyone been able to confirm that this M42 command works on the UM2? Both of my UM2 machines crash when I send this command either through a terminal or running off the SD card. Very strange, right?

[scottd 0]

A little additional info about the SD card testing... I put the M42 S0 command at the beginning of one of my prints and when I ran it from the SD card it crashed the printers. This is happening on all 3 UM2s that I tested it on.

Any help would be appreciated!

Thank you,

--Scott

[tinkergnome 927]

Has anyone been able to confirm that this M42 command works on the UM2?

 

I found some time today and made a short test.

I can confirm that this command does not work properly. Your printers hardware is ok and Octoprint too, i'm pretty sure that you found a bug in the Marlin firmware. Honour to whom honour is due.

I will take a closer look at it in the next days and fix it for the tinker firmware. Which firmware version are you using?

[scottd 0]

WOW! That is good that it was not just me, I thought I was crazy for a moment. I am using firmware version 15.04.02 on all of my machines. I believe this is the latest.

Please let me know if you need anything else. Thanks!

--Scott

[tinkergnome 927]

Ok, it was i simple fix. The M42 command works like intended now.

Here is the updated release of the tinker firmware. You can install it with Cura 15.04 (Machine -> Install custom firmware...)

I also made a pull request for the standard firmware, but there was no activity for months -

so this may take some more time...

Edited October 23, 2015 by Guest

[scottd 0]

Thank you so much for taking a look at that!

I will install the tinker firmware once my printing queue frees up a bit.

Thanks again! Hope to see this in an official release soon.

--Scott

[gpb01 23]

@scottd

listen to me ...

... one time you install "Tinker" firmware ... you never go back to the "official" :D

Guglielmo

P.S.: I hope ... maybe one day ... "Tinker" firmware becomes the "official" one

Edited October 24, 2015 by Guest

[scottd 0]

@scottd

listen to me ...

... one time you install "Tinker" firmware ... you never go back to the "official" :D

Guglielmo

P.S.: I hope ... maybe one day ... "Tinker" firmware becomes the "official" one

 

Installing Tinker now!

[scottd 0]

Oh no! I installed the Tinker Firmware and when I use OctoPrint, my nozzle will shut off as soon as it gets to temperature on every print. Is there a place where I can log this issue for this Firmware?

Thanks,

--Scott

[tinkergnome 927]

Oh no!  I installed the Tinker Firmware and when I use OctoPrint, my nozzle will shut off as soon as it gets to temperature on every print.  Is there a place where I can log this issue for this Firmware?

 

Assuming that everything else is the same as before (esp. the gcode file), this indeed should not happen.

Best would be to report a new issue on the GitHub page. You can attach additional files there. Though you would need to create an account first (it's free).

[gpb01 23]

Oh no!  I installed the Tinker Firmware and when I use OctoPrint, my nozzle will shut off as soon as it gets to temperature on every print.

 

Hi Scott,

I don't use OctoPrint (... I still believe that USB printing is NOT reliable, but it is just my personal opinion), but, as also tinkergnome said, this should not happen so ... please follow thinkergnome instructions and open ad issue on GitHub ...

... and you help all the community to have a better firmware

Guglielmo

[scottd 0]

My Tinker Firmware is now installed and functioning correctly! This is outstanding firmware with great support. I am not sure I will be able to switch back.

--Scott

[ultiarjan 1,223]

So what was the problem with octoprint?

[tinkergnome 927]

So what was the problem with octoprint?

 

Actually it's a firmware bug...

I think the heater timeout prohibits USB printing at the moment. The (temporary) solution was to disable the timeout in the preferences.

Who has programmed this nonsense? ... ... ... oh ...