Sean Meighan
Welcome => Do You Need Help? Post it here => Topic started by: wftxlites on December 26, 2015, 04:32:54 PM
-
I am trying to do some testing with the latest XL version on Win7 and have no output on my Lynx Ethernet Dongle, but do have output on my Lynx USB Dongle.
SETUP:
Univ 1 Multicast 1-512
Univ 2 Multicast 513-1024
Univ 3 Multicast 1025-1536
Univ 4 COM4 USB 1537-2048
I know this must be something simple.
-
Hi,
I don't know anything about this hardware , but which channels of your setup correspond to the Ethernet dongle that wont light up and how have u defined that in the setup screen ?
- have you tried the test output ?
-
Universe 1 to 3 channels 1 to 1536
I'm wondering if XL can output only DMX and not Pixelnet. Now that I've thought about it.
-
I wouldn't think we would have PixelNet in the selection box if we didn't support it.
-
We need more info. What are you connecting to? And how are you connecting? I am running my whole show from the etherdongle. which is then connected to an active hub. I'm using all 4 pixelnet universes. Post a screenshot of your setup screen.
Gerry the etherdongle is an e1.31 device that outputs 16k channels, usually pixelnet (multicast only) or with a firmware change DMX.
-
Here is the Setup. The firmware is Pixelnet and connected to Active DLA Hub.
-
So you don't have any Pixelnet outputs defined. When you say "Add USB" and change the drop-down to Pixelnet then that's what you will see listed for the output type.
-
I see that in USB, but what about Ethernet? Or I am I missing something?? The pixelnet firmware is on the Ehternet dongle and not USB. The USB is DMX Firmware and works fine.
Thanks,
Greg
-
Sorry I don't know enough about that hardware or how Pixelnet works.
-
What you are connecting too and that the Etherdongle is flashed with Pixelnet firmware are needed.
-
Your setup looks fine. If you are pulling DMX from the DMX Out jack on the active hub then you need to delete the dmx row. DMX from the active hub will come in the 512 address block that you select with the jumpers. I dedicated the first 512 to dmx and I suspect most folks with active hub do that also. I do not connect any pixelnet stuff to channels 1-512. Just understand that whatever block you select for DMX, the channels are output to both pixelnet and dmx. ie. 16 mini trees (one color) set to channels 1-16 will also have pixelnet channels 1-16 be the same exact effect. All the DMX out does is copy and convert the designated channel block to dmx protocol.
-
Right I have an additonal DMX universe setup and that is why I added the extra USB dongle.
So, for next year I want to use XL to redesign my show. To get the full understanding of how XL works I am building a test seq in XL and trying to test all the outputs directly from XL while my display is up. I have the output turned on and have also tried the test tab in XL. I am getting no output to my Lynx ethernet dongle. I also have a USB connected to my computer and setup in XL. The USB dongle is outputing DMX just fine. However, the ethernet dongle which is connected on my network and then to a DLA Active HUB that outputs the pixelnet to my megatree is not outputing to the mega tree pixels. I am running my current show with no problem using an Rasberry Pi FPP with fseq file that were converted from LSP by an earlier Beta version of XL. So, I know that on the FPP the ethernet output is setup the same way for multicast as XL to the ethernet dongle. In my opinion both XL and FPP is setup the same way. So, I can't understand why no pixelnet output to the ethenet dongle from XL.
I am considering taking the test seg and making the fseq file and placing it on the FPP and see if that might work. At least it may tell me something.
Hope this all makes sense.
-
I have loaded the XL test seq file into the FPP and the outputs are working to both the ethernet and USB dongles.
Playing the test seq directly from XL doe not work on the ethernet dongle. I doubt this is by design, so I am wondering if this is a bug.
Could someone test this on the newest version of XL 4.3.0.
-
So from Jim's description the etherdongle is a E1.31 device so I assume you are sending it E1.31 data and it converts it to Pixelnet? If so then we know E1.31 data outputs is working. There is no way xLights would even know you have a device converting it to Pixelnet so there can't be a bug in the E1.31 output.
-
So, how does the FPP know that it is pixelnet? Likewise, XL does not have any "pixelnet data" settings either. I am not aware of any FPP setting for E1.31 data related to pixelnet output. The only settings in FPP for pixelnet is related to using an FPD! When the fseq file is played on the Pi player it works fine, but not straight out of XL on the PC. You can see why I am confused about why XL E1.31 output is not driving the ethernet the same way as the FPP natively from XL on a PC. The data stream has to be in a particular format for the DLA Active Hub to translate it.
Still confused......... and at this point only way to test the sequence is to put the fseq file on the FPP and play it. I would think either way would work. But, apparently not.
I'm thinking that the XL E1.31 output is only being interpreted by the E1.31 device into whatever protocol the devices firmware supports.
-
The etherdongle is an E1.31 device that converts to pixelnet. Everything you are explaining sounds correct as xLights doesn't know anything about Pixelnet and doesn't need to. That's why we can use the etherdongle with programs like LOR.
I think you need to post and image of you Channel Outputs from the Pi. If it works in the Pi it should work in xLights. In fact I always test stuff in xLights first and then move on to the Pi.
-
Pixelnet is a protocal that rj created over at dla. Its pertty simple 1 Pixelnet universe is 8 dmx universes. So if you set it up in xlights you just define e131 as 32 universes for etherdongle in set up tab and its that simple. The fpp takes e131 and outputs it to equipment that accepts e131. Or there is the option to use the falcoln fpd with the fpp which then takes 64 dmx universes and converts them up to 12 pixelnet universes to output to devices that can accept pixelnet as a protocal for which they were designed for in their firmware. This is what I understand as to be true
Set up you etd as defined above , pick the universe on the hub you want to use put the proper start address in your models for the universe you are using and make sure e 131 is enabled on setup page ( the dmx universes will say yes or no, you want yes) click on output to lights and play. Hope some of this helps
Joe
-
Here is the FPP Outputs. They are identical to XL Setup of outputs. I will setup all 32 universes if you think that is the issue.
Thanks for the detailed explanations.
-
2 questions,
Are you trying to go through the fpp with the etd for lights
What are you using off of the hub to your tree
-
I am using both pixels and DMX devices off the Hub. The problem is trying to test using Xlights. The fpp output works fine when I import the Xlights file to the FPP.
-
I'm thinking that the XL E1.31 output is only being interpreted by the E1.31 device into whatever protocol the devices firmware supports.
You are correct, the ETD does the conversion to pixelnet or with different firmware it converts it to DMX. I use my spare etd with xl test all the time, but I have never tried to run a sequence from xl. I have been using the Pi and FPP for 3 years so have not used xl in production for a while. I will have to try to run a sequence during the day when the show is not running. Maybe it has something to do with fseq file format now that the sequencer automatically makes that the file of choice. Wonder what would happen if you used convert to go from fseq to xseq. Remember that the current devs have not touched the base xl player and the player was designed for xseq.
-
How is your computer connected to the network? Wired or wireless?
-
When you say coming off the hub to pixels, what are you connecting the pixels to after the hub? . I would then try the etd by it self without the fpp in xlights. I have been doing that the last couple of weeks working out issues. I just start a new squence and bring in the model view I am testing , throw an element on it and hit output to lights. If you want to go through the fpp as I have been doing the last couple of days then put it in bridge mode and enable e131 output, then go into xlights and try it the way its stated above. Alot of most issues are improper channel assignments or setup. Thats why I asked what you are connecting the pixels to after the hub
Joe
-
Hub = Pixelnet 16 port Active Hub
Pixels = Smart String Controllers
DMX Devices = DMX Light Controllers
The issue is with Xlights output to ETD. When I test my sequence from Xlights there is no blinky.
Here are my tests:
Test 1. Xlights with test sequence on Win7 PC ---> Network to ----> ETD ----> Smart String Active Hub ------> Smart String Controllers
Does not work.
Test 2. Xlights on Win7 PC ---> USB Dongle ---DMX out---> Light Controller
Works
Test 3. Xlights generated .fseq file from same test sequence ----> transfered to FPP ---> Network to -----> ETD ------> Smart String Hub ------> Smart string controllers.
Works
It is the Xlights output from the PC that does not work. My other sequencing program LSP works on the PC just fine and generates output to ETD, Hub, and controllers, so it is Xlights that has the problem. I just need to figure out why. From what everyone here and on other forums are saying this should work.
Still baffled.
-
How is your computer connected to the network? Wired or wireless?
How is the PC connected to the network? Wired or wireless?
-
Are you running the sequence play from the layout tab or are you using the scheduler to play. I'm beginning to think there may be an issue with the scheduler and fseq files vs xseq files.
-
How is your computer connected to the network? Wired or wireless?
How is the PC connected to the network? Wired or wireless?
ETD is wired.
Are you running the sequence play from the layout tab or are you using the scheduler to play. I'm beginning to think there may be an issue with the scheduler and fseq files vs xseq files.
I have tried the test tab and play from sequencer tab. I am turning on the light bulb too.........sigh.......
Now I have uninstalled on my PC and went backwards to V4.0.35 Beta and started from scratch. Added ETD with all 32 universes, built an RGB model of a tree in universe 2 starting at chan 513 where they are currently addressed on my mega tree (outside in the snow), added the model, created an animation seq this time, added timing marks, added effects, saved and rendered. Turned on the output light blub and pressed play. AND no blinky.....sigh again............... I'm watching the tree on my cameras, so at least I don't have to go outside and occasionally I will go look out the front door........even started my show from FPP for a sanity check. (Which works by the way)
I know I am close to the solution when I am ready to give up! That would be close to now.
-
ETD is wired. Is the PC also wired?
-
Yes, PC is wired too.
Are you running the sequence play from the layout tab or are you using the scheduler to play. I'm beginning to think there may be an issue with the scheduler and fseq files vs xseq files.
Now, I have converted the fseq file to xseq and set it in the scheduler and No blinky. It was a good thought from jnealand.
-
I don't know you tell me how you setup your FPP to get it to work? Did you use an E1.31 output or the Falcon Pixelnet/DMX page?
-
Yes, E1.31 on FPP Multicast it works. I don't have an FPD.
-
So then FPP doesn't know it's Pixelnet data either. Your dongle is doing the conversion.
-
Yes, that is my conclusion as well. It makes sense that the ethernet data side is just a stream and then the dongle does the interpretation.
Maybe no one has tried this before and they just use XL to create the file for other players.
It seems like I saw a post a while back that said the XL output didn't work, but that was long ago. However, the USB does work just fine. Maybe it is just the E131. I have not seen anyone reply to this thread that claims they have made it work directly from XL.
The jury is out.......for me at least. Check YES or NO!
-
Attached is a photo of a test I did a few days ago with a PC, ED and Falcon F8 using the test tab. I'm starting to think that the firewall on your PC is blocking the traffic.
-
Humm...no firewall active on PC.
FYI..LSP output works fine to ETD, Hub, and SSC's.
-
I have been using the test funtion in xlights to set the proper color order for the different strings I am using, with the etd to f8 and 16s ssc, and uscs. When you are making your tree model are you setting up each string for each ssc with the proper start address for each. That I know of you cannot set the start address for only 1 ssc and have xlights know that you are using ( lets say 8 sscs) individual controllers. Each ssc is its own controller with its own start address. I can tell you from experience if your model is not set up correctly with the controllers it will not work. You have me stumped on how you can get output out of the fpp to etd to hub to sscs by converting xlights but you cannot get xlights to play from computer. I used lsp for years and xlight is 10 times simpler to set up for output..
Try this: put you fpp in bridge, make sure you have the e131 output box ticked, in xlights make sure you have each universe activated as yes take your model and put it in a new sequence, you dont need timing marks, throw an effect on your model, I would use something more defining like spiral or bars, click on the effect so it shows in the model preview window an hit output to lights.If you controllers are set up correctly you should have light. This would be the exact same info you would be converting to the fpp that you say works using fpp to etd ect. You dont even have to hit render or save. I just hooked up my etd istead of my fpd and did this just a few minutes ago, and have been doing it for several days so I can adjust my effects visually before I put them into a sequence.
Joe
-
What? You think none of us have used xLights to output E1.31? Sorry but you are barking up the wrong tree.
-
What? You think none of us have used xLights to output E1.31? Sorry but you are barking up the wrong tree.
LOL I got a response that I wanted to hear!
I have been using the test funtion in xlights to set the proper color order for the different strings I am using, with the etd to f8 and 16s ssc, and uscs. When you are making your tree model are you setting up each string for each ssc with the proper start address for each. That I know of you cannot set the start address for only 1 ssc and have xlights know that you are using ( lets say 8 sscs) individual controllers. Each ssc is its own controller with its own start address. I can tell you from experience if your model is not set up correctly with the controllers it will not work. You have me stumped on how you can get output out of the fpp to etd to hub to sscs by converting xlights but you cannot get xlights to play from computer. I used lsp for years and xlight is 10 times simpler to set up for output..
Try this: put you fpp in bridge, make sure you have the e131 output box ticked, in xlights make sure you have each universe activated as yes take your model and put it in a new sequence, you dont need timing marks, throw an effect on your model, I would use something more defining like spiral or bars, click on the effect so it shows in the model preview window an hit output to lights.If you controllers are set up correctly you should have light. This would be the exact same info you would be converting to the fpp that you say works using fpp to etd ect. You dont even have to hit render or save. I just hooked up my etd istead of my fpd and did this just a few minutes ago, and have been doing it for several days so I can adjust my effects visually before I put them into a sequence.
Joe
Ok, this is interesting. In bridge mode on the FPP it shows the bytes being transmitted. With Xlights in output mode there are no bytes being transfered. Doing the same kind of test with LSP the Bytes start to increment. Now I know it is not exactly the same test because I think I would be sendinging double the data. That is LSP is send to ETD and so would be the FPP sending to the ETD. It confirms that XL is not sending as I suspected. I think no matter what the controller address as long as they are in the range defined in the setup on XL that there would be output. I did however make sure the SSC models addresses were correct and tried everything recommended.
Now for the good news bad news. I did the same test on an XP PC and it worked. So now my task is to figure out what has happened on my Win7 PC. Probably some damn Microsoft update crap. >:(
I hope I didn't offend anyone in the progress and really appreciate your time and help to isolate the issue.
:)
Greg
-
Ok, this is interesting. In bridge mode on the FPP it shows the bytes being transmitted. With Xlights in output mode there are no bytes being transfered. Doing the same kind of test with LSP the Bytes start to increment. Now I know it is not exactly the same test because I think I would be sendinging double the data. That is LSP is send to ETD and so would be the FPP sending to the ETD. It confirms that XL is not sending as I suspected. I think no matter what the controller address as long as they are in the range defined in the setup on XL that there would be output. I did however make sure the SSC models addresses were correct and tried everything recommended.
Now for the good news bad news. I did the same test on an XP PC and it worked. So now my task is to figure out what has happened on my Win7 PC. Probably some damn Microsoft update crap. >:(
I hope I didn't offend anyone in the progress and really appreciate your time and help to isolate the issue.
:)
Greg
[/quote]
I did not know xlights 4.0 would work on win Xp.
Well if you can get stuff to work together in lsp then it definatly points to a set up issue between the fpp and xlights. You are missing something in your setup. The point that you made about the sscs working if channels are off may be true to a point but if your setup is not the same in the fpp and xlights it will cause output issues. I personally could not get some of my controllers to work if I was off in the defined channels that I set up in the controller software with the fpp and xlights. I hope you can figure it out as xlights is light years ahead of lsp and its much easier to use with awsome effects ( coming from a previous lsp user)
-
I used Wireshark and the FPP Bridge Mode to troubleshoot this. I have Virtualbox on my Win7 PC, so I needed to disable the interface for it.
Moral to this story is be careful what software you place on your development or show PC.
Thanks Again,
Greg