Marlin Firmware Upgrade 1.1.0 RC8 & RCBugFix (For R1 & R1+PLUS)

@danzca6 It just takes too long.

1. What do you think of the way the LCD works now?
2. Have you set a FADE yet?

 

@danzca6, @Ed Ferguson
I would think that it is model dependent. And based on where exactly you need to have any details close to the bottom of your model. I don't think the developers addressed that particular question. I am pretty sure it was 'stolen' from the UBL code that Roxy-3D is working on and added to Marlin 1.1.0. Since my bed is fairly warp free when heated I did not set a value for FADE (M420)

One more note, there is something I want to try and it's in yesterday's commits. They added M-code commands to control a 3-pin RGB LED direct from the RAMPS (with the appropriate pull-down resistor). So I am going to replace the files from yesterday's posts, sometime this morning.

The code used was M150 (examples below):

Code:

M150 R255  ; Turn LED red
M150 R255 U127  ; Turn LED orange (PWM only)
M150   ; Turn LED off
M150 R U B  ; Turn LED white

I believe if you have done this RGB LED mod by @Marquis Johnson you will need to assign pins 4, 5 and 6. You would replace these lines in Configuration.h (# 1368 - 1370):

Code:

  #define RGB_LED_R_PIN 34
  #define RGB_LED_G_PIN 43
  #define RGB_LED_B_PIN 35

With these new values:

Code:

  #define RGB_LED_R_PIN 6
  #define RGB_LED_G_PIN 4
  #define RGB_LED_B_PIN 5

You do not use any of his code.

 

New functionality added to the November 30th files located at these posts, RGB lighting control:

Auto bed leveling: http://community.robo3d.com/index.p...st-rc7-for-r1-r1-plus.5806/page-45#post-97535

MESH bed leveling: http://community.robo3d.com/index.p...st-rc7-for-r1-r1-plus.5806/page-45#post-97536

 

@danzca6, note that this is different than CASE_LIGHT and TEMP_STAT_LEDS.

CASE_LIGHT defaults to Pin 4 and is controlled either by a menu choice on the LCD controller or M355

Code:

M355 S0 - Case light off
M355 S1 - Case light on
M355 Sx - Set case light intensity between 2 and 255

TEMP_STAT_LED is different again, and seems to be only relegated to basically 'cold' or 'warm to hot.' I don't even know where those connect and don't know how it's controlled other than the fact that there are a blue (or green) one and a red one. The blue (or green) one is on if the hotend and bed are below 54°C and the red on is on if either are above that temperature. -- This must be for the LEDs soldered to the RAMPS board.

So it looks like you could have a dimmable CASE_LIGHT that you can turn off and on via the LCD and dim with M355 and at the same time an RGB LED (or strip) that can be turned to any color by using M150 and parameters behind it. I could see some use for RGB lighting based on G-code positioning. Lighting for the case might be more important if I was doing time-lapse, maybe have extra LEDs that turn on when engaging the PHOTOGRAPH_PIN or doing some OctoPrint stuff.

If I only had a Robo R2, I could see modding it to add a bunch of lights controlled by g-code. Maybe you could then see inside that dark cavity.

 

No, the TEMP_STAT_LEDS can't be controlled other than enabled or disabled.

The STAT_LED_RED|BLUE_PIN in the pins file is only for the Viki2 and MiniViki, No one should be using those since they are built unlike any other controller on the market and are incredibly slow, because they built the screen in upside down and it requires the LCD routines to rotate the screen 180°. Even the new screen writing routines do not help the Viki, it writes at about half the speed of even the cheapest Chinese LCD screens.

But it does seem out of character to put the pin definitions in Configuration.h.

Yes, but I could also see it using something like the post processing routine in S3D to inject different values at different points in the code.

On a side note, you could use #define LCD_SCREEN_ROT_180 and then you could mount the LCD controller upside down if you wanted the encoder knob on the left side.

 

@danzca6 you are making this more complicated than it is. You can use it if you enable RGB_LED. They are predefined for the Viki which actually has a blue and red LED mounted behind the encoder knob. Otherwise you need to use Configuration.h to enable line # 1366 and connect each LED leg to the appropriate pin and gnd to the LED common. It was basically added to give Vicki like functionality extended to three colors without all the downside of owning a Viki.

I believe they chose those pins out of convenience and legacy for the Viki. I would instead use the ones that @Marquis Johnson chose as they are all able to output 8-bit PWM. Without additional circuitry they can only output about 40mA at 5V. Plus they are easier to get to if you have an LCD installed.

 

I could see using the CASE_LIGHT as some kind of notification signal at the end of a print. In the Scripts tab of S3D in Ending Script you could do something like this

Code:

M104 S0 ; turn off extruder
M140 S0 ; turn off bed
M84 ; disable motors
M355 S0
G4 S2
M355 S1
G4 S2
M355 S0
G4 S2
M355 S1
G4 M2
M355 S0
G4 S2
M355 S1
G4 S2
M355 S0

This code would blink the case lights 3 times at 2 second intervals before eventually turning them off.

 

Marlin has some cool stuff (like this) that is why we used it for the DLP -- it was easy to add the solenoid commands to open/close the shutter.

 

I don't currently have any RGB LEDs other than in a pre-configured 12v strip. I also don't need another project.

 

I hear that...

 

If you use the Print from SD function and bury your files below the root directory there is some screen updating bug in the GLCD routines. They are fixed as of Dec 2nd. I won't upload a new set of files until the 15th or so. I don't print from SD since I use a Raspberry Pi and OctoPrint and the corruption is just related to the screen and goes away when you exit the Print from SD menu selection.

 

I just tried all filesets and they compiled fine on Arduino IDE 1.16.13 Don't know what this one is:

Either a corrupt download, or an incomplete directory (did you create a new subdirectory or just overwrite an existing one?) or IDE configuration issue.

Download the latest version of the IDE from www.arduino.cc and do not use the one on Miscrosoft Store. The latest version is 1.6.13.