Pixel Controller Ne...
 
Notifications
Clear all

Pixel Controller Networking Issue

10 Posts
6 Users
0 Reactions
2,692 Views
StickyWicket
Posts: 548
(@stickywicket)
Honorable Member
Joined: 14 years ago

There is an app called Fing that I use on my phone to scan the network for devices. You might try that at well.


Reply
dpitts
Posts: 1020
(@dpitts)
Noble Member
Joined: 16 years ago

If you still need help you can call me. Number on PixelController.com.


Reply
Posts: 1592
(@ruppro)
Noble Member
Joined: 11 years ago

If you can communicate w/ the controller when connected directly to the router, then there is nothing wrong w/ the controller. You need to be looking at the network run (why StickyWicket ask if you could connect something else at the end of the run) 20' is short for a network run, ethernet is good for 100 M or 328'. While mixing 568A and 568B is technically OK, I have seen issues when it is done, some device just do not like it. I would test the line to make sure you have continuity end to end as my 1st step, I assume that patch cable to the wall is the same one you use to connect the controller to the router, so that should be good (if not test it), so you will need to test the run up the wall into the attic and then the run from the attic to where the controller will reside. If they all test fine, try replacing the 586B segment w/ a 586A, if you can't find one I can make you one to the length you need.

whitesoup12 wrote:I have an AlphaPix 4 controller that is connected to my home network. The controller has a static IP address of 192.168.0.50. When the controller is on it shows it's connected to the network, but I can't connect to it from my PC. From my router, I have probably 20 some feet of Cat 5 before it reaches my controller. I have a 568A patch cable from the router to the wall, 568A Cat 5 going up through the wall into the attic, and a 568B going down the wall to the controller (I ran off an existing line). Not sure what's going on, but I do have a long run, which I don't think would matter, and a mix in Cat 5 protocol, which I also don't think should matter as long as the cable begins and ends on the same configuration (non crossover cable). Any ideas what it could be? I'm able to connect if I attach it directly to my router.

Sent from my SAMSUNG-SM-G930A using Tapatalk


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

The only difference between 568A and 568B is the color coding. (Perhaps the number of twists in each pair since each pair is a different twist rate - but that has always been insignificant until you start pushing the limits. We don't do that here.) As long as you haven't wired 568A on one end, and 568B on the other - you are good.


Reply
Posts: 40
Topic starter
(@whitesoup12)
Trusted Member
Joined: 11 years ago

Thanks everyone for your replies! I haven't had the chance to look at it yet, but the first thing I'm going to check is where my line connects in the attic. On my existing line I put a female RJ45 plug, but it's one of those that have the plastic piece you just press down over over the wires to connect the plug. Something about it didn't feel right when I was putting it on and it felt like a poor connection. So I'm going to just get an RJ45 coupler and connect it that way. I'll let you all know how it turns out.


Reply
Page 2 / 2
Share: