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

Using --led-slowdown-gpio=2 as argument doesnt work #37

Open
Mschul opened this issue Mar 23, 2021 · 4 comments
Open

Using --led-slowdown-gpio=2 as argument doesnt work #37

Mschul opened this issue Mar 23, 2021 · 4 comments

Comments

@Mschul
Copy link

Mschul commented Mar 23, 2021

My setup (3x2, 192X64) works, but has quite some jitter. Using hzeller implementation, I can fix this issue with using --led-slowdown-gpio=2. Also tried to fix it in node-red by adding --led-slowdown-gpio=2 to the "Command-Line Arguments" field but it seems it doesnt affect anything.

@hennerdiy
Copy link

same here. any solution for that. maybe a workaround?

@mark77-DE
Copy link

mark77-DE commented Jun 13, 2021

If you also need a solution, quick an dirty would be to edit:
/root/.node-red/node_modules/easybotics-rpi-rgb-led-matrix/external/matrix/include/gpio.h
and change line 40
slowdown = 1
to
slowdown = 2

after that go to "/root/.node-red/node_modules" and do "npm rebuild"

not nice, but working

@abwilson2020
Copy link

@mark77-DE is there a way to do the same with the other flags? I was looking to do the pixel mapper

@mark77-DE
Copy link

@abwilson2020 I'm not an expert (was more luck, I did find the solution) but maybe if you specify, what you are looking fore, I can help.

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

No branches or pull requests

4 participants