• I've tried the alternative firmware and - you're right - it makes the neopixels act a little randomly, with flashes and unpredictable colour changes!

    I've improved my script quite a bit since my earlier post. I now use a node.js server to batch up my colour changes and only release them to the Espruino via MQTT after a predetermined time. I've currently set this to 250ms to give the Espruino time to update the neopixels.

    This mostly works very reliably, however I sometimes get errors in my packets. The basic neopixel packet is 12 hex characters, with multiple packets being grouped together. Here is a run of correct packets:

    [0000E1FF0000]
    [0000E2FF00000000DCFF00000000DAFF0000000­0C6FF00000000C8FF00000000B5FF00000000B4F­F00000000B2FF00000000ADFF00000000AEFF000­00000AFFF0000]
    [0000AEFF00000000ADFF00000000ACFF0000000­095FF0000]
    

    However, every now and then I get some erroneous data in the packet. It appears to be the MQTT topic, eg. "biosphere/ecology/matrix/color", preceded by text in the form "+IPD,0,70:0". As you can see from the example below, this erroneous data is stuck in the middle of a packet.

    [000085FF000000000052FF000000006DFF00000­00071FF000000008EFF0000
    +IPD,0,70:0Dbiosphere/ecology/matrix/col­or000091FF00000000AEFF00000000ADFF0000
    +IPD,0,46:]
    

    Any thoughts about what the problem might be? Like I say, I'm only sending a packet every 250ms now and they are at the very most 100 or so characters.

    Sean

About

Avatar for seanclark @seanclark started