First time terminating ethernet cable

vette-kid

Young grasshopper
Dec 12, 2017
44
7
What did I do wrong? I'm using cat 6 solid copper cmr riser rated cable. I copied the sequence from some premade patch cables that are known to work. With my cable, the camera powers on and the nvr trios to detect it and even sees it in poe management, but it will not fully detect it, no image. Camera works with premade cable, so it must be my cable. But it obviously works to some degree as the camera is getting power. Where do I look?

Sent from my SM-G900T using Tapatalk
 
What did I do wrong? I'm using cat 6 solid copper cmr riser rated cable. I copied the sequence from some premade patch cables that are known to work. With my cable, the camera powers on and the nvr trios to detect it and even sees it in poe management, but it will not fully detect it, no image. Camera works with premade cable, so it must be my cable. But it obviously works to some degree as the camera is getting power. Where do I look?

Sent from my SM-G900T using Tapatalk
Use the 568B standard.
 
As an Amazon Associate IPCamTalk earns from qualifying purchases.
OK, you guys were right (you already knew that! ). Why does the camera care what color the jacket is? As long as both ends are the same I would think it would not matter. Are the different colors somehow different beyond color?

Sent from my SM-G900T using Tapatalk
 
Transmit and receive data, and the polarity of the signal, are on specific pairs and colors within those pairs. The same is true of PoE power. It doesn't matter if it's a camera, phone or simple ethernet connection.
 
OK, you guys were right (you already knew that! ). Why does the camera care what color the jacket is? As long as both ends are the same I would think it would not matter. Are the different colors somehow different beyond color?

Sent from my SM-G900T using Tapatalk
They are twisted in a specific order to prevent cross talk and interference
 
  • Like
Reactions: awsum140
The reality is that the colors don't really matter other than to conform to spec and keep it simple. What does matter is the "pairing", pins 1&2 being a pair, pins 3&6 being a pair, pins 4&5 being a pair and pins 7&8 being a pair. Of course, the same pair has to be on the same pins on both ends for it to work. If you interchange wires from pairs, say all the white/color on pins 1-4 and color/white on pins 5-8, then crosstalk will go sky high and dropped packets will kill things rather quickly.
 
And the difference between getting a good connection and no connection can be hard to see. That's why a simple tester is such a handy thing to have when making cables.
 
OK, so essentially what I was doing is introducing so much cross talk that I want able to get data through it? But the shorter patch cable was short enough as to not be significant (5ft), but at 35ft it's significant?

Sent from my SM-G900T using Tapatalk
 
OK, so essentially what I was doing is introducing so much cross talk that I want able to get data through it? But the shorter patch cable was short enough as to not be significant (5ft), but at 35ft it's significant?

Sent from my SM-G900T using Tapatalk
Ethernet is sent as a differential signals over twisted pairs. Meaning there's a positive and negative version of the same thing sent over each wire of a twisted pair. The twists purpose is to add capacitance to the cable. It actually be a bit more than crosstalk when you mess this up.

It's possible that the twisted wires in your other cable don't follow the normal color scheme.
 
Did you test the cables with a tester? If they "rang out" there could have been a wiring error depending on the tester. Some test as single connections 1 to 1, 2 to 2, ect, others test the pairing, orange, green, etc. Worst case, cut the ends off and start over again. It does take some practice, and patience, to be able to do it well and quickly.
 
Nice color code chart at post #6 ==>> here.
 
  • Like
Reactions: fenderman