WS-12-250-DC Input voltage too low

[Dave]

mayeb some screen shots from status page??

[Eric Stern]

I just checked the code and there is a small bug. The voltage reported in the message (52.6) is wrong.

To clarify, the code worked correctly. The input voltage must have been < 43V and so it refused to enable PoE on the port. It was just the voltage reported in the message in the log that was wrong.

I'll correct this in the next version.

[sirhc]

I just checked the code and there is a small bug. The voltage reported in the message (52.6) is wrong.

To clarify, the code worked correctly. The input voltage must have been < 43V and so it refused to enable PoE on the port. It was just the voltage reported in the message in the log that was wrong.

I'll correct this in the next version.

But Eric this model is the WS-12-250-DC not the WS-12-DC unit, this condition check should not be done?

[petecarlson]

Here is all the info from the status page:
Status
System
Current Time 12/31/1969, 8:25:15 PM
Uptime 01:25:15
CPU Usage 27%
Memory Usage 46.76 MB
MAC Address ec:13:b2:81:02:5a
IP Address xx.xx.xx.xx
Firmware Version 1.3.2
Board Rev D
Power Supply Firmware Version 28
Power
Board 24V 6.6 Vdc
Board 3V 0.3 Vdc
Power Supply Input Voltage 52.6 Vdc
Power Supply Output Voltage 49.3 Vdc
Power Supply Efficiency > 92 %
Thermal
Board Temp 52 C / 126 F
CPU Temp 58 C / 136 F
PHY Temp 56 C / 133 F
Power Supply Board Temp 35 C / 95 F
Power Supply Heatsink #1 Temp 33 C / 91 F
Power Supply Heatsink #2 Temp 33 C / 91 F
Power Supply Controller Temp 44 C / 111 F
Cooling
Fan 1 Speed 6600 RPM

[sirhc]

Apparently there was a mis-communications here and that check was NOT removed from all the models except the WS-12-DC.

We are discussing internally what exactly is going on here.

I will put up a v1.3.3rc4 later today that will remove this check as we originally only intended for it to be in the WS-12-DC

[petecarlson]

I just checked the code and there is a small bug. The voltage reported in the message (52.6) is wrong.

To clarify, the code worked correctly. The input voltage must have been < 43V and so it refused to enable PoE on the port. It was just the voltage reported in the message in the log that was wrong.

I'll correct this in the next version.

Voltage reported on the switch matches voltage measured with a digital multimeter at the switch. Not that that should matter as it is a WS-12-250-DC. Our other one is running on a 24V system just fine powering 48VH.

Looking forward to new code.

Any ideas how the voltage sensor could be damaged or why a one WS-12-250-DC running at 24V does 48V fine while another running at 48V can't do 48V?

Thanks,

Carl

[petecarlson]

Apparently there was a mis-communications here and that check was NOT removed from all the models except the WS-12-DC.

We are discussing internally what exactly is going on here.

I will put up a v1.3.3rc4 later today that will remove this check as we originally only intended for it to be in the WS-12-DC

Thanks for the super fast response Chris! We will get the new code loaded tonight and let you know how it goes.

[sirhc]

Any ideas how the voltage sensor could be damaged or why a one WS-12-250-DC running at 24V does 48V fine while another running at 48V can't do 48V?

What we do and do not know yet:
1) We do not know or think the sensor is damaged, this is more than likely a fluke issue.
2) The check it is doing was not meant to be there so we are removing it.
2) Eric does see a bug in his code on the measurement (how he reads and reports it) but it is not a bug that is always seen.
3) Other people are running the switch on 48V sites and have not reported this issue.

I am confused on how you are poring this:
You have a DC switch being powered by an AC power supply?
Or is this a DC to DC converter powering the switch and if so why, the idea is to connect this model to the batteries direct?

Is this condition constant or just happend once?

[petecarlson]

What we do and do not know yet:
1) We do not know or think the sensor is damaged, this is more than likely a fluke issue.
2) The check it is doing was not meant to be there so we are removing it.
2) Eric does see a bug in his code on the measurement (how he reads and reports it) but it is not a bug that is always seen.
3) Other people are running the switch on 48V sites and have not reported this issue.

I am confused on how you are poring this:
You have a DC switch being powered by an AC power supply?
Or is this a DC to DC converter powering the switch and if so why, the idea is to connect this model to the batteries direct?

Is this condition constant or just happend once?

1) It is a persistent issue. i.e it wouldn't power 48V devices from the get go.
2) It is currently being powered via an AC-DC PS. It will be moved over to a 24V battery system in the next few weeks.

[sirhc]

Here is all the info from the status page:
Status
System
Current Time 12/31/1969, 8:25:15 PM
Uptime 01:25:15
CPU Usage 27%
Memory Usage 46.76 MB
MAC Address ec:13:b2:81:02:5a
IP Address xx.xx.xx.xx
Firmware Version 1.3.2
Board Rev D
Power Supply Firmware Version 28
Power
Board 24V 6.6 Vdc <== WHAT IS THIS
Board 3V 0.3 Vdc <== WHAT IS THIS
Power Supply Input Voltage 52.6 Vdc
Power Supply Output Voltage 49.3 Vdc
Power Supply Efficiency > 92 %
Thermal
Board Temp 52 C / 126 F
CPU Temp 58 C / 136 F
PHY Temp 56 C / 133 F
Power Supply Board Temp 35 C / 95 F
Power Supply Heatsink #1 Temp 33 C / 91 F
Power Supply Heatsink #2 Temp 33 C / 91 F
Power Supply Controller Temp 44 C / 111 F
Cooling
Fan 1 Speed 6600 RPM

After talking to you on the phone Carl we believe this switch is either damaged or defective.
As I said I am sending you an RMA form.
You are getting incorrect voltage readings and current readings.
This can happen if someone hooked up the DC power backwards, not saying your techs did but that can damage the unit in this way.