We use the LinkPower battery system to allow installers to connect to the radios in the field. Those devices put out 24v which has always worked fine for the Force 180, 190, 200 radios. When we plug in a Force 300, it won't power. I see the spec sheet calls for 30v on the 300 series where the older radios had a small range of voltages.
If 30 volts is a hard and fast rule, how to we power one of these from a Netonix or any other POE swtich out there??
Probably will have to make a reversed cable. We had to for our installers to allow Tiks with POE output to power the 300's. At least some of the 300's. Newer ones will run off Tik/Netonix POE. Cambium made this confusing, and I'm not sure why.
Ugh! That is it. I thought I read this was only an issue on the first few devices manufactured or is this a thing on all ePMP 300 series radios?
We still get them needing a cross-over cable. And it does not matter who we buy from. The last batch we just got need a cross-over cable. Ones before that was a mix.
Hi. We power Force300's with a 24v test batter pack, no problem. What i would suspect maybe that you're running into is the build version of the Force300 you have maybe? If you have an old stock Force300, this might be the issue.
The situation is that the first production runs of Force300's only supported "Cambium Power" with pins 4&5 being DC- and with pins 7&8 being DC+, which is sometimes caleld "Reverse Polarity" The Cambium supplied power supplies work with those Force300's, but if you supply ''Standard" (4/5 + 7/8 -) those old stock Force300 don't work with that polarity.
Around spring of 2018, they made a change to the design of the Force300's to be ''polairy agnostic'' so that they work with both polarities of Passive POE.
.
Here is the how you can tell.
- Check the MSN / Servia Number of the Force3000. If the 3rd letter is U and 4th letter is E or later, then it's made in the Spring of 2018 or later, and it will work wth both POE polarities. So basically, all Force300's with the 3rd & 4th letters of UE of later, are both poe polarieies.
If it's before 'UE', then you have old stock from the original build, and it'll need to reverse the POE lines. We use these POE Crossover cables (about $5) but it's basically just swaping the Blue's and the Brown's on the ethernet is all they do.
http://www.tycononline.com/POE-Crossover-Cable-Shielded-Cambium_p_162.html
@CWB wrote:We still get them needing a cross-over cable. And it does not matter who we buy from. The last batch we just got need a cross-over cable. Ones before that was a mix.
Only the first couple of batches of Force 300's that we got needed a PoE cross-over cable, and only the 300-25. I think we've used at least a few dozen of them now, and I haven't come across anymore with issue... it could be that there are just still some early radios that haven't gotten cleared out of the supply chain yet.
Ugh, lame. Well, knowing there are two batches of radios out there, it made us dig into another issue we see: Lots of wireless disconnects and high packet latency. It seems that the older 300-25's are the radios that are responsible for frequent brief disconnects (without a reboot) from the AP and periods of high latency (30 - 50ms). The newer 300-25's do not experience this. I have no idea if this is just a coincidence or not but we have been chasing weird issues on all 4 of our 3000 towers since installing them. We have RMA'd two 300-25s for being DOA. Another was RMA'd for having the Ethernet pins in the radio being too recessed so it would not make an Ethernet connection (but it would power). Another is sitting on my desk for trouble shooting. It would stop passing traffic to the customer router until a reboot but other than that, seemed to be working normally.
All of our radios are runing 4.4.1.
I have a dental pick set for doing circuit rework. I find these help with the port pins that arrive not fully seated properly. look inside the connector and see if the metal contact is fully seated in the plastic holder, if not, just put the pick in behind the pin and press it into position. I used to get a fair amount of this from curious clients that seen the rj11 connector on our old fsk equipment, had to start telling new clients that it was not a phone port and they would be liable for any damages, including the service call if they plugged anything into the port.
