That business about powering off for at least 40 seconds for a sure reset is very good to know.
kayjay wrote:I'll refer you to this thread: http://doityourselfchristmas.com/forums/showthread.php?33537-GECE-strange-results-when-pluging-in-the-E682-into-outlet&highlight=GECE+pixels
kayjay wrote:I'll refer you to this thread: http://doityourselfchristmas.com/forums/showthread.php?33537-GECE-strange-results-when-pluging-in-the-E682-into-outlet&highlight=GECE+pixels
Thanks
I came across that thread earlier, but I am not quite sure what to take away from it. Does this mean I need to replace the first pixel in the string that comes on (or the pixel before the one that comes on?). This approach concerns me as the stuck pixels are random between power ups.
If you're getting random results its probably not (but not 100% sure) bad pixels.
The way the GECEs work with the 682 is as follows.
On a cold start the GECEs go into addressing mode. In this mode, they have no address and do not forward data past the pixel until the address is set. the first packet each pixel receives becomes the address. It then starts operating normally and passing data. So to properly address a GECE string, it needs to be sent a stream of data that starts at address 1 and, in order, goes to the highest address of the string.
The 682 assumes that the string is in addressing mode when it boots up. It doesn't actually do anything special to address the string. But it always sends a full string worth of data in every frame and it sends it in order. So the first frame it sends performs the addressing operation. In theory, after the addresses are set, you can address pixels directly without sending a whole string worth of data. But the 682 doesn't use this, it always sends a full string update. It's been a while since I've verified, but I think the 682 sends data right away even before it has received any sACN data.
The 682s function for writing to the strings is a constant loop. It just keeps reading the buffer and pumping those data values out to the string over and over as fast as it can. Data can get into the buffer in two ways, first is from received sACN data, and second is from the internal test patterns.
Based on your symptoms, I don't think your problems are wireless related, but you might try eliminating that variable for testing. Try a wired connection. Also try starting everything with the 682 in test pattern mode. That will rule out the network altogether.
I have had problems with the web page on occasion, but very infrequent. And it was always when I was connecting to it wirelessly.
-- Jon Chuchla --
Sent from my iPad using Tapatalk
It looks like problem #2 is due to the GECE pixels and the power supply not getting along with each other.
The controller was wired to switch 120V on/off to the power supply, which then had it's 5V output wired directly to the pixel controller. Below is a scope capture of the power output once switched on. The rise from 0V to 5V is fairly slow (relatively speaking) and on average takes 7 to 9ms. Upon reaching 5V it also overshoots to 5.3 volts momentarily. This combination of slow rise time and overshoot causes some of the GECE pixels to lock up.
I tested this theory 10 to 15 times by applying 5V to the E682 controller AFTER the power supply was started and had time to stabilize. The problem went away.
Ed
Are you doing anything that requires a current version of firmware? I have source for an older version that could be modded for a longer wait time before starting the data stream.
On second thought Never mind. You said 682. My version will only work with the older wiznet modules. You might reach out to Jim to see if he'd be willing to cut you a version with a delay line in the startup.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
