Notifications
Clear all

6804 flicker

11 Posts
6 Users
0 Reactions
3,623 Views
Posts: 295
Topic starter
(@daytimer)
Reputable Member
Joined: 15 years ago
[#33080]

I have a brandy new 6804. Kit, checked and double checked for any solder issues.
When running any of the test patterns, I get random flickering and some other goofy random outputs. When I touch the shield of the network connector on the 6804, all my problems go away! It's not a pressure thing, as I can touch the shield of the connector anywhere and the problem goes away. As soon as I take my finger off, the problems are back.
What in the sam hill is going on here? Are the network connections of the 682 and 6804 interchangeable? I have a 682 I could pull the network module off and put on the 6804 and see what happens if they are compatible.


10 Replies
Posts: 230
(@trcons)
Reputable Member
Joined: 17 years ago

Well this is an easy one... Whatever you do don't take your finger off that shield .

In all seriousness have you tried different strings on the same port, and that strings on other ports? I have one string that does that on most but not all of my 682s works fine when it's being told to be red green or blue, but when it's supposed to be off it flickers random colors.


Reply
Posts: 352
(@pmscientist)
Reputable Member
Joined: 16 years ago

The shield on the network interface is grounded. By touching it, you're essentially connecting it to earth ground, albeit at low current and with some amount of capacitance and resistance in between. This could be of a whole range of things. Both the E682 and E6804 use the Wiz5200, you could swap modules between them and see if the issue goes away. Swapping strings is a good idea as well.

Since altering ground seems to help, you might try to get down to a single supply connected at just a single point to see if you can replicate the issue. Not sure if you're injecting power at multiple points and/or have multiple power supplies, but using a single power supply connection will simplify troubleshooting.


Reply
Posts: 295
Topic starter
(@daytimer)
Reputable Member
Joined: 15 years ago

I have tried the other 3 ports and other strings. I plugged the strings in to my 682 and it works fine. It all changes when the shield of the network port on the 6804 is touched.
I need at least one more controller (pixels are getting out of hand quick!), but I want to get this resolved first.


Reply
Posts: 295
Topic starter
(@daytimer)
Reputable Member
Joined: 15 years ago

I am injecting power at multiple points. I have tried with the ethernet module from the 682 and I still have the same problem on the 6804. I do not have the problem if I connect them to the 682.


Reply
wbottomley
Posts: 550
(@wbottomley)
Prominent Member
Joined: 18 years ago

Do you have all of your ground wires connected at the injection point?


Reply
Posts: 295
Topic starter
(@daytimer)
Reputable Member
Joined: 15 years ago

Yes. It doesn't do it when I plug the pixels into the 682.same power supply and wiring.


Reply
Posts: 295
Topic starter
(@daytimer)
Reputable Member
Joined: 15 years ago

Another thing I just found out, I don't have to touch the shield of the connector. It would change by touching anywhere on the data wire. This is beyond weird.
But, of course, now it's been running for an hour without a problem!


Reply
bcwhitehead
Posts: 119
(@bcwhitehead)
Estimable Member
Joined: 15 years ago

What firmware are you running.


Reply
Posts: 91
(@rednelb)
Estimable Member
Joined: 13 years ago

:: Attempt at your own risk ::

Before I built my e684, I was using an arduino to test my pixels. Unless I tied the power supply ground to the the arduino ground, they would act erratic. As soon as I connected the two, everything ran fine.

Since you say everything is fine on the e682, I would bust out your meter and check all your grounds. For giggles, place a jumper between the output ground and the power supply ground.

Also, the standard firmware that I had on the 682 would make my TM1803 pixel go crazy. Nothing to do with ground. Jim sent me an alternative firmware that corrected the issue right away!

Good luck!


Reply
Page 1 / 2
Share: