pmdavis300

MrPLC Member
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About pmdavis300

  • Rank
    Hi, I am New!

Profile Information

  • Country United States
  1. Yes you can write active x controls I believe. We run them on our SE setup. Its all written in visual studio, usually in vb+. The customm program utilizes a OPC server to read and write tag values to/from the plc. It works, but its not pretty. I believe .net w/aspen tec is the way to go these days. Of course like I said this is all server based SE I'm relating to. Checkout the Factory Talk View Studio user manual on the rockwell literature page.
  2. For starters, you will need version 16 of Logix5000. As a side note, this is not a current version. I believe v24.xx is the most current. At my plant I have been going to version 21.xxx which is compatible with newer windows servers. You will have to reschedule any controlnet networks. Also, you may lose aliased tags if you have to change a major revision of any associated cards. Be sure to make note of those tags beforehand. Backup your program before and after any changes are made. I usually write a procedure for myself well before commencing any work so I don't miss anything. Also, I use ControlFlash for my firmware updates. I believe you can use Logix5000 if you want. 1. Backup all possible files. 2. Insert a SEPERATE ethernet card OR plug in with a usb cable if you have the means. 2. Flash all moduels. If flashing a sercos card and servo drives, do the drives first, then sercos card. 3. Flash ethernet cards, controlnet cards etc. 4. Flash controller 5. Open saved PLC program and update the firmware revisions. If changing the major revision level of any i/o, you will have to delete the card in your program i/o tree and then readd it at the proper firmware version. 6. After you have updated the cpu revision and all other's the program will recompile, save this file as yourplcprogram_vXX.acd where XX is your new revision of your processor. Now you have 2 copies, one of the old verison program and one of the new. 7. Download your new program to the plc and fire it up. Check for comm faults. You will probably have to reschedule your controlnet networks. This is just a rough outline from my memory... REASEARCH!!!! If your not confident you could probably call in a controls engineering firm to do it for you.
  3. Wouldn't an OPC server take care of this?