Jasondelane
Lifetime Supporting Member
I have 2 different MTS Temposonics R-Series position sensors being used in a program. Each MTS is tracking a single axis on separate machines. They are each assigned an IP and are WORKING in the program. I did all caps on working because I am receiving position information from both of the rods.
I have several issues with one of the sensors (Sensor #1).
RSLinx does not see the sensor on either ETH or ETHIP drivers. Sensor #2 is visible and recognized.
I cannot ping sensor #1 via CMD. I am getting a good ping on Sensor #2.
I cannot disable BOOTP/DHCP via the Rockwell BOOTP/DHCP tool, even though I can apparently assign an IP. I can't do it via any other tool including RSLinx because it's not visible.
Any time power is lost, Sensor #1 loses it's IP and I'm forced to reassign it. I do not have this problem with Sensor #2.
I have tried using both ports on the sensor, but it doesn't seem to make a difference.
I'm coming to the conclusion that the firmware is corrupt on the sensor. It seems strange to me that the program is receiving position feedback somehow, but it's invisible on RSLinx.
I have several issues with one of the sensors (Sensor #1).
RSLinx does not see the sensor on either ETH or ETHIP drivers. Sensor #2 is visible and recognized.
I cannot ping sensor #1 via CMD. I am getting a good ping on Sensor #2.
I cannot disable BOOTP/DHCP via the Rockwell BOOTP/DHCP tool, even though I can apparently assign an IP. I can't do it via any other tool including RSLinx because it's not visible.
Any time power is lost, Sensor #1 loses it's IP and I'm forced to reassign it. I do not have this problem with Sensor #2.
I have tried using both ports on the sensor, but it doesn't seem to make a difference.
I'm coming to the conclusion that the firmware is corrupt on the sensor. It seems strange to me that the program is receiving position feedback somehow, but it's invisible on RSLinx.