Jump to content
Light-O-Rama Forums
xmasjam

Smart RGB lights will not stop blinking while Idle, no shows playing

Recommended Posts

I've run it multiple ways so far.  The listener is ALWAYS running in each of these circumstances (obviously)

 

Sequence Editor running:

  • but not running a sequence (6 million packets)
    • Then forcing a reload of the Listener by making a trivial network configuration change (a couple of million)
  • running a constant color change sequence on those universes (9 million packets)
    • Also then forcing a reload of the Listener by making a trivial network configuration change (a couple of million)

 

No sequence editor running at all (5 million packets)

and then forcing a reload of the Listener by making a trivial network configuration change (a couple of million)

 

 

Currently I am testing connecting and disconnecting to the listener with different programs in the suite to see if I can get it to dump a bad packet.  8.5 million so far.  

 

 

I have not captured any weird packet with any test.  

 

LOR 4.1.2.  The Network Config is Intel 82566DC-2 GB NIC -> D-Link 24 port unmanaged -> D-Link 8 port unmanged -> devices.  Wireshark running on the computer with the listener.

post-7637-0-44677100-1439754665_thumb.jp

Share this post


Link to post
Share on other sites

Mike - 

 

I just sent the requested information (LOR Diag output / Wireshark data) and I've produced another video showing the hardware configuration and the problem happening in "real time":

 

http://youtu.be/fovZEeW_3ZE?hd=1

 

Thanks,

David

Share this post


Link to post
Share on other sites

Received my Pixcon16 today. It'll have to wait to test it as I have to jump in the car and drive all the way to California due to a funeral. 

Share this post


Link to post
Share on other sites

As I said two nights ago, I started a Wireshark capture overnight for my live show.  Because of logistics, it did not happen until early Monday morning so therefore, it was about 4.5 hours of my overnight show (which does not have any of the E1.31 lights on), and 6 hours of no show running, but the comm listener running.  There were a little over 6 million packets and I just finished the search and there were no packets that had the extra characters David mentioned.

 

I did the search twice using the two filters below.  The only difference is the destination IP address since there were packets to two different SanDevices E6804 cards.

ip.dst == 192.168.131.98 and frame[110:18] != 65.72.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00

ip.dst == 192.168.131.99 and frame[110:18] != 65.72.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00

 

All was done in unicast and using LOR 4.1.2 on an WinXP based computer.

 

 

Share this post


Link to post
Share on other sites

I was testing some strips last night for dead pixels, and I noticed something I hadn't before. The random blinking occurs even when a strip is active. Obviously it's hard to see during a sequence, but while I was testing I had them on solid colors. While on, you can still see that random quick blinking throughout the strip. It's much less noticeable while the strip is lit, but it's there just the same.

 

Mike

Share this post


Link to post
Share on other sites

Please contact Holiday Coro as we have determined that the issue is not with the LOR Showtime Software, but with the firmware and/or the controller they are selling.  They did provide us with several captures that they assumed were incorrect, but as per the E1.31 specifications those packets are indeed properly formatted.

 

The field David pointed out should have no impact on if lights flash or not.  There are 2 reasons for this:

 

  1. As per the ANSI E1.31 (2009), that particular field should be NULL terminated, and the S3/S4 software is correctly NULL terminating the field.  (Non computer geek: There are up to 64 characters available for the source name.  You don't need to use them all.  If you use 63 chars or less, the name ends with a NULL character.  When you find a NULL character it, and anything past it is to be ignored).  That means the packets with and without the extra garbage data should be treated identically.
     
  2. The field referenced actually should not be impacting lights at all.  The field can be used by a device to decide if it should or should not use a particular value (something called 'merge and negotiation' if I remember correctly).  Even if the 2 packets for the same universe were setting the field differently (see #1 -- they aren't but lets assume they are),  both packets payload (the actual lighting data) are identical:0.  

We have ran multiple other E1.31 devices and none of them experience the same issue.

 

We have not heard back from them in nearly 2 weeks, so we assume they have found the issue with their hardware.

Share this post


Link to post
Share on other sites

David - I have hidden your reply for now.  Please reply back to the eMail that I just sent.  

Share this post


Link to post
Share on other sites

I hate to pile on, but I too have this issue and no pixel controlling software or testers , except the LOR Listener/control panel is causing my issue.  I've tried every combination I can think of and the issue only occurs with the LOR Listener running.  No sequence of any kind needs to occur to see this, just fire up the LOR Control Panel.

 

This may not be scientific or technical, but it's what I'm seeing.  I do hope SOMEONE finds a solution before October, or I'll have to shelf the ton of pixels I purchased this year.

Edited by Liberty-Laser

Share this post


Link to post
Share on other sites

did notice the same while sequence was playing hard to see it but for sure it was there. the only thing that works correctly is the test patterns with the alpha pix.

Share this post


Link to post
Share on other sites

Due to restrictions on posting in our competitors forum, we will be unable to answer additional questions in this location.  Please contact us at:

 

http://holidaycoro.com/contactus

 

Note that you would like to be notified when a work around for this issue has been completed (this will be well before the start of halloween) and we'll send you an email.  If you are on our mailing list, we will also be sending an update their additionally.

 

Thank you,

David

Holidaycoro.com

Share this post


Link to post
Share on other sites

Updating to 1.04 Firmware has solved my issues as well with two long runs channels which had three nulls installed.  

Share this post


Link to post
Share on other sites

Pixcon 16 controller, brand new, is having similar issues with random blinking on single pixels. Configured properly, ws2811 pixels being used. Issue happens even when no data wire is connected to the board(that is actually when I first noticed the problem during the first test to see the pixels). Powered the board from a clean dedicated circuit breaker. Used built in hardware test and did not notice any random blinking or abnormalities while in test mode. Took the controller out of test mode and random blinking occurs while in stand by mode. Then Connected PixCon16 to a lap top ethernet port(turned off internet), checked out configuration then loaded sequence editor. Random blinking occurs during sequence. At one point it stopped after opening the pixcon assistant utility, even while running the same sequence from earlier. When I thought the problem was gone and began closing some windows, it started again and I could not re create events to start or stop the random blinking. I just bought this equipment and am extremely disappointed. Now Thanksgiving is almost here. What is the fix Lightorama?

Share this post


Link to post
Share on other sites

I tripped on this thread because I too had RGB blinking light issues that would begin randomly while the show was idle (came home from getting Christmas tree and house was going wild) and once the control panel was unloaded, it would stop.  So the symptoms are similar and may be completely unrelated but in my case I have 100% LOR controls and networks.  

 

This is my first year running 2 HS RS485 networks with 4 CCPixel 100 controllers on one COM and 1 CMB24D Controller and an older 16 channel legacy controller on the other COM.  I ran all the same hardware last year with 1 HS and one standard and did not have this issue.  In my case the issue seemed to only impact the CMB24D controller with the latest firmware.  For the LOR networks, I had set their speed higher in the network preferences but what I eventually had to do to get them to stop (at least I think it stopped) is turn off power save and hibernate options on the PC and then go to the System Panel and adjust the baud rate on the COM devices.  

 

As I said before, this may be completely unrelated but I thought I would throw it out there just in case it might be helpful to others.

Shane

Share this post


Link to post
Share on other sites

If it's any consolation, I have seen the same issue with my J1Sys P2 controller...

Oddly enough, I turned the whole pixel tree on Red, then Green then blue and the problem did not persist.

However when chasing colors they would flash..

Eventually, the problem ceased and for the last 3 nights I have had no issues.

We loving it call it our Christmas Ghost... A couple of years ago he was picking on my MiniTrees which are incans and driven from LOR controllers...

For what its worth .............

Bob

Edited by bob_moody

Share this post


Link to post
Share on other sites

RF noise on RS485 is Voodoo :(  You may never find it, or go nuts trying.

Share this post


Link to post
Share on other sites

Already nuts ... (I'm a decorator in year 14.....)

considering the weather, the lay of the cords, the phase of the moon .. etc .. RF noise wouldn't surprise me ...

Bob

Share this post


Link to post
Share on other sites

Already nuts ... (I'm a decorator in year 14.....)

considering the weather, the lay of the cords, the phase of the moon .. etc .. RF noise wouldn't surprise me ...

Bob

 

If you do a search, you can find a thread around here (from last year I think) about a poor guy who had the same 3 channels blinking when they shouldn't.  Turned out it was his electric fence.

Share this post


Link to post
Share on other sites

I see this happening on my P12S too but only when a sequence is actually running. Its not enough to make me take things apart and it was not doing this last year. I emailed Ed today about this and another P12S that has other issues (not in use). I'm using Cat6 throughout so should be very well shielded...still can't rule out noise though.

Share this post


Link to post
Share on other sites

I wish I knew more about the protocols that all these different pixel strings use (that is, the protocol of what goes up the data wire on a pixel string).  I am all too familiar with how E1.31 works.  I will have to dedicate some study time next year.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...