Issue with UCS2904

[bigstott]

I had just got the falcon controller and wanted to use it this year to just run some of my lights that run UCS2904. Since in the documentation you show APA109 will run it I set it up wit that protocol. I set the number of pixels to 97. When i run an rgb test on it, it will turn on all lights running all pinkish green blue and then repeat. I tried just 1 node and noticed it does not change the count of channels from 3 to 4. is this right?? With 1 one node running it wont run RGB either, IT will run like a pink, green and blue.

I have tried every order on there with no change.

IS this the same as what i was reading in another issue report where the test mode wont work with

[bigstott]

It really needs RGBWWW i think

[keithsw1111]

So dont get too fussed about the test modes. Most are not 4 channel pixel aware. The only one that is is the number test mode. All the others work as if the pixels are 3 channel. That said if you send 4 channels of data from your sequencer you should see it working as expected.

There is one known bug relating to the display of end channels on these pixels. I can send you a beta of the latest firmware if you need it as it has a fix for it.

[bigstott]

Ok I will go back and run a sequence and see what happens

On Tue, Nov 16, 2021, 1:41 AM Keith Westley @.***> wrote:

So dont get too fussed about the test modes. Most are not 4 channel pixel aware. The only one that is is the number test mode. All the others work as if the pixels are 3 channel. That said if you send 4 channels of data from your sequencer you should see it working as expected.

There is one known bug relating to the display of end channels on these pixels. I can send you a beta of the latest firmware if you need it as it has a fix for it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-970046136, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWPY4Y3AUOO2TEML4P7IBW3UMIKNLANCNFSM5ICRPRBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[bigstott]

So I ran a sequence where I had it in a single strand chase. Xlights is set to ucs2904 falcon to apa109 and I have tried 512 channels 510 and matching it in all areas. I have tried different RGBW orders and I still get the same issue. I also just tried to get the all on RED color to work... and it didn't. IT turned on alternating colors.

I have a video link attached. The only time i can ever get ANY node to go RGB is if i set it to only have 1 node and use 2811.... then i can get the first node to actually do it.... otherwise APA109 wont even do that..

https://drive.google.com/file/d/19ai1OvLedH4MBJOe8JwbbNDMTl2HZNtx/view?usp=sharing https://drive.google.com/file/d/19dJY_9-e3M7M-vL0wOM9bEkDohJR6mma/view?usp=sharing

If you can please call me 303-919-5895

On Tue, Nov 16, 2021, 5:48 PM Michael Onstott @.***> wrote:

Ok I will go back and run a sequence and see what happens

On Tue, Nov 16, 2021, 1:41 AM Keith Westley @.***> wrote:

So dont get too fussed about the test modes. Most are not 4 channel pixel aware. The only one that is is the number test mode. All the others work as if the pixels are 3 channel. That said if you send 4 channels of data from your sequencer you should see it working as expected.

There is one known bug relating to the display of end channels on these pixels. I can send you a beta of the latest firmware if you need it as it has a fix for it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-970046136, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWPY4Y3AUOO2TEML4P7IBW3UMIKNLANCNFSM5ICRPRBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[keithsw1111]

I will wire mine up tomorrow to verify they work.

[bigstott]

Ok, let me know.

On Thu, Nov 18, 2021, 3:08 AM Keith Westley @.***> wrote:

I will wire mine up tomorrow to verify they work.

Sent from my iPhone

On 18 Nov 2021, at 10:34 am, bigstott @.***> wrote:



So I ran a sequence where I had it in a single strand chase. Xlights is set to ucs2904 falcon to apa109 and I have tried 512 channels 510 and matching it in all areas. I have tried different RGBW orders and I still get the same issue. I also just tried to get the all on RED color to work... and it didn't. IT turned on alternating colors.

I have a video link attached. The only time i can ever get ANY node to go RGB is if i set it to only have 1 node and use 2811.... then i can get the first node to actually do it.... otherwise APA109 wont even do that..

https://drive.google.com/file/d/19ai1OvLedH4MBJOe8JwbbNDMTl2HZNtx/view?usp=sharing

https://drive.google.com/file/d/19dJY_9-e3M7M-vL0wOM9bEkDohJR6mma/view?usp=sharing

If you can please call me 303-919-5895

On Tue, Nov 16, 2021, 5:48 PM Michael Onstott @.***> wrote:

Ok I will go back and run a sequence and see what happens

On Tue, Nov 16, 2021, 1:41 AM Keith Westley @.***> wrote:

So dont get too fussed about the test modes. Most are not 4 channel pixel aware. The only one that is is the number test mode. All the others work as if the pixels are 3 channel. That said if you send 4 channels of data from your sequencer you should see it working as expected.

There is one known bug relating to the display of end channels on these pixels. I can send you a beta of the latest firmware if you need it as it has a fix for it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-970046136>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AWPY4Y3AUOO2TEML4P7IBW3UMIKNLANCNFSM5ICRPRBQ>

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-972280442>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/ACOOXKHUDSYWZZRKEYO2CMDUMQ3XPANCNFSM5ICRPRBQ>.

Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-972719672, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWPY4Y3NTREIALUFZOPOS6DUMTGBNANCNFSM5ICRPRBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[keithsw1111]

Wired up my UCS2904 and they work perfectly.

So some things to check. Make sure you have enough pixels defined on the port you are testing with. Not having enough can do weird things.

Don’t use remotes in any initial testing … you want it working off the base board first.

Make sure you have the wires correctly connected to the euro connector.

My UCS2904 strip is 24V so I only connect ground and data to the euro connector and provide voltage directly to the pixels.

Finally here is a test version of the next firmware where I have added a 4 Channel RGBW test mode which may help minimise interpretation issues with 4 channel pixels in test mode. https://www.dropbox.com/s/h51bngnoyagpllc/Falcon_16_V4_Firmware_13.fl3?dl=0

I will be around in about 12 hrs from now if you want to jump on zoom and discuss the issue. I cant call you on the phone as I am in Australia. So zoom or maybe facebook messenger works best.

[bigstott]

Ok. I have defined it to the 97 that it had all the way up to the max 768 for the protocol. no change I am only using the board with no remote Just data and ground to the lights power from elsewhere. a meeting would be awesome. I would like to get this knocked out. You can message me on facebook: Michael Onstott and do it whenever you are available.

On Fri, Nov 19, 2021 at 3:06 AM Keith Westley @.***> wrote:

Wired up my UCS2904 and they work perfectly.

So some things to check. Make sure you have enough pixels defined on the port you are testing with. Not having enough can do weird things.

Don’t use remotes in any initial testing … you want it working off the base board first.

Make sure you have the wires correctly connected to the euro connector.

My UCS2904 strip is 24V so I only connect ground and data to the euro connector and provide voltage directly to the pixels.

Finally here is a test version of the next firmware where I have added a 4 Channel RGBW test mode which may help minimise interpretation issues with 4 channel pixels in test mode. https://www.dropbox.com/s/h51bngnoyagpllc/Falcon_16_V4_Firmware_13.fl3?dl=0

I will be around in about 12 hrs from now if you want to jump on zoom and discuss the issue. I cant call you on the phone as I am in Australia. So zoom or maybe facebook messenger works best.

Keith

From: bigstott @.> Sent: Friday, 19 November 2021 11:23 AM To: dpitts/f16v4_issues @.> Cc: Keith Westley @.>; Comment @.> Subject: Re: [dpitts/f16v4_issues] Issue with UCS2904 (Issue #13)

Ok, let me know.

On Thu, Nov 18, 2021, 3:08 AM Keith Westley @.<mailto:@.>>

wrote:

I will wire mine up tomorrow to verify they work.

Sent from my iPhone

On 18 Nov 2021, at 10:34 am, bigstott @.<mailto:@.>> wrote:



So I ran a sequence where I had it in a single strand chase. Xlights is set to ucs2904 falcon to apa109 and I have tried 512 channels 510 and matching it in all areas. I have tried different RGBW orders and I still get the same issue. I also just tried to get the all on RED color to work... and it didn't. IT turned on alternating colors.

I have a video link attached. The only time i can ever get ANY node to go RGB is if i set it to only have 1 node and use 2811.... then i can get the first node to actually do it.... otherwise APA109 wont even do that..

https://drive.google.com/file/d/19ai1OvLedH4MBJOe8JwbbNDMTl2HZNtx/view?usp=sharing

https://drive.google.com/file/d/19dJY_9-e3M7M-vL0wOM9bEkDohJR6mma/view?usp=sharing

If you can please call me 303-919-5895

On Tue, Nov 16, 2021, 5:48 PM Michael Onstott @.<mailto:@.>> wrote:

Ok I will go back and run a sequence and see what happens

On Tue, Nov 16, 2021, 1:41 AM Keith Westley @.<mailto:@.>>

wrote:

So dont get too fussed about the test modes. Most are not 4 channel pixel aware. The only one that is is the number test mode. All the others work as if the pixels are 3 channel. That said if you send 4 channels of data from your sequencer you should see it working as expected.

There is one known bug relating to the display of end channels on these pixels. I can send you a beta of the latest firmware if you need it as it has a fix for it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-970046136>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AWPY4Y3AUOO2TEML4P7IBW3UMIKNLANCNFSM5ICRPRBQ>

. Triage notifications on the go with GitHub Mobile for iOS <

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>

or Android <

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-972280442>,

or unsubscribe<

https://github.com/notifications/unsubscribe-auth/ACOOXKHUDSYWZZRKEYO2CMDUMQ3XPANCNFSM5ICRPRBQ>.

Triage notifications on the go with GitHub Mobile for iOS<

https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>

or Android<

https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-972719672,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AWPY4Y3NTREIALUFZOPOS6DUMTGBNANCNFSM5ICRPRBQ>

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-973557324>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/ACOOXKE6HMOYERLQ4D4KNFDUMWKHTANCNFSM5ICRPRBQ>.

Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dpitts/f16v4_issues/issues/13#issuecomment-973929320, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWPY4Y4XAGHUTC6MHWOB26LUMYOTPANCNFSM5ICRPRBQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[keithsw1111]

Closing as this was a bunch of xLights config issues.