250W DC I2C 100% failure rate

[expohl]

I apologize if this has been covered but I couldn't find much in search..

I've noticed nearly a 100% failure rate with i2c communication between 250W DC PSU and the switch board (i2c errors in log, and no input data on status screen from DC PSU) from the WS-12-250-DC...

Is this a known failure? Am I the only one? Every other function works fine and the switch still works 100% other than the missing data

Thank you

TJ

[sirhc]

No there is no known issues? I hope v1.5.2 or v1.5.3rcX

Better be at least v1.5.0 as we warned SMART DC users months ago to upgrade to v1.5.0

What version of firmware are you using?

Try a reboot and if no luck a power cycle.


Now ground current can damage the I2C if your on grid and your electrical service ground rods are bad and are not BONDED to the tower ground then the switch and Ethernet able becomes the bond between service ground and tower ground.


Below is an exert from an email I just sent to a Distributor in another country about ground current and how to educate their customers (PLEASE READ):
Yes, best practices is to stress to customers the importance of proper grounding especially with the SMART DC units (not including the WS-26-400-IDC) we sell as their power supplies are not isolated which means that earth ground and DC negative are bonded in the switch.

Most DC chargers also bond earth ground to DC negative and lastly “most” radios WISPs use such as UBNT, MIMOSA, Cambium, and so on also bond POE DC negative to chassis/earth (tower) ground.

Then the Ethernet cable becomes the bond between 2 ground potentials.

If there is a bad electric motor or other appliance such as an AC compressor that is going bad it can inject ground current often at harmonics far above 50/60 Hz which damages the switches and or radios.

Also ground current can come from the electrical provider as your electric company usually hands off hot/neutral/ground and the ground they hand you is bonded to neighboring electrical services so if you have say an industrial park nearby and they have failing electrical motors and poor grounding this ground current can enter your site from the provider.

It is always best practice to add additional electrical service ground rods to handle any ground current coming in from off site and or ground current generated on site. If the service ground rods are poor and there is a surge of ground current it will seek out the path of least resistance which is often the nicely newly installed tower ground rods and the path for the ground current is through the switch and across the Ethernet cable through the radio to the tower to the tower ground rods – POOF.

Often ground current damage occurs during rain events as water wicks down the service ground rods increasing their resistance to ground. Often rain events are during electrical storms and people often mistake ground current damage as storm damage (surges) and this is incorrect.

It is also practice in the telecom industry to make sure there is ONE ground potential for the entire site meaning BOND electrical service ground rods to tower ground rods with heavy gauge wire.

I have been a WISP for 20+ years and until I understood what ground current was I lost equipment all the time. Now I only lose equipment when someone messes with the grounding improvement we put at sites we use that are leased and are messed with by the site owner or other tenants of the tower.

Now as of this past few months we made changes to our AC switch models to make them more isolated in hopes to better survive poor grounding but our SMART DC models WS-8-150-DC / WS-12-250-DC / WS-26-500-DC will require a redesign of the power supplies which we are contemplating but again if people do proper grounding this is not an issue.

Rules of thumb for WISPs:
Add NEW additional ground rods to existing electrical service and or double the usual required # of ground rods for NEW electrical services. Here in the US code requires 2 so we add 2 more = 4

Always bond electrical service ground rods to tower grounding system if at all possible. If not then for sure add additional service ground rods to make sure tower ground path never looks better than service ground path.

Never plug in cable to ports with POE already turned ON and always make sure the device is compatible and you use the correct POE option. The second most common RMA damage is from shorted cables or incorrect POE option applies which fries the Ethernet Transformer and sometimes the entire switch as it can create a conductive path for POE current to enter the PHY/SOC, all depends on how the Ethernet Transformer fries.

Here are 2 good posts to make sure customers read:
viewtopic.php?f=6&t=1178#p8809
viewtopic.php?f=6&t=1215#p9040

With the WS-12-DC and WS-26-DC make sure the power supplies they use are ISOLATED power supplies meaning earth ground is not bonded to DC negative and follow the grounding suggestions above.

Ground current damage usually results with the current sensors being damaged whereas shorted cables usually does not harm the current sensors it just fries the Transformer and sometimes the SOC. Ethernet Transformer damage usually can only be seen when the Transformer is removed and flipped over as seen in previous pictures I sent you.


Another common mistake people do is run Ethernet Copper cable from one device on one electrical service/panel to another device on another electrical service/panel which will have different ground potential and thus the Ethernet cable becomes the BOND or ground loop. Now ground current from the one service with the higher resistance to ground will try and cross the Ethernet Cable. One should always use FIBER when connecting devices across different ground potentials.

99% of all WISP equipment damage is from ground current (I own a WISP)
Another common cause for damage is a shorted cable or incorrect POE option applied to device.

Here are some good posts on grounding:
viewtopic.php?f=30&t=2786#p19279
viewtopic.php?f=30&t=1816
viewtopic.php?f=30&t=188
viewtopic.php?f=17&t=1786&start=30#p13447
viewtopic.php?f=30&t=1429

Read the posts above but the basics are as follow:
Tower ground rods must be bonded to electrical service ground rods HEAVY #2 wire.
I always add 1 or 2 “new” ground rods to older existing electrical services.
In the event bonding service rods to tower rods is not possible then definitely add additional NEW ground rods to electrical service to help prevent service ground current from ever seeing tower ground rods as a better path to ground.

One last thing, Electrical and Ethernet Surge suppressors will do nothing to prevent ground current surges and damage. Think about it, how surge suppressors work is to shunt excess voltage to ground but there is nothing in them to prevent ground current from simply passing right through.
In fact I use ZERO Ethernet Surge suppressors in my entire WISP, I do though use GOOD electrical surge suppressors to combat electrical surges.

[expohl]

1.5.2 and I have done both a reboot and power cycle. Interestingly as I have began swapping out these switches and bringing them back to the shop and defaulting them for testing the i2c starts working again...

[Dave]

is your location where they were fairly close to any FM/AM transmitters, or other RF sources?

[expohl]

Dave thanks for taking the time to reply. I could see that being an issue but our switches are located inside a metal box all of the cables are properly grounded but even if that was the issue why would the i2c not respond when the switch was moved from the tower to my office desk ? They required a factory default to restore the i2c communication and I have replicated this on 5 switches so far...

[Dave]

interesting & different....haven't seen/heard of this one before...I can only guess some error condition (i2c related maybe) triggered the software to think I2C bus is bad so blocked all I2C...what I would suggest is next time you get a switch like this back in your lab, and it still fails...do not default it, but let one of our developers (Stephen) remote into it to see if he can find anything.....

[Stephen]

expohl,

If you would like to go with the option Dave pointed out. Feel free to private message me on the forum's.