DiyLightAnimation
Hardware => Lynx EtherDongle => Topic started by: onesmoothhead on January 30, 2012,
-
Hello everyone. I was not sure where to place these comments, but after much testing i believe it should be in Ethernet area. I will refer to the pictures attached.
First, the green light at node 207 is always on and the node works fine in all the channels. It has been on since the day I received them from Ray. I call it my power light. It functions normal and I can tell I have power out of the hub.
Node 341, pictured with green and blue always on very dim, does not respond to channels commands very bottom of picture. Node 171 shown in the picture red dim always on, responds to blue commands, but does not work on red or green channel commands. Node 170 shown in the picture with blue dim always on, does not control, green and red respond to commands. I have set to separate ssc to the same start channel and both demonstrate the same node issues. All of this happens when I set Vixen to EtherNet settings in the manager.
The second picture with only the ever shinning green light is the same board, but controlled with Pixelnet through the USB dongle. I have zero node issues and everything works as it should.
I am using the same hub, ssc and power supply. The only change was in vixen under the manager. Any ideas?
-
Just so you know, it's not just you, I have just recently noticed the same thing.
-
Thanks, I can even pin down to other nodes or channels in the 2000 range. I am sure it has something to do with the eD. I can switch the ssc and get the same response on different rigid strips, but same nodes are still effected when using the eD. I am not sure if it is my router. I am going to try direct tomorrow with a crossover direct from my computer and see what that outcome will be.
-
I think some of those may be boundary pixels.
170 x 3 = 510
E1.31 has 512 channel blocks.
Channels 511, 512, & 1 from the next block should make the boundary pixel.
I noticed this with both LSP and xlights using the etherdongle, but it works properly with the USB dongle.
Not sure if it is an etherdongle issue or a LSP/xlights issue.
RM
-
I am only using Vixen channel test and a short sequence. I will keep testing all aspects I can think of and any suggestions from our blinky friends. Thank you for your help also. This is what is great about this group.
-
I had a similar issue with six (6) lights on my ribbon tree (12 flexible ribbons). I have not had the chance to troubleshoot the board or isolate the exact nodes. The lights were faintly lit with the eD, but worked fine with two USB dongles. I used LOR3 converted to xLights sequences. Will try to post picture.
tlh/Terry
Sent from my iPhone using Tapatalk
-
What is the start address of the first SSC?
E1.31 and Pixelnet sends out the data in different size blocks of data
Rick R.
-
In this set up the start address is 1. I have moved the start address to 513 and 2000 and have the same issues with different nodes and all related to the eD. I think you are on to something Rick.
Sent from my SGH-T989 using Tapatalk
-
If you change the start channel from 513 to 516, does the problem move by 1 node?
-
or even to 514, does the problem change color?
-
I do not have an answer for either the color or node change. I will test tonight and see if these change by a node or channel.
-
We saw the same issue in the beta testing but it was fixed. I and some of the beta guys are wondering if the firmware is not the one that included the fix.
Here is the hex firmware for the etherdongle (pixelnet) and the DLL for the etherdongle vixen plugin that got updated to fix these issues.
Try these and let me know we may need to update the wiki if it fixes it.
-
RJ,
Should the wiki be updated with these files?
Rick R.
-
I will do this tomorrow. I just ran out of time today. Thank you RJ and everyone for the help. I will post the results tomorrow night.
Sent from my SGH-T989 using Tapatalk
-
RJ,
Should the wiki be updated with these files?
Rick R.
If this is the issue Rick. I thought these were the ones you put up but if it turns out not then we should change them.
RJ
-
we are currently using EtherDongle_Pixelnet.hex, EtherDongle_DMX, Lynx EtherDongle.dll files
Rick R.
-
Using a file compare utility there is definitely a difference between the .hex and .dll files from what RJ posted and what's in the Wiki.
Denny
-
<pop..
-
RJ, and everyone helping with this issue. I know the fix has already posted on the site, but it is truley the fix. RJ, you may verywell make Albert Einstein look like the kid sitting in the corner with a cone on his head. You and this site are truley brilliant.
Thank you everyone and I am sorry I could not test earlier. I had been working for 29 hours non-stop and did not want my human error to effect the outcome.
Kevin
-
<fp. I must of give rick the wrong file. When you guys started posting I and the beta guys were like... We seen that but we fixed it?
RJ
-
<res.You are very humble. I am more than proud to help you with creating smiles on more people every year. I never new there could be that many smile in just one community.
Again, <res. and thank you.
-
.
-
Finally got around to reprogramming my etherdongles and I don't think EtherDongle2.hex is the right firmware either.
This firmware solves the boundary pixel problems, but it does not output the pixelnet smothly. With the first first etherdongle firmware, the motion on my sign was fluid, but with etherdongle2.hex, the motion is mostly jerky with stretches of smoth motion mixed in. Only difference is the firmware.
RM
-
RM I am agreeing with you. Can you post some video to Vimeo so we can see what it is your are talking about. When I have an S scrolling it really looks like a fluttering snake. I am out on travel for a week and can not get any video. It could be the refresh rate, but I am not sure.Kevin