E682 What am I doin...
 
Notifications
Clear all

E682 What am I doing wrong?

12 Posts
5 Users
0 Reactions
3,555 Views
Barnabybear
Posts: 1583
(@barnabybear)
Noble Member
Joined: 15 years ago
ezellner wrote:As I understand it, the timing has to do with how long it takes to reset the chip for the next piece of data. The old chips reset in 50 nanoseconds. The new chips require 250 nanoseconds to reset. So if the controller was sending data faster than the chip could reset, results would be unpredictable from no light to random colors and flickering. Somebody else jump in here if I didn't get this all right.

Hi, yep that’s about it.
The pixels don’t update until all of them have their new data, which ensures they all change at the same time. They use a very simple way to let all the pixels know that all the data has been sent, they stop sending data. It makes sense when you think about it, so if the pixels see that the controller has stopped sending data for what used to be 50uS (microseconds) they would all update to the new colour / brightness. The new ones need 280uS of not data being sent.

Tec bit:
It takes 30uS to send the new data to one pixel. Under the old reset timing if a pixel didn’t see data for 50uS it updated and went back to the start. This meant that an output could only send data to a maximum of two strings of pixels. Not something we used in the DIY Christmas world as we update the pixels to fast but for something like an advertising board that just has a static picture the update timing may be in seconds rather than the 20 frames per second we use.

So what difference does the reset time make?

In reality I suspect that even though the big advertising boards could use one controller output to update two strings of pixels they didn’t. With this change of timing they can now:
Send data to pixel 1 of string 1 =30uS total = 30uS.
Send data to pixel 1 of string 2 = 30uS total = 60uS.
Etc.
Send data to pixel 1 of string 8 = 30uS total = 240uS.

Interesting that’s less than the 280uS time at which the pixels will update so we can go back to string 1 and do this all again without the pixels updating. The down side is this all takes 8 times longer and is of very little use to us in the DIY Christmas world; to the display people it’s fantastic a controller can now run 8 times the number of pixels, so you only need an 1/8 of the number of controllers - wow that cuts out some cost.

So yes it’s been a bit of a pain in the DIY Christmas world as we’ve all had to do updates to accommodate this new timing but it has made a big difference to other pixel users and at the end of the day this ensures that the pixels we work with will be available for the next few years at least.


Reply
Posts: 740
(@ezellner)
Prominent Member
Joined: 11 years ago
Barnabybear wrote:Hi, yep that’s about it.
The pixels don’t update until all of them have their new data, which ensures they all change at the same time. They use a very simple way to let all the pixels know that all the data has been sent, they stop sending data. It makes sense when you think about it, so if the pixels see that the controller has stopped sending data for what used to be 50uS (microseconds) they would all update to the new colour / brightness. The new ones need 280uS of not data being sent.

Tec bit:
It takes 30uS to send the new data to one pixel. Under the old reset timing if a pixel didn’t see data for 50uS it updated and went back to the start. This meant that an output could only send data to a maximum of two strings of pixels. Not something we used in the DIY Christmas world as we update the pixels to fast but for something like an advertising board that just has a static picture the update timing may be in seconds rather than the 20 frames per second we use.

So what difference does the reset time make?

In reality I suspect that even though the big advertising boards could use one controller output to update two strings of pixels they didn’t. With this change of timing they can now:
Send data to pixel 1 of string 1 =30uS total = 30uS.
Send data to pixel 1 of string 2 = 30uS total = 60uS.
Etc.
Send data to pixel 1 of string 8 = 30uS total = 240uS.

Interesting that’s less than the 280uS time at which the pixels will update so we can go back to string 1 and do this all again without the pixels updating. The down side is this all takes 8 times longer and is of very little use to us in the DIY Christmas world; to the display people it’s fantastic a controller can now run 8 times the number of pixels, so you only need an 1/8 of the number of controllers - wow that cuts out some cost.

So yes it’s been a bit of a pain in the DIY Christmas world as we’ve all had to do updates to accommodate this new timing but it has made a big difference to other pixel users and at the end of the day this ensures that the pixels we work with will be available for the next few years at least.

Thanks for the correction on reset time (it's microseconds not nanoseconds).


Reply
Page 2 / 2
Share: