Netonix Forums

I need to know the self consumption on the switches. The DC version are going to be deployed on towers presently fit with several routerboard 750UP's.

In this specific case I have one WS-12-250DC that is going to replace 3 x rb750UPs. The self consumption (so without any 3rd device being powered) is roughly 2W max for a 750. 3 times gives me 6W only to 'run' these devices. Is do switch doing better?

Since battery budget is important I would like to know if the WS-12-250-DC by itself is consuming more, or hopefully less power than the 3 rb750s?

All the devices connected stay the same for each concept. So it comes down to the extra/less consumption that the Netonix will consume compared to the 750s


Actually we talk about a tower running on Solar with some battery set. During the winter we might have some days without sun so we need to roughly calculate how long the tower will survive.
On the moment we are reforming the tower, meaning several AP's and backhauls will see more powerfull radio's in them. So the general consumption goes up anyway. By replacing all rb750's (low performance, only fast ethernet) for one Netonix Switch I was hoping at least to gain something on the consumption?

I have no amp meter so can't test it. Tried to hook the switch on to a rb750 (that has power output reading) but it won't even startup due 'too low current' in 'auto' modus or 'power overload' in the 'forced output' modus (!)

A bit weird, because first failure would make me think the netonix uses so little power by itself the rb750 can't even see it as a 'load',
but in the second case we get a 'power overload'? That would make me to think the netonix consumes more than the rb750 can handle on one of its ports.....

WirelessRudy wrote:I have no amp meter so can't test it...

Now might be a good time to get one.

I don't have any Netonix DC models but I thought they monitored and reported power stats. What about the main page, does not not show wattage used? Anyway, when trying to power it with the RB, I think it is simply the inrush that is preventing it.

There is going to be an initial in rush for the switch that is too much for the MT

The switch by itself should consume less than 10 watts depending on what it's doing such as how many ports are active and I do not mean providing poe but rather how active it is once you get past the in rush.

Also right now we are discussing implimenting a function of the switch core that will power down PHYS that are inactive especially on DC models that would lower the consistent power draw once past the in rush.

However the DC2DC power supply in rush would be too much for the MT board

I was just setting up a new one, it was reporting 8 watts with no POE turned on with the fan running in a room at about 70 degrees.

But the ability to power the radios with a battery bank that has dropped lower than 24 volts is a huge plus. We don't want the bank to go below 24 volts so that we don't lower the life of the batteries, but we also don't want the tower going down.

We finally have one WS-12-250-DC up and running in a Solar/Battery operated tower.
It supplies 1x rb800 with 2 radios, 2x SXT-SAac, 4xNetmetal and 2x SEXTANT continuously. Total Power consumption is around 60 Watts depending on the traffic demand.

We hooked this one onto one WS-8-250-AC and running idle (no devices connected) the unit consumed 8 - 8,5 Watts. The moment the ventilator runs at high speed it consumes almost 1 watt extra.

We are very satisfied with its functionality so far. Nice graphics and data monitors. Very good.

Some wishes we would like to see (if possible) are:

1. Manually switch ventilator on/off or on high/low cooling. In the summer, when cooling is a must the solar panels produce plenty of power to waste as much energy as the box will have to to keep it cool. But in the winter, specially when there is no sun, temperature is low, but energy production too. Every watt we can save is one.....
Ventilator always runs, even during pretty cold nights. It runs at low speed (+/-5700-5900rpms) while the temp is only about 20 degrees in the cabinet.

2. An external 12V power outlet to connect one or two external extra ventilators, possibly with temperature control. (Environment temp sensor?)

3. In the 'real time' monitor a amp meter could complement the status messages. It makes it easy to calculate how long batteries might run at certain power consumption without the need to do the calc yourself.....

4. Although it probably needs more memory, it would be nice to have longer status monitor span. 1 day, weekly would be nice. Not so much for the traffic but for the power usage/amps. It could give you good insight on how batteries are performing compared to the average consumption. If memory is an issue, a log export option for such data would be nice...

WirelessRudy wrote:1. Manually switch ventilator on/off or on high/low cooling. In the summer, when cooling is a must the solar panels produce plenty of power to waste as much energy as the box will have to to keep it cool. But in the winter, specially when there is no sun, temperature is low, but energy production too. Every watt we can save is one.....
Ventilator always runs, even during pretty cold nights. It runs at low speed (+/-5700-5900rpms) while the temp is only about 20 degrees in the cabinet.

The system monitors its own temperatures and if it does not need the fan it will turn it off.
IF THE FAN IS ON THEN IT IS ON BECAUSE THE UNIT NEEDS IT ON.

WirelessRudy wrote:2. An external 12V power outlet to connect one or two external extra ventilators, possibly with temperature control. (Environment temp sensor?)

The switch does not have 12V inside the chassis to put a 12V output jack. If you want you can purchase 24V and 48V fans and wire them into an unused Ethernet port and control the fans by turning on or off the POE on that port but be careful that you do everything correctly and test your fan rig on a POE brick first or you may fry a port and that is not covered under warranty obviously if you do fry it.

WirelessRudy wrote:3. In the 'real time' monitor a amp meter could complement the status messages. It makes it easy to calculate how long batteries might run at certain power consumption without the need to do the calc yourself.....

I will kick this around with Dave and Eric.

WirelessRudy wrote:4. Although it probably needs more memory, it would be nice to have longer status monitor span. 1 day, weekly would be nice. Not so much for the traffic but for the power usage/amps. It could give you good insight on how batteries are performing compared to the average consumption. If memory is an issue, a log export option for such data would be nice...

I will kick this around with Dave and Eric.

The nr 3 and 4 suggestions would be awsome if implemented!

Basdno

The nr 3 and 4 suggestions would be awsome if implemented!

yes, we will be adding these features to an upcoming software releases.....(hmmm, plus some other really cool features)...please keep up the great recommendations!