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 for #19224 for independent neopixel strip control option not being separated #19250

Merged
merged 52 commits into from
Sep 3, 2020
Merged

Conversation

Bacon-Fixation
Copy link
Contributor

@Bacon-Fixation Bacon-Fixation commented Sep 3, 2020

Description

TERN_(NEOPIXEL2_SEPARATE,adaneo1.setPin(NEOPIXEL2_PIN)); stops NEOPIXEL2_SEPARATE From working as intended, It is bleeding into the separate channel.

Problems with this macro:

  • printer events and first strip Start up test bleeds into the second strip when they are supposed to be separated
  • all M150 S1 commands do not work at all

But with the #if DISABLED(NEOPIXEL2_SEPARATE) it works like it is supposed to.

is there a different macro other than TERN_(NEOPIXEL2_SEPARATE,adaneo1.setPin(NEOPIXEL2_PIN));?
because it doesn't have the desired effect.

I apologize, I made an assumption and didn't have the opportunity to test #19224 on my equipment until today.

Related Issues

#19224 - bug NEOPIXEL2_SEPARATE with TERN_(NEOPIXEL2_SEPARATE,adaneo1.setPin(NEOPIXEL2_PIN));

Bacon-Fixation and others added 30 commits August 22, 2020 13:10
sorry im not a programer but i did my best to get 2 seperated controls for extra  visual indiaction from the LEDS by keeping the Printer Events on the main channel .
Originally labeled as DUET_SMART_EFFECTOR
but this is incorrect as MarlinCore looks for SMART_EFFECTOR and not DUET_SMART_EFFECTOR
for some reason NEOPIXEL_SEPERATE ended up missing in config
Bacon-Fixation and others added 20 commits August 25, 2020 10:40
trying out stuffs
with NeoPixel2_separate enabled there isnt a conflict if they are different Neo type
i dont know why i thought this was needed

if neopixel is't enabled then there wont be a neopixel2
M150 S1 I1 R    ; Set SEPARATE index 1 to red
I dont know why but in Conditionals_LCD.h

MULTIPLE_NEOPIXEL_TYPES  isn't carried over from its definition in neopixel.h
moved the CONJOINED_NEOPIXEL from Conditionals_LCD.h to neopixel.h

because MULTIPLE_NEOPIXEL_TYPE wouldnt trip the trigger in conditionals
adaneo1 still was set to NEOPIXEL2_PIN and was bleeding into the separated neopixel bank during start up and regular M150 commands

found that adaneo never set a pin once NEOPIXEL2_SEPARATE is enabled
TERN_(NEOPIXEL2_SEPARATE,,adaneo1.setPin(NEOPIXEL2_PIN)); dosent compile as is. i believe it has an extra comma in it
TERN_(NEOPIXEL2_SEPARATE,adaneo1.setPin(NEOPIXEL2_PIN)); stops NEOPIXEL2_SEPARATE From working as intended it bleeds into the separate channel #if Disabled(NEOPIXEL2_SEPARATE) Works like its supposed to

is there a different macro than TERN_(NEOPIXEL2_SEPARATE,adaneo1.setPin(NEOPIXEL2_PIN)); becuase it dosnet have the desired effect
@Bacon-Fixation Bacon-Fixation changed the title Bugfix 2.0.x for independent neopixel strip control fix for independent neopixel strip control option Sep 3, 2020
@Bacon-Fixation Bacon-Fixation changed the title fix for independent neopixel strip control option fix for #19224 for independent neopixel strip control option not being separated Sep 3, 2020
@thinkyhead thinkyhead merged commit 26858fd into MarlinFirmware:bugfix-2.0.x Sep 3, 2020
vgadreau pushed a commit to vgadreau/Marlin that referenced this pull request Dec 9, 2020
kageurufu pushed a commit to CR30-Users/Marlin-CR30 that referenced this pull request Apr 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants