Page 3 of 7 FirstFirst 12345 ... LastLast
Results 21 to 30 of 63

Thread: Teensy 3.2

  1. #21
    Join Date
    Sep 2017
    Posts
    23
    Post Thanks / Like

    Default Re: Teensy 3.2

    What ethernet module are you using? I probably won't attempt that for now but will be nice to convert to that later on.

    Thanks!

  2. #22
    Join Date
    Dec 2016
    Location
    Tremonton Utah
    Posts
    107
    Post Thanks / Like

    Default Re: Teensy 3.2

    W5200 module. I have a board that I made that allows you to connect all the parts.

  3. #23
    Join Date
    Sep 2017
    Posts
    23
    Post Thanks / Like

    Default Re: Teensy 3.2

    I finally got a rough count of how many LEDs I will have on the roof line. I am looking at about the 550 LED mark. Do either of you know what the max LED per strand would be for the Teensy? I could easily split them into 2 stands but wanted to see if it would be possible to keep them on one strand. I will test it out but I don't have all the LEDs yet. Thanks!

  4. #24
    Join Date
    Dec 2016
    Location
    Tremonton Utah
    Posts
    107
    Post Thanks / Like

    Default Re: Teensy 3.2

    4 universes per octo pin (680 pixels) with current code and settings. That's running the controller at 32 universes. If you run it half then you can use two pins


    Sent from my iPhone using Tapatalk

  5. #25
    Join Date
    Mar 2017
    Location
    Indiana
    Posts
    114
    Post Thanks / Like

    Default Re: Teensy 3.2

    Assuming you have enough power for the leds, you could do 1108 per string running at a 33ms aka 30 frames per second. With the Teensy 3.2 running 8 strings, you'd have 8864 LEDs
    That's based on the info in the right side bar here: https://www.pjrc.com/store/octo28_adaptor.html

    For my setup, using a serial/usb connection, I'm running 220 leds on the longest of 5 strings and am having no issues. I'm running with 25ms timing (40 fps). I'd love to go to 16ms timing (roughly 60fps), but Vixen and/or FPP don't support it by default...(yet?)
    Halloween 2019 Lights: https://youtu.be/QbNE1x21gqA
    Christmas 2018 Lights: https://youtu.be/pkcxuiiSdhc

    Other shows and behind the scenes:
    https://www.youtube.com/channel/UCg1...c85-wgbnkNiLOw

  6. #26
    Join Date
    Dec 2016
    Location
    Tremonton Utah
    Posts
    107
    Post Thanks / Like

    Default Re: Teensy 3.2

    Quote Originally Posted by ShadowLight8 View Post
    Assuming you have enough power for the leds, you could do 1108 per string running at a 33ms aka 30 frames per second. With the Teensy 3.2 running 8 strings, you'd have 8864 LEDs
    That's based on the info in the right side bar here: https://www.pjrc.com/store/octo28_adaptor.html

    For my setup, using a serial/usb connection, I'm running 220 leds on the longest of 5 strings and am having no issues. I'm running with 25ms timing (40 fps). I'd love to go to 16ms timing (roughly 60fps), but Vixen and/or FPP don't support it by default...(yet?)
    I was hoping to get the DMX e1.31 ethernet close to that many pixels. at about 33-34 universes I started loosing too many frames to where the pixels were getting very low frame rates. I think I have found a way to squeeze more by reading the ethernet buffer more efficiently. So its very possible to get the ethernet method up to that 8000 LED figure. Right now I am elated to get it doing 5440. Still need to get some FPP tests. If the controller connects at the 11Mbps and the FPP will send at that rate then we should be able to get really good frames and pixel counts via USB. This scenario will be a great bundle with a rpi zero. Imagine having many rpi remote players synced by a simple clock and each paired with one of these controllers doing some serious pixel power and very little wifi overhead.

  7. #27
    Join Date
    Mar 2017
    Location
    Indiana
    Posts
    114
    Post Thanks / Like

    Default Re: Teensy 3.2

    My setup this year is a RPi B running FPP with a USB connection to the Teensy 3.2 for the LEDs. I also have a 32*64 matrix running off a RPi Zero W running FPP. The sync has been working well over wifi so far.

    crees are you running your show from a PC (which makes ethernet a good option)?
    Halloween 2019 Lights: https://youtu.be/QbNE1x21gqA
    Christmas 2018 Lights: https://youtu.be/pkcxuiiSdhc

    Other shows and behind the scenes:
    https://www.youtube.com/channel/UCg1...c85-wgbnkNiLOw

  8. #28
    Join Date
    Dec 2016
    Location
    Tremonton Utah
    Posts
    107
    Post Thanks / Like

    Default Re: Teensy 3.2

    Quote Originally Posted by ShadowLight8 View Post
    My setup this year is a RPi B running FPP with a USB connection to the Teensy 3.2 for the LEDs. I also have a 32*64 matrix running off a RPi Zero W running FPP. The sync has been working well over wifi so far.

    crees are you running your show from a PC (which makes ethernet a good option)?
    I plan on using both methods. Its much more convenient to use the USB method and skip the network module. I have a couple rpi waiting for me to get fpp running and tested out.

  9. #29
    Join Date
    Oct 2017
    Location
    Slovakia
    Posts
    8
    Post Thanks / Like

    Default Re: Teensy 3.2

    I'm trying to prepare LEDs for my show, around 1500 LEDs.
    My intention is to setup it on following way: RPi (FPP) - Generic Serial (115200 baud rate) over USB -> Teensy 3.2 (3-4 pieces synced via PIN 12).
    I want to use Teensy sketch above posted by: ShadowLight8 where I modified type of LEDs and update frequency based on that which I have founded in OctoWS2811 library:
    OctoWS2811 leds(MAX_PIXELS_PER_STRIP, displayMemory, drawingMemory, WS2811_GRB | WS2811_400kHz);

    My current test is just about strips (each have 50 LEDs), which are working fine with test sketch from ArduinoIDE -> OctoWS2811 -> Rainbow
    Till now everything looks fine and working, at least I can prove, that update frequency is suitable for my LEDs and I do not have any interference between cables from Teensy 3.2 to LEDs.
    I uploaded, seems succesfully above sketch, connect USB to RPi, found out correct tty* port in dmesg, setup Header to: <>, set count of channels to right number: NUM of LEDs * 3 (8 * 50 * 3 = 1200) just to cover all Teensy outputs, even if I'm having connected just 2 strips during the test.
    When I start Display Test in FPP, I can see serial output in FPP logs:

    2017-10-26 18:37:51 (3659) channeloutput/GenericSerial.cpp:155:GenericSerialOutput::RawSend Data(0xff49e8)
    2017-10-26 18:37:51 (3659) common.c:112:Generic Serial: (18 bytes)
    2017-10-26 18:37:51 (3659) common.c:135:000000: 3c 3e ff 00 00 00 ff 00 00 00 ff ff 00 00 00 ff <>..............
    2017-10-26 18:37:51 (3659) common.c:161:000010: 00 00 ..
    2017-10-26 18:37:51 (3659) channeloutput/ChannelOutputBase.cpp:272:ChannelOutputBase thread: sent: 1509035871501391, elapsed: 22831
    2017-10-26 18:37:51 (3921) common.c:112:Channel Data: (16 bytes)
    2017-10-26 18:37:51 (3921) common.c:161:000000: ff 00 00 00 ff 00 00 00 ff ff 00 00 00 ff 00 00 ................
    2017-10-26 18:37:51 (3921) channeloutput/ChannelOutputBase.cpp:134:ChannelOutputBase::SendD ata(0x76793018)
    2017-10-26 18:37:51 (3921) Sequence.cpp:349:ReadSequenceData()
    2017-10-26 18:37:51 (3659) channeloutput/ChannelOutputBase.cpp:298:ChannelOutputBase thread: woke: 1509035871528738
    2017-10-26 18:37:51 (3921) channeltester/ChannelTester.cpp:161:ChannelTester::OverlayTestDa ta()
    2017-10-26 18:37:51 (3659) channeloutput/ChannelOutputBase.cpp:152:ChannelOutputBase::SendO utputBuffer()
    2017-10-26 18:37:51 (3659) channeloutput/GenericSerial.cpp:155:GenericSerialOutput::RawSend Data(0xff49e8)
    2017-10-26 18:37:51 (3659) common.c:112:Generic Serial: (18 bytes)
    2017-10-26 18:37:51 (3659) common.c:135:000000: 3c 3e ff 00 00 00 ff 00 00 00 ff ff 00 00 00 ff <>..............
    2017-10-26 18:37:51 (3659) common.c:161:000010: 00 00 ..
    2017-10-26 18:37:51 (3659) channeloutput/ChannelOutputBase.cpp:272:ChannelOutputBase thread: sent: 1509035871551201, elapsed: 22465
    2017-10-26 18:37:51 (3921) common.c:112:Channel Data: (16 bytes)
    2017-10-26 18:37:51 (3921) common.c:161:000000: ff 00 00 00 ff 00 00 00 ff ff 00 00 00 ff 00 00 ................
    2017-10-26 18:37:51 (3921) channeloutput/ChannelOutputBase.cpp:134:ChannelOutputBase::SendD ata(0x76793018)
    2017-10-26 18:37:51 (3921) Sequence.cpp:349:ReadSequenceData()
    2017-10-26 18:37:51 (3659) channeloutput/ChannelOutputBase.cpp:298:ChannelOutputBase thread: woke: 1509035871578673
    2017-10-26 18:37:51 (3659) channeloutput/ChannelOutputBase.cpp:152:ChannelOutputBase::SendO utputBuffer()
    2017-10-26 18:37:51 (3921) channeltester/ChannelTester.cpp:161:ChannelTester::OverlayTestDa ta()
    2017-10-26 18:37:51 (3659) channeloutput/GenericSerial.cpp:155:GenericSerialOutput::RawSend Data(0xff49e8)
    2017-10-26 18:37:51 (3659) common.c:112:Generic Serial: (18 bytes)
    2017-10-26 18:37:51 (3659) common.c:135:000000: 3c 3e ff 00 00 00 ff 00 00 00 ff ff 00 00 00 ff <>..............
    2017-10-26 18:37:51 (3659) common.c:161:000010: 00 00 ..
    2017-10-26 18:37:51 (3659) channeloutput/ChannelOutputBase.cpp:272:ChannelOutputBase thread: sent: 1509035871594676, elapsed: 16006


    During that time, LEDs are doing nothing, so I decide to Stop display testing and unplug the Teensy from RPi.
    When I plug Teensy to different power source e.g.: PC, USB charger ... Teensy will light up LEDs and "draw" one frame.
    With repeating this, unplugging and plunging Teensy to different power source I can light different frames one by one.
    As WS2811 remember last state and will remain on with last color after exercise with different power supply, when I plug Teensy pack to RPi, LEDs goes off, even that time, when I'm not "playing" any display test sequence or something else.

    For me it looks like, Teensy boot up, start reading serial data, but hang in some point, where data are not transmitted to the LEDs.
    Does anyone have any experience or suggestion how to proceed ?
    Last edited by nitrox788; 10-27-2017 at 07:14 AM.

  10. #30
    Join Date
    Dec 2016
    Location
    Tremonton Utah
    Posts
    107
    Post Thanks / Like

    Default Re: Teensy 3.2

    Check power grounds and make sure PI has a good ground to the strips as well.


    Sent from my iPhone using Tapatalk

Page 3 of 7 FirstFirst 12345 ... 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
  •