Mega Tree Help
 
Notifications
Clear all

Mega Tree Help

15 Posts
7 Users
0 Reactions
6,487 Views
Posts: 373
(@blantrip)
Reputable Member
Joined: 16 years ago

Since you are only using Universes 20 thru 25 I would suggest deleting the other universes and selecting multicast instead of unicameral.

This probably won’t fix your problem but just clean up your configuration.

Suggestions:

1) on the controller (green connectors) move the non-working string to a different port and move a working string to the port that the non-working strand was connected to. Does the non-working string work? Does the working string work?

2) check the wiring connections at the green connector. I suggest loosening the screws pulling the wires out and then reconnect them. Make sure there are no stray wire strands from the data, positive and negative wires sticking out and touching the wires next to them.

3) check the LED string to make sure there isn’t a difference in how they are connected to their plug. You can usually see on the LED which wire is connected to data, positive and negative. I’ve also used a pin/needle to puncture the wire and then using an ohm meter test between the pin and the plug connections. Remote possibility that tHe non-working strings were built incorrectly. I have had this before.

Good luck.


Reply
Posts: 3735
(@algerdes)
Famed Member
Joined: 15 years ago

techs21 -
Each string/strip has a timing requirement to get the data to each pixel. A while back the timing rate changed on most newer strings, hence the request to check the timing set on your controller. I'm not near a controller at this time so I can't get the numbers from the old setting to the new. If I remember correctly, they actually slowed down. 🙁

As far as all the suggestions for swapping a known good string and your suspect string, this is basic troubleshooting for many. Simply move the connection of a good string onto the port that is giving you problems. If the good string is still good in the suspect port, then the string originally on that port becomes suspect and probably needs attention. If the good string starts acting like the original, then you know it is in the controller or what feeds it.


Reply
Posts: 64
Topic starter
(@techs21)
Trusted Member
Joined: 16 years ago

Ok if I take the non working strand and move that to a working port the strand works fine, If I take the working stand and move it to the non working port that stand doesn't work


Reply
gassy
Posts: 548
(@gassy)
Honorable Member
Joined: 17 years ago
techs21 wrote:Ok if I take the non working strand and move that to a working port the strand works fine, If I take the working stand and move it to the non working port that stand doesn't work

Is that when testing from the controller (Test Mode) or running a sequence?


Reply
Posts: 8517
(@angus40)
Illustrious Member
Joined: 15 years ago

Was this a kit or pre assembled controller . Could you give the specifics as to which port/cluster #'s that are not working .

It could be that a supporting Ic is not seated correctly . The ic could be bad or soldered poorly . The port sock ( namely the data pins) could be soldered poorly also .

If you can visually inspect all the above and re-flow some solder points you may solve the issue .


Reply
Page 3 / 3
Share: