Jump to content
Light-O-Rama Forums

smithzone

Members
  • Content count

    52
  • Joined

  • Last visited

Community Reputation

1 Neutral

About smithzone

  • Rank
    Member

Profile Information

  • Gender
    Not Telling
  • Location
    Tampa, FL
  • Occupation
    Call Center Management

More About Me

  • Interests
    Beer?
  • How I learned about Light-O-Rama -
    Searching on more "Professional Grade" set-ups versus the one box automated systems available at big box stores
  • Favorite Decorating Holiday?
    XMAS

LOR Software

  • License Level
    Advanced

Recent Profile Visitors

279 profile views
  1. Multiple Universes in LOR and SANDEVICES

    Perfect - that is what I wanted to hear, before I hit the "Buy" button (or send email in this case)
  2. Multiple Universes in LOR and SANDEVICES

    This is great - I already updated to the new Firmware so my screens match. I just wasn't sure I could start at some random universe point above 12 on the SANDEVICE (as the manual also references that 12 universe limit). Looks like I will have no issues expanding. I have the dedicated light network up on a gigabit router with CAT6 so should be fine there (I understand the 6804s only run 100B on their port). While researching this, I keep reading about the Falcon F4V3 Pixel Controller - might be another option as well.......
  3. I have two SANDEVICE 6804 running on e1.31 using lightorama for my show (latest firmware on both). I have CAT6 running to everything and I am using Unicast.Only my second year adding e1.31 so now thinking about adding two-three more 6804s (as I like them close to props). Current SANDEVICE #1 (unique IP) has each of the ports aligned with a universe - (so Port 1= Universe 1, Port 2= Universe 2, Port 3= Universe 3, Port 4= Universe 4)Current SANDEVICE #2 (unique IP) has each of the ports aligned with a universe - (so Port 1= Universe 5, Port 2= Universe 6, Port 37= Universe 7, Port 4= Universe 8)Adding a New SANDEVICE #3 (unique IP) looks simple enough, it will be the last 4 slots on the SANDEVICE webpage - Universe 9->12My question is how do I add SANDEVICE #4 (unique IP)? Do I change the SANDEVICE webpage to start at Universe 13 and run up to Universe 24? Can I run five 6804s and 20 universes all on same network (will it support that many)? The old SANDEVICE manual says "76 universes of E1.31 multicast, and up to 12 universes of E1.31 Unicast" so thinking not on Unicast? If that doesn't work is there a way I can set-up each SANDEVICE as Universe 1->4 and tell LOR that Universe names overlap, but they are on unique IPs? I don't see a way in LOR Network Config.
  4. Anyone doing Despacito?

    Might be completely worn out by Christmas, but 3 BILLION YouTube views.......
  5. RJ45 Ports - Outside?

    That is a nice method - I was going to run a short piece of conduit and then wall mount the box. I like this concept better - nice and clean
  6. I am looking into running some CAT6 through the attic to 4 RJ45 ports on the left side of the house. I run a mix of LOR and e1.31 through a dedicated router and PC on the far right side of the house. In previous years I had to run the cables across the entry way to connect all the controllers. I have a pretty good understanding of LOR network and star topology so I am fine there. What are some best practices for installing RJ45 ports outside? I am in Florida (so no snow) and thinking I'll just place an exterior rated wall box with a short peace of conduit up through the soffit right under the eave. Then some sort of of flip cover over all the plugs. Anyone have a similar set-up? Rust issues?
  7. TABCTL32.OCX Error

    Sort of solved - just installed 4.3.18 over existing install No more error
  8. TABCTL32.OCX Error

    WIn10 4.3.14 Advanced Everything seems okay, but I get this error everytime it loads
  9. What did you MAD GRAB?

    2 * Pixcon16 and 8 more RGB floods with controller:) Paypal and out by 9:02p
  10. TSO - Paul O'Neil has passed

    Sad day for many of us - may have to double down on TSO this year Paul O'Neill, the Tampa-based rock composer and mastermind of one of the biggest touring acts in the world, the Trans-Siberian Orchestra, has died at age 61. The entire Trans-Siberian Orchestra family, past and present, is heartbroken to share the devastating news that Paul O’Neill has passed away from chronic illness. He was our friend and our leader -- a truly creative spirit and an altruistic soul. This is a profound and indescribable loss for us all. We ask that you respect Paul’s family’s privacy now. We will make additional announcements shortly. [Admin Note: Thread Merged]
  11. Most out of a E1.31 controller

    Interested in seeing as well - just picked up three of the holiday Coro grids and 1600+ pixels in their sale
  12. Tesla and TSO

    Video Just saw that Tesla came out with a new holiday easter egg that plays TSO Pretty cool
  13. Comm Listener error 3: Comm Winsock Error

    Success - thanks so much!
  14. Comm Listener error 3: Comm Winsock Error

    Okay, makes sense on the DMX port - I will update those to "5568" is "8877" appropriate for the COMM listener port?
  15. So took a shot at expanding the system a bit with a SanDevice 6804 and now stumped. Issue: "Comm Listener error 3: Comm Winsock Error" about every three seconds whenever I add the DMX network to the LOR Network Configuration panel. Nothing will then work as I am getting this error repeatedly. Current System: 11 CTB16s - pushing about 28k LEDs 4 CMD-24D - pushing dumb ribbons and LOR floods USB485B v4.1.2 Advanced on dedicated light PC Light PC is a HP laptop with Win7 What I have done: Laptop wireless is off (via hardware switch) and the laptop and SansDevice are on their own dedicated network with unique router. I can navigate to the SansDevice website from laptop and run a test pattern just fine (rules out a lot). LOR network is running on COMM5 and works just fine as long as no DMX networks are in the LOR Network Configuration panel. SansDevice is set to Multicast (I have tried unicast as well) I have tried just adding one universe as well (versus the two in screenshot) - same issue Thoughts on what else I can do to resolve COMM issue? I found some old info in forums, but nothing recent that seemed applicable (v3, reinstalling windows, Smart DMX, etc).
×