Jump to content
Light-O-Rama Forums

jim st john

Members
  • Content Count

    55
  • Joined

  • Last visited

  • Days Won

    1

jim st john last won the day on March 17 2013

jim st john had the most liked content!

Community Reputation

3 Neutral

About jim st john

  • Rank
    Member
  1. The easiest way to verify color order is to use test patterns 1, 2, and 3. They should be RED, GREEN, and BLUE, in that order. If the colors you see are different, just make a list of what color order you see from 1 to 3, then select that color order from the drop-down list. If color order is correct and there are still problems coming up with the colors you want, it's going to be a matter of trial and error, playing with different choices in the color picker until you get what you want. Once you get outside of the primary and secondary colors, color matching can be a chore.
  2. Well, setting LOR Adapter to NONE solved the problem. But, what if I want to run LOR controllers and E1.31 at the same time?
  3. I did have a LOR USB485 connected, since I remember that there was an issue if one wasn't used. Not sure about setting LOR Adapter to None in network preferences. I will check that. I'm curious why that would cause a problem though...
  4. I am trying to get LOR to output E1.31 for controlling Madrix. (I did read the stickied thread). I use this arrangement already on my normal show computer, and all is well. Now I'm trying to set up a similar arrangement on a laptop for a presentation. My problem is that I can't get LOR to output E1.31 when playing a sequence from the sequence editor. Every time I open the Play menu, "Control Lights" is unchecked. If I check it, and start a playback, it immediately unchecks itself. The only way that I can run a sequence in the sequence editor without it unchecking "Control Lights" is if I unload the LOR Control Panel. But it appears that without the Control Panel running, LOR doesn't want to send any E1.31. Obviously I'm missing something, but I just don't know what it is.
  5. Not to be too repetitive, but in response to concerns about the complexity of the E68X series user interface, it has been completely rewritten in version 4 and now uses buttons, check boxes, and drop-down tables in place of the old "command line" interface. Capacity has also been increased from 6 to 7 universes of Multicast E1.31, Unicast E1.31 and Art-Net have been added, both handling up to 12 universes.
  6. You may want to consider upgrading the firnware. The new version 4 has a much nicer user interface, adds capacity, new modes such as Unicast E1.31 and Art-Net, and adds several new features. One new feature is the ability to force a range of over-rides on the IP address at startup, and should cover 99% of IP address ranges found on typical LANs. Also it's now possible to read out the current IP address of the board using the LEDs, in order to find out the IP address of the board or verify that it's what you think it is.
  7. Old thread, I realize. Just wanted to make everyone aware that the new version 4 firmware for the E68X controller series is out. It adds a much nicer user interface using drop-down lists, check boxes, and buttons (no more command line), increases Multicast E1.31 capacity to 7 universes, adds support for 12 universes of E1.31 Unicast, also adds support for Art-Net, 12 universes. This firmware will run on the E682s, also on the new E6804 (small low-cost 4-output board), and can run on the older boards as well (E680 and E681) if they are upgraded to the new ethernet module.
  8. New firmware is posted on doityourelfchristmasforum, or pm me here.
  9. A bit belated, and definitely long-winded, but possibly of help to others. The term 'socket' as used in the E682 setup can be confusing because we think of a 'socket' as a physical electrical connector. In this case 'socket' is a networking term that refers to a "virtual" connection, an imaginary wire that carries one universe of DMX data from our show PC to the E682. The E682 supports 6 sockets, or 6 DMX universes. The first step in configuring the board is to determine which universes your board needs to respond to. Typically, but not always, these will be sequential universe numbers, and typically, but not always, the first controller will start with universe number 1. Once you have identified which universes you need, you use the UNiverse command to map those 6 universe numbers to the E682s sockets S1 thru S6. Let me give an example of configuring 2 E682s for a total of 32 50-pixel strings, beginning at universe 1 channel 1, with all pixel addressses being assigned contiguously (no gaps). Since we start with universe 1, we will map the first 6 DMX universes to the first controller. This is actually the default configuration that ships with the controller, so we don't have to change anything, sockets 1-6 will already be mapped to universes 1-6. What this is telling the controller is that those 6 virtual DMX wires between our PC and the E682 are bringing in universes number 1 thru 6 to this E682. If we did have to do this manually we would type 6 UNiverse commands: UN 1 1, UN 2 2, UN 3 3, UN 4 4, UN 5 5, UN 6 6 (and of couse we would end with a SAVE 0!) Now the 2nd step of configuring an E682s addresses is to map the individual clusters of pixel strings to those 6 sockets (and by doing that we are mapping them to the DMX universes that are assigned to those sockets). Again, since this is board number one,and our configuration matches the factory default, we don't have to do anything. Cluster 1 starts with socket 1 channel 1 and runs thru socket 2 channe 90. This is a total of 600 DMX channels (510 in the first universe <remember 511 and 512 are NEVER used> and 90 in the 2nd, total 600). 600 channels = 4 strings * 50 pixles * 3 channels per pixel. Cluster 2 begins at 2-91 and runs thru 3-180. Cluster 3 begins at 3-181 and runs thru 4-270, and cluster 4 begins at 4-271 and runs thru 5-360. So, even though we've assigned universes 1-6 to the 6 DMX sockets on this board, as it turns out we're only using the first 5. Now, let's continue with our remaining pixels on the 2nd E682, and this is where it gets interesting. First we need to decide which 6 universes to map to our 6 sockets on the 2nd E682. Remember, we only used a portion of universe 5 on the first controller, and we want all of our addresses to run with no gaps, so the 2nd controller will begin by using the last part of universe 5. That means controller #2 will be mapped to DMX universes 5 thru 10. To do that we use the UNiverse command: UN 1 5, UN 2 6, UN 3 7, UN 4 8, UN 5 9, UN 6 10. (I have typed that as 1 long line whereas when actually entering those commands each would be on its own line.) This would be a good time to point out that YOU SHOULD NEVER DUPLICATE A UNIVERSE NUMBER when mapping sockets to universes. Start out with the specific universe numbers that you need, and if you don't need all 6, then just map the unused ones to the next universe numbers in order. OK, now we will set the DMX start addresses for the clusters on the 2nd E682. The first board ended with cluster 4 using up thru socket 5 (universe 5) channel 360. So, the 2nd E682 should start with universe 5 channel 361. Remember we enter the DMX addresses as socket numbers 1-6, not universe numbers, so we will use the command: DMX 1 1 361 to set the first dmx address of the 1st cluster to Socket 1 channel 361. Since socket 1 on this board is mapped to universe 5 this will give us the result we want, a start address of universe 5, channel 361. Cluster 1 will run from 1-361 to 2-450. So we use the command DMX 2 2 451 to assign socket 2 (univ 6) chan 451 thru socket 4 (univ 8) chan 30, to the 2nd cluster. Notice here that this cluster actually uses 3 universes, parts of universes 6 and 8, and all of universe 7. DMX 3 4 31 sets cluster 3 to use 4-31 thru 5-120, and DMX 4 5 121 sets cluster 4 to use socket 5 chan 121 thru socket 6 channel 210. (If you notice, it's easy to know what address to use in the DMX command because we just go 1 more than the ending address of the previous cluster). And please don't forget to SAVE 0 when done... As a check, board #2 uses chans 361 thru 510 of universe 5 (150 channels), all of universes 6 thru 9 (2040 channels) and 210 channels of universe 10, for a total of 150+2040+210=2400 channels. And the 2 boards together use a total of 4800 channels (all of universes 1-9 = 9*510=4590 plus 210 of universe 10, total 4800). 4800 channels = 1600 pixels, so everything seems right.
  10. I think closing and reopening everything did it, thanks!
  11. I'm trying to send E1.31 to Madrix for remote control. I exited and restarted the sequencer, and that's all I've tried so far is using the sequencer to play.
  12. Well, I've finally gotten around to trying the E1.31 output of LOR, and I'm obviously doing something wrong because I can't make it work. I went into network preferences and defined DMX universe 8 as E1.31, multicast. I took an existing sequence and changed the channels that I use for Madrix remote control from type standard LOR device (I had been using an idmx1000) to type DMX universe 8. When I play the sequence, I don't see any E1.31 being output on universe 8, either using Sacnview or Wireshark. Obviously I'm missing something. I do have an RS485 output dongle that I use to drive the LOR controllers.
  13. Documentation has not been updated yet, guess I need to get on that..
  14. Not that it will help you now, but the latest firmware allows you to over-ride the default IP at startup with the program button to force an address of 192.168.x.206 where X can be anywhere from 0 to 15.
×
×
  • Create New...