E682 Firmware Versi...
 
Notifications
Clear all

E682 Firmware Version 4 Beta

113 Posts
24 Users
0 Reactions
31.2 K Views
Posts: 124
(@frankaz)
Estimable Member
Joined: 14 years ago

Jim, I may also be experiencing some flicker also.

So far, I only see it when the star itself is all white. Pixels are 12v ws2811 from Ray Wu (received on Tuesday)

Program: xLights, using the nutcracker function - was able to get it the easiest in color wash mode.

Total Pixels - 80, occurs with zig zag on or off. Mode is in Unicast. The lights are on plug 2-1, only 1 output in use. Board is the e682

Firmware v4.012-01 - occurs
Firmware v4.003-001 - occurs, but, no where near as bad as 4.012-01
Firmware v3.009-001 - occurs, but, no where near as bad as 4.012-01
Firmware v3.007-001 - first 40 is OK, small amount of flicker on the second 40.

Balanced jumpers are off.


Reply
klyneshouse
Posts: 230
(@klyneshouse)
Reputable Member
Joined: 16 years ago

I think what jcmarksafb (and myself) may be quite different that what you are experiencing Frank.
My 2811's with ver 4 (also with the first posted ver 2? I thiink it was) basically do not work at all with 2811's 50 ct strings from diyledexpress, unless you define length as 85 or 170.
The first 2 or so pixles try, but the remainder are non responsive, or stuck.
2801's work fine.

I have not tried ver 3, (where do i find it ? ) so i can try it when i get back home.
The original Ver 2.05 works fine. (E682)


Reply
Posts: 482
(@jcmarksafb)
Honorable Member
Joined: 15 years ago

The model is E682 .. I have 2 of them and the last firmware version was 3.007. That version is the version that is failing. The last version (2.050) worked fine. I have not yet installed version 4.
Thanks
John


Reply
Posts: 1249
Topic starter
(@jstjohnz)
Noble Member
Joined: 17 years ago

To be honest I don't have an explanation for why the flicker issue would change from one firmware version to another since the assembly language objects that drive the pixels haven't changed. Klyneshouse, if you would be willing to send me a string for testing that would be a big help.

I am testing with 2 16x16 pixel arrays of 2811s connected in series, so basically it's a 512-pixel string, and I'm not seeing the problem.

The basic issue with the 2811s is that they tend to vary dramatically from their spec sheets in regard to the data gap time that is interpreted as end-of-frame. The 2811s look for a certain time interval to pass with no data bit being received as a marker that the full data frame has been sent. This is 50us according to the data sheet. The actual value seems to run from 5-10us. The problem is that the assembly language object that drives the pixels needs about 30us between pixels in order to do the crunching it needs to get to get the next pixel's data ready to send. The 1804s/2811s have some special code that divides this time up into chunks of no more than a few us so that the maximum time between bits is less than 5us. It sounds like some of the latest 2811s may in fact need a shorter delay still. The symptom is generally that some number of pixels will work, but nothing after that point. Basically everything is fine until the datastream hits a pixel that's further out of spec with its timing.

I have posted the latest version for the E682 in post #1. There was an issue with the 4.014 version that was causing the IP address overrides not to work properly.


Reply
Posts: 1249
Topic starter
(@jstjohnz)
Noble Member
Joined: 17 years ago

4.016 attached to 1st post, improved timing for 2811s/18042. Please let me know if this helps with the flicker issues.


Reply
budude
Posts: 10400
(@budude)
Illustrious Member
Joined: 18 years ago

So - - none of these recent issues affect the other E68x controllers?


Reply
klyneshouse
Posts: 230
(@klyneshouse)
Reputable Member
Joined: 16 years ago

Ver 4.016 seems to have a an overall grouping issue for any pixel type.
Both 2801 & 2811 if grouped other than 1, will random/Easter egg 25% of the string, as soon as e682 restarted,, even with no data received.

Good news is, both types incl the 2811's , if not grouped, DO appear be working fine, even in lengths other than 85 or 170.

Budude, I have no upgraded 681's, so no new firmware exists for me to play with on anything other than a 682.
Any controller with the original release firmware works perfectly for me.


Reply
budude
Posts: 10400
(@budude)
Illustrious Member
Joined: 18 years ago
klyneshouse wrote:
Budude, I have no upgraded 681's, so no new firmware exists for me to play with on anything other than a 682.
Any controller with the original release firmware works perfectly for me.

Actually the question was for Jim - I assume these use common bits for most functions so it would seem likely that it would affect all types.


Reply
Posts: 18
(@denis-09)
Eminent Member
Joined: 17 years ago

Can I upgrade my firmware from V2.05 to V4.016 or do I need to upgrade to the previous ones first ? I cannot find them on your site ,I have tried to upgrade and get timeout or Not for me error.


Reply
dsmjuggalo
Posts: 663
(@dsmjuggalo)
Prominent Member
Joined: 15 years ago

I am trying to install this update. ive updated every other time just fine but this one will say update running then next time I load the page it says "not for me" where it says update. what am I doing wrong? I have the 682 and ive redownloaded the firmware 3 times. Any chance you linked the wrong firmware?


Reply
Page 2 / 12
Share: