trueninjalo
Lifetime Supporting Member
I am using 1794-ABS flex I/O. They are no longer available through normal vendor channels. While I can get them on EBAY, I need to find a more permanent solution. I am thinking I will get the 1794-AENT as I can still order these through our normal vendor. Then all I need to do is change the device in the program to match. Here is where my issues start though.
Can I change the adapter module without needing to readdress tag info the from the modules attached (ie. Local:3:I.Data.0 address)? Will the cards and addresses need to be redone?
Now I know what some may be thinking. Why not just upgrade to Point I/O? Module costs is the main reason. I will replace one flex system at a time with point I/O but I cant do them all at once. I have too many flex systems out there right now using the ABS for comms.
On another issue, when I inherited this "Cluster --Beep--", I found that my remote I/O network is linked to all remote I/Os. I have a plant network that starts with 10.xxx.xxx.xxx the my devices are connected to the controllers via 192.xxx.xxx.xxx and instead of each 192 being isolated from the others they are all linked together. Due to all the remotes, drives, and other Ethernet devices, we are running out of 192 addresses. Is there an easy way to isolate these networks so I can free up some hosts? In my experience, you set up devices connected to a controller as private networks this way you get up to 253 devices per controller. The way it is setup now you only get 253 devices in the plant. Any suggestions would be greatly appreciated.
Thanks in advance gentlemen, have a good day.
Anthony
Can I change the adapter module without needing to readdress tag info the from the modules attached (ie. Local:3:I.Data.0 address)? Will the cards and addresses need to be redone?
Now I know what some may be thinking. Why not just upgrade to Point I/O? Module costs is the main reason. I will replace one flex system at a time with point I/O but I cant do them all at once. I have too many flex systems out there right now using the ABS for comms.
On another issue, when I inherited this "Cluster --Beep--", I found that my remote I/O network is linked to all remote I/Os. I have a plant network that starts with 10.xxx.xxx.xxx the my devices are connected to the controllers via 192.xxx.xxx.xxx and instead of each 192 being isolated from the others they are all linked together. Due to all the remotes, drives, and other Ethernet devices, we are running out of 192 addresses. Is there an easy way to isolate these networks so I can free up some hosts? In my experience, you set up devices connected to a controller as private networks this way you get up to 253 devices per controller. The way it is setup now you only get 253 devices in the plant. Any suggestions would be greatly appreciated.
Thanks in advance gentlemen, have a good day.
Anthony