Re: X32 Discussion
X Cups, that is what I am doing wrong.
http://www.newark.com/agilent-technologies/dso7104a-gsa/oscilloscope-1ghz-4-channel-4gsps/dp/69R7205
To your question. Yes, loads of field experience with Ethernet from Thin and thick wire days, dang I am old. And yes I know that AES50 is not normal Ethernet packets or devices. Most of what I have seen comes from a few installations where video, data, or audio streaming packet loss followed some electro magnetic interference from surrounding cable or devices. UTP cable used in Ethernet systems is 2 bal. pairs twisted just right and 2 more put to use as a 2nd ch. or PoE. The devices listening and driving the lines low impedance can overcome loads of common mode noise. Just like the audio world, low Z, bal, shielded good. In most of the newer protocols computing devices use today not only give great fault tolerance but if a collision or drop occurs a rebroadcast takes place. For an email you would hardly notice. In a video or audio stream that does not happen due to some of the older but more efficient protocols used that does not use up the time needed to verify the packet made it to the destination. That sound you hear is a click or pop if short, a drop if long, and in rare cases a digital zipper sound.
ESD on the shield causes this if the connection is not good. But I was just referring to the times when I've seen or heard that happen from other EMI sources near or running long distances right next to the network cables. I've seen cable movement, not at the ends, but in the middle cause drops if they were near mild magnetic fields, and where are there not any? Again most devices would retransmit the packet lost as a result, others would go into the bit bucket. On a TDR and spectra meter even a fiber when moved can alter the signal going thru. There is even a fence alarm system the uses that signal to tell you if a human is climbing a fence or it is just the wind blowing on it causing the motion. Yep a fiber optic cable.
It seems though I have not kept up with the latest chips driving this cable as it can take and cancel a much greater range of noise that I thought. And it looks like the shield has no reference to the console ground or the stage box grounding that could cause that old fashion ground loop noise that if happened could still overwhelm those chips with so much noise that drops would occur especially at much higher frequencies. Why do you think they limit the distance to 100 meters? Cable capacitance rounding over the leading edge and noise rejection.
Sorry if this flys in the face of those with other tests and experiences, all I can say is , seen it, found it, fixed it. Electrons are a wild bunch.
X Cups, that is what I am doing wrong.
http://www.newark.com/agilent-technologies/dso7104a-gsa/oscilloscope-1ghz-4-channel-4gsps/dp/69R7205
To your question. Yes, loads of field experience with Ethernet from Thin and thick wire days, dang I am old. And yes I know that AES50 is not normal Ethernet packets or devices. Most of what I have seen comes from a few installations where video, data, or audio streaming packet loss followed some electro magnetic interference from surrounding cable or devices. UTP cable used in Ethernet systems is 2 bal. pairs twisted just right and 2 more put to use as a 2nd ch. or PoE. The devices listening and driving the lines low impedance can overcome loads of common mode noise. Just like the audio world, low Z, bal, shielded good. In most of the newer protocols computing devices use today not only give great fault tolerance but if a collision or drop occurs a rebroadcast takes place. For an email you would hardly notice. In a video or audio stream that does not happen due to some of the older but more efficient protocols used that does not use up the time needed to verify the packet made it to the destination. That sound you hear is a click or pop if short, a drop if long, and in rare cases a digital zipper sound.
ESD on the shield causes this if the connection is not good. But I was just referring to the times when I've seen or heard that happen from other EMI sources near or running long distances right next to the network cables. I've seen cable movement, not at the ends, but in the middle cause drops if they were near mild magnetic fields, and where are there not any? Again most devices would retransmit the packet lost as a result, others would go into the bit bucket. On a TDR and spectra meter even a fiber when moved can alter the signal going thru. There is even a fence alarm system the uses that signal to tell you if a human is climbing a fence or it is just the wind blowing on it causing the motion. Yep a fiber optic cable.
It seems though I have not kept up with the latest chips driving this cable as it can take and cancel a much greater range of noise that I thought. And it looks like the shield has no reference to the console ground or the stage box grounding that could cause that old fashion ground loop noise that if happened could still overwhelm those chips with so much noise that drops would occur especially at much higher frequencies. Why do you think they limit the distance to 100 meters? Cable capacitance rounding over the leading edge and noise rejection.
Sorry if this flys in the face of those with other tests and experiences, all I can say is , seen it, found it, fixed it. Electrons are a wild bunch.
Last edited:
