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

[BUG] MKS_MONSTER_V2 NEOPIXEL_PIN redefined #26227

Closed
1 task done
AssortedMapTacks opened this issue Sep 4, 2023 · 3 comments
Closed
1 task done

[BUG] MKS_MONSTER_V2 NEOPIXEL_PIN redefined #26227

AssortedMapTacks opened this issue Sep 4, 2023 · 3 comments

Comments

@AssortedMapTacks
Copy link

Did you test the latest bugfix-2.1.x code?

Yes, and the problem still exists.

Bug Description

When using a MKS Monster8 V2 board with the MKS MINI 12864 V3 (FYSETC_MINI_12864_2_1), the variable "NEOPIXEL_PIN" is defined twice. This is because the Monster8 V2 board includes a new neopixel pin on the board and was given a name that conflicts with the name of the neopixel pin used for the display. This throws an error when trying to build.

Marlin\src\pins\stm32f4\pins_MKS_MONSTER8_common.h
338: #define NEOPIXEL_PIN EXP1_06_PIN

Marlin\src\pins\stm32f4\pins_MKS_MONSTER8_V2.h
55: #define NEOPIXEL_PIN PC5

Commenting out line 55 in V2.h allows successful build and use of neopixel on the display.

Bug Timeline

unknown

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

No response

Version of Marlin Firmware

2.1.1.1

Printer model

No response

Electronics

No response

Add-ons

No response

Bed Leveling

None

Your Slicer

None

Host Software

None

Don't forget to include

  • A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

@thisiskeithb
Copy link
Member

This is an ongoing issue for boards & LCDs with NeoPixels:

@thisiskeithb thisiskeithb changed the title [BUG] MKS_MONSTER_V2 NEOPIXEL_PIN redefined error [BUG] MKS_MONSTER_V2 NEOPIXEL_PIN redefined Sep 8, 2023
@thisiskeithb
Copy link
Member

Fixed in #26492

Copy link

github-actions bot commented Feb 2, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Feb 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants