Notifications
Clear all

E682 issues

33 Posts
9 Users
0 Reactions
10.7 K Views
Posts: 99
(@sulrich)
Estimable Member
Joined: 13 years ago

from what I have heard, unplug the e682 and let sit for 30 seconds. The pixels get their address at startup and they can get a little screwy if they had an issue at startup.. my 2 cents.. I had an issue with them not being in sequence.

also remember in the webpage to use BGR in stead of RGB, colors will be inverted if RGB in the E682 Control Panel

~SULRICH


Reply
ebrady
Posts: 670
Topic starter
(@ebrady)
Prominent Member
Joined: 17 years ago
Sulrich wrote:from what I have heard, unplug the e682 and let sit for 30 seconds. The pixels get their address at startup and they can get a little screwy if they had an issue at startup.. my 2 cents.. I had an issue with them not being in sequence.

also remember in the webpage to use BGR in stead of RGB, colors will be inverted if RGB in the E682 Control Panel

~SULRICH

Actually, I think the troubleshooting rules out the E682 completely and points to the power supply instead. There does not appear to be an addressing problem, as pixels before and after the stuck pixels are correctly addressed.


Reply
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

The weird thing is that a GECE pixel should not pass data until it's received a valid address. So if pixels farther down a string are getting data updates, that means that the stuck pixel is in fact getting addressed. but then isn't responding to anything subsequently. If the pixel is actually "locked up", it shouldn't be forwarding data either. It could be that it got the wrong address such as an unused address (higher than 25). You could experiment with this to discover it's address by adjusting the string length setting in the 682 to 63 while the GECEs are still powered up in a failure state. The idea is that you'd start it as normal, and observe the stuck pixel problem. And then adjust the 682 so that you can address the rest of the range. Then you can test it by sending values to each address to see what it's actually getting.
I tried using 16/3 power cord as a pixel extension cable last year with horrendous results. I was trying it with a 2811 pixel string, but I found that while it was a great power conductor, it was an awful data cable, and I could never get a reliable data signal down the line. I've never tried it with GECEs, but you might be getting a similar bad data result. It could be that the power up inrush is causing enough interference on the cable that the first addressing packets aren't getting received cleanly. If they don't get set right in the first place, you'll never see anything correct on that pixel. With any other shift register style pixel, they'll catch up on the next frame, so while I was seeing a lot of incorrect data arrive at the pixels, especially on startup, it would eventually clear and an subsequent frame would give it good data.
Do you know which generation your GECEs are? were they 2010-2011 versions that came with the remote control, or the 2012/13 versions that had the pushbutton control boxes? I found that the build quality of the later models was lower than the early ones. Water intrusion issues and bad solder joints got a lot worse on the more recent versions.


Reply
ebrady
Posts: 670
Topic starter
(@ebrady)
Prominent Member
Joined: 17 years ago
jchuchla wrote:The weird thing is that a GECE pixel should not pass data until it's received a valid address. So if pixels farther down a string are getting data updates, that means that the stuck pixel is in fact getting addressed. but then isn't responding to anything subsequently. If the pixel is actually "locked up", it shouldn't be forwarding data either. It could be that it got the wrong address such as an unused address (higher than 25). You could experiment with this to discover it's address by adjusting the string length setting in the 682 to 63 while the GECEs are still powered up in a failure state. The idea is that you'd start it as normal, and observe the stuck pixel problem. And then adjust the 682 so that you can address the rest of the range. Then you can test it by sending values to each address to see what it's actually getting.

It is definitely forwarding data, however when a pixel is stuck, it may not necessarily mean that ALL of its functionality is lost, hypothetically it could still partially function. I have seen thru occur on multiple LED driver design times in the last couple of years. (Projects at my place of employment not Christmas stuff). If I get a chance, I will investigate if ANY address got assigned to the bad pixel, as it would be an interesting data point to know.

I tried using 16/3 power cord as a pixel extension cable last year with horrendous results. I was trying it with a 2811 pixel string, but I found that while it was a great power conductor, it was an awful data cable, and I could never get a reliable data signal down the line. I've never tried it with GECEs, but you might be getting a similar bad data result. It could be that the power up inrush is causing enough interference on the cable that the first addressing packets aren't getting received cleanly. If they don't get set right in the first place, you'll never see anything correct on that pixel. With any other shift register style pixel, they'll catch up on the next frame, so while I was seeing a lot of incorrect data arrive at the pixels, especially on startup, it would eventually clear and an subsequent frame would give it good data.

I thought about that, which is why I connected the GECE string directly to the E682 on the bench test. I can get stuck pixels regardless if 16/3 is used or not. I would think if 16/3 were causing problems, my fix to switch the 5V side of the power supply would have failed also as power inrush is should be greater in this case. With the 5V workaround, I also do not see any addressing or data problems when using 16/3 either. I can't argue with your experience with it, but I don't think those issues are coming into play here.

Do you know which generation your GECEs are? were they 2010-2011 versions that came with the remote control, or the 2012/13 versions that had the pushbutton control boxes? I found that the build quality of the later models was lower than the early ones. Water intrusion issues and bad solder joints got a lot worse on the more recent versions.

They are the 2012/13 version with push button. My suspicion is that they are a cheaper design and more finicky when it comes to power than previous models. This might have something to do with why GE decided to ship with 6V supplies with the newer types as opposed to 5V the older types shipped with. When the problem was first noticed, they were NIB, so water can be ruled out. Bad solder joints can't completely be ruled out, but I think they are unlikely as I would have still seen failures when I did the 5V switch workaround.


Reply
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

Well it looks like you're getting a pretty thorough look into this. I'm surprised I haven't seen similar threads in the past. There's many GECE trees out there. I'm surprised someone else hasnt come up with problems like this.
Does your ps have a voltage adjust pot? Can you try trimming it up a bit to see if that helps?

--Jon Chuchla--

Sent from my iPhone using Tapatalk


Reply
Page 5 / 7
Share: