Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix status LEDs for separate nozzle and logo LEDs #322

Merged
merged 2 commits into from
Nov 6, 2023

Conversation

kdomanski
Copy link
Contributor

The macro aways uses TRANSMIT=0 for the logo LEDs, which assumes that the subsequent call to nozzle LEDs will flush the data. That will only work if both sets of LEDs are on the same chain.

The chains can be different though - configured through status_leds_nozzle_led_name and status_leds_logo_led_name. With this change, separate logo LEDs will use TRANSMIT=1 instead.

@kdomanski
Copy link
Contributor Author

Tested on my Voron v0.2, with logo LEDs connected to the main MCU and nozzle LEDs connected to toolhead MCU.

@Frix-x Frix-x changed the base branch from main to develop November 1, 2023 14:45
macros/hardware_functions/status_leds.cfg Outdated Show resolved Hide resolved
@Frix-x
Copy link
Owner

Frix-x commented Nov 1, 2023

Hey, thanks for the PR, it's a great patch! I'll merge it after you fix the typo :)

The macro aways uses TRANSMIT=0 for the logo LEDs, which assumes
that the subsequent call to nozzle LEDs will flush the data.
That will only work if both sets of LEDs are on the same chain.

The chains can be different though - configured through
`status_leds_nozzle_led_name` and `status_leds_logo_led_name`.
With this change, separate logo LEDs will use TRANSMIT=1 instead.
@Surion79
Copy link
Collaborator

Surion79 commented Nov 1, 2023

Very nice! 👍🏻

Copy link
Owner

@Frix-x Frix-x left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I'll merge it :)

@Frix-x Frix-x merged commit d47e520 into Frix-x:develop Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants