-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
dmx_receive blocking #58
Comments
The last argument of
As a side note, This is a relatively new feature so let me know if this is not the behavior you see! |
Thanks for the very prompt response, using 0 does resolve my blocking issue. However, I'm now seeing some rather odd glitches with WLEDs output when DMX is active if I then use that. Is 0 a magic value to trigger a different behavior? So with the blocking, all is fine when I have DMX, but no signal blocks my main loop for the timeout. |
Setting the block time to 0 should not cause another behavior. What do you mean by erratic behavior? Do you mind sharing your code? |
The LEDs star showing incorrect values, I wondered if we were seeing clashing interrupts https://github.com/netmindz/WLED/blob/DMX-Input-esp_dmx/wled00/dmx.cpp |
Thanks for the code link. It is possible that this is related to interrupts clashing. It should be possible to check this by adjusting the DMX driver interrupt priority. The constant You should also check to ensure that your other components are using lower level interrupts. |
That seems to be working nicely, thank you |
If you are trying to write code that optionally expects DMX data, how can you prevent the code from being blocked while waiting for DMX timeout?
Most DMX libraries I've worked with before allow you simple
void loop() {
Dmx.loop();
if (Dmx.newFrame()) {
}
}
The text was updated successfully, but these errors were encountered: