|
One of my co-workers is converting a PLC5 program with racks on RIO to controllogix. He was wondering how to handle the block transfers and data for RIO. Here's what I told him: Let the conversion tool work it's magic... Once converted Rename the tags "N##:##/##" to match the desired format "I/O_Slot_Channel_Rack_Slot" or whatever. He can then alias those tags to the PLC's real work I/O (Rack#:I/O.Slot[#]... ) Was this good advice? We'd welcome any better Ideas! |
|
I helped design and create a program that used RIO, old PLC 5 Racks, plus ControlNet on a ControlLogix Platform. I was able to keep things straight by separating the different Rack Sections in the Code. I used two Message Blocks Analog Slots (first used for configuration, the second used for Data Passing). There is a lot of information around the Allen Bradley Online Technical Support Webpage as far as programming, I would recommend the sequential setup. I was able to keep my sanity when using naming convensions by following the a simple sequence. Block Transfer Write Commands (Configuration Settings): _BTW_NX_RX_SX_xxxx Block Transfer Read Commands (Data Passing): _BTR_NX_RX_SX_xxxx NX - was used for Network Number - The original setup had over 60 Racks seperated into 5 different PLC 5 Networks. RX - was the Rack Number SX - was the Slot Number Hope this information is somewhat useful. |
|
Use the 1756-RIO module and it's associated mapping utility |
