ESPixelSticks

Yeah the units I have used previously (for other normal lighting applications appear to have quite reasonably made drivers with adequate isolation). I bet there are some dodgy units around though for sure.
 
-Old Firmware

Universe Range :
27 to 27
Last Universe :​
27
Total Packets :​
213885
Sequence Errors :​
2
Packet Errors :​


-second controller - latest firmware
E1.31 Status
Universe Range26 to 26
Total Packets213674
Sequence Errors213
Packet Errors0
 
smartalec said:
-Old Firmware

Universe Range :
27 to 27
Last Universe :​
27
Total Packets :​
213885
Sequence Errors :​
2
Packet Errors :​


-second controller - latest firmware
E1.31 Status
Universe Range26 to 26
Total Packets213674
Sequence Errors213
Packet Errors0
Click to expand...


Interesting......


No packet errors. Few sequence errors though?
 
smartalec said:
what do they mean by sequence errors tho..
Click to expand...


It appears that the sequence error counter gets incremented here:

Code: 
/* Parse a packet and update pixels */
        if (e131.parsePacket()) {
            if ((e131.universe >= config.universe) && (e131.universe <= uniLast)) {
                /* Universe offset and sequence tracking */
                uint8_t uniOffset = (e131.universe - config.universe);
                if (e131.packet->sequence_number != seqTracker[uniOffset]++) {
                    seqError[uniOffset]++;
                    seqTracker[uniOffset] = e131.packet->sequence_number + 1;
                }
 
Specifically this

Code: 
    if (e131.packet->sequence_number != seqTracker[uniOffset]++) {
                    seqError[uniOffset]++;
 
The E1.31 "sequence number" is extracted from the incoming e1.31 packet (in the frame layer).


I am assuming that the stick firmware tracks the numbers as well as does a compare


ie. if the incoming sequence number does not match the firmware's seqTracker count, increment the sequence error counter.


This is interesting....... could be a bug in the original author's firmware.


I will look into this further before I do my code release.


Out of curiosity though alec, the pixels attached to both of your sticks seemed to behave themselves and do as they should?
 
It seems that the firmware is reporting a missing/lost packet as a sequence error when the device is in pixel mode.


Packet error counter only increments when the stick is in serial mode.


Just keeping this logged in this thread as this has been discussed in further detail in chat tonight.
 
smartalec said:
-Old Firmware

Universe Range :
27 to 27
Last Universe :​
27
Total Packets :​
213885
Sequence Errors :​
2
Packet Errors :​


-second controller - latest firmware
E1.31 Status
Universe Range26 to 26
Total Packets213674
Sequence Errors213
Packet Errors0
Click to expand...

old firmware
Universe Range :
26 to 26
Last Universe :​
26
Total Packets :​
207597
Sequence Errors :​
221
Packet Errors :​
0
latest firmware

E1.31 Status
Universe Range27 to 27
Total Packets207733
Sequence Errors85
Packet Errors0

so all i did was change the esp01 modules over an there ip an univ number..
weird outcome
 
Thanks Alec.


Yes that is weird. I will look into it further over the next few weeks.


My pcb order shipped today so should be a week or so and I will have them to start testing.
 
Components have started arriving. PCBs are due to arrive tomorrow at this stage.
 
Just flashed up my first 8266 module with modified ESPixelStick firmware....


:)
 
I have a web store half setup on my domain.


Once I have assembled the prototypes and fully tested them (test results will be in this thread) I will link the web store.


You will get a genuine invoice/receipt also as I will simply just sell them through my existing electrical business, the web store will just be a nice front end for it.


Happy to take expressions of interest for qty's of either of the three current boards though if you wish.
 
You must log in or register to reply here.
Back
Top