I’ve used the Detect Cable feature in other Mikrotik devices with success. I’m looking forward purchasing a couple of mAP Liite devices to have this capability in a portable device.
From the website the mAP Lite model name is RBmAPL-2nD and mAP is RBmAP2nD. But in the table, a “RBmAP2n” model appears and no product name that matches that appear in the website (neither current or archived). Is that a typo perhaps?
Can somebody confirm me if the mAP Lite works for Cable Detect? Or do I need to go for the mAP?
I have to presume that the mAP (and consequently the mAP lite) are loosely similar to the hAP lite, last time I tested this latter I came out with more than a few oddities (JFYI):
Yeah, that’s why it was strange for me. To be more precise, the RBmAP2n doesn’t exist, since the mAP is RBmAP2nD. This made me guess that RBmAP2n was referring to the lite (although the real name is RBmAPL-2nD), but obviously it was just my guess and not a confirmation.
Since you have a mAP Lite, can you try performing the cabe test using CLI? In my RB5009 I was able to measure cable lengths by having the other end unplugged. However, I don’t see the lengths in your screenshot (even in the “no link” screenshot) and I wonder if it’s a visualization problem with Winbox or somehow there’s also a distinction between devices that can/can not measure the distance (although it’s not mentioned in the docs).
@normis Can you guys fix the model typo in the documentation as well please?
I’m still mostly using Winbox 3 and the Android app, with that I had no problems showing the distance on my RB5009.
However, it’s in @holvoetn first set of screenshots where Winbox 4 was used, and the field for the cable distance was missing, hence why I asked for a test with the CLI (which shows the result completely fine, hence confirming it’s not a feature missing in the mAP, but rather a visualization bug in Winbox).
I also had a problem a few weeks ago with inconsistencies (in the registration view of WiFi clients, clients connected through ft-wpa2-eap appeared as ft-wpa2-psk in Winbox, but not in CLI. This has been already reported to Mikrotik support and it’s on track to be fixed), hence why I was extra careful before extracting any conclusion from the Winbox screenshots in this thread.