Hi Dan,

One measurement was made with a bare roach2 board just sitting on the bench in the lab.

The other was made with the vertical mount roach2 arrangement that we use in the vegas rack.

Thanks,
Jason


At 01:19 PM 12/6/2013, Dan Werthimer wrote:


hi jason,

thanks for the temperature data and measurements.

were your temperature measurements in the
standard roach2 enclosure?

i think the VEGAS SFP+ PHY's are mounted
differently and have different cooling than the
standard roach2 enclosure.

best wishes,

dan





On Fri, Dec 6, 2013 at 9:53 AM, Jason Ray <<mailto:j...@nrao.edu>j...@nrao.edu> wrote:
Hi Rich,

So far we haven't had any trouble with the SFP+ boards (8 total) in our vegas machine. I guess they've been powered up continuously and in use for around a year now.

We were concerned about how warm the PHY chips run so I spent a little time looking into it. The datasheet says:

"For typical applications, the VSC8486 can be operated in an ambient temperature environment of +80 degrees C with no airflow and without a heatsink."

It also states that the maximum specification for case temperature is 85C (95C in one case). I used our IR viewer and noted that the case temperature reached ~60degC on the bench and a little less on the ones in the rack.

I should note that the datasheet was for the VSC8486 so I had to assume that the thermal specs are similar for the VSC8488, which is the actual chip on the SFP+ mezz boards.

Given all of that info, we elected not to put heat sinks on ours.

Hope this helps,
Jason



At 12:25 PM 12/6/2013, Rich Lacasse wrote:
Hi All,

We've had a failure of an SFP+ board for no apparent reason. We've not put any work into trouble shooting except to isolate the failure to the SFP+ board, as opposed to a ROACH2 or optical transceiver.

Has anyone else experienced failures?

The two PHY chips on these boards run very warm whether or not they are transmitting data. We are considering putting heatsinks on them. Has anyone else been down this road already? Any other advice?

Thanks,
Rich



Reply via email to