Is the firmware working? RUN Mode I/O, etc.?
G.I.T said:
...it looks like I need to buy the firmware kit for the upgrade
It looks like the card was upgraded in the past by someone... it has a label over the orginal 1747-OS501C10
Not so fast...
AFAIK, you can upgrade the SLC firmware no problem, to take advantage of new instructions and features, but if you do that, you must not choose settings for the ethernet port that are not supported by the hardware.(<-EDIT).
I don't recall if its still possible to use RSLogix 500 to choose settings that are unsupported by the daughter card rev. level, or if that value gets overwritten by a firmware upgrade, making it possible to choose 100Mb/s and thereby disabling the port. I wouldn't be surprised if the daughtercard rev level system register came into existence with the newer firmware, thereby making it impossible for Logix to tell the difference...
Rockwell has recommended to us to set the 5/05s on our FTViewSE sytems as well as the switch ports they're connected to, fixed baud (turn of autonegotiate) fixed duplex.
IIRC, 10Mb/sec, half duplex, I can't remember if full duplex in supported in the older daughtercard.
I once worked on one in that condition that ran just fine. I think it was upgraded (firmware) just to get the DEM (devicenet explicit message) instruction, or some other value, but we found out after downloading a file with full duplex or 100Mb/s, and having to go back in serially to put it back.
I have also seen them die a slow death twice, and a fast death many times.
I am now reducing my odds that a PIC did it in to 30%, since there's evidence of a firmware upgrade, and I haven't seen your channel settings, or confirmed physical media connection.
You can always throw a digi on it (Digi One IAP Haz.)
MORE EDIT:I have also seen one go fubar after having it's IP address changed. It effectively doubled the number of connections that were being made by other devices on the network, exceeded the limit, and went into timeout mode. 30 minutes later it would have started talking, but after fifteen minutes I got off my butt and went out there and power cycled it.
I had already used the built in web page to see the connection limit was exceeded which was corrected by the power cycle, by then, the old connections were dropped and it ran fine.
So you've already ruled out the connections exceeded possibilty unless its doing lots of comms on a network during your tests.
After you rule out the physical connection and verify your PC port works, ring the dinner bell and call it done.
