InterchangeIT (Customer) asked a question.
T1H-EBC100 MAC address in ERM workbench reads 00 00 00 00 00 00 in an ethernet network containing an ERM100 + 5 slave T1H-EBC + 1 slave T1H-EBC100 that appears offline.
The actual MAC address printed on the label is 00.E0.62.40.B8.2E. ERM WB says the slave module is "offline".
** The MODULE GOOD led is on solid green
** The LINKED ACTIVITY led is flashing
** The 100 MBIT led is on solid
** The ERROR-Serial TX and RX are all 3 OFF
I think since the MAC address is burned in at the factory, for it to now read all zero's, must mean that it (T1H-EBC100) has failed?
Module replaced with new module - All is good.
I can't remember if you said you had the latest NetEdit3. It's currently at version 3.17 M release from March of 2026. It has better handling of multiple subnets (IT vs OT networks) and addresses a couple bugs from the previous standalone install from 2022.
NetEdit is good for querying your OT network, updating firmware of your ERMs and EBCs (et. al.), assigning IP Addresses (which you may be doing now?)
ERM Workbench is primarily for configuring your ERM and I/O, but no longer does fimrmware support et. al.
https://hosteng.com/SW-Products/SP_Demo_Utilites.htm#NetEdit3
The install also installs the latest ERM Workbench (not sure what you have).
My software is current. In this case I believe the unit was damaged during a swap with a working unit. I'm just the integrator so it's usually akin to investigating a crime scene when I arrive to solve a problem. After all the knobs have been turned, a few components replaced and new ideas are gone, my phone rings.
The bear has been tamed. After all this "network problem" hub bub, it turns out they didn't have a network problem at all. They had an unidentified analog problem from which they assumed was a network problem and then they created the network problem when they pulled an working, but obsolete T1H-EBC, and they damaged it during removal.
Now, their mtce staff has been trained how to change a module without damaging it and I rearranged the network so the ERM is looking for the slave dip switch setting to ID module addressing.
The moral of the story - It's usually more than 1 problem and several "who-when-why" series of questions must be answered. The problem that started all of this was a bad remote i/o analog socket (T1K-08B). It was reading 20.3vdc on the reference pins of the analog output signals (all of them read the same), with all of the output wires disconnected from the socket. My thought was that if I unplug one output at a time I would find the bad device downstream causing the short. After all the wires were unplugged and the 20.3vdc signal remained, I replaced the socket and the problem vanished.
Thanks again for your time to comment. It can get lonely out here