morrellh;
I believe that mikes response was correct, but predicated on your original statement that you were using the MODBUS driver to talk to the Koyo PLC. If you are using the 205 driver object, you are probably using the k sequence protocol. In any case you can export from the 205 driver object and then import to the modbus object after an intermediate step. The k (or N) sequence addressing in the 205 driver is different from MODBUS so you will have to change the addresses. These are listed under the Member column in the export file. You have some other challanges. First; Assuming that you will have similar items defined in the scadapak plc but with different addresses from the koyo, I would copy the alias names from the 205 driver object to the to the MODBUS driver object. This is easily done in the .xls export file. While working in the file that you will import into the MODBUS driver object you must assign the corresponding Scadapak MODBUS address for each alias. The scond challange is that all of your existing items that reference the 205 driver will now have to point to the MODBUS driver. I feel that this is most easily done by editing the individual process .lks files. A simple find and replace will do the trick. If you have a large application and have not messed with the .lks file before, you might want to practice on a simple process to learn about the .lks file. This is all easier to do than it is to describe. I don't know if there is any doucumentation that describes the .lks file, but it's not to hard to figure out but when you first look at it it can look intimidating. Before editing your actual lks file(s) be sure to save them in case you make a mistake. If you do edit the lks file i would strongly recommend using a text editor that provides line numbers. You didn't state why you were changing the PLC, but if you just want to put it on an Ethernet, you could either add an Ethernet module or use a serial device server.
Jim Besselman
Control Automation, Inc.
