Jump to content
Light-O-Rama Forums

dmoore

Members
  • Content Count

    314
  • Joined

  • Last visited

  • Days Won

    3

dmoore last won the day on August 11 2013

dmoore had the most liked content!

Community Reputation

12 Good

About dmoore

  • Rank
    Member

Contact Methods

  • Website URL
    http://www.HolidayCoro.com

Profile Information

  • Gender
    Not Telling
  • Location
    Houston, TX, USA
  • Occupation
    Sales and Support

More About Me

  • How I learned about Light-O-Rama -
    Purchased my first LOR controller in 2002.
  • Favorite Decorating Holiday?
    Christmas

LOR Software

  • LOR Software Version
    3.9.0
  • License Level
    Advanced
  1. This blog article might help narrow down the root cause of the issue as there are many things other than the controller that can cause random behaviour. http://blog.holidaycoro.com/2015/10/how-to-troubleshoot-random-flashing-in.html Thanks, David
  2. We have released an updated firmware for the AlphaPix V1 and V2 controllers that fixed an issue with "lagging" of output on E1.31 and it can be found here: http://www.holidaycoro.com/Firmware
  3. Please contact us at www.HolidayCoro.com/contactus and we'll be happy to help you through the setup process.
  4. George - I'm showing only a single order in 2014, did we accidentally make a mistake with an order we are not aware of?
  5. The biggest issue we had in solving this problem was actually reproducing it - it took us awhile to find a sequence that would produce the error. We did get that and the developer has located the issue as one invoked when the universe count was upped to 999. We absolutely will be releasing this fix and a number of other tweaks and other improvements before the season starts - our target date is the 15th for the full release.
  6. I'm not sure this goes to fixing his issue. canadianchristmas - Please contact us at support@holidaycoro.com and we'll be happy to diagnose the issue.
  7. Updated firmware to resolve this issue can be found at the following location: https://www.holidaycoro.com/kb_results.asp?ID=114
  8. 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
  9. 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
  10. Mike - Is this capture being run without the Sequence editor running but with the Comm Listener running? It doesn't matter what hardware that is connected or even if any hardware is connected. I'll work on getting the other data you requested and send it to you.
  11. The issue that was originally reported and that I've repo'ed is not consistent - it is random in nature. Anything that is happening over the same pixel, over multiple outputs is likely a configuration issue, possibly with respect to RGB order.
  12. The E1.31 protocol is in this format: CAT5/CAT6 > Ethernet > TCP/IP > E1.31 (E1.17) The "speed" part there comes in the Ethernet section of the protocol and is known by common amounts such as haf/full duplex over 10/100/1000 Mbps. The LOR protocol (along with DMX 1.11) is in this format: Telephone Wire-CAT2/CAT3 to CAT6 > RS-485 > LOR / DMX (E1.11) protocols The speeds used on RS485 are based on network quality and other factors and while LOR's network (actually RS485) "speed" can be varied, DMX is set at 250 kbit/s or about .24 Mbps. This explains why you can only shove so much data (such as in pixels) over a limited amount of bandwidth and at some point, you have to move to Ethernet as a transport - RS485, as great as it is, just can't cut it at higher rates. See http://www.holidaycoro.com/v/vspfiles/downloads/UnderstandingDMX.pdf and http://www.holidaycoro.com/v/vspfiles/downloads/DMXandLORProtocols.pdf So the short of it - if changing the "speed" of the LOR network really does affect the output of E1.31 data, that would be a bug but I suspect that we'll find no connection between the two.
  13. We have narrowed the issue that causes the blinking lights to a change in the Source Name (BSR E1.31 - 201x revision 1.14, section6.4.2) in octet 44-107. What happens is that the Source Name changes from "Light-O-Rama CommListener" to "Light-O-Rama CommListener 3BBA5777A4EF7F\DMX580". We have no idea why the source ID in the LOR CommListener changes in what appears to be a random way but this, along with the Sync address seems to throw off the controller, possibly making it think that the packet is from another controller. We are working with our firmware developer to figure out why this happens but we'd also like to understand from LOR why the packet randomly changes. Here is a video that shows the issue: https://youtu.be/xjGbIWl_UEs Here is the packet that results in a random blink: Here is a "normal" packet: If anyone would like the Wireshark data capture so they can repo the issue, please let me know via PM. Thank you, David HolidayCoro.com
  14. Mike - We are sorry if the perception was that it was an LOR issue - we do not have a conclusive answer at this time as we are still researching the issue so we cannot confirm a root cause at this time. We work hard to remain factual in the information we provide and we of course always want our customers to state factual information. In the years we've been working with disparate hardware and software combinations, we have always found a solution to issues and we expect this to be no different. The firmware author is getting ready to start repo on this issue after we narrowed down the specific driver behind the issue. Yes, we would prefer that customers work directly with us instead of on a competitor's forum but we've come to understand that we need to communicate with the customer in the format and location that they feel comfortable with. Thank you, David HolidayCoro.com
  15. We narrowed the issue down to data that changes inside the E1.17 packet constantly output by LOR's "control panel", even when the show isn't "running". All the packet data has been captured and provided to the firrmware author and he is going to work on it ASAP. I can assure our customers that we'll resolve the problem if it is specific to our firmware well before the season starts but should you have an extenuating situation (a production show in the upcoming few weeks, etc), please contact us directly at www.HolidayCoro.com/ContactUs Thank you for your continued patience. For customers that have opened a support ticket, we will notify you directly when the solution is available. Thank you, HolidayCoro
×
×
  • Create New...