individual strip mode breaks the world #70
Labels
No labels
Core
Fixed
Godot
HardwareIssue
LEDS
Networking
Problem
SoftwareIssue
duplicate
enhancement
good first issue
help wanted
invalid
on hold
question
reminder
todo 🗒️
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
squatnet/ArduinoStuff#70
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
when turning auto strip mode on, causes crashes, as yet unsure if just strips themselves or if this also crashes the routers (looks like t may be a different problem see #71)
https://github.com/Squatnet/ArduinoStuff/tree/DV2Work/2.aNCS_LED_DV2/DV2Working/I2CtoFastLEDs
may of found the issue, will push now but needs testing, (was missing expected setLEDs call from pattern in parser).
Would say this is different problem. It's not actually crashing the MCU as sending ISt,0 brings them back to life. With #71 the router loses connection.
agree with Matt. Looks like there is some shenanigans going on somewhere. Will need to build a simple setup so i can live test it, I2CToFastLEDs needs to be on a nano so i can see the debug and push variables.
Any info on how to make it easier to debug if a new feature breaks it?
On Sat, 30 Mar 2019, 19:55 kieran-boyle, notifications@github.com wrote:
sorry just saw this. you can turn debug mode on on the strips (you will need to use a nano) then debug through serial if required.
Closed in error then possibly mate?
On Mon, 1 Apr 2019, 19:52 kieran-boyle, notifications@github.com wrote:
You've lost me mate, when testing everything was working sweet as, multiple commands through parser. Individual strip mode works fine now. If on each strip remembers both the pattern and palette assigned to it. I set some initial values in setup, so it doesn't initialise turned off (pattern 0) was having some issues getting the app working, but it was late at that point so I'm not surprised lol. You know way more about that side of it than I do. We will have to do another full network test, but I am quietly confident that the problem has been resolved.
Ah that's sound.
On Mon, 1 Apr 2019, 23:46 kieran-boyle, notifications@github.com wrote: