Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: ESP Async E131 test.ino

  1. #1
    Join Date
    Dec 2011
    Posts
    6,322
    Post Thanks / Like

    Default ESP Async E131 test.ino

    Ignoring all my prior posts on the E131 topics as I just noticed my error posting .
    I was too focused on the esp32 in experimenting with this sketch that I failed to test on esp8266 until today .
    Voila the code works excellently .
    I cannot say the same for the esp32, but it does work on that module also , with artifacts that I cannot understand why .

    Thanks Shelby for making this to experiment with !

  2. #2
    Join Date
    Dec 2011
    Posts
    6,322
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    I can see now why there is 0 response to the Esp32 questions etc that I have posted .


    Well I finally cracked this awesome piece of hardware and now have the Async E131 fully functioning . The Adafruit_NeoPixel lib is not up to the task even though they suggest that it supports The Esp32 .
    At the start of this endeavour I searched and searched for any and all reference to the Esp32 and e131 . What I found was 1 single sketch from a member at this forum .

    Solution -> Neopixel_bus !

    Woot

  3. #3
    Join Date
    Dec 2011
    Posts
    6,322
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    Could someone give me a clue as to how to expose Universe #2 ?
    I am not clear on how to actually get the packet info specific .
    Thanks in advance .

  4. #4
    Join Date
    Dec 2012
    Location
    Newtown CT
    Posts
    4,197
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    what does expose mean?


    2020 Full sized show reworked for the new location. Only adding (famous last words) 13 RBLs that I finally got converted to using pixels
    2019 - Just moved into a new home (yet another change of plans). Will be dim but not dark. Too much to do at the new place to leave time for a show. Dim show (3000 pixels) had regular visits most nights.
    https://www.youtube.com/channel/UCyX...ttrsZNARkUce0Q

  5. #5
    Join Date
    Dec 2011
    Posts
    6,322
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    Hi Martin .

    I am trying to apply Universe 2 to a Gpio without luck .
    Universe 1 works great , but am struggling with #2

  6. #6
    Join Date
    Oct 2014
    Location
    Sauk City, WI USA
    Posts
    1,251
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    Universe 2 should be just like universe 1. You check for the universe in the data header and process it appropriately. The universe is sent as part of the packet.
    https://www.diychristmas.org/wiki/in...itle=Protocols

  7. #7
    Join Date
    Dec 2011
    Posts
    6,322
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    It appears there is no way to #define more than 1 UNIVERSE without having the higher # take precedence.

    If # define UNIVERSE 1
    # define UNIVERSE 2
    Universe 1 never gets processed as the // First DMX Universe to listen for always seems to start at universe 2 .
    Is this the design and workings of the ring buffer ? Or having the addition of #define UNIVERSE_COUNT ?
    Either way , this sorta dampen hopes of this ever working like the previous E131 with multiple output capability .

  8. #8
    Join Date
    Oct 2014
    Location
    Sauk City, WI USA
    Posts
    1,251
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    I thought you wanted to pull out the universe separately for some reason. In either case, I would assume you can get the data you need by following along with the example in the github.

    #define UNIVERSE 1 // First DMX Universe to listen for
    #define UNIVERSE_COUNT 2 // Total number of Universes to listen for, starting at UNIVERSE

    After the e131.pull(&packet); you now have data. Check the universe (packet.universe) and then the data will be in packet.property_values[1] (this being the first channel). Use the packet.property_values as you need.

  9. #9
    Join Date
    Dec 2011
    Posts
    6,322
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    Thanks Mike

    I have that all sorted . The issue remains that I cannot seem to break away from the pipe created by #define UNIVERSE_COUNT

    It seems as though this may be by design to only be a single Pin application .

    In other words , this is no longer possible as far as I am capable . ( which doesn't say much )

    Code:
    #define NUM_PIXELS_A 600 /* roof Number of pixels */
    #define UNIVERSE 1 /* Universe to listen for */
    #define CHANNEL_START_A 1 /* Channel to start listening at */
    #define DATA_PIN_A 5 /* Pixel output - GPIO5 / nodeMCU D1 */
    
    #define NUM_PIXELS_B 123/* star Number of pixels */
    #define UNIVERSE 5 /* Universe to listen for */
    #define CHANNEL_START_B 1/* Channel to start listening at */
    #define DATA_PIN_B 4 /* Pixel output - GPIO4 / nodeMCU D2 */
    Last edited by angus40; 02-21-2020 at 01:24 AM.

  10. #10
    Join Date
    Dec 2011
    Posts
    6,322
    Post Thanks / Like

    Default Re: ESP Async E131 test.ino

    MikeKrebs , your are my hero today

    Thanks to you , I figured out how to break out of the pipe

    I can now use multiple Gpio on the Esp32 YAhoooooooooooooooooo!!!!!!!


    Woot

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •