Guest
The module I'm using is a RCM2100. This module is connecting to
LabView software using TCP/IP. This module was running and
communicating fine for some time. I was usign a linear 5V regulator,
but it was getting too hot even with a large heatsink. I switched to a
simple switching regulator, and as far as I can tell the voltages are
dead on and the regulator is operating properly. I turned off power,
then back on, and the ethernet link light stayed lit. LabView gives
an Open TCP/IP connection error. Now when the board is turned on, the
link light stays lit most of the time. Sometimes it stays off when
turned on, but whatever state it is in when it is turned on is what it
stays as. It doesn't matter if an ethernet cable is connected or not,
the light does the same thing. The act light never comes on anymore.
As far as I can tell, the ethernet section of the board is blown. The
microcontroller still acts completely normal, and has no problem
running programs. I'm out on a limb here, so any help or ideas would
be greatly appreciated. Do you think the ethernet chip is stuck in
some state? Is it possible a power surge corrupted the ethernet chip
data and it is now blown? Thanks for your time, Steve
LabView software using TCP/IP. This module was running and
communicating fine for some time. I was usign a linear 5V regulator,
but it was getting too hot even with a large heatsink. I switched to a
simple switching regulator, and as far as I can tell the voltages are
dead on and the regulator is operating properly. I turned off power,
then back on, and the ethernet link light stayed lit. LabView gives
an Open TCP/IP connection error. Now when the board is turned on, the
link light stays lit most of the time. Sometimes it stays off when
turned on, but whatever state it is in when it is turned on is what it
stays as. It doesn't matter if an ethernet cable is connected or not,
the light does the same thing. The act light never comes on anymore.
As far as I can tell, the ethernet section of the board is blown. The
microcontroller still acts completely normal, and has no problem
running programs. I'm out on a limb here, so any help or ideas would
be greatly appreciated. Do you think the ethernet chip is stuck in
some state? Is it possible a power surge corrupted the ethernet chip
data and it is now blown? Thanks for your time, Steve