individual strip mode breaks the world #70

Closed
opened 2019-03-26 21:26:17 +00:00 by kieran-boyle · 9 comments
kieran-boyle commented 2019-03-26 21:26:17 +00:00 (Migrated from github.com)

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)

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)
kieran-boyle commented 2019-03-26 21:39:59 +00:00 (Migrated from github.com)
https://github.com/Squatnet/ArduinoStuff/tree/DV2Work/2.aNCS_LED_DV2/DV2Working/I2CtoFastLEDs
kieran-boyle commented 2019-03-27 14:28:59 +00:00 (Migrated from github.com)

may of found the issue, will push now but needs testing, (was missing expected setLEDs call from pattern in parser).

may of found the issue, will push now but needs testing, (was missing expected setLEDs call from pattern in parser).
Squatnet commented 2019-03-27 14:29:09 +00:00 (Migrated from github.com)

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.

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.
kieran-boyle commented 2019-03-27 21:10:33 +00:00 (Migrated from github.com)

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.

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.
Squatnet commented 2019-03-30 21:27:38 +00:00 (Migrated from github.com)

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:

Closed #70 https://github.com/Squatnet/ArduinoStuff/issues/70.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Squatnet/ArduinoStuff/issues/70#event-2241213225, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AZCEGqeL7Gnw9guEOdlvY2ypJW_4MhWvks5vb8E3gaJpZM4cMfDU
.

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: > Closed #70 <https://github.com/Squatnet/ArduinoStuff/issues/70>. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/Squatnet/ArduinoStuff/issues/70#event-2241213225>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AZCEGqeL7Gnw9guEOdlvY2ypJW_4MhWvks5vb8E3gaJpZM4cMfDU> > . >
kieran-boyle commented 2019-04-01 19:52:37 +01:00 (Migrated from github.com)

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.

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.
Squatnet commented 2019-04-01 20:58:39 +01:00 (Migrated from github.com)

Closed in error then possibly mate?

On Mon, 1 Apr 2019, 19:52 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.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Squatnet/ArduinoStuff/issues/70#issuecomment-478700495,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZCEGhQIbsKm34rXIQqCsqrb1lDZxBxaks5vclV1gaJpZM4cMfDU
.

Closed in error then possibly mate? On Mon, 1 Apr 2019, 19:52 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. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/Squatnet/ArduinoStuff/issues/70#issuecomment-478700495>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AZCEGhQIbsKm34rXIQqCsqrb1lDZxBxaks5vclV1gaJpZM4cMfDU> > . >
kieran-boyle commented 2019-04-01 23:46:54 +01:00 (Migrated from github.com)

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.

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.
Squatnet commented 2019-04-01 23:51:43 +01:00 (Migrated from github.com)

Ah that's sound.

On Mon, 1 Apr 2019, 23:46 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.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Squatnet/ArduinoStuff/issues/70#issuecomment-478774483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZCEGobsKHwDChQK4zrFvVEQ9LTdm1RMks5vcoxegaJpZM4cMfDU
.

Ah that's sound. On Mon, 1 Apr 2019, 23:46 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. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/Squatnet/ArduinoStuff/issues/70#issuecomment-478774483>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AZCEGobsKHwDChQK4zrFvVEQ9LTdm1RMks5vcoxegaJpZM4cMfDU> > . >
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
squatnet/ArduinoStuff#70
No description provided.