Jump to content
Ultimaker Community of 3D Printing Experts
Daid

Inside the Ultimaker 3 - Day 1 - GCode

Recommended Posts

Setting the LED colors from the API is broken in the current firmware release I think.

Issue: EM-563: API set lighting does not work (status: todo)

Most things are indeed python. Except for the display interface and marlin (and linux stuff like the kernel)

Share this post


Link to post
Share on other sites

Ultimaker absolutely needs all resellers to have a few micro SD cards to unbrick machines that get corrupted such that the reseller can mail the SD card to the customer who can insert it into the A20 board and reload the operating system (and then of course update it to latest the normal way through Internet).

and arduino github link would be nice. :)

 

I don't think there's a need for SD cards for that. The USB plug on the front of the machine connects directly to the miniusb port, the documentation shows that is posible to use it as boot. They just need to make a system check so when the machine turns on, while pressing the wheel (for example) it forces a USB check and firmware install if the USB drive has the firmware files on it. Of course, that system restore should be a check that loads before any other service, so it can have a fast/easy factory restore.

I think resellers should just buy the 12€ cable if they have linux know-how to debug failing parts. Is quite un-intrusive and easy to do. Ofc, the UM3 already have a really good DUMP LOG that shows almost everything that happens or doesn't happen on the machine.

Of course, with the SD boot img to burn on a SDcard, it could be much easier to play with the little board and do experiments without risk of bricking the linux boot.

Edited by Guest

Share this post


Link to post
Share on other sites

Nope, the USB booting is done after MMC2 booting (on which the bootloader is contained) so unless you mess up the bootloader, it will try to boot your system instead of the USB booting.

And most likely, if you messed with python code, linux is starting fine. It's just that the display cannot run because other parts fail. As long as you don't mess up the griffin.system service, you should still be able to ssh into the machine and fix up your mistake.

Share this post


Link to post
Share on other sites

That won't work with our image, due to the USB port being configured differently. I thought you where talking about: http://linux-sunxi.org/FEL/USBBoot

But do note that putting any image on an micro sd card and putting that in does boot from that. So that's always a recovery path. Even if you use the stock Olimex image to boot and fix our installation from there.

  • Like 1

Share this post


Link to post
Share on other sites

Hey guys! So just to make sure I understood correctly. To change/turn off the LEDs I add the M142 RxxxGxxxBxxxTx code after the header (not in it).

 

doesn't matter where you put it, but put it after the header anyway.

M142 is for the case leds. (has no T parameter) and has rgbw parameters (note: lowercase!)

M143 is for the head leds.

There is an API for the case leds that will work in future firmware version 3.5.x

Share this post


Link to post
Share on other sites

 

Hey guys! So just to make sure I understood correctly. To change/turn off the LEDs I add the M142 RxxxGxxxBxxxTx code after the header (not in it).

 

doesn't matter where you put it, but put it after the header anyway.

M142 is for the case leds. (has no T parameter) and has rgbw parameters (note: lowercase!)

M143 is for the head leds.

There is an API for the case leds that will work in future firmware version 3.5.x

 

Alright! Thanks! So I'm guessing in order to turn off the LEDs just input the code for the color black, right?

Share this post


Link to post
Share on other sites

Yes. In the future, M142 will change to M142 H[hue] S[saturation] V[value]

I've submitted that patch for review yesterday. Will be most likely in the December firmware update.

As right now, the M142 bypasses the whole system and directly sets the leds. Which means the "led subsystem" as no idea that you did that. And the API values also do not update.

We are using HSV instead of RGB because that is a more natural way to work with colors. And you can dim the lights without changing the color way more easily.

Edited by Guest
  • Like 1

Share this post


Link to post
Share on other sites

if I change this file, will it be overwritten with a firmware update?

also, if i wanted to reverse the feeder, is that possible?

 

 

  1. Yes it will be overwritten.

  2. we will probably have a way to override these files that is not overwritten when you update your machine in the future but be patient for that :)

  3. you can't reverse the direction from that file AFAIK (maybe we should add that... but for now that is still compiled into marlin)

 

Edited by Guest
  • Like 1

Share this post


Link to post
Share on other sites

The motor might reverse if you put in negative E steps. But that could also break things, didn't try that.

Planning to make it easier to have a custom json file. This also helps us internally on various experimental machines. I took a quick look at doing this today, but the code was a bit more complex then a quick patch.

  • Like 2

Share this post


Link to post
Share on other sites

The motor might reverse if you put in negative E steps. But that could also break things, didn't try that.

Planning to make it easier to have a custom json file. This also helps us internally on various experimental machines. I took a quick look at doing this today, but the code was a bit more complex then a quick patch.

 

you are the best. next time i'll bring you beer.

also, is there a simple way I can get printer statistics ? like hours printed witha  core?

also : is there a way to easily change the current to the stepper motors?

Edited by Guest

Share this post


Link to post
Share on other sites

you are the best. next time i'll bring you beer.

also, is there a simple way I can get printer statistics ? like hours printed witha  core?

also : is there a way to easily change the current to the stepper motors?

 

Printer stats will be added in the API on a firmware update. We are already collecting things, but they are not yet exposed.

Currently the motor current is hard-coded in griffin/printer/controller.py

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • Architect Design Contest | People
      The goal of this contest is to design a set of people figurines that could be used in such a project to make an area, office or mall seem populated. 
      Think of different types of people in different environments, like walking people, people standing still, working people, and both men and women.
       
      • 31 replies
    • Taking Advantage of DfAM
      This is a statement that’s often made about AM/3DP. I'll focus on the way DfAM can take advantage of some of the unique capabilities that AM and 3DP have to offer. I personally think that the use of AM/3DP for light-weighting is one of it’s most exciting possibilities and one that could play a key part in the sustainability of design and manufacturing in the future.
        • Like
      • 3 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!