Tue Jun 25, 2019 2:57 pm
So the cable test routine is built into the core, we do not write it nor have the ability to modify it.
We simply request it to run and the core returns values we display.
Normally the cable test length is pretty accurate but external things can affect it such as:
A damaged Ethernet Transformer. I have seen Transformers that were carrying AC ground current all the time and get hot but do not fry and it changes the attenuation on the magnetic coupling. Also would introduce errors and shorten the cable length that achieves 1G connections.
A damaged ESD protection DIODE - CAN HAPPEN BUT NOT COMMON
Use of Ethernet Surge Protectors - varied results depending on make
Bad or damaged (kinked) cable - attenuation (but normally shows differnt lengths per pair)
RF Noise on cable
If you suspect a port is damaged test the same cable on multiple ports and compare answers.
Also try a longer cable, short cables are inaccurate.
Try the test multiple times, the way it works a bad answer can occur.
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
