Router resets #71

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

router to LED end seems to keep losing conectivity.

router to LED end seems to keep losing conectivity.
kieran-boyle commented 2019-03-26 21:39:24 +00:00 (Migrated from github.com)
[https://github.com/Squatnet/ArduinoStuff/tree/DV2Work/2.aNCS_LED_DV2/DV2Working/pjonToI2C](url) [https://github.com/Squatnet/ArduinoStuff/tree/DV2Work/2.aNCS_LED_DV2/DV2Working/2560PROPjonMast](url)
Squatnet commented 2019-03-27 16:00:46 +00:00 (Migrated from github.com)

from #44

Rio
yeah stay away from hard delay, use fastLED delay, carefulk using twice before fastLED show(). We already have (and since probably deleted) pixel reference code in alphabetMatrix (When this Git Started) But great to see you're becoming familiar with it!

Squatnet
On Tue, Feb 12, 2019 at 4:15 PM Squatnet @.***> wrote: Correct me if I'm wrong but I thought there was some reason we shouldn't use delay() with FastLED. If I'm remembering correctly there is a FastLED.delay() which is preferable although from memory I'm not sure why

from #44 > Rio > yeah stay away from hard delay, use fastLED delay, carefulk using twice before fastLED show(). We already have (and since probably deleted) pixel reference code in alphabetMatrix (When this Git Started) But great to see you're becoming familiar with it! > Squatnet > On Tue, Feb 12, 2019 at 4:15 PM Squatnet ***@***.***> wrote: Correct me if I'm wrong but I thought there was some reason we shouldn't use delay() with FastLED. If I'm remembering correctly there is a FastLED.delay() which is preferable although from memory I'm not sure why
kieran-boyle commented 2019-03-27 16:05:15 +00:00 (Migrated from github.com)

where are you referencing mate? we got some hard delays in there somewhere?

where are you referencing mate? we got some hard delays in there somewhere?
Squatnet commented 2019-03-27 16:28:32 +00:00 (Migrated from github.com)

yeah stay away from hard delay, use fastLED delay, carefulk using twice before fastLED show().

> yeah stay away from hard delay, use fastLED delay, carefulk using twice before fastLED show().
Squatnet commented 2019-03-27 16:29:45 +00:00 (Migrated from github.com)

thinking that was going to be the issue tbh

thinking that was going to be the issue tbh
kieran-boyle commented 2019-03-27 16:37:09 +00:00 (Migrated from github.com)

i see, there are no other instances of delay in the strips code now, one fastled.delay in setup and one at end of loop

i see, there are no other instances of delay in the strips code now, one fastled.delay in setup and one at end of loop
Squatnet commented 2019-03-27 16:51:51 +00:00 (Migrated from github.com)

Excellent let's hope it's another fix then

On Wed, 27 Mar 2019, 16:37 kieran-boyle, notifications@github.com wrote:

i see, there are no other instances of delay in the strips code now, one
fastled.delay in setup and one at end of loop


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

Excellent let's hope it's another fix then On Wed, 27 Mar 2019, 16:37 kieran-boyle, <notifications@github.com> wrote: > i see, there are no other instances of delay in the strips code now, one > fastled.delay in setup and one at end of loop > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/Squatnet/ArduinoStuff/issues/71#issuecomment-477243535>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AZCEGg8qsaXaSfUBZ-suBYEvfOlrZIZrks5va542gaJpZM4cMfH8> > . >
Riolaurenti commented 2019-05-10 13:44:02 +01:00 (Migrated from github.com)

Closed. Unnecessary to bring up issue really, moving on...

Closed. Unnecessary to bring up issue really, moving on...
Squatnet commented 2019-05-10 16:09:29 +01:00 (Migrated from github.com)

Fine by me.

On Fri, 10 May 2019, 13:44 Riiio, notifications@github.com wrote:

Closed. Unnecessary to bring up issue really, moving on...


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

Fine by me. On Fri, 10 May 2019, 13:44 Riiio, <notifications@github.com> wrote: > Closed. Unnecessary to bring up issue really, moving on... > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/Squatnet/ArduinoStuff/issues/71#issuecomment-491275650>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AGIIIGUZWSI72C75MPMRS3LPUVUZFANCNFSM4HBR6H6A> > . >
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#71
No description provided.