dpitts / f16v3_issues

Track issues for F16V3 software
12 stars 0 forks source link

Smart receiver B, Empty port 4 with 0 pixel count effects port 4 on smart rec. 1 #77

Open bchiaino opened 5 years ago

bchiaino commented 5 years ago

finally figured this out. was driving me nuts

I have coming out go F48 port 1, 2 smart receivers set to A and B, in xlights my arches are smart receiver A ports 1,2,3 and 4 and smart receiver B only has ports 1,2 and 3 assigned to props, port 4 is empty. when I upload to the F48 from xlights it adds port 4B as black and puts pixel count at "0", this for some reason completely locks up the first 8 pixels on receiver board A and turns them all white and they don't respond to anything but if I simply go to the 4B column and add a 1 for pixel count, then 4A works fine.

I recorded a video with my phone so you can see everything, please let me know if there's anything I can test urther

this is on 2.52 (and 2.51) and xlights 2019.43.

seems if xlights just adds a 1 to pixels on blank ports it will be ok unless a 0 shouldn't cause this issue

https://youtu.be/kjIusRSMp2I

dpitts commented 5 years ago

Hi

A count of zero at this time will not work. I will make controller internally set all counts to one if zero.

David

From: bchiaino notifications@github.com Sent: Tuesday, August 27, 2019 7:29 PM To: dpitts/f16v3_issues f16v3_issues@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [dpitts/f16v3_issues] Smart receiver B, port 4 effect port 4 on smart rec. 1 (#77)

finally figured this out. was driving me nuts

I have coming out go F48 port 1, 2 smart receivers set to A and B, in xlights my arches are smart receiver A ports 1,2,3 and 4 and smart receiver B only has ports 1,2 and 3 assigned to props, port 4 is empty. when I upload to the F48 from xlights it adds port 4B as black and puts pixel count at "0", this for some reason completely locks up the first 8 pixels on receiver board A and turns them all white and they don't respond to anything but if I simply go to the 4B column and add a 1 for pixel count, then 4A works fine.

I recorded a video with my phone so you can see everything, please let me know if there's anything I can test urther

this is on 2.52 (and 2.51) and xlights 2019.43.

seems if xlights just adds a 1 to pixels on blank ports it will be ok unless a 0 shouldn't cause this issue

https://youtu.be/kjIusRSMp2I

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/dpitts/f16v3_issues/issues/77?email_source=notifications&email_token=AARHOBG4OLULYLYW6SI5ADDQGXIHNA5CNFSM4IQUY6PKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHZPXUA, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AARHOBAZILLZJKLUQK53CMTQGXIHNANCNFSM4IQUY6PA.

bchiaino commented 5 years ago

Hi A count of zero at this time will not work. I will make controller internally set all counts to one if zero. David From: bchiaino notifications@github.com Sent: Tuesday, August 27, 2019 7:29 PM To: dpitts/f16v3_issues f16v3_issues@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [dpitts/f16v3_issues] Smart receiver B, port 4 effect port 4 on smart rec. 1 (#77) finally figured this out. was driving me nuts I have coming out go F48 port 1, 2 smart receivers set to A and B, in xlights my arches are smart receiver A ports 1,2,3 and 4 and smart receiver B only has ports 1,2 and 3 assigned to props, port 4 is empty. when I upload to the F48 from xlights it adds port 4B as black and puts pixel count at "0", this for some reason completely locks up the first 8 pixels on receiver board A and turns them all white and they don't respond to anything but if I simply go to the 4B column and add a 1 for pixel count, then 4A works fine. I recorded a video with my phone so you can see everything, please let me know if there's anything I can test urther this is on 2.52 (and 2.51) and xlights 2019.43. seems if xlights just adds a 1 to pixels on blank ports it will be ok unless a 0 shouldn't cause this issue https://youtu.be/kjIusRSMp2I — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#77?email_source=notifications&email_token=AARHOBG4OLULYLYW6SI5ADDQGXIHNA5CNFSM4IQUY6PKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHZPXUA>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AARHOBAZILLZJKLUQK53CMTQGXIHNANCNFSM4IQUY6PA.

ok cool, you know I can test changes if you need before a final release... thanks David!