This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TPS23754: Using TPS23754 with un-reliable POE sources....

Part Number: TPS23754

We design a PD with the TPS23754PWPR, and the POE works great most of the time in most environments.  We have had some scenarios where the POE infrastructure is flakey, so we see the POE/POE+ flapping on and off, or where the infrastructure is over-subscribed.  Can anyone post some hints on how to make the ref material less sensitive to crappy deployment environments?  I thought about tightening up the tolerance by adjusting the DEN pull-up to a value other than the 24.9K in the reference material, but I think it will take more than that.  Also, simulating an un-reliable POE environment for testing seems hard to do in the lab.  Any suggestions on good ways to simulate this so we can try ideas?

Suggestions?

Thanks,

-Ted

  • Hi Ted,

    This is a very interesting topic and completely agree with you. I have found that in typical PoE applications in the past, these end equipments were deployed in very 'safe' envronments (like in a corporate building, strategically placed, away from foot traffic and in proper bundles). With the Internet of Things, PoE devices are being put into non-traditional environments like warehouses, conveyer belt apparatuses, or entertainment studios (lots of moving parts). There is a current trend for high reliability PoE PDs to have dual PoE inputs for PoE redundancy where if one PoE input is faulted, the other PoE input will provide the power/data. Is this the kind of reliability you're referring to?
  • Darwin,

    Actually, imagine something much worse. Possibly a POE nightmare scenario. Imagine an apartment building with 100's of units in it, where the landlord was providing an Ethernet jack, with free internet for all the tenants. So, dicey CAT5 wiring already all over the place, tons of other unknown devices on the network, and then the landlord decides to "upgrade" and install POE switches, so that every jack has POE. So, now you are sharing this network with 100's of unknown PD's hanging off of it. Now someone comes along and plugs a device that YOU designed into this mess of a network. How does it behave? At some point your device needs to be smart enough that if the infrastructure is super-duper crappy, and can't support your PD, it shouldn't power up at all. It shouldn't sit there and oscillate between powering up, browning out, and powering up again and again. Also, if you are supporting the ability to run off a separate DC jack, as an alternate power method, the unit shouldn't sit there and negotiate the POE, work for awhile, have the connection crap out, and then flap back to the DC supply over and over. The document TPS23753-Support Features.pdf seems to document lots of these connection ORing solutions, and ways to gang things up to be smart, but it really doesn't show the basics of how do I setup the device so it won't power up at all if the POE is good, but not good under load.

    Any thoughts on how to set-up a circuit so that the threshold for power-good is higher than normal, so it just doesn't come on at all? The only one I have been able to think of so far is to use a microcontroller to forcibly be able to disable the POE supply if on a DC jack using the stuff shown on page 13 of that document. Another thing is to just not use the onboard MOSFET switch to handle the switch over from DC jack to PD mode. One solution I have thought of here, is to put a separate DC jack supply into the circuit, and use an ideal-diode block to allow for both to either power everything in parallel, or use one or the other. This removes all the in-rush issues from the puzzle completely. It still doesn't totally solve the problem doing all this though, because it still negotiates the POE PD mode if it is present. The only true way to disable it, is to use the Page 13 circuit to shut off the DEN completely if you detect the POE power sucks. I am looking for better suggestions than stuff like this I can easily come up with on my own..... Is there any other references other than this I could be looking at?

    Thanks,

    -Ted
  • Hi Ted,

    Sorry for the delayed reply. I can see how bad those conditions can be and can add to the design consideration that a PSE's 'detection acceptance range' can be quite wide. It must accept detection resistance 19k-26.5k, can choose to accept or reject detection between 15k-19k and 26.5k-33k, and reject detection <15k or >33k.

    The IEEE standard assumes a reliable CAT5e and RJ45 infrastructure. If this is not available, I agree it might be best to corrupt detection and not have the PSE try and turn ON (where it should restart the load). Figure 10 that you reference is the best approach for this. However, even if the power is solved, the data through the Ethernet cable can also be poorly connected still.