Howdy,
I see strange interesting behavior with POE on the RB960PGS:
POE is on auto, works fine for devices like hAP lite, Ubiquity nanobeam ( M5 devices)
Connecting a Ubiquity Rocket prism or Powerbeam AC Gen2 - the board stays on “waiting for load”
Using a hex POE, same model RB960PGS - however a revision r2 the board behave like expected and powers up any of the above mentioned devices.
I also encountered strange things. I wanted to see the RouterOS log as current-too-low or voltage-too-low but it looks like it’s just on paper.
I tried to fix the problem like this https://youtu.be/sO7dn_usApo - but the problem didn’t go away.
P.S. Compliment MT, because the router is not at fault even after the flight.
all the devices use the same voltage. I can “forced on” the output then it works.
However, it is not clear to me me, if I force the output, will the POE priority still work in case of a overload ?
Connecting a Ubiquity Rocket prism or Powerbeam AC Gen2 - the board stays on “waiting for load”
Probably the “internal resistance” is unknow to mikrotik PoE chip, and on r2 have added that. Ubiquiti is not maded from MikroTik
It might be that you are providing 24v to the input. And as the device has no dc/dc conversion it will only provide its own line voltage to the POE port. If the connected devices require the POE/POE+ voltage of 48-57 volts to turn on, it will remain off. However, if you set the power to always on, it will revert to passive POE, and if your device supports that, it will turn on.
Mikrotik sells higher voltage PSU’s for exactly this purpose.