From cacf1197b6fba499980aeb0e3c8946a6fdede204 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Fri, 9 Apr 2021 17:50:30 -0400 Subject: [PATCH] docs: Minor changs to pca9533 in Config_Reference.md Signed-off-by: Kevin O'Connor --- docs/Config_Reference.md | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/docs/Config_Reference.md b/docs/Config_Reference.md index 9c9755ff..d2c2c0b8 100644 --- a/docs/Config_Reference.md +++ b/docs/Config_Reference.md @@ -2471,27 +2471,29 @@ clock_pin: #initial_BLUE: 0.0 # See the "neopixel" section for information on these parameters. ``` + ## [PCA9533] + PCA9533 LED support. The PCA9533 is used on the mightyboard. ``` [pca9533 my_pca9533] #i2c_address: 98 -# The i2c address that the chip is using on the i2c bus. The default -# is 98 for the PCA9533/1, 99 for the PCA9533/2. +# The i2c address that the chip is using on the i2c bus. Use 98 for +# the PCA9533/1, 99 for the PCA9533/2. The default is 98. #i2c_mcu: #i2c_bus: #i2c_speed: # See the "common I2C settings" section for a description of the # above parameters. -#initial_RED: 1 -#initial_GREEN: 1 -#initial_BLUE: 1 -#initial_WHITE: 1 -# The PCA9533 only supports 1 or 0, any other values will be considered as 1. The default is 0. -# On the mightyboard, the white led is not populated. -# Use GCODE to modify led values after startup. -# set_led led=my_pca9533 red=1 green=1 blue=1 +#initial_RED: 0 +#initial_GREEN: 0 +#initial_BLUE: 0 +#initial_WHITE: 0 +# The PCA9533 only supports 1 or 0. The default is 0. On the +# mightyboard, the white led is not populated. +# Use GCODE to modify led values after startup. +# set_led led=my_pca9533 red=1 green=1 blue=1 ``` ## [gcode_button]