Jump to content
Light-O-Rama Forums

bob_moody

Members
  • Content Count

    749
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by bob_moody

  1. Glad it worked for you. As I said if you want to convert those to RGB, its just one more click. Futuretechguy.... Appreciate the option. Looks like it takes a lot of real estate to load though. I usually jump on options to beta test new stuff, but for now.. I'll have to pass .. sorry... Bob
  2. Yes .... I am assuming that both nics are not on the same network... If you run Unicast, then you can specify the address to your controller. Only the traffic on that network will go out on that nic. if you are using multicast, it will broadcast across both nics. However, you can add a static route that will contain the multicast traffic to the nic you are using for E1.31 traffic ... route -p add 224.0.0.0 mask 240.0.0.0 <ip of correct pc interface to use> metric 5 The "p" in the route command will make this a persistant route meaning you dont have to set it everytime you boot. I use the static route because I have the show nic and a Wifi connection to the house router (it updates the web page when the show starts) . Bob
  3. +1 to Phil and +1 to Dennis. Just to expand... look in the RJ45 jack on the controller. Are all 8 pins there and parallel ? Sometimes one of the fingers will lift out of the slot and slip over .. you can usually fix this with a careful toothpick. Had a similar problem and it was a downstream cable. verify that all you cables are good .. my 3rd controller wouldnt work and it was the cable between the 1st and 2nd .... go figure .. thought I would never find it .. Also .. make sure you try Phil's suggestion and switch connectors. Either RJ45 will work... if its the last controller then your okay.. if there is another behind it, you might have swap them around to make the one with the bad connector the last in the chain. Bob
  4. It's never to late. LOR is outstanding when it comes to stuff like this. They have done the EXACT same thing for me and I have had some of my controllers since 2005. Open a service ticket or give them a call.. both take only a minute and both are free (service ticket and/or call) Worse comes to worse ..they can tell you exactly what to get and from where .. Bob
  5. Is your CCR tree programmed in SuperStar? If so, then you can open the sequence (assuming S4), go to EXPORT, Export in Legacy Mode and UNCHECK the Include Macro Channels for Cosmic Color Devices. If not Superstar, then you can manually remove the macro channels (7 channels * 12 ribbons = 84 macro channel deletes.) Of if you have the CCR tree sequence isolated. I have a program that wrote a couple of years ago for doing just that. I gave to Dave (the pixel tree sequencing God!!) and he used it to provide both CCR and Pixel based version. It reads the file and exports it with the macro channels deleted. Its actually a pretty easy conversion to get from CCR to Pixel based.... Ashame though .. You have a lot of $$$ in the CCR's Bob
  6. I will assume you adding 96 single function channels -- channel 145 thru 240 ? Right click on an existing channel (for this explanation I created an animation sequence with 1 channel) Mouse over INSERT DEVICE then click INSERT DEVICE BELOW. Configure the device with a NAME, DEVICE (DMX Universe), Universe # Click the Radio button for CHANNLES then click the drop down box. You asked for 96 channels starting at 145 --- Select 240 in the drop down box To make it easy to pare it down.... Right click the 1st DMX channel and click on "CONVERT TO GROUP" Select the 1st channel for the First is Group Box. Select channel 144 as the Last in Group Click Create Group Right Click the Group you just created Click on DELETE CHANNEL GROUP LIST (and confirm) What yo are left with is 96 channels starting at Channel 145 and ending at channel 240 You can now Group them, or convert them to 32 RGB channels ... Hope this helps ... Bob I was typing this as I was doing it .. I HOPE I didn't miss a step or miscount ...
  7. <invisible text> </invisible text> Glad you got it working ... Kudos to Jim and Mr. P good catch guys !! Bob
  8. Jim, take a look at his Wireshark post when you get home.. I think it looks spot on.. Bob
  9. Excellent work!! Wireshark looks good.. Route Table looks good. The TPLink is an unmanaged switch ... 1. Have tried connecting the laptop to the SanDevice without the switch? 2. Clear your ARP cache. First enter the command "arp -a" this is display the arp cache. Next clear the cache with the command " arp -d * " Run the arp -a again Now try again to see if the pixels will light up. I am remembering a conversation with Ed from J1Sys about Ethernet ...I was having a similar problem ... "Ethernet switches detect the mac address from transmissions and store them. once detected on a port the switch will only send to that port. Since the e131 protocol and etc doesn’t go bi-directional the ECG units don’t transmit much, so the switch remembers the old location until it resets or times out" So ... lets see if this helps.. ALSO...... try it direct ... without the switch.. new computers will automatically detect the cable type/connection needed. Bob
  10. I guess a couple of final thoughts.. If the DELL is working, use it for the show computer. I have a separate machine to run the show. My desktop is powerful enough to do all the sequencing and my show laptop is a OLD dell inspiron 1300 running XP .. However, is this HP a laptop? You didn't post the route print command so I cant help there .. however, if the HP has WiFi, turn it off as well so they only network comm is via the NIC card. You also didn't post if this was a direct connect or through a hub, switch or router I run a static route on my PC for the Multicast. This keeps the traffic off my home network since I still have the show computer on the home network to update our website with show status. Finally your didn't post the status of the little block in the lower right of the sequencing screen. after that ... without having access tot he machine, running wireshark or something to view the output packets .. not much more I can do or say. Bob
  11. From the SanDevice web page: 1. Make sure of the IP address set matches IP and subnet the PC is on. (we did that... correction on the 10.x.x.x subnet .. 255.0.0.0 is correct ) 2. Make sure the Receive Mode is set correctly. If you going to use Multicast, Unicast or Artnet 3. Make sure the TEST is set to zero (0) From the LOR Network: 1. Select Universe (1 in your case) 2. click on Use E1.31 radio button 3. Select Multicast - Port 5568 and total universes is 1 4. Verify Comm Listener Port is 8837 From the PC: 1. Verify IP network on the wired NIC port is 10.10.10.x (your choice) and subnet is 255.0.0.0 2. IPv6 networking is turned off (unchecked) 3. Disable Windows firewall -.. Private and Public Make sure you are using the "not recommended" setting and just didn't select one the check boxes while its on. 4. open the LOR Control Panel 5. Open LOR Sequence editor 6. Verify channel config is using Device Type DMX, Network Universe 1 and the correct Circuit # 7. From PLAY - Make sure that Control lIghts is checked. This check mark does have a tendancy to disappear depending on the rest of the network config. If you have ONLY DMX devices then no.. you don't need a LOR dongle plugged in and connected to a LOR controller. However, if you do have LOR controllers defined then its a matter of if you have the drivers for the LOR dongle loaded. This is especially true with the older serial dongles. However, for this exercise, plug in the LOR dongle and verify that when the sequence is running that PAY -- Control Lights stays checked though out the sequence. Also observe the colored square in the lower right hand corner of the sequence editor. What color is it when your playing your sequence? I think that about covers my setup. As I mentioned I have several pixel and node controllers from J1Sys, SanDevice and AC controllers from LOR and an AC (DMX) controller from Minleon. Bob I have CDO ... its like OCD but all the letters are in the right order .. Like the SHOULD be !!! LOL
  12. 100% sure the (ALL) firewall is off? Remember there would be a Home (private) network and a Public network. Not a 3rd party firewall or virus filter running? Also, from a command line run a "route print" command (post it if you can) Make sure you have IPv6 turned off as well... yes .. I know shouldn't affect it... but .. Dbl check on the SanDevice webpage that test is set to 0... replace the CAT5 cable from the PC to controller. Is this a direct connection or is there a hub/switch involved? Bob One more thing .. you changed from multicast to unicast or vice versa ... set to multicast and dblcheck your LOR network settings since we changed the IP config.
  13. Let me throw one more shotgun load in the chamber. Turn off your Windows Firewall (all of it .. PUBLIC and HOME) ... I always see my LOR connections on the PUBLIC side .. but to make testing easy .. shut down all of it .. Also if you don't use Windows firewall, shut down any 3rd party firewall you may have running. I just tested this on my machine ... Firewall --- no LOR... Firewall OFF.. LOR good .. If that resolves the issue, you can turn the firewall back on and then set the Pubic side to block inbound and ALLOW outbound traffic. Bob
  14. Also since you loaded Xlights, make sure it is NOT loaded or running when working with LOR ... I have had weird results when both are present. As Walt mentioned, make sure the LOR control panel is running. Also make sure you can ping the SanDevice ... from a command line issue ping 10.10.10.1 and make sure you are getting a reply Bob
  15. Is your computer set up for DHCP? I ask because you have selected what is called an APIPA address. This is an alternate address set (class B ) that is used when a DHCP request fails. APIPA addresses are very limited in what they can do. Yes. they can communicate among themselves but ... Also note.... in your IPCONFIG image. It is running autoconfig. note that you will get a different address to the PC everytime you boot. If this is a dedicated NIC card. Set the IP static ... 10.10.10.254 255.255.255.0 Start you devices at the bottom ... 10.10.10.1 255.255.255. Fix your network config in LOR and you should be up and running.. This is the exact setup I use.. I have LOR, Sandevices and J1Sys.. all running happy and fast.. Bob
  16. Phil, There is an open spot in the file. That blob of what looks like unformatted text at the top has the rest of the opens. I have started and restarted the process several times since I began seeing all this .. Last night, I fired it up and was play around and accidentally closed the CMD window while it was running. It immediately restarted and since 9:00PM last night .. not a SINGLE ERROR has occurred. I do have a help ticket in with LOR. I'll get their eyes on it and see what the guru's have to say. I appreciate your file and thank you for taking a look .. Bob
  17. Thank you very much. It was a labor of love. Sent from my Nexus 7 using Tapatalk
  18. Submitted a ticket to LOR ... If allowed, I will post the resolution when they get one. Bob
  19. Thanks Jim. I'll open a case with LOR. I'm striking out on the forums :-( ... So really weird stuff happening this year .. Bob
  20. Thank you Doug... that is exactly what I have set Bob
  21. Still having issues ... (arrrghhhh) I noticed that as each song loaded and played the memory usage increased. Not releasing?? BUT.. the kicker is, as I reported in another post I am seeing errors during playback in the command window. When i was preloading and a song threw an error everything continued on. Now the show stops and wont load the next song. Memory is at about 1GB but everything appears locked up on the player. If you or someone could take a look at thread: This will explain the command window errors I am seeing. Bob
  22. Well your suggestion made a big impact!!! I reconfigured the show to load as needed. I'm not seeing any real extra time delay between songs and memory usage has dropped from 1.4 Gigs to 436 Megs. I'll run it for a while and see how it goes on some of the larger sequences and get back to you.. THANK YOU VERY MUCH ... for the advice ... Bob
  23. Your size observation is about what I'm seeing as well. The show is somewhat behaving better now. I think I have only thrown 1 error in about 3 hours of running .. MUCH better than what I was seeing earlier. I did rework everything and the verifier is only showing warnings about channels not being turned on which in this case is expected. I think the verifier needs to look at the whole RGB pixel not just 3 individual channels. The warnings are coming up on the hat part of my Chromahat. It's turned on red and stays there. The blue and green pixels are never used. The pixel is being used but not all three channels so it throws warnings on the B ad G parts... no biggie.. its can be explained. I will try turning off the load all sequences and see what happens. I'm currently playing with a 3 sec delay between songs. I'll see how the playback is affected. This may be a good opportunity to get Sandra a new laptop use her old one ( i would at least get dual core, 4GB and and SSD drive) for a show computer and retire the old Dell 1300 to the workshop. Bob
×
×
  • Create New...