You are here

LQ/NLQ mismatch on DtD?

8 posts / 0 new
Last post
KM6SLF
KM6SLF's picture
LQ/NLQ mismatch on DtD?

What could be causing this?

My M5 and M2 Rockets are connected to the same Ubiquiti Nanoswitch. I can see the M2 from the M5, but with 100/0 LQ/NLQ, but the M5 cannot be seen from the M2.

K6CCC
K6CCC's picture
One way communication.

One way communication.  Suspect either a cable problem or an issue with the switch.  Try different cables (tested good if you have a cable tester), and / or bypass the switch.
 

KM6SLF
KM6SLF's picture
The Rockets only have 1 RJ45

The Rockets only have 1 RJ45 port, so I can't connect them any more directly than they are... If there is a problem with a cable, I would think the nodes wouldn't power up, since they're powered by PoE, but I guess it's possible. They're wired up as follows:

PoE injector connected to a Mikrotik mUPS PoE-In port (w/ battery backup)
mUPS PoE-Out connected to Ubiquiti Nanoswitch PoE-In
Rocket M2 and Rocket M5 connected to PoE-Out ports on the Nanoswitch. 

There is one empty port on the Nanoswitch, I can try swapping some cables and switching one of the Rockets to the empty port. I'll give it a shot and will report back on the results. 

k1ky
k1ky's picture
Rocket DTD

You either have a cable issue or it's possible that the ethernet driver chip onboard the Rocket has a bad channel either TX or RX. 

K6CCC
K6CCC's picture
Remember that with passive

Remember that with passive PoE, data and power are on different wires, so a bad wire could easily affect data without affecting power.

If you have a cable tester, test each cable.
 

KM6SLF
KM6SLF's picture
I replaced the cables and am

I replaced the cables and am having the same result. I don't have a cable tester, so I couldn't test the cables, but I have no reason to expect there's anything wrong with them aside from this issue, which is occurring with both sets of cables. In case it was an issue with the Nanoswitch, I ordered a replacement and tested it - same result. Could there be an issue in the settings that is basically disabling the DtD link on the Rocket M2? It could also be that the Rocket M2 is damanged, but I don't have another one handy to test.

kc8ufv
kc8ufv's picture
It could be the switch, but

It could be the switch, but that's an easy test - swap ports on the switch between the two nodes, and see if the problem moves. If it does, you've got a bad port on the switch. If it doesn't, it's in one of the nodes. At that point, there's a couple possible tests... Could plug in a computer and see which node assigns addresses, and it is able to talk to directly. If DtD were disabled on either device, it shouldn't see anything via DtD link, nor should anything see it that way.

Could also plug in a 3rd node, if you can borrow one from somewhere, and see which ones can see each other via DtD link. 

KM6SLF
KM6SLF's picture
The Rocket M2 was damaged. It

The Rocket M2 was damaged. It still worked from an RF perspective, but something was wrong that prevented it from achieving a DtD connection. Both the M2 and M5 had apparently suffered mechanical damage that prevented the ethernet cord from "locking" into place, too. I expect this was the result of the cords being physically yanked out when part of the assembly blew off my roof, along with a solar panel, during some heavy wind a few weeks ago. 

I replaced the M5 with one I had lying around, and the M2 with a replacement I just picked up from Don, and now they have a perfect DtD connection through the Nanoswitch. There was no bug or software issue, apparently, all mechanical. Thanks for help! 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer