Charlie_A

yikes. I was looking at a pdf with both input and output and grabbed the wrong information. Thank you for clearing things up for me. cheers

In one of my application I have 30 drives in one large cabinet that require 0-10V signal. I was afraid of too much noise on the signal lines so I thought the best method would be to use 0-20mA signal with a 500ohm precision resistor on the input of the drive. In the 1794-OE12 manual it states under maximum overload: 30V continuous or 32mA continuous, one channel at a time I just need a clarification on this. Can I do what I want to do with this module for my application? This is my first AB project and any help is appreciated.

It was version 1.4. I actually tried entering that entry along with the other entries I've made, but it didn't work. I've tried just entering the suggested routing entry and everything works beautifully. Thank you for your assistance.

The two programming machines are accessing the plant file server with the CX program. The drivertab screenshot that wasn't posted has the .61 for the last octet.

The workstation number is set to auto detect.

I am using Auto-Dynamic I will see if firmware upgrade is possible on this unit on Monday and let you know how it pans out. Can you think of a reason why the one programming computer can connect with the PLC but not the other? Thank you for your help.

Can you identify which sub menu you got in to in order to get to that screen? I do not see it within the IO TABLE CS1w-ETN21 menu

One of the setup has CS1G-CPU42H and a CS1W-ETN21 module. The IP address of the ethernet module is 10.160.5.6 with a subnet of 255.255.255.0 The CX programming computers are on the same subnet with IP addresses of 10.160.5.25 and 10.160.5.61 The computers with the SCADA packages (10.160.6.72 and 10.160.6.73) hits the PLC through a router which has an address of 10.160.5.254 Depending on which SCADA computer is run, only one will be trying to access the PLC at a given moment. The IP Router Table in the ETN21 setup is set as follows: 10.160.5.25 10.160.5.25 10.160.5.61 10.160.5.61 10.160.6.72 10.160.5.254 10.160.6.73 10.160.5.254 The anomoly is the programming computers. I can connect to the PLC through CX with 10.160.5.25 but not 10.160.5.61 I realize that if the programming computers are on the same subnet you do not need a routing table. The reason for that being there is that when the ip routing table for the SCADA computer was put in, the programming computers were no longer able to connect with the PLC. Once I put the routing table for the Programming computers via serial connection, the one programming computer was able to talk to the PLC. The programming computers are exact VM clones with except with different software serial numbers. Can anyone suggest where the fault lies?